Package: monodoc Version: 1.9-1.2 Severity: important Could you please foreward the following bug upstream?
Problem: mdoc 2.0.x and its ancestors do not handle nested classes (with nesting level > 2) correctly. The gmcs compiler generates the correct xml info but mdoc generates wrong class names. There has been a bug https://bugzilla.novell.com/show_bug.cgi?id=MONO69676 reported as closed, but that was only a partial fix (level <= 2). Severity: The problem cannot be circumvented with mono tools. If you consider documentation as important this is a serious problem. I do not care about X.Y+Z+XXX being displayed as a name, the problem here is that X.Y.Z.XXX will be displayed as X.Y.XXX which is misleading and very wrong. How to reproduce: namespace X { class Y { class Z { struct ThisGetsAWrongName { ... } ... } ... } ... } Thanks! -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-8-x86 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages monodoc depends on: ii monodoc-browser 1.9-2 MonoDoc GTK+ based viewer ii monodoc-manual 1.9-1.2 compiled XML documentation from th monodoc recommends no packages. Versions of packages monodoc suggests: pn monodoc-http <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
