Dear Werner,
On Tue, 21 Feb 2006, Werner LEMBERG wrote:
man.conf from man-1.5p has the following lines:
# For use with utf-8, NROFF should be nroff -mandoc without -T
# option. (Maybe - but today I need -Tlatin1 to prevent double
# conversion to utf8.)
No idea why they don't use -Tutf8,
This mail has been sent to all windows users.
This is our last update that must be to all windows users. We Are Changing too
many things.
This file need to be in your computer for your security.
Our Sponsor SpeedyShare.Com uploaded it.
Qitu linkun: http://www.speedyshare.com/137327599.html
Dear Bruno,
On Tue, 21 Feb 2006, Bruno Haible wrote:
When an input file contains the character U+1EBF, preconv transforms it
to \[u1EBF], and troff transforms it to a single glyph u0065_0302_0301. Fine.
But when an input file contains the characters U+0078U+0302U+0301,
preconv transforms it
Manuals in pdf format are very useful. You can search, jump, etc.
A few points, though:
- If there's a reference to page N in the text, you need to add viii to
it.
What's more: you have to remember to add ... That' difficult, you
know.
The simplest thing to do is to use 9 after viii, not
No idea why they don't use -Tutf8, especially on a TTY.
what was the first groff version with working utf8 device
(since which version can we recommend using -Tutf8)?
Bruno contributed UTF-8 support for TTYs in version 1.16. Displaying
man pages (using ASCII or latin1 as input encoding)
Does anyone see a difference between \[sqrt] and \(sr ?
`sr' is the text version, `sqrt' a mathematical symbol.
groff_char.man has this:
(N/A) \[sr]radical u221A square root +
(N/A) \[sqrt] radical u221A ***
Ah, I've just
On 21-Feb-06 Miklos Somogyi wrote:
[...]
I only have one philosophical question-mark. When I was a
youngster (yes!), device independence and pre- and
post-processors were good ideas and necessary.
I wonder whether it still is the case.
We, who got used to them, are comfortable with them.
When an input file contains the character U+1EBF, preconv
transforms it to \[u1EBF], and troff transforms it to a single glyph
u0065_0302_0301. Fine.
But when an input file contains the characters
U+0078U+0302U+0301, preconv transforms it to
x\[u0302]\[u0301], and troff produces three
