Re: input encodings in info files

[Werner LEMBERG]

> I think the most practical solution is not to use accented letters
> in the documentation at all.

But this is a lame solution...  With my attached stuff latin-1 is
supported quite well.

BTW, it is better not to name the file tex/texinfo.cnf but, say,
Documentation/user/latin1.itexi, and it then is included in all
texinfo files -- texinfo.cnf is rather reserved for local adjustments.

> For the longer term, we need to
> 
> * handle encodings in a sane manner in Postscript

We'll discuss this soon.

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

What exactly do you mean?  All lilypond snippets should be EPS?

> 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?

I don't think that this is efficient.


    Werner