[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Groff] An uppercase mode
From: |
Anton Shepelev |
Subject: |
Re: [Groff] An uppercase mode |
Date: |
Wed, 23 Nov 2011 00:23:44 +0400 |
Werner LEMBERG:
> Can you prepare a small example which really
> demonstrates what you want to do?
Sorry for the innacurate example. I used a latin
letter instead of a Russian one and a random unicode
entity just to show the kind of translation I was
using.
Here is what I want to do (the Cyrillic symbols in
this e-mail are in KOI8-R):
Input Result
This is normal case This is normal case
.br Это нормальный регистр
Это нормальный регистр THIS IS UPPER CASE
.br ЭТО ВЕРХНИЙ РЕГИСТР
.UPCASE ON
This is upper case
.br
Это верхний регистр
But I can't find how to implement this in the latin1
device. I have tried these translations:
.tr бБ
.tr б\[char226]
but they both don't work and yield the warning:
can't find character with input code 226
while this input character is quite legal for the
latin1 device.
Anton
- [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, 2011/11/22
- Re: [Groff] An uppercase mode,
Anton Shepelev <=
- 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