Changes between Version 4 and Version 5 of Ticket #67, comment 40


Ignore:
Timestamp:
Apr 12, 2014, 2:37:08 PM (10 years ago)
Author:
Yves

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #67, comment 40

    v4 v5  
    1919||56||Newlines in textfiles for formatting||There are some messages like this at startup: „tinygettext: Couldn't translate: „[[BR]]It's caused by the newlines in splashscreen.txt. The newlines are there for formatting purpose and our localization system tries to find a translation for „\n“.||Bug||
    2020||57||Trying to translate already translated template data||GetTechnologyData in session.js calls translateObjectKeys and translates the technology's genericName. Later getEntityNames in utility_functions.js tries to translate it again and fails because it passes the already translated string as msgid.[[BR]][[BR]]Steps to reproduce (I've used the German translation):[[BR]]1. Enable translation error logging in Log.cpp[[BR]]2. Singleplayer->Matches[[BR]]3. keep the default setup, just set your civ to Iberians[[BR]]4. Start the game and then select a female citizen[[BR]][[BR]]I'm getting the message „tinygettext: Couldn't translate: Stadtphase“||Bug||
    21 ||58||Strings not yet added for translation||- simulation/components/BuildRestrictions.js (multiple strings)[[BR]]- simulation/components/Player.js („Insufficient resources“)[[BR]]- Gui/session/messages.js ("You have been attacked by %(attacker)s!")[[BR]]- ... others?||Todo||
     21||58||Strings not yet added for translation||Also check nbr 59 in regard to the simulation localization[[BR]]- simulation/components/BuildRestrictions.js (multiple strings)[[BR]]- simulation/components/Player.js („Insufficient resources“)[[BR]]- Gui/session/messages.js ("You have been attacked by %(attacker)s!")[[BR]]- ... others?||Todo||
     22||59||Localization of components||How do we localize strings coming from components?[[BR]]These can be sent over the network as messages or be part of the simulation state (and must therefore not differ). [[BR]]Localization should most likely be deferred to the GUI code.||Question||