Re: Why utf8_linux_frame_seqs?

On Wed, May 16, 2007 at 09:09:02AM +0300, Kalle Olavi Niemitalo wrote:
> In ELinks 0.12.GIT (f8f99cc04ea0ff1f64c0452f5232e1b2567493c2):
> 
> - If UTF-8 I/O is disabled, then src/terminal/screen.c outputs
>   normal characters in the terminal charset, and frame characters
>   usually in a separate frame charset.  To switch between the
>   charsets, it outputs strings from screen_driver.frame_seqs[].
> 
> - If UTF-8 I/O is enabled and CONFIG_UTF8 is not defined, then
>   src/terminal/screen.c outputs all characters in UTF-8.  It
>   converts frame characters first to some unibyte codepage that
>   supports them (typically CP437), and then to UCS-4 and UTF-8.
> 
> - If UTF-8 I/O is enabled and CONFIG_UTF8 is defined, then
>   src/terminal/screen.c outputs normal characters in UTF-8,
>   and frame characters usually in a separate frame charset.
>   To switch between the charsets, it outputs strings from
>   screen_driver.frame_seqs[], which may be
>   utf8_linux_frame_seqs[] defined for this purpose.
> 
> I would like to change src/terminal/screen.c so that UTF-8 I/O
> always outputs frame characters in UTF-8, regardless of whether
> CONFIG_UTF8 is defined.  I have already implemented this but the
> change is currently entangled with fixes for bug 914 and
> separating it will take some time.

You can remove utf8_linux_frame_seqs. It forces the UTF-8 mode on
the Linux console. Proper way is to set the UTF-8 mode before starting
the ELinks.

-- 
Witek