eg wrote:
> Stefan Küng wrote:
>>
>> If you read those you will see that it's not really a windows problem
>> but a problem with code pages. Of course it's not possible to convert
>> all utf8 sequences into one codepage. And windows has its own local
>> codepages (because they're not really standardized (is that a word?)).
>> And since each OS has its own local (custom) codepages, you can get
>> into troubles. But: as it also says there: both MultiByteToWideChar()
>> and WideCharToMultiByte() work just fine, and that's all we use.
>>
>
> Did a search of the MS Knowledgebase and only came across the following
> reported problem with respect to Japanese Shift-JIS. See the following
> link:
>
> http://support.microsoft.com/kb/170559/en-us
>
> Is this an issue for this approach?
Not really: that happens when converting from the codepage 932 to UTF16.
But since the Subversion lib only converts from/to utf8, this is not an
issue. It can be an issue for the command line client since that one is
not compiled as an utf16 application on windows, but it would also be an
issue with apr-iconv: it can use the same codepage (932) and would
suffer from the same problems.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 4 21:25:04 2007