[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Groff] An uppercase mode
From: |
Werner LEMBERG |
Subject: |
Re: [Groff] An uppercase mode |
Date: |
Tue, 22 Nov 2011 10:22:58 +0100 (CET) |
> [...] it turned out that simple requests like
>
> .tr aAbBcC or
> .char aA
>
> do not work with Russian (non-ACSII) symbols and that I have to do:
>
> .char a\[u0431]
>
> which of course only works with the PostScript de- vice, but fails
> with latin1 which I use for text output.
It is a limitation of groff that a character must be a one-byte entity
or `\[...]'. Hence no native UTF-8 input support, but you have to use
the preconv preprocessor.
However, I don't understand this line:
.char a\[u0431]
You want to map `Latin small letter a' to `Cyrillic small letter be'?
Can you prepare a small example which really demonstrates what you
want to do?
Werner
- [Groff] An uppercase mode, Anton Shepelev, 2011/11/21
- Re: [Groff] An uppercase mode, Clarke Echols, 2011/11/21
- Re: [Groff] An uppercase mode,
Werner LEMBERG <=
- Re: [Groff] An uppercase mode, Anton Shepelev, 2011/11/23
- [Groff] Detection of PATH_SEPARATOR in configure, Jeff Conrad, 2011/11/24
- Re: [Groff] Detection of PATH_SEPARATOR in configure, James K. Lowden, 2011/11/28
- Re: [Groff] Detection of PATH_SEPARATOR in configure, Jeff Conrad, 2011/11/30