Mail Archives: cygwin-developers/2002/07/03/08:57:09
>>> On Wed, 3 Jul 2002 11:07:15 +0100
>>> "Chris January" <chris AT atomice DOT net> said:
> My question is, does anyone have any objections to doing things this way,
> and if so, can they suggest a better way? I don't want to patch the whole of
> Cygwin and then have to re-write everything at a later date.
I'd like to propose supporting other codepages than UTF8 and
making it connected with other portions than filenames.
For example, in case of CYGWIN=codepage:20866, suppose
the `parse_options' set current_codepage = other_cp and
current_cpnum = (UINT)20866.
Your example would become as follows.
if (current_codepage == other_cp)
if (MultiByteToWideChar (current_cpnum, 0, get_win32_name(), -1,
wbuf, MAX_PATH) == 0)
x = CreateFileW (wbuf, access, shared, &sa, creation_distribution,
x = CreateFileA (get_win32_name (), access, shared, &sa, creation_distribution,
Moreover, get_cp in miscfunc.cc would have to become as follows.
When we want to use UTF8, we set codepage:65001 or codepage:utf8.
The latter case needs for the parser to accept "utf8" and
translate it to CP_UTF8 (65001).
How about this idea?
| AIST Kazuhiro Fujieda <fujieda AT jaist DOT ac DOT jp>
| HOKURIKU Center for Information Science
o_/ 1990 Japan Advanced Institute of Science and Technology
- Raw text -