From: Timur Sufiev <tsufiev@gmail.com>
To: git@vger.kernel.org
Subject: Timur Sufiev: Re: [PATCH I18N filenames v2 3/3] Provide compatibility with MinGW
Date: Fri, 06 Nov 2009 13:00:42 +0300 [thread overview]
Message-ID: <4af3f3cb.0305560a.7a34.0f43@mx.google.com> (raw)
[-- Attachment #1: forwarded message --]
[-- Type: message/rfc822, Size: 2205 bytes --]
From: Timur Sufiev <tsufiev@gmail.com>
To: Peter Krefting <peter@softwolves.pp.se>
Subject: Re: [PATCH I18N filenames v2 3/3] Provide compatibility with MinGW
Date: Tue, 03 Nov 2009 19:53:44 +0300
Hello, Peter
> Hi!
>
> Instead of calling the open_i18n() which converts from UTF-8 to a local
> 8-bit character set, this should probably call a version that converts from
> UTF-8 to UTF-16 and uses _wopen().
>
> Same thing for fopen_i18n() and _wfopen().
>
> I created a small RFC patch for that that changed parts of the system
> earlier this year - http://kerneltrap.org/mailarchive/git/2009/3/2/5350814
>
> I did not address readdir() and friends, I'm not sure if they are available
> in UTF-16 form or if they need to be rewritten using findfirst()/findnext().
>
> --
> \\// Peter - http://www.softwolves.pp.se/
I've decided to stick to local 8-bit encoding for now having considered
the following issues:
1. Many git front-ends, e.g. TortoiseGit, use 8-bit set, not UTF-16:
they call git plumbing commands and pass filenames to command line (in
local 8-bit encoding). So, using [UTF-8] <-> [UTF-16] approach, I had to
deal with 3 different encodings: UTF-8, UTF-16 and local 8-bit one
(CP1251 in my case). Moreover, Windows itself uses both UTF-16 and
CP1251, so one had to deal with reencoding between them (if he plans to
support UTF-16). Too much confusion.
2. UTF-16 is a proper solution for Windows, but my patch is useful for
other OSes with locales different from UTF-8 (e.g. Linux with KOI8-R
locale).
Still there is a possibility that one day we'll stumble upon some UTF-8
symbol which cannot not be correctly mapped into 8-bit encoding. UTF-16
would be a remedy in this case, but what if don't have it (see 2)?
--
Timur Sufiev
[-- Attachment #2: Signature --]
[-- Type: text/plain, Size: 17 bytes --]
--
Timur Sufiev
next reply other threads:[~2009-11-06 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 10:00 Timur Sufiev [this message]
2009-11-06 14:55 ` Timur Sufiev: Re: [PATCH I18N filenames v2 3/3] Provide compatibility with MinGW Peter Krefting
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4af3f3cb.0305560a.7a34.0f43@mx.google.com \
--to=tsufiev@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox