Eli Zaretskii <[EMAIL PROTECTED]> ha escrit:

> Could we please discuss the design of this?  In particular, what do
> you mean by ``LC_ALL is set appropriately'',

I mean that LC_ALL settings should match the @encoding used in the
document. In particular, if [EMAIL PROTECTED] UTF-8' was used, then locale
settings should end in `.UTF-8' (language and territory settings do not
matter in this case). There's nothing new in it: it is the way info
worked before. 

> and how do you intend to
> handle possible differences between the file's encoding and the
> encoding supported by the terminal?

Generally speaking, libiconv can be used for that. But I doubt if info
should try to handle such differences. That's the same thing as with
text editors: you cannot edit a document written in UTF-8 on a terminal
set to ISO-8859-2. In my opinion, it is user's responsibility
to ensure his terminal is set appropriately. 

Regards,
Sergey


Reply via email to