Author Topic: [3.5.1] Localization problem  (Read 4522 times)

rextr

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 15
    • View Profile
[3.5.1] Localization problem
« on: February 28, 2014, 05:11:16 PM »
Hi,

In NGUI 3.5.1 , the "knownLanguages" property became static, so we cannot drag and drop our txt files to this list. What is the proper way of localization with separate txt files?

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: [3.5.1] Localization problem
« Reply #1 on: February 28, 2014, 05:37:09 PM »
You don't need to set your known languages. This is now set from the CSV localization file based on the number of columns and the value of the first row.

rextr

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 15
    • View Profile
Re: [3.5.1] Localization problem
« Reply #2 on: March 01, 2014, 06:03:54 AM »
So, you are saying that a separate txt for each language is no longer supported? (Txt files with key = value pairs)

If we go to csv route we have problems with labels that contains "," such as as "10,000 cash" , because comma means new column.

Therefore, it would be great if we can have separate files for each language as before.

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: [3.5.1] Localization problem
« Reply #3 on: March 01, 2014, 08:56:55 PM »
Not if it's wrapped in quotes. And yes, the text version is still supported, but the list of known languages now comes from the CSV file.