OpenXcom Forum
Contributions => Translations => Topic started by: SupSuper on August 14, 2012, 02:50:13 am
-
This is where I'll periodically post whenever new text strings are added to the game that will need translation. You can usually find any new strings at the bottom of English.lng (https://raw.github.com/SupSuper/OpenXcom/master/bin/data/Language/English.lng).
STR_NEW_SAVED_GAME
STR_NEW_BATTLE
STR_OPTIONS
STR_TERRAIN
STR_DARKNESS
STR_DISPLAY_RESOLUTION
STR_DISPLAY_MODE
STR_WINDOWED
STR_FULLSCREEN
STR_LANGUAGE
STR_SECTOID_AUTOPSY
STR_SNAKEMAN_AUTOPSY
STR_ETHEREAL_AUTOPSY
STR_MUTON_AUTOPSY
STR_CELATID_AUTOPSY
STR_SILACOID_AUTOPSY
STR_CHRYSSALID_AUTOPSY
STR_FLOATER_AUTOPSY
STR_REAPER_AUTOPSY
STR_SECTOPOD_AUTOPSY
STR_CYBERDISC_AUTOPSY
STR_DESTINATION_UC_
STR_DESTINATION_UC
STR_FARM
STR_FOREST
STR_JUNGLE
STR_MOUNTAIN
STR_DESERT
STR_POLAR
STR_NOT_ENOUGH_ammotype_TO_ARM_HWP
STR_DAY
STR_EQUIPMENT_FOR_craftname
STR_SELECT_SQUAD_FOR_craftname
STR_n_UNITS_IN_EXIT_AREA
STR_n_UNITS_OUTSIDE_EXIT_AREA
STR_RANDOM_BATTLE
STR_MIXED
STR_RIGHT_CLICK_TO_DELETE
STR_ABANDON_GAME_QUESTION
STR_ZOMBIE
STR_FLOATER_SOLDIER
STR_FLOATER_NAVIGATOR
STR_FLOATER_MEDIC
STR_FLOATER_ENGINEER
STR_FLOATER_LEADER
STR_FLOATER_COMMANDER
STR_SECTOID_SOLDIER
STR_SECTOID_NAVIGATOR
STR_SECTOID_MEDIC
STR_SECTOID_ENGINEER
STR_SECTOID_LEADER
STR_SECTOID_COMMANDER
STR_SNAKEMAN_SOLDIER
STR_SNAKEMAN_NAVIGATOR
STR_SNAKEMAN_ENGINEER
STR_SNAKEMAN_LEADER
STR_SNAKEMAN_COMMANDER
STR_MUTON_SOLDIER
STR_MUTON_NAVIGATOR
STR_MUTON_ENGINEER
STR_ETHEREAL_SOLDIER
STR_ETHEREAL_LEADER
STR_ETHEREAL_COMMANDER
STR_CYBERDISC_TERRORIST
STR_REAPER_TERRORIST
STR_CHRYSSALID_TERRORIST
STR_CELATID_TERRORIST
STR_SILACOID_TERRORIST
STR_SECTOPOD_TERRORIST
STR_HAS_BEEN_KILLED
STR_DRAG_SCROLL
STR_HIT_MELEE
STR_CONTROLS
STR_RESTORE_DEFAULTS
STR_GENERAL
STR_GEOSCAPE
STR_BATTLESCAPE
STR_SCREENSHOT
STR_FPS_COUNTER
STR_ROTATE_LEFT
STR_ROTATE_RIGHT
STR_ROTATE_UP
STR_ROTATE_DOWN
STR_ZOOM_IN
STR_ZOOM_OUT
STR_TOGGLE_COUNTRY_DETAIL
STR_TOGGLE_RADAR_RANGES
STR_SCROLL_LEFT
STR_SCROLL_RIGHT
STR_SCROLL_UP
STR_SCROLL_DOWN
STR_VIEW_LEVEL_ABOVE
STR_VIEW_LEVEL_BELOW
STR_CENTER_SELECTED_UNIT
STR_PREVIOUS_UNIT
STR_NEXT_UNIT
STR_DESELECT_UNIT
STR_INVENTORY
STR_MINIMAP
STR_END_TURN
STR_ABORT_MISSION
STR_UNIT_STATS
STR_KNEEL
STR_RELOAD
STR_TOGGLE_PERSONAL_LIGHTING
STR_DONT_RESERVE_TUS
STR_RESERVE_TUS_FOR_SNAP_SHOT
STR_RESERVE_TUS_FOR_AIMED_SHOT
STR_RESERVE_TUS_FOR_AUTO_SHOT
STR_CENTER_ON_ENEMY_1
STR_CENTER_ON_ENEMY_2
STR_CENTER_ON_ENEMY_3
STR_CENTER_ON_ENEMY_4
STR_CENTER_ON_ENEMY_5
STR_CENTER_ON_ENEMY_6
STR_CENTER_ON_ENEMY_7
STR_CENTER_ON_ENEMY_8
STR_CENTER_ON_ENEMY_9
STR_ENEMY_WEAPON_LEVEL
STR_GROUNDED
STR_LIVING_QUARTERS_PLURAL
STR_OPENXCOM
STR_LIST_ITEM
STR_DISPLAY_FILTER
STR_ADVANCED
STR_ADVANCED_OPTIONS
STR_AGGRESSIVERETALIATION
STR_AGGRESSIVERETALIATION_DESC
STR_ALIENCONTAINMENTHASUPPERLIMIT
STR_ALIENCONTAINMENTHASUPPERLIMIT_DESC
STR_CANSELLLIVEALIENS
STR_CANSELLLIVEALIENS_DESC
STR_ALLOWAUTOSELLPRODUCTION
STR_ALLOWAUTOSELLPRODUCTION_DESC
STR_ALLOWBUILDINGQUEUE
STR_ALLOWBUILDINGQUEUE_DESC
STR_BATTLEAUTOEND
STR_BATTLEAUTOEND_DESC
STR_BATTLEINSTANTGRENADE
STR_BATTLEINSTANTGRENADE_DESC
STR_BATTLENOTIFYDEATH
STR_BATTLENOTIFYDEATH_DESC
STR_BATTLEPREVIEWPATH
STR_BATTLEPREVIEWPATH_DESC
STR_BATTLERANGEBASEDACCURACY
STR_BATTLERANGEBASEDACCURACY_DESC
STR_CANMANUFACTUREMOREITEMSPERHOUR
STR_CANMANUFACTUREMOREITEMSPERHOUR_DESC
STR_CANTRANSFERCRAFTSINAIRBORNE
STR_CANTRANSFERCRAFTSINAIRBORNE_DESC
STR_CRAFTLAUNCHALWAYS
STR_CRAFTLAUNCHALWAYS_DESC
STR_CUSTOMINITIALBASE
STR_CUSTOMINITIALBASE_DESC
STR_GLOBESEASONS
STR_GLOBESEASONS_DESC
STR_PLAYINTRO
STR_PLAYINTRO_DESC
STR_SHOWFUNDSONGEOSCAPE
STR_SHOWFUNDSONGEOSCAPE_DESC
STR_SHOWMORESTATSININVENTORYVIEW
STR_SHOWMORESTATSININVENTORYVIEW_DESC
STR_SNEAKYAI
STR_SNEAKYAI_DESC
STR_STRAFE
STR_STRAFE_DESC
STR_BATTLESCROLLDRAGINVERT
STR_BATTLESCROLLDRAGINVERT_DESC
STR_BATTLEEXPLOSIONHEIGHT
STR_BATTLEEXPLOSIONHEIGHT_DESC
STR_ALLOWPSIONICCAPTURE
STR_ALLOWPSIONICCAPTURE_DESC
STR_HAS_GONE_BERSERK_MALE
STR_HAS_GONE_BERSERK_FEMALE
STR_HAS_PANICKED_MALE
STR_HAS_PANICKED_FEMALE
STR_HAS_BECOME_UNCONSCIOUS_MALE
STR_HAS_BECOME_UNCONSCIOUS_FEMALE
STR_HAS_DIED_FROM_A_FATAL_WOUND_MALE
STR_HAS_DIED_FROM_A_FATAL_WOUND_FEMALE
STR_HAS_BEEN_KILLED_MALE
STR_HAS_BEEN_KILLED_FEMALE
STR_DELETE_UNSUCCESSFUL
-
I see. I will add these to my Chinese translation.
-
@SupSuper
Ok
-
Are the terrain names hardcoded? Can they be referenced somewhere in the language file to translate them?
I'm talking about the ones from the battle simulator.
-
Are the terrain names hardcoded? Can they be referenced somewhere in the language file to translate them?
I'm talking about the ones from the battle simulator.
Currently they are the the direct map names, but I guess I could replace them with some language strings.
-
https://www.ufopaedia.org/index.php?title=Terrain
-
here is the german translation with the new strings :)
-
Based on feedback, I've added some new strings (see OP). Grab the new version of the language files from Git and make any updates necessary.
-
Should i post the german updates here? or in a new thread?
anyway here the updatet files :)
-
Better to make a new thread for it, keeps things organized. :)
Also feel free to review the original translation for any issues, as I've heard they're a bit sloppy (eg. STR_TANK_CANNON and STR_TANK_ROCKET_LAUNCHER had the same text, I fixed that myself :P).
-
new string STR_RANDOM_BATTLE
-
Is it possible to separate some strings on various places in the game? I have tested the Polish translations and I have found some problems. In Polish "names" of people and "names" of things are not the same word. Unfortunately, both people's names on soldier list and object names on craft are the same string STR_NAME_UC.
Another problem is with UFOpedia titles and names of base facilities in the right list on the construction screen. The problem is that some Polish names are enough long. In Ufopedia they are generated with a smaller font, and looks right. But on the list mentioned above they do not fit and are seen broken. The optimal solution would be the full form in Ufopedia while a kind of abbreviation in the list. Now it is impossible as both are the same string.
In fact this is not a serious problem - but I am just asking :)
-
oh, i should probably add these:
STR_MIXED
and
STR_RIGHT_CLICK_TO_DELETE
i've added what google thinks is the correct translation, but i put about as much faith in google translate being correct as i do in prayer stopping the spread of aids in africa
-
+1 grzegorj
Actually Ukrainian language as well as Russian also have distinct words to denote the name of a thing and the name of a person. I'll provide PR to fix the issue later on.
-
In UFOpedia pages in the game, weapons on tanks are named with the same strings as the tanks themselves. It is not like in the original game, see the attachment. Hence my request to make a separate strings on tank weapons.
Namely, the weapon mounted on Tank/Cannon is called Armour piercing in the original game while Tank/Cannon in OXC.
The weapon on Tank/Rocket Launcher is called Rocket Launcher in the original game while Tank/Rocket Launcher in OXC.
Etc.
-
So, just to clarify, what new strings have been added in the last month?
-
So, just to clarify, what new strings have been added in the last month?
Nothing as far as I know, karvanit did some changes to the translation system (https://openxcom.org/forum/index.php/topic,791.0.html) but I think he kept everything synced, you'd have to check with him.
-
I have made some changes that enable translating complete some complete sentenses. Also changed some code to use count-depended code.
I have placed the strings last in the file, based on original language content (see commit 7433e2 (https://"https://github.com/SupSuper/OpenXcom/commit/7433e2b51e470338ece44fbf977874cf905b0e2f")).
The following now have a '{1}' marker where the actual craft name will appear:
STR_EQUIPMENT_FOR => STR_EQUIPMENT_FOR_craftname
STR_SELECT_SQUAD_FOR =>STR_SELECT_SQUAD_FOR_craftname
The following have many forms, based on the value of n: The suffix "_0" means the form will only be called if n is 0, the rest are language specific. All can handle a '{N}' marker that will be replaced with the actual value.
STR_n_UNITS_IN_EXIT_AREA
STR_n_UNITS_OUTSIDE_EXIT_AREA
There is also a STR_ABANDON_GAME_QUESTION, which only the Spanish translation should care about (because it needed to have the extra inverted '?' at the front).
-
Ok I've tracked down and compiled all the changes.
These strings need reviewing (see this thread for explanation (https://openxcom.org/forum/index.php/topic,791.0.html)):
STR_NOT_ENOUGH_ammotype_TO_ARM_HWP
STR_DAY
STR_EQUIPMENT_FOR_craftname
STR_SELECT_SQUAD_FOR_craftname
STR_n_UNITS_IN_EXIT_AREA
STR_n_UNITS_OUTSIDE_EXIT_AREA
These strings might be new or just need reviewing:
STR_RANDOM_BATTLE
STR_MIXED
STR_RIGHT_CLICK_TO_DELETE
STR_ABANDON_GAME_QUESTION
STR_ZOMBIE
STR_FLOATER_SOLDIER
STR_FLOATER_NAVIGATOR
STR_FLOATER_MEDIC
STR_FLOATER_ENGINEER
STR_FLOATER_LEADER
STR_FLOATER_COMMANDER
STR_SECTOID_SOLDIER
STR_SECTOID_NAVIGATOR
STR_SECTOID_MEDIC
STR_SECTOID_ENGINEER
STR_SECTOID_LEADER
STR_SECTOID_COMMANDER
STR_SNAKEMAN_SOLDIER
STR_SNAKEMAN_NAVIGATOR
STR_SNAKEMAN_ENGINEER
STR_SNAKEMAN_LEADER
STR_SNAKEMAN_COMMANDER
STR_MUTON_SOLDIER
STR_MUTON_NAVIGATOR
STR_MUTON_ENGINEER
STR_ETHEREAL_SOLDIER
STR_ETHEREAL_LEADER
STR_ETHEREAL_COMMANDER
STR_CYBERDISC_TERRORIST
STR_REAPER_TERRORIST
STR_CHRYSSALID_TERRORIST
STR_CELATID_TERRORIST
STR_SILACOID_TERRORIST
STR_SECTOPOD_TERRORIST
These strings are definitely new and need to be translated:
STR_HAS_BEEN_KILLED
STR_DRAG_SCROLL
STR_HIT_MELEE
STR_CONTROLS
STR_RESTORE_DEFAULTS
STR_GENERAL
STR_GEOSCAPE
STR_BATTLESCAPE
STR_SCREENSHOT
STR_FPS_COUNTER
STR_ROTATE_LEFT
STR_ROTATE_RIGHT
STR_ROTATE_UP
STR_ROTATE_DOWN
STR_ZOOM_IN
STR_ZOOM_OUT
STR_TOGGLE_COUNTRY_DETAIL
STR_TOGGLE_RADAR_RANGES
STR_SCROLL_LEFT
STR_SCROLL_RIGHT
STR_SCROLL_UP
STR_SCROLL_DOWN
STR_VIEW_LEVEL_ABOVE
STR_VIEW_LEVEL_BELOW
STR_CENTER_SELECTED_UNIT
STR_PREVIOUS_UNIT
STR_NEXT_UNIT
STR_DESELECT_UNIT
STR_INVENTORY
STR_MINIMAP
STR_END_TURN
STR_ABORT_MISSION
STR_UNIT_STATS
STR_KNEEL
STR_RELOAD
STR_TOGGLE_PERSONAL_LIGHTING
STR_DONT_RESERVE_TUS
STR_RESERVE_TUS_FOR_SNAP_SHOT
STR_RESERVE_TUS_FOR_AIMED_SHOT
STR_RESERVE_TUS_FOR_AUTO_SHOT
STR_CENTER_ON_ENEMY_1
STR_CENTER_ON_ENEMY_2
STR_CENTER_ON_ENEMY_3
STR_CENTER_ON_ENEMY_4
STR_CENTER_ON_ENEMY_5
STR_CENTER_ON_ENEMY_6
STR_CENTER_ON_ENEMY_7
STR_CENTER_ON_ENEMY_8
STR_CENTER_ON_ENEMY_9
It's not as scary as it looks. :P As usual, grab the latest language files from Git (https://github.com/SupSuper/OpenXcom/tree/master/bin/data/Language) and update them accordingly.
-
Excellent work, SupSuper.
I'll get around to checking them over the next few days.
-
Now, with the feature freeze happening, has there been any new strings?
-
added three more
STR_GROUNDED
used to describe UFOs/Craft that are on the ground on the geoscape, seperate from items on the ground in battlescape.
STR_LIVING_QUARTERS_PLURAL
used in the base information screen to describe how many of that facility type you have operational.
STR_ENEMY_WEAPON_LEVEL
used in the "new battle" menu to describe what level of equipment the enemy will have (pistols, rifles or heavy plasma)
-
STR_LIVING_QUARTERS_PLURAL
used in the base information screen to describe how many of that facility type you have operational.
This should use the translation's ability to provide different forms (like the STR_DAY_* strings), so we can use the proper forms from different languages.
I'll look into it.
-
This should use the translation's ability to provide different forms (like the STR_DAY_* strings), so we can use the proper forms from different languages.
I'll look into it.
They're two strings used in different places, not a pluralization.
-
They're two strings used in different places, not a pluralization.
Yes, but we should still use the translation's support, because different languages have more than one plural form, depending on the actual number referenced.
-
Yes, but we should still use the translation's support, because different languages have more than one plural form, depending on the actual number referenced.
It's for the base stats menu. Hangar has "Hangars". General Stores have "Stores". We needed one for "living quarters" because in some languages, the best term for the building might be singular, yet we still need a plural or generally differing term to apply in the base stats menu. In my case (portuguese) I translated living quarters as "Bloco Habitacional" (which is singular) but translated this new base stats screen living quarters as "Habitações" (which is plural). Other languages could also use an equally plural term but require a completely different word. This is why we needed a new string here.
Karvanit, whenever you have the time, please show up on IRC. There are a few new strings which I feel they also must be added regardless of pluralization rules.
-
STR_LIST_ITEM
Articulo (https://plus.google.com/photos/100410619030173574921/albums/5865396048243702097/5865398570964301730?partnerid=gplp0)
-
sorry guys.
STR_ADVANCED
STR_ADVANCED_OPTIONS
STR_AGGRESSIVERETALIATION
STR_AGGRESSIVERETALIATION_DESC
STR_ALIENCONTAINMENTHASUPPERLIMIT
STR_ALIENCONTAINMENTHASUPPERLIMIT_DESC
STR_CANSELLLIVEALIENS
STR_CANSELLLIVEALIENS_DESC
STR_ALLOWAUTOSELLPRODUCTION
STR_ALLOWAUTOSELLPRODUCTION_DESC
STR_ALLOWBUILDINGQUEUE
STR_ALLOWBUILDINGQUEUE_DESC
STR_BATTLEAUTOEND
STR_BATTLEAUTOEND_DESC
STR_BATTLEINSTANTGRENADE
STR_BATTLEINSTANTGRENADE_DESC
STR_BATTLENOTIFYDEATH
STR_BATTLENOTIFYDEATH_DESC
STR_BATTLEPREVIEWPATH
STR_BATTLEPREVIEWPATH_DESC
STR_BATTLERANGEBASEDACCURACY
STR_BATTLERANGEBASEDACCURACY_DESC
STR_CANMANUFACTUREMOREITEMSPERHOUR
STR_CANMANUFACTUREMOREITEMSPERHOUR_DESC
STR_CANTRANSFERCRAFTSINAIRBORNE
STR_CANTRANSFERCRAFTSINAIRBORNE_DESC
STR_CRAFTLAUNCHALWAYS
STR_CRAFTLAUNCHALWAYS_DESC
STR_CUSTOMINITIALBASE
STR_CUSTOMINITIALBASE_DESC
STR_GLOBESEASONS
STR_GLOBESEASONS_DESC
STR_PLAYINTRO
STR_PLAYINTRO_DESC
STR_SHOWFUNDSONGEOSCAPE
STR_SHOWFUNDSONGEOSCAPE_DESC
STR_SHOWMORESTATSININVENTORYVIEW
STR_SHOWMORESTATSININVENTORYVIEW_DESC
STR_SNEAKYAI
STR_SNEAKYAI_DESC
STR_STRAFE
STR_STRAFE_DESC
STR_BATTLESCROLLDRAGINVERT
STR_BATTLESCROLLDRAGINVERT_DESC
STR_BATTLEEXPLOSIONHEIGHT
STR_BATTLEEXPLOSIONHEIGHT_DESC
-
Well since warboy broke the camel's back I might as well add a tiny little thing. :P
STR_DISPLAY_FILTER
Also I have reviewed the Advanced Options english text based on user feedback, check if it affects your translations.
-
STR_ALLOWPSIONICCAPTURE
STR_ALLOWPSIONICCAPTURE_DESC
i won't be adding any more.
-
New strings to accommodate translators. They have already been added to every language file but might need reviewing:
STR_HAS_GONE_BERSERK_MALE
STR_HAS_GONE_BERSERK_FEMALE
STR_HAS_PANICKED_MALE
STR_HAS_PANICKED_FEMALE
STR_HAS_BECOME_UNCONSCIOUS_MALE
STR_HAS_BECOME_UNCONSCIOUS_FEMALE
STR_HAS_DIED_FROM_A_FATAL_WOUND_MALE
STR_HAS_DIED_FROM_A_FATAL_WOUND_FEMALE
STR_HAS_BEEN_KILLED_MALE
STR_HAS_BEEN_KILLED_FEMALE
STR_DELETE_UNSUCCESSFUL
-
Hythlodaeus brought up a good point on IRC: Would now be a good time to issue a formal request for some TFTD translations?
-
I'd have to convert them to the proper format first. :P
-
and i thought i was done with this thing!!!
-
STR_NOT_ENOUGH_SPACE
STR_WEAPONSELFDESTRUCTION
STR_WEAPONSELFDESTRUCTION_DESC
STR_ARROWS
STR_FULL
-
Probably all new strings (not reported yet).
STR_RESEARCHEDITEMSWILLSPENT
STR_RESEARCHEDITEMSWILLSPENT_DESC
STR_ALIENCONTAINMENTLIMITENFORCED
STR_ALIENCONTAINMENTLIMITENFORCED_DESC
STR_SACK
STR_CANCEL_PROJECT
STR_TIME_UNITS_RESERVED_FOR_KNEELING
STR_TUS_RESERVED_FOR_KNEELING_AND_FIRING
STR_RESERVE_TUS_FOR_KNEEL
STR_EXPEND_ALL_TIME_UNITS
STR_CENTER_ON_ENEMY_10
STR_ANYTIMEPSITRAINING
STR_ANYTIMEPSITRAINING_DESC
STR_QUICK_SAVE
STR_QUICK_LOAD
STR_AUTOSAVE
STR_AUTOSAVE_DESC
STR_SAVE_VOXEL_VIEW
STR_BATTLENEWPREVIEWPATH
STR_BATTLENEWPREVIEWPATH_DESC
STR_ABORT_MISSION_QUESTION
STR_WEAPONSELFDESTRUCTION
-
Added/revised strings:
STR_UNIT_LEVEL_ABOVE
STR_UNIT_LEVEL_BELOW
STR_PREVIOUS_UNIT
STR_NEXT_UNIT
STR_DESELECT_UNIT
STR_MULTI_LEVEL_VIEW
-
At this point I think we should insert 3 new text strings for the following events:
"The construction of X at Y has been completed" -> specifically for when notifying the player when the construction of a base installation is done. Currently the game uses "The production of" for both items and installations, which can lead to some translation problems. Having a separate string for constructions would look better and would be more explicit for first time players.
"Equip Soldiers" -> the new feature that allows equipping soldiers in the base menu is currently accessed by a button named "Inventory", after the battlescape button of the same name, which I feel it isn't explicit enough. It would perhaps be better to have a separate string for it, something like "Equip Soldiers".
"Explosive Primed for X turns" -> a new feature displays an alarm message, every time a grenade is primed. This message is using the "Grenade is already primed!" text which is originally used whenever the player attempts to move a primed grenade in the soldier inventory screen. Because the "already" doesn't fit in this context, and because there are other explosives aside from grenades in the game (namely the High Explosive), I propose the addition of a new string for this event's message, which also indicates the amount of turns selected on the timer. Something like "Explosive Primed for X turns" would do good.
-
just came across "STR_COMMITTED", which was translated rather weirdly in the german localization strings as "einsatzfreudig" (which literally/approximately translates as "enthusiastic for missions"), and now I was trying to find out what it is being used for. I couldn't find the string name within the github master branch outside of the language files, though, so now I was wondering: a) is it used at all? and b) what was it supposed to be?
-
just came across "STR_COMMITTED", which was translated rather weirdly in the german localization strings as "einsatzfreudig" (which literally/approximately translates as "enthusiastic for missions"), and now I was trying to find out what it is being used for. I couldn't find the string name within the github master branch outside of the language files, though, so now I was wondering: a) is it used at all? and b) what was it supposed to be?
Doesn't seem to be used in the original. If I had to guess, it was some kind of relations indicator:
STR_HOSTILE: "HOSTILE"
STR_NEUTRAL: "NEUTRAL"
STR_FRIENDLY: "FRIENDLY"
STR_COMMITTED: "COMMITTED"
-
so "committed" as in "committed to the cause"? on the same line as "loyal" or "allied"? or do I get that wrong?
-
I think you're correct.
-
you know what, I thought of this a little more, and I believe that this is a remnant of the complex diplomatic system that was planned initially, then scrapped (for lack of time and money) and then much later used for apoc.
My best guess is that these strings
STR_HOSTILE: "HOSTILE"
STR_NEUTRAL: "NEUTRAL"
STR_FRIENDLY: "FRIENDLY"
STR_COMMITTED: "COMMITTED"
were used to describe the diplomatic state of the funding nations, depending on their level of pissed-off-ness ;), with the last of them meaning that the nation had signed a pact with the aliens. Do you think that's possible? In that case, I will translate it as "paktiert" for the german version, because I think these strings might be used by people in the near future. (people that create a total conversion involving more lateral diplomatics, like wars for example... :)
-
STR_MAXFRAMESKIP
STR_MAXFRAMESKIP_DESC
should be pretty self-explanatory.
they go in advanced options.
-
I don't think it's necessary to keep posting updates here since GetLocalization does that, unless you got a pretty good explanation I guess. :P
-
With the last few nightlies, some strings have vanished from localization files. Modifications to other strings on GetLoc seem to be synced OK.
These are the gremlins (from tr-TR.ylm):
STR_DATE_UC
STR_MAXFRAMESKIP
STR_MAXFRAMESKIP_DESC
STR_MEMORIAL
STR_PSISTRENGTHEVAL
STR_PSISTRENGTHEVAL_DESC
STR_RESET
STR_SOLDIERS_LOST
STR_SOLDIERS_RECRUITED
There is also a mismatch in STR_DAY entries:
en-US.yml:
STR_DAY:
one: "{N} day"
few: "{N} days"
many: "{N} days"
other: "{N} days"
tr-TR.yml:
STR_DAY:
1: "{N} gün"
2: "{N} gün"
Edit: A similar mismatch is also present with the following entries:
STR_UNITS_IN_EXIT_AREA:
zero: "No Units in Exit Area"
one: "{N} Unit in Exit Area"
few: "{N} Units in Exit Area"
many: "{N} Units in Exit Area"
other: "{N} Units in Exit Area"
STR_UNITS_OUTSIDE_EXIT_AREA:
zero: "No Units outside Exit Area"
one: "{N} Unit outside Exit Area"
few: "{N} Units outside Exit Area"
many: "{N} Units outside Exit Area"
other: "{N} Units outside Exit Area"
-
Ok clearly I can't just wait for GetLoc or you guys will swarm me with reports. :P I've manually reuploaded the file so it should be all sorted now. Hopefully GetLoc can still find the bug, seems to be related to importing from GitHub.
-
Apologies. I did not mean to pester ;D
Actually, some of those new strings were already in nightly 2013_10_27_2053. When they up and disappeared, I thought there was some problem in downloading from (as opposed to uploading to) GetLoc, because they were still visible on the web site, intact with their translations.
I figured it was probably something trivial and certainly would be fixed sooner rather than later -- I just wanted to save you the trouble of hunting them all down, if it would help any.
So, the sync with GetLoc is still a manual process? In that case, I'll keep my trap shut and be patient next time. :-[
-
Don't worry about it. Normally GetLoc automatically imports updates from GitHub fine, but when it doesn't I just have to go in there and import the file myself, so it's good to be warned about this as I don't check the site much.
I was just leaving the bug open in case GetLoc needed to check it out, but they haven't gotten back to me yet so.
-
I have a question about "STR_INCREASE_UC". is that used in the stat screen to mark the improvement of the stats?
-
I have a question about "STR_INCREASE_UC". is that used in the stat screen to mark the improvement of the stats?
It is used in the manufacture screen. There are two pairs of arrow buttons, used to increase and decrease the amounts of assigned engineers and total units to be manufactured.
-
Ah, thanks. that clears it up :)