Karl Berry <[EMAIL PROTECTED]> writes:

>     The Right Thing is probably to write the source file in latin-1 (or
>     whatever charset seems approriate), use @documentencoding ISO-8859-1,
>     and fix texinfo.tex to deal with that. 
> 
> I agree.  I have no estimated time frame on completing this, though.

I spent a few hours trying things out last night, with quite small
progress. I'm a LaTeX user, but I'm *no* TeXpert, and appearantly I'm
not good enough at cargo cult programming.

I've been reading latex/base/inputenc.sty (which I don't understand),
and misc/isolatin1.sty. Some notes and questions:

If I add

  \catcode246=13 \def^^f6{\"o}

to my source file (test.texinfo) before \input texinfo, that makes the
� character work. So far so good. But now I want to get it into
texinfo.tex. I'd like to try to use file inclusion, similarly to
documentlanguage, like

  \def\documentencoding{\parsearg\dodocumentencoding}
  \def\dodocumentencoding#1{\input #1.def}

this way, the latin1 specific definitions would be saved in a file
ISO-8859-1.def. But I can't figure out how to get it to work. If I put

  \catcode246=13 \def^^f6{\"o}

directly in ISO-8859-1.def, the \catcode command is not recognized,
TeX complais about wrong arguments to the "c" command. Next I copy the
inclusion code from dodocumentlanguage, which uses \tex ... \endgroup
(which I have no idea what it does). TeX stops complaining, but I
don't get any � in the output.

It seems I have to do the

  \catcode246=13 \def^^f6{\"o}

at top level; if I add it again in my source file, enclosed in {}, it
seems to lose its effect.

Finally, I don't want to have raw catcode commands in the include
file, I'd prefer to write

  \fooencode{246}{\"o}

and define \fooencode in texinfo.tex, to make this expand to

  \catcode246=13 \def^^f6{\"o}

But I can't figure out how to do that; in particular I cant figure out
what I should do to be able to use the string "246" (#1 to the macro),
and convert it something I can use as the first argument to \def.

I think that's all for now. I'll appreciate any advice.

Regards,
/Niels

Reply via email to