Re: [Groff] [PATCH] compiling error on grolbp with latest CVS update

[Werner LEMBERG]

> PS: what do you think about my latin9 patch? is 8-bit char encoding
> considered obsolete?

Your patch is OK, but I don't know how to proceed.  Creating more and
more directories for the various encodings + devices isn't a valid
solution, so I will postpone your changes.

A guy is trying to make Unicode input possible (BTW, any results
meanwhile?), and I will try to remove input encoding stuff from the
font description files.

I'll probably introduce a kind of `fonts.dir' file to register the
(font) encoding of the fonts for a particular device to have the
following chain:

  groff glyph -> lookup the device's fonts.dir
              -> search a font which covers the input encoding
              -> check font shape, slant, etc.
              -> if no results, check the special fonts

For example, having `devX100' and `latin2', let's assume that the font
for shape `Roman bold italic' is called TBI2.  In fonts.dir, this
would be mapped to `TBI', and everything works as expected.

Such an approach of course assumes that a particular font covers a
given input encoding, but anything else would be much more
complicated.

Comments?


    Werner