git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/4] Add routines for filenames encoding <local encoding> <-> UTF-8

From
Timur Sufiev <tsufiev@gmail.com>
Date
Oct 28, 2009, 07:15 UTC
Message-ID
<4ae7ef9d.0f1abc0a.5b53.1a73@mx.google.com>
In-Reply-To
<alpine.DEB.2.00.0910271515270.17168@ds9.cixit.se>
Show 5 quoted lines
>> If `i18n.filenameslocalencoding' option was set via git-config to a 
>> correct <codepage> encoding, 2 things should be done:
> 
> Windows supports UTF-16 file names, but need to use wchar_t APIs for fopen() 
> and friends. Have you looked at any of that?
No, I didn't look towards Windows handling of Unicode, because Git under
Windows works well enough without that: I've built Git in MinGW/MSYS
environmment (using the patches we're discussing) and it handles
cyrillic filenames in Windows ANSI CP1251 codepage just as was planned:
writes filenames to tree objects in UTF-8, checks out them into working
dir in CP1251, other stuff as git-clone, git-diff, git-status, etc also
works ok. One remaining issue (offtopic here, as far as I understand) to
make TortoiseGit work with UTF-8 Git's output.
 
> -- 
> \\// Peter - http://www.softwolves.pp.se/
-- 
Timur Sufiev
Previous: Peter KreftingNext: Timur Sufiev
Message 7 of 8 in “Add routines for filenames encoding <local encoding> <-> UTF-8”
  1. 1/4 Add routines for filenames encoding <local encoding> <-> UTF-8Timur Sufiev, Oct 27, 2009
  2. 2/4 Add I18N-wrappers for low-level IO-routinesTimur Sufiev, Oct 27, 2009
  3. Jeff KingOct 27, 2009
  4. Timur SufievOct 28, 2009
  5. Jeff KingOct 28, 2009
  6. Peter KreftingOct 27, 2009
  7. Timur SufievOct 28, 2009
  8. 4/4 Make mingw-compatibility layer to be aware of I18N-wrappersTimur Sufiev, Oct 27, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.