Re: [Groff] Installing Russian Type-1 Fonts

[Anton Shepelev]

Werner LEMBERG:

> I've  posted  a  solution  a  few years ago to the
> groff list which is still valid.

Ah, thank you. So you are mapping the Russian alpha-
bet to internal characters correspoinding to KOI-8-R
and then using  hyphenation  patterns  in  the  same
encoding.

This  way, not only UTF-8 input may be fed to groff,
but also KOI-8-R --  just  omit  preconv  processing
(the -K or -k option to groff)!

Here's my understanding of what happens:

----------------------------------------------------
       8-bit input                UTF-8 input
----------------------------------------------------
The  input  file  is read  The input file  is  first
in, and  the  input  map-  processed   by   preconv,
ping, in your case speci-  that converts input char-
fied in  koi8-r.tmac,  is  acters  into AGL-compati-
...skipping...
and then using a hyphenation  pattern  in  the  same
encoding.

This  way, not only UTF-8 input may be fed to groff,
but also KOI-8-R --  just  omit  preconv  processing
(the -K or -k option to groff)!

Here's my understanding of what happens:
Therefore, I suppose that groff applies the existing
character translations inversely to get back to some
simple  characters.  Then,  hyphenation codes can be
computed and compared against the  hyphenation  pat
terns.
----------------------------------------------------

So, only the input stream gets processed by preconv,
while the hyphenation codes and patterns are read in
directly.  To  make pattern matching possible, a set
of .trin commands is used to define a  mapping  from
internal entites to simple input characters and, via
.hcode requests, to hyphenation codes.

But generally, this map cannot be inversely  applied
becuase  several input characters may be mapped into
one internal entity. What  does  groff  do  in  this
case?

It wasn't clear that preconv is only used with input
files, but not with hyphenation codes and patterns.

Anton