input encodings in info files

[Han-Wen Nienhuys]

address@hidden writes:
> texinfo files are very limited w.r.t. input encodings.  Currently,
> latin1 is the best choice -- in reality, even this is not handled

I think the most practical solution is not to use accented letters in
the documentation at all. For the longer term, we   need to

* handle encodings in a sane manner in Postscript

* dump systems both for latex and texinfo as separate .EPS files in
  lilypond-book, and import them in that way.


[let's continue on lp-devel]

BTW, I recently came across the glyphshow command in GS/PS. Doesn't
glyphshow obviate the (hairy) hack of recoding fonts on the fly for
encoded PostScript output?


-- 

 Han-Wen Nienhuys   |   address@hidden   |   http://www.xs4all.nl/~hanwen