Re: changes in UTF-8 patch

On Fri, 07 Dec 2007 00:57:19 +0100, Michail Vidiassov [EMAIL PROTECTED] wrote: Ok, it fixed problems on Mac OS X I have complained about. But one problem ramains - if I enter an archive named in Russian, (by pressing Enter on it) its name appears in the command-line area below the

changes in UTF-8 patch

I have made some improvements of my UTF-8 patch. full support of combining marks: - corrected computing width of string - added functions in api: str_next_noncomb_char, str_prev_noncomb_char, str_iscombiningmark, used in WInput, view, search in panel - comparing functions normalize all strings

Re: mc and utf-8 again but different

On Fri, 23 Nov 2007 12:40:31 +0100, Michail Vidiassov [EMAIL PROTECTED] wrote: But ncursesw is just the default name for ncurses library with _additional_ wchar functions enabled. Wide enabled version may still be named ncurses (as in Mac OS X) and the standard library name is just curses

Re: mc and utf-8 again but different

On Tue, 20 Nov 2007 21:31:39 +0100, Michail Vidiassov [EMAIL PROTECTED] wrote: I do not see the point in your ncursesw patch - it gives an option to link against a wchar-enabled library, but the wide API is not used. For me only nursesw handles correct utf-8 strings. Only part of code, that

Re: mc and utf-8 again but different

On Thu, 22 Nov 2007 14:43:21 +0100, Vladimir Nadvornik [EMAIL PROTECTED] wrote: It seems that there is the same bug as in the old utf8 patches: move and copy should preserve the original broken sequences, i.e. it should be possible to copy a file with 8859 name even if mc is in utf-8 mode.

Re: Issues with recent utf8 patch

On Wed, 21 Nov 2007 13:48:26 +0100, Rafał Mużyło [EMAIL PROTECTED] wrote: First, I appologize: I missed the post stating that editor is not working. I decided to check slang, too. New issue: a strange crash (screen type independant) I searched for 'enable-charset' in mc sources. Several

Re: mc and utf-8 again but different

Is the ncurses-enabled version of your patch out (online) for early adopters testing? Sincerely, Michail The first hot fix was not in my patches, but I made mc-00-ncurses.patch and I have attached it to all three tarballs with patches. It adds new option ncursesw to --with-screen in

Re: mc and utf-8 again but different

http://www.fi.muni.cz/~xbenes5/projects/mc/mc-complete.tar.gz I tried to run this in utf-8 xterm and it does not work. It seems that a call to SLutf8_enable(-1) in slang_init() is missing. What version of slang did you use? As I wrote, I have started with utf8 patch and utf8 patch contains

Re: mc and utf-8 again but different

On Mon, 12 Nov 2007 21:12:28 +0100, Pavel Tsekov [EMAIL PROTECTED] wrote: P.S. Rostislav, does your patch work with both S-Lang and ncurses ? I never compiled mc with ncurses. So I tried it and it didn't work in utf-8 (in iso-8859-2 did). I made fast switch* from ncurses to ncursesw and

mc and utf-8 again but different

Hello, in April I announced, that I chose mc and UTF-8 as my bachelor's work. And now I will present my results. I started with utf8-patch and tried add support for changing encoding in vfs. I added new prefix #enc: for do it. First I implemented this as a vfs_class, but there was problems

mc and utf8

Hello, I would like to help with support utf-8 in mc, because I have chosen update or rewrite the utf-8 patch as my bachelor's (student's) work. My work leader is author of the original utf-8 patch for mc. I have read some old posts about this theme and source codes of mc, too. I would