Tasharen Entertainment Forum
Support => NGUI 3 Support => Topic started by: mcarriere on March 12, 2014, 11:19:30 AM
-
Just a small Localization bug to report:
We're using the old localization method, where you have different languages in separate text files, rather than one CSV. Even with you moving the Localization CSV to a deeper folder, the CSV in the examples will be picked up before the individual text files are. I had to rename the CSV in order to use our old files.
(edit: this is in 3.5.3)
-
Yes, that's why the examples folder has their own Resources folder where the localization file resides. Just delete it if you aren't using it.
-
Spent an hour or two locating this problem today :(. Renaming/deleting it fixed it.
To be clear, when the localization example is still in your project, setting a different language does nothing at all, it chooses the English as defined in the example.
It's pretty annoying. Is there no way that this example can be removed or renamed in the next version of NGUI? Or just NOT USED when not explicitely wanted.
It seems like a very poor solution for the end-user having to manually remove it.
Or maybe just a big fat bold warning in the Localization.cs comment section?
Thanks in advance for your answer.
Diederik / Xform