[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Spanish font failure in Table of Contents
From: |
Robert J. Chassell |
Subject: |
Re: Spanish font failure in Table of Contents |
Date: |
Fri, 28 Jun 2002 15:43:11 +0000 (UTC) |
Basically, 8-bit input does not work in the current texinfo.tex.
Oh! I thought it did work -- I thought that some people in Spain
were writing documentation in Spanish. I guess I was wrong.
Also, I thought that the @documentlanguage command implied support
for many languages. Now, however, I read the next node in the
Texinfo manual and it says
File: texinfo, Node: documentencoding
address@hidden ENC': Set Input Encoding
===========================================
The address@hidden' command declares the input document
encoding. Write it on a line by itself, with a valid encoding
specification following, such as `ISO-8859-1'.
At present, this is used only in HTML output from `makeinfo'.
which implies it does not yet work for dvi output.
Clearly it's highly desirable that it should, but I have not had the
chance to work on it. It's a large job, ....
<sigh> Over the next few months, I hope to inspire more translations
including German, French, and Chinese, and would like to produce them
in Texinfo. I did not know that could not be done.
The only workaround is to use composite accents such as @'o,
That might work with Spanish, but not with Chinese.
As a work around, can I convert the Texinfo file with the Spanish in
it to DocBook or other XML using makeinfo and then print the result
and convert it to an HTML page?
--
Robert J. Chassell address@hidden
Rattlesnake Enterprises http://www.rattlesnake.com