On Sun, 18 Jun 2000, Karl Heinz Marbaise wrote:
> The following extract of the project should make clear where the
> problems are
> (It's part of a portuguese translation, frensh can produce the same
> problems). As you can see there is the need for
> cedilla and accents etc. in node names, usual Text and index entries.
Is it true that the problem is *only* with cedilla? I tried other
accents, and they do seem to work. However, your messages, both this one
and the original one, seem to imply that other accents don't work either,
so I wonder whether we are talking about the same problem...
If indeed you have problems with other accents, please give more details.
As for cedilla, the problem is that "@,{c}" includes a literal comma, and
a comma is, of course, special in a @node directive.
I looked into the code that processes @node, and my conclusion is that it
might be tricky to fix without thorough rewrite of the functions that
extract arguments from @node, @xref, and other related commands. I'm not
sure whether such a rework is justified.
In general, I'd expect that Texinfo files in languages other than English
be written in 8-bit Latin-N encoding directly, rather than using Texinfo
commands. I always thought that the Texinfo commands are for those rare
cases where you need to show a Latin-1 character in an otherwise English
text; isn't that so? AFAIK, Texinfo commands don't support all of the
Latin-1 characters, to say nothing of Latin-2 and others.
If somehow you _must_ use Texinfo commands such as @,{}, I suggest a
work-around. Put the following somewhere near the beginning of your
document:
@definfoenclose cedilla,,,
and then use it like so:
@node Come@cedilla{c}ando um projeto novo CVS
You will have to provide a different @definfoenclose for the HTML case.
