> > ... groff doesn't yet support UTF8 input.
>
> Attached is a small C program that does that.
Michail,
sorry for not answering such a long time. Currently, I don't have
time to look into your stuff since the deadline of the next TeXLive is
near, but I will check it in a few weeks.
We
Greetings from Tokyo.
Question: What's the correct inline groff markup for preventing an
individual word from being hyphenated?
I notice that the groff info page says this:
To tell `gtroff' how to hyphenate words on the fly, use the `\%'
escape, also known as the "hyphenation character". Pr
> I notice that the groff info page says this:
>
> 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 [...]
>
> But that does not seem to actually wo
Werner LEMBERG <[EMAIL PROTECTED]> writes:
> > I notice that the groff info page says this:
> >
> > 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 hyphen
Am Donnerstag, 30. Juni 2005 16:19 schrieb Michael Smith:
> And if I just specify in my XSLT stylesheet that each option needs
> to be output with an .nh before it and an .hy after it, what I end
> up with is this:
>
> .nh
> encodings
> .hy
> ,
> .nh
> catalogs
> .hy
> ,
>
> Which i
> Here's a minimal example that illustrates the problem: [...]
I've tried both groff 1.17.2 and the current CVS, and your man page
example works just fine (I don't have 1.18.1 installed on my system).
> If I run that through man(1), I still get breaks within the words
> that fall at the end of l
Werner LEMBERG <[EMAIL PROTECTED]> writes:
> I suggest that you download an original version of the groff package
> (from gnu.org), not the Debian version which is heavily patched --
> maybe the Japanese extension (which I don't support) is buggy, causing
> the problems you experience.
Indeed, it
