Re: Midnight Commander within console in UTF-8 mode

I guess it's not an urgent problem and with upcoming glib 1.4 we'll
get nice unicode module, so we can be independent from platform
and have a better framework to deal with different charsets.

I should mention, that MC wasn't(and still not completly) 8-bit
clean quite recently - I've commited patches to work with russian
filenames and strings in the input less than year ago.

And noone complained before :) So, I hope, we can wait a bit untill
new version of glib will be released.

Also, I don't remember claims that Slang is UTF8 or UCS16 safe..


On Tue, Oct 23, 2001 at 08:45:44PM -0700, Andy Rysin wrote:
> --- Pavel Roskin <proski gnu org> wrote:
> ...
> > My guess is that MC is most likely not responsible for that.  You
> > could
> > check how the screen library (included S-Lang, system installed
> > S-Lang,
> > ncurses) affects this behavior.  Also you could look into
> > "Options->Display bits..." in MC and make sure that you have "Full
> > 8 bits
> > output" enabled.
> 8 bits are defenitely turned on, and I'll try to play with those
> libraries soon. 

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]