I looked at the code and UTF-16 encoding for string file is broken and
has been broken for a while. UTF-8 works fine and I have done UTF-8
string encoded file for English, French, Arabic and Japanese. You have
to be careful as the system or the IDE sometimes messes up the files.
Encoding de
Just FYI, UTF-16 used to work fine for me (as soon as I edited the
files in BBedit and nothing else) using the latest WO 5.3 and Apple
Tiger...
UTF-8 did not work properly for french accents, unbreakable spaces and
so on if I remember properly.
Regards and thanks for taking care about this
Am 27.11.2007 um 20:45 schrieb Chuck Hill:
IIRC, there is a problem with UTF-8 in that it does not always
detect UTF-8 properly and sometimes uses a western latin encoding
for UTF-8 files. That is why people started to use UTF-16. Anjo
should recall more.
It sucked, so I converted the
Hi!
True, I use UTF-16 (with no WO-related problems at all) because of
that. I would love to go back to UTF-8, as Subversion is not the best
friend of UTF-16...
Yours
Miguel Arroz
On 2007/11/27, at 19:45, Chuck Hill wrote:
IIRC, there is a problem with UTF-8 in that it does not alway
IIRC, there is a problem with UTF-8 in that it does not always detect
UTF-8 properly and sometimes uses a western latin encoding for UTF-8
files. That is why people started to use UTF-16. Anjo should recall
more.
Chuck
On Nov 27, 2007, at 11:42 AM, Daryl Lee wrote:
Looks like this has
Looks like this has been a bug in WO for quite a while and not a
regression in WO 5.4. Our Unicode/UTF-16 detection for .strings files
is faulty. Until we fix this, UTF-8 is working great. Thanks for
filing a bug Fabrice.
On Nov 22, 2007, at 1:18 AM, Fabrice Pipart wrote:
Hi dear list !
Hi dear list !
Like many I guess, I am adapting my project to Leopard and WO 5.4
I have many details to solve but one is more a problem than others.
My app is terribly slowed down under Leopard.
But now it becomes even more obvious why.
I very often get that kind of error after something like 2
