Re: [Haskell-cafe] Haddock/hscolour integration broken on Hackage?

2007-09-12 Thread Roberto Zunino
Malcolm Wallace wrote: David Menendez [EMAIL PROTECTED] writes: I was looking at the Data.Binary documentation[1] on Hackage, and I've noticed some problems with the associated source listings[2]. First, none of the Source links work. They all refer to fragment IDs (e.g., #Binary) that are

Re: [Haskell-cafe] Haddock/hscolour integration broken on Hackage?

2007-09-12 Thread Roberto Zunino
Roberto Zunino wrote: Would be enough to use the %xx encoding of parenthesis? Would you instead use another prefix (it is enough that no haskell identifier can start with it)? Maybe .line or -line ? AFAICS, I think line- should do. From w3.org: ID and NAME tokens must begin with a letter

[Haskell-cafe] Haddock/hscolour integration broken on Hackage?

2007-09-10 Thread David Menendez
I was looking at the Data.Binary documentation[1] on Hackage, and I've noticed some problems with the associated source listings[2]. First, none of the Source links work. They all refer to fragment IDs (e.g., #Binary) that are not defined. I'm not sure if this is a problem with hscolor, haddock,

Re: [Haskell-cafe] Haddock/hscolour integration broken on Hackage?

2007-09-10 Thread Thomas Schilling
On Mon, 2007-09-10 at 14:11 -0400, David Menendez wrote: I was looking at the Data.Binary documentation[1] on Hackage, and I've noticed some problems with the associated source listings[2]. First, none of the Source links work. They all refer to fragment IDs (e.g., #Binary) that are not

Re: [Haskell-cafe] Haddock/hscolour integration broken on Hackage?

2007-09-10 Thread Malcolm Wallace
David Menendez [EMAIL PROTECTED] writes: I was looking at the Data.Binary documentation[1] on Hackage, and I've noticed some problems with the associated source listings[2]. First, none of the Source links work. They all refer to fragment IDs (e.g., #Binary) that are not defined. I'm not