Werner LEMBERG:
> Unfortunately, I don't have enough time currently
> to find a solution for your original problem.
Thank you very much for your time! Now I have more
options to choose from.
Anton
> Your example works perfectly with -Tutf8 if the source file is in
> UTF-8 and the -K preprocessor is used, and was the first thing that
> I tried.
OK.
> But it does not work either for -Tlatin1, or for -Tutf8 with the
> source in KOI8-R,
Processing my example works just fine if the input file
The previous post was encoded in CP-1251.
Please, accept my apology.
I can re-post it if necessary.
Anton
Thanks for your reply, Werner:
> What about doing it the naive way?
>
> File `lcuc' in UTF-8 encoding:
> [...]
> Provided you have proper PS fonts, this works with
> -Tps also.
>
> Am I missing something?
Your example works perfectly with -Tutf8 if the
source file is in UTF-8 and the -K pr
> 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):
>
> InputResult
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
> [...] 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.
I
Clarke Echols:
> [...]
> I went through the entire system and changed it so
> the name of a command, system call, etc. was al-
> ways lowercase unless the actual command or name
> was uppercase or mixed-case.
>
> That eliminated the confusion and improved usabil-
> ity. I am still opposed to
On 11/21/2011 09:12 AM, Anton Shepelev wrote:
Hello all,
I want to typeset headers in man pages (an-old.tmac)
differently for text-based and PostScript devices.
For the former I want them to be uppercase, while
for the latter -- in the normal case, as they were
typed.
I thought I would
Hello all,
I want to typeset headers in man pages (an-old.tmac)
differently for text-based and PostScript devices.
For the former I want them to be uppercase, while
for the latter -- in the normal case, as they were
typed.
I thought I would prepend the TH and SH macros with
code that woul
10 matches
Mail list logo
