On Fri, Jul 01, 2005 at 10:14:33AM +0900, Michael Smith wrote: > Bad news: Handling of \% in LANG=ja_JP.eucJP environments is borked. > > In a LANG=C environment, a word preceded by a \% character does > not get hyphenated under any circumstances. That is good. It is > the expected behavior. > > But n a LANG=ja_JP.eucJP environment, if a word preceded by a > hyphen ends up falling at the end of a line in rendered output, it > may unexpectedly get hyphenated. That is bad. > > The groff info docs make it clear that \% prevents hyphenation: > > To tell `gtroff' how to hyphenate words on the fly, use the `\%' > escape, also known as the "hyphenation character". Preceding a > word with this character prevents it from being hyphenated [...] > > Here is a minimal document that can be used to see the problem: > > .TH "EXAMPLE" 7 "2007\-09\-04" "Version 1" "Controlling hyphenation" > .\" ================================================================ > .SH "NAME" > .\" ================================================================ > example \- show some problem with preventing hyphenation > .\" ================================================================ > .SH "DESCRIPTION" > .\" ================================================================ > .PP > Values for the \%version, \%recovery, \%debugging, \%timing, > \%output, \%repeat, \%compression, \%insert, \%formatting, > \%encodings, \%catalogs, \%automation, \%register, \%validate > options may be set in the configuration file as well as via the > command line.
Thanks, belatedly, for your report. I think it's probable that groff 1.20.1-1 or newer (in Debian unstable as of last night) fixes this, since it disposes of the old multibyte patch used to support CJK languages and relies on upstream code instead. However, I can't seem to reproduce your original report - none of the words in your document seem to get hyphenated in my tests - and thus I can't in good conscience close this as fixed. Do you think you could retest this with 1.20.1-1 at some point, and let me know if it still seems to be an issue? If so, perhaps you could tell me a little more about the environment in which I could reproduce this: what groff command line should I use, exactly how wide a terminal should I use, and so on. Thanks, -- Colin Watson [[email protected]] -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
