Your message dated Tue, 26 May 2009 17:07:25 -0400
with message-id <[email protected]>
and subject line Re: Bug#530654: bad markup of multiline comments
has caused the Debian Bug report #530654,
regarding bad markup of multiline comments
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
530654: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530654
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: highlight
Version: 2.9-1
Severity: normal
Note: I'm using the as-yet not in Debian new version.
highlight does not markup multiline type comments in any color. The
html it emits is rather strange:
C:
input: /* comment */
output: <span class="hl kwa"></span>/* comment */<span class="hl kwa"></span>
input: // comment
output: <span class="hl kwd">// comment</span>
haskell:
input: -- comment
output: <span class="hl kwa"></span>-- comment
Why does it generate these empty spans instead of wrapping the comment
inside the span?
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.29-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages highlight depends on:
ii highlight-common 2.9-1 source code to formatted text conv
ii libc6 2.9-12 GNU C Library: Shared libraries
ii libgcc1 1:4.4.0-4 GCC support library
ii libstdc++6 4.4.0-4 The GNU Standard C++ Library v3
highlight recommends no packages.
highlight suggests no packages.
-- no debconf information
--
see shy jo
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
André Simon wrote:
> This is a issue of the API: initTheme() needs to be called before
> initLanguage(), as initLanguage initializes HTML open and close
> delimiters based on infomation provided by the color theme.
Thanks! I had not realized order could matter there.
--
see shy jo
signature.asc
Description: Digital signature
--- End Message ---
