Re: Problem with texi2dvi on spanish texi source

[Grzegorz Adam Hankiewicz]

>     I presume I will have to deal with this odd behaviour, so what can I
>     do with 8-bit characters in xrefs?
> 
> About all I can propose is to run sed or something in between, to
> fix up the .aux file by hand.  I don't know what other people do.  Does
> anyone else on the list have suggestions/experience?

Can you tell me more about the purpose/use of the .aux file? Or
point me into the documentation? I don't know how should I 'hack it'.

> Unless you can rewrite the preaccented characters into constructs like
> @'a or @~n.  This is not nearly as good (because it interferes with
> hyphenation), and not all characters are available, but it does (or
> should) work with texinfo.tex.

Er... I'm actually using those constructs, you can check that in the
attached file I sent, unless I forgot the attachment or there are
*other* constructs I'm not aware of. With 8-bit characters texi2dvi
works, but swallows accented characters. With 7-bit constructs,
texi2dvi fails to generate correctly the .ps file, as shown in my
previous mail.

>     PD: While I'm at it, what's the 7-bit version of the latin character
>         'º'? 
> 
> I'm sorry, but that character does not display as anything meaningful
> for me.  What is it?

Character 186 from iso-8859-1. If you have python you can do "print
'\xba'" in the interpreter. It's used in spanish for 1st, 2nd, etc, where
'st', 'nd', etc are substituted by that character.

> I'm sorry I don't have a better answer, but that's where things stand ...

I would welcome pointers to the patches you have recieved, in order
to check them myself. Also, any anonymous cvs with the texinfo source?