Re: Differences between generic names in the documentation.

Hi,


On 12/12/2007, Jonathan Pryor <[email protected]> wrote:
> On Wed, 2007-12-12 at 05:57 -0500, Jonathan Pryor wrote:
> > On Sat, 2007-12-08 at 12:04 +0100, Valentin Sawadski wrote:
> > > But then again it seems that the browser uses the Test&lt;T&gt;
> > > everywhere. Sometimes it gets parsed and will be displayed as Test<T>
> > > but other times not and some ugly HTML-Entities are being shown as the
> > > class name.
> >
> > After looking into this further, I *think* this is a GTKHTML rendering
> > bug.
>
> Perfect test case:
>
> 1. Start Monodoc.
> 2. Click File -> Lookup URL, or type Ctrl+L.
> 3. Enter the URL: <a href="foo.bar&lt;T&gt;">foo.bar&lt;T&gt;</a>
>
> It displays as "foo.bar&lt;T&gt;" (i.e. no escaping is occurring), and
> if you hold your mouse over the link the target is "foo.bar&lt;T&gt;".
>
> You can in fact change the URL to be:
>
>         <a href="foo.bar<T>">foo.bar&lt;T&gt;</a>
>
> Despite being invalid XML (is it even valid HTML?), GTKHTML displays it,
> and shows the desired target when you mouse over it (foo.bar<T>), but it
> still shows "foo.bar&lt;T&gt;" as the link text.  I can't find any way
> to get "foo.bar<T>" as the link text. :-/
>
> (Not that a href of "foo.bar<T>" helps anyway, as that's invalid XML,
> and thus cannot be used within the documentation.)
>
> So it's definitely a GTKHTML bug; no idea how to fix it.  This has also
> been reported:
>
>         http://bugzilla.gnome.org/show_bug.cgi?id=340007
>         http://bugzilla.gnome.org/show_bug.cgi?id=494315
>         http://bugzilla.gnome.org/show_bug.cgi?id=498847
>
> The latter two were opened in November of this year.  The first one also
> seems applicable, and was opened in 2006.
>

  I couldn't reproduce the problem with rendering generics you are
talking about. I think this is related to the version of gtkhtml. I've
noticed I only have the old gtkhtml-2.0 and, maybe, this is a issue
with 3.14 (I've seen the bugs you reported are related to the 3X
series). Could you try to compile with old libgtkhtml-2.0 and see If
the problem is still there?

Maybe we should stick with the old 2.0 gtkhtml; by the way I don't
know what exactly gives us the 3X series, nor why it was enabled by
default?

> Sounds like the actual solution is to get Gecko working again.  Anyone
> know why it dies?

Well, it seems related to a change in monodoc script "configuring"
something to get the gecko library. In the bug report
(https://bugzilla.novell.com/show_bug.cgi?id=341815) Wade points to a
change made on r81537 but I can not try it myself because I don't have
OpenSUSE. Does removing these two lines (which I don't think are so
much useful) fixes the problem for you?

Mario


>
>  - Jon
>
>
> _______________________________________________
> Mono-docs-list maillist  -  [email protected]
> http://lists.ximian.com/mailman/listinfo/mono-docs-list
>
_______________________________________________
Mono-docs-list maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-docs-list