I did some further research, and I think I have figured this out.

It seems to me you aren't really using the system-locale to determine the 
output encoding, but the user-locale, or culture, i.e. the setting that 
governs the format of money, date and time. I'm not sure if this is a good 
choice, but at least I know how to get the results I need. 

I guess you don't want to change this for backwards compatibility reasons, 
but using the real system locale would be more intuitive, and UTF-8 encoded 
temp files would be ideal. (The commit message file already is utf-8 
encoded, so at first I assumed all others are, as well).

Can you comment on this?

thanks,
Csaba

On Friday, May 31, 2019 at 10:26:49 PM UTC+2, Csaba Merényi wrote:
>
> Thanks for the reply!
>
> When you say system locale, what EXACTLY do you mean? To the best of my 
> knowledge, my system locale IS hungarian, which allows these characters to 
> be encoded (cp1250). See below:
> PS C:\Users\csaba> Get-WinSystemLocale | Select-Object Name, DisplayName,
> >>                         @{ n='OEMCP'; e={ $_.TextInfo.OemCodePage } },
> >>                         @{ n='ACP';   e={ $_.TextInfo.AnsiCodePage } }
>
> Name  DisplayName         OEMCP  ACP
> ----  -----------         -----  ---
> hu-HU Hungarian (Hungary)   852 1250
>
> Could the SVN process be running under a different locale? Sorry, I'm not 
> very familiar with the inner workings of Windows locales.
>
> On Friday, May 31, 2019 at 9:46:50 PM UTC+2, Stefan wrote:
>>
>> The encoding of those files is the system locale.
>> So you have to make sure that the filenames can be encoded with that 
>> locale, otherwise you'll get the problem you've just described.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tortoisesvn/baddd116-aa9f-4e97-9b8c-7cc02220e8a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to