<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2014-11-20 13:21 GMT-03:00 Mattias Gaertner <span dir="ltr"><<a href="mailto:nc-gaertnma@netcologne.de" target="_blank">nc-gaertnma@netcologne.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
2. The new mode: The LCL, FCL and RTL treat all "String" as UTF-8<br>
encoded. Most RTL file functions now work with full Unicode.<br>
For example FileExists and aStringList.LoadFromFile(Filename) now<br>
support full Unicode.<br></blockquote><div><br>[..] <br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Please test and tell what you find out.<br>
<br></blockquote><div><br></div><div>The FormatSettings fields are still encoded with System Code Page regardless of DefaultSystemCodePage value.<br><br></div><div>While for english locales there's no problem, other locales like PT-BR have accented names in days and monthes.<br></div><div><br></div><div>The problem is in windows SysUtils.GetLocaleStr function that uses non unicode Win Api function. This problem will affect also the UnicodeString RTL.<br><br></div><div>Attached is a test app that shows the issue. It also has a version of GetLocaleStr that fixes the issue for the RTL (both versions)<br></div><div><br></div><div>Luiz<br></div></div></div></div>