Bug#389832: only reproduces for me in ja_JP.UTF-8 environment

2007-01-08 Thread Michael(tm) Smith
Here's a data point: If I set my environment to LANG=en_US.UTF-8, I don't observe this problem. I only observe it when I have my environment set to LANG=ja_JP.UTF-8. --Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#384127: can't reproduce

2007-01-08 Thread Michael(tm) Smith
I can't seem to reproduce this now, and anyway I suspect that it might have been caused by a bug in jless, not in groff. --Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#340637: Debian bug #385240 (Cannot find unicode character file)

2007-02-28 Thread Michael(tm) Smith
moved to Serious or Important -- because as far as I can see, it breaks nxml fontification in any XML file that contains character references. --Mike -- Michael(tm) Smith http://people.w3.org/mike/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#377783: mutt: segfault w/ ".mh_profile not found.." when doing change-folder+

2006-07-11 Thread Michael(tm) Smith
Package: mutt Version: 1.5.11+cvs20060403-2 Severity: important When doing c+? (change-folder+), mutt emits an error message saying, "/home/mikes/.mh_profile not found, mh format names disabled", then segfaults. This is with IMAP, connecting to a UW-IMAP server. -- System Information: Debian Rel

Bug#384127: groff: Special characters within \fB font escape not displayed correctly

2006-08-21 Thread Michael(tm) Smith
Package: groff Version: 1.18.1.1-12 Severity: important I have a file containing the following and am viewing it in an en_US.UTF-8 environment. .SH "AUTHOR" .PP \fBSebastian\fR \fBDr\(:oge\fR .sp -1n .IP "" 3n Author. .SH "COPYRIGHT" Copyright \(co 2005 Sebastian Dr\(:oge The second instance of

Bug#332474: (no subject)

2006-08-21 Thread Michael(tm) Smith
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#332474: [EMAIL PROTECTED]"strong" supported in docbook-xsl 1.70.1.dfsg.1-0.2

2006-08-21 Thread Michael(tm) Smith
Hi. I'm the upstream developer for the DocBook XSL manpages stylesheet. I added support for [EMAIL PROTECTED]"strong" to the upstream source quite a while back. I guess it was in the 1.69.1 release (which never got packaged for Debian). Anyway the Debian docbook-xsl 1.70.1.dfsg.1-0.2 package does c

Bug#383874: contrib normalization fixed upstream

2006-08-21 Thread Michael(tm) Smith
Hi. I'm the upstream developer for the DocBook XSL manpages stylesheet. Daniel Leidert brought Debian bug #383874 to my attention. I've checked in a fix for bug #383874 to the upstream source. You can test it using the latest snapshot: http://docbook.sourceforge.net/snapshots/ The fix will be

Bug#383874: contrib normalization fixed upstream

2006-08-21 Thread Michael(tm) Smith
Daniel Leidert <[EMAIL PROTECTED]>, 2006-08-22 04:32 +0200: > Thanks for the reply Michael. Just a question: The same issue affects > also other children of author|editor|othercredit (like email, firstname, > surname, authorblurb, ...). Shouldn't they be treated the same way? The authorblurb elem

Bug#383874: contrib normalization fixed upstream

2006-08-21 Thread Michael(tm) Smith
Daniel Leidert <[EMAIL PROTECTED]>, 2006-08-22 05:49 +0200: > I think, the firstname and surname (othername too?), email, honorific > and probably lineage elements should be normalized too, to avoid > unintended linebreaks in the AUTHOR section. Fixed. Please test with the latest snapshot. All "p

Bug#254811: UTF-8 characters in docbook-xsl output

2006-08-21 Thread Michael(tm) Smith
As noted, the unsightly accented characters are a result of HTML output being encoded in UTF-8 but being displayed in a browser with the encoding set to ISO 8859-1. This is not a bug in the DocBook XSL stylesheets. The stylesheets provide mechanisms for enabling you to set output encoding to whate

Bug#291813: passivetex bugs, not docbook-xsl ones

2006-08-21 Thread Michael(tm) Smith
xmlto relies on passivetex to convert the XSL-FO output from the DocBook XSL stylesheets to PDF. The error messages you cite are messages generated during the passivetex phase, not messages generated by any processing done with the DocBook XSL stylesheets. You could file this bug against the passi

Bug#377783: debug log

2006-08-23 Thread Michael(tm) Smith
Here's the last part of the debug log before it segfaults. mutt_index_menu[633]: Got op 99 > a0007 NAMESPACE < * NAMESPACE (("" "/")("#mhinbox" NIL)("#mh/" "/")) (("~" "/")) (("#shared/" "/")("#ftp/" "/")("#news." ".")("#public/" "/")) browse_get_namespace: adding #mhinbox browse_get_namespace: a

Bug#377783: Gnatsweb bug #2444 filed upstream

2006-08-23 Thread Michael(tm) Smith
Just FYI -- I've filed problem report #2444 for this issue in the mutt Gnatsweb bug-tracking system: http://bugs.mutt.org/cgi-bin/gnatsweb.pl?debug=&database=mutt&cmd=view+audit-trail&cmd=view&pr=2444 smime.p7s Description: S/MIME cryptographic signature

Bug#385940: Fixed.

2006-09-04 Thread Michael(tm) Smith
I've checked in a fix for this to upstream source. If possible, please test with the latest snapshot: http://docbook.sourceforge.net/snapshots/ But note this: address is a block element, always, and a DocBook "verbatim" also (the equivalent of an HTML PRE -- all linebreaks and whitespace within

Bug#385940: Fixed.

2006-09-04 Thread Michael(tm) Smith
Daniel Leidert <[EMAIL PROTECTED]>, 2006-09-05 02:49 +0200: > > Foo2 FooScreen > > I was just testing with several verbatim elements to isolate the cause > of this issue and the last I used was . That's the whole > reason. Ah, I see that now. I guess I would have realized that if I had taken t

Bug#382505: We'd need to update the upstream docs also

2006-09-05 Thread Michael(tm) Smith
If you were to change the Debian docbook-xsl package such that it uses /etc/papersize as a default papersize instead of using "letter", as the upstream docs say, then you run the risk of a users discovering that every time they generate FO output, they are getting a different default thatn what the

Bug#382505: We'd need to update the upstream docs also

2006-09-05 Thread Michael(tm) Smith
Daniel Leidert <[EMAIL PROTECTED]>, 2006-09-05 15:23 +0200: > I thought about simply patching the docs in the debian package along > with the param.xsl adding a notes That assumes the users actually have installed docbook-xsl-doc and that they are reading it instead of say, simply reading them ov

Bug#382505: We'd need to update the upstream docs also

2006-09-05 Thread Michael(tm) Smith
Hi Daniel, > I could simply add a note [1] to the xsl:message, where you (upstream) > output, which format is used (fo/docbook.xsl -> root.messages). IMHO > this is enough to make users aware of this little workaround. > > [1] E.g.: > "See /usr/share/doc/docbook-xsl/README.Debian for more informa

Bug#340637: patch breaks nxml-mode startup

2006-09-05 Thread Michael(tm) Smith
The following part of the patch seems to break nxml-mode in my environment. See bug #385240 (Cannot find unicode character file) --- nxml-mode-20041004-4/rng-auto.el2004-10-04 13:57:56.0 +0900 +++ nxml-mode-20041004-6/rng-auto.el2006-09-06 13:35:11.0 +0900 @@ -56,8 +56,7 @@

Bug#385240: change to

2006-09-05 Thread Michael(tm) Smith
The culprit seems to be the following change that was made to the rng-auto.el file. --- nxml-mode-20041004-4/rng-auto.el2004-10-04 13:57:56.0 +0900 +++ nxml-mode-20041004-6/rng-auto.el2006-09-06 13:35:11.0 +0900 @@ -56,8 +56,7 @@ (let* ((dir (file-name-directory load-file

Bug#386580: Adding warning message and suppressed footnote marker

2006-09-08 Thread Michael(tm) Smith
The manpages stylesheet does not yet support output for footnote. The reason the footnote marker was being output is because the HTML stylesheets (which the manpages stylesheet) output it and I had not overridden that. The footnote marker is now suppressed, and if a refenty contains a footnote, th

Bug#386580: Initial footnote support added

2006-09-21 Thread Michael(tm) Smith
regressions in other areas, including basic paragraph handling, handling of "mixed block" content, handling of other indented content, and handling of authorblurb and personblurb in the AUTHORS section. -- Michael(tm) Smith xmpp:[EMAIL PROTECTED] irc://irc.freenode.net/mobile-web

Bug#389694: xsltproc: problems with dblatex interaction (possibly due to patch for bug #383408)

2006-09-27 Thread Michael(tm) Smith
Package: xsltproc Version: 1.1.17-4 Severity: important The dblatex application makes use of xsltproc. Since upgrading to xsltproc 1.1.17, I am getting error messages such as the following, which I do not get with xsltproc 1.1.16 - /usr/local/share/dblatex/xsl/common/mklistings.xsl:104: elemen

Bug#383408: this patch seems to break dblatex behavior

2006-09-27 Thread Michael(tm) Smith
supported I suspect the cause is the patch that was applied to fix bug #383408. Perhaps Andreas (dblatex packager for Debian) can try to see if he can reproduce the errors. --Mike -- Michael(tm) Smith xmpp:[EMAIL PROTECTED] irc://irc.freenode.net/mobile-web -- To UNSUBSCRIBE, email to [EMAIL

Bug#389832: xchat: words/characters getting truncated

2006-09-27 Thread Michael(tm) Smith
Package: xchat Version: 2.6.4-2.1 Severity: important I just upgraded my xchat yesterday, and now parts of words and characters at the ends of lines are getting cut off in chat windows. Example: if the word "windows" falls at the end of a line, only half of the "s" will be rendered. Or it just ma

Bug#383408: [Dblatex-users] xsltproc: problems with dblatex interaction

2006-09-27 Thread Michael(tm) Smith
"benoit.guillon" <[EMAIL PROTECTED]>, 2006-09-27 23:35 +0200: > Do the warnings still appear when using the -X option? Nope. Which is I guess what you'd probably expect. A "No external file support" message is emitted instead. > Can you try the attached test case (from the docbook test suite)? C

Bug#383408: [Dblatex-users] xsltproc: problems with dblatex interaction

2006-09-27 Thread Michael(tm) Smith
"benoit.guillon" <[EMAIL PROTECTED]>, 2006-09-27 23:35 +0200: > Can you try the attached test case (from the docbook test suite)? Can you > confirm that the listings are correctly displayed with the callouts > bullets inside (and the callout list below)? I just tried it. Results are here:

Bug#383507: xml-core: Catalogs for ISO character entities should contain SYSTEM ID references

2006-08-17 Thread Michael(tm) Smith
Package: xml-core Version: 0.09-0.1 Severity: important The XML versions of the ISO 8879:1986 character-entity sets are officially maintained by the W3 and the official base URL for them is: http://www.w3.org/2003/entities/iso8879/ The xml-core package adds data to the Debian XML and SGML cat

Bug#442049: pam_env "Unable to open env file: /etc/environment"

2007-09-13 Thread Michael(tm) Smith
hing related to locale stuff; I update just by running "apt-get update && apt-get upgrade" every few days. --Mike -- Michael(tm) Smith http://people.w3.org/mike/ http://sideshowbarker.net/ smime.p7s Description: S/MIME cryptographic signature

Bug#408842: Saxon 8 and Saxon 6 are separate upstream packages

2007-09-25 Thread Michael(tm) Smith
, not a replacement of the docbook-xsl package. -- Michael(tm) Smith http://people.w3.org/mike/ http://sideshowbarker.net/ smime.p7s Description: S/MIME cryptographic signature

Bug#385240: Debian bug #385240 (Cannot find unicode character file)

2007-07-24 Thread Michael(tm) Smith
Vincent Lefevre <[EMAIL PROTECTED]>, 2007-07-23 12:08 +0200: > This bug seems to be fixed in 20041004-7. Yep --Mike -- Michael(tm) Smith http://people.w3.org/mike/ http://sideshowbarker.net/ smime.p7s Description: S/MIME cryptographic signature

Bug#420114: DocBook XSL and git man pages

2007-07-26 Thread Michael(tm) Smith
n this bug report. I have reverted that for the 1.73.0 release. (and unfortunately managed to introduce some additional regressions while I was at it -- but I think Daniel will have patched those downstream for the Debian 1.73.0 package). --Mike -- Michael(tm) Smith http://people.w3.org/

Bug#310895: docbook-xsl: Add option to enable filenames like $NAME.$LANG.$SECTION

2006-10-27 Thread Michael(tm) Smith
pt-get.fr.8 man page instead of just a man/fr/apt-get.8 page? > In the case of implementing this, I guess such manpages should be put into > $base.dir/$LANG if man.output.subdirs.enabled is enabled. Yep. But would that be in addition to adding support for foo.$LANG.1 ? --Mike --