OpenXcom Forum
Contributions => Translations => Topic started by: SupSuper on September 25, 2013, 04:55:44 pm
-
From now on all translation work should be done at: https://www.getlocalization.com/openxcom/ (https://www.getlocalization.com/openxcom/)
This gets rid of a lot of old problems and annoyances such as:
- Keeps track of translated/needs revising/untranslated string status, no more wondering about translation progress.
- Allows cooperative translating, no more sharing files back and forth to work with multiple people, and incomplete translations being forever abandoned.
- Automatically informs translators of new/changed strings, no more looking through posts for new strings and losing track of stuff.
- All translations are synced with the master file, no more translations breaking with updates.
- Handles all file format wizardry for you, translators can just focus on translating.
I've imported all our current translations, so please try it out and let me know what you think! Keep an eye out for any bugs or missing info. Note that since we didn't keep track of "untranslated strings", any string matching the English version was removed, which is why none of the languages are at 100%. Just revise as appropriate.
If you have a translation not on the site, please post it here so I can import it, it doesn't matter how old or crappy or incomplete it is. If it's on the website everyone can work and improve on it, instead of being left to rot.
You can get the latest version of the translations on GetLocalization here: https://openxcom.org/translations/latest.zip
-
I tried it out and it's looking pretty good. Although there is a problem regarding the strings: STR_ST, STR_ND, STR_RD, STR_TH - these are not needed for my language (romanian), but empty strings are not allowed.
P.S. it seems to work if I just put one space, so it's ok
-
How to add new strings?
For example: I wrote new feature. I sent pull request of this new feature. New feature required several new strings. I don't know when will merging with upstream/master. Perhaps, merging will never be. How to add new strings in this case?
-
I tried it out and it's looking pretty good. Although there is a problem regarding the strings: STR_ST, STR_ND, STR_RD, STR_TH - these are not needed for my language (romanian), but empty strings are not allowed.
P.S. it seems to work if I just put one space, so it's ok
I'll let them know. Those strings probably need to be revised anyways because of different date formats.
How to add new strings?
For example: I wrote new feature. I sent pull request of this new feature. New feature required several new strings. I don't know when will merging with upstream/master. Perhaps, merging will never be. How to add new strings in this case?
You have to add any new strings to "en-US.yml" like before. GetLocalization will automatically get the changes from GitHub and sync it to the other translation files.
If your stuff never gets merged you will just have to manage the files manually like before.
-
Hi SupSuper,
thank you for this big improvement for the translator's life! The new platform is fantastic in comparison and as such :)
But there's one thing not clear to me: how can I obtain my recent changes back in order to test them? Is there any way to fetch latest version of the translation, or maybe there are periodic auto-merges and I need to wait for one to occur?
-
Use the latest git build? I know, it's a bit cumbersome...
-
Use the latest git build? I know, it's a bit cumbersome...
Upstream branch (master) currently doesn't contain my changes from GetLocalization. Thus there was no auto-merging of localization files, at least for last 8 hours (measured between my edits on GetLocalization site and now).
So I still wonder how can I get my latest changes in a form of yaml file? I don't like such a time gap between the actual changes made and the possibility to test them in-game :'(
-
There's a Files tab on the website, can you access it? It might be developer-only. :(
There's also an API, see if this works for you:
https://api.getlocalization.com/openxcom/api/translations/file/bin/data/Language/en-US.yml/[language-code]/ (put the appropriate language code there)
If not I'll just try to integrate the translations into Git regularly. I imagine it can't be done automatically because constantly generating translation files would hammer their site. :P
-
There's a Files tab on the website, can you access it? It might be developer-only. :(
Unfortunately the Files tab seems to be dev-only, because I can't see it. Provided API link doesn't work either, since they describe (https://www.getlocalization.com/library/api/get-localization-file-management-api/) it as "meant for developers".
I hope you'll find some time to setup a scheduler to perform periodic (say, once per hour) fetches'n'merges of localizations to make translators happy :)
-
I imagine it can't be done automatically because constantly generating translation files would hammer their site. :P
A cron that runs a bash script every 3-4-5-6 hours? It's easily adjustable, and besides, you can ask a support question to Github regarding this.
-
but that would also spam our git build page (https://openxcom.org/index.php/git-builds/), wouldn't it?
-
It would be a "Translation update" commit... how about one every six hours?
-
I'd prefer some lower value, like 1-3 hours, since "translation commit" shouldn't trigger auto-build anyway. But virtually any frequency would be good, should it is run automatically, by scheduler 8)
-
Launchpad (https://launchpad.net) has an automatic translation-to-version-control feature, and the standard frequency there is "once per day, if there have been any changes since the last time".
Of course, Launchpad's translation feature allows translators to download translation files, though there's a queue (you ask for translations, then wait for a notification e-mail to get a link to the file, which expires in X hours). Perhaps this is something that can be suggested to the developers of getlocalization.com?
-
I have a question regarding the strings that start/end with a space.
It seems that spaces are ignored when the original translation (english) is copied to the editor. The ones allready translated have the spaces at the begining/end.
That can confuse those starting a translation from scratch.
-
I'll have a talk with the GetLocalization guys, see what they think, since so far they've been real helpful. I don't fancy keeping translations in the codebase since it gives the illusion that they're up-to-date and might get manually edited. But given the regularity of your work, I don't think mixing it with Git updates or waiting for manual updates is gonna cut it either. Maybe some kind of cron tied to their API.
I have a question regarding the strings that start/end with a space.
It seems that spaces are ignored when the original translation (english) is copied to the editor. The ones allready translated have the spaces at the begining/end.
That can confuse those starting a translation from scratch.
This will probably be cleaned up once all "sentence strings" are combined to get rid of trailing whitespace, since this was already a problem when people were manually editing files and easily missed important spacing.
-
Looks good, but I not fully understand workflow of translation. Is there something like a Translation Manager or Reviewer role for translation team, that will approve translation variants?
-
Hey everyone,
i like the idea, but from a first glance at the website is not too intuitive. In any case i hope i get used to it fast :) and i hope this makes thigs easier. Also i see that you are using only one Spanish translation.
-
Looks good, but I not fully understand workflow of translation. Is there something like a Translation Manager or Reviewer role for translation team, that will approve translation variants?
Well normally the way public translation software works is people can submit and vote on translations. Since there can be multiple translations for a string, votes help decide which one people prefer. Then some appointed moderator approves them and they get rolled out to the software.
That's a premium feature in GetLocalization though :P so it seems everyone gets to submit and vote and the software figures it out based on the votes, so I guess I have to trust you guys to not go mad with power. That's the developers' job. ;)
Hey everyone,
i like the idea, but from a first glance at the website is not too intuitive. In any case i hope i get used to it fast :) and i hope this makes thigs easier. Also i see that you are using only one Spanish translation.
No they are both in there. :) If you have problems/suggestions try using the Feedback link as they seem pretty receptive to that sort of stuff.
-
In the meantime I just put all the latest translations in Git.
-
unexpected changes: https://github.com/SupSuper/OpenXcom/commit/658a3c44a4f571854ce52af12111f4114ce2a940
- STR_DAY:
- 1: "{N} dzień"
- 2: "{N} dni"
- 3: "{N} dni"
+ STR_DAY:
+ 1: "{N} dzień"
+ 2: "{N} dni"
- STR_UNITS_IN_EXIT_AREA:
- 0: "Brak jednostek na terenie ewakuacji"
- 1: "{N} jednostka na terenie ewakuacji"
- 2: "{N} jednostki na terenie ewakuacji"
- 3: "{N} jednostek na terenie ewakuacji"
- STR_UNITS_OUTSIDE_EXIT_AREA:
- 0: "Brak jednostek poza terenem ewakuacji"
- 1: "{N} jednostka poza terenem ewakuacji"
- 2: "{N} jednostki poza terenem ewakuacji"
- 3: "{N} jednostek poza terenem ewakuacji"
+ STR_UNITS_IN_EXIT_AREA:
+ 0: "Brak jednostek na terenie ewakuacji"
+ 1: "{N} jednostka na terenie ewakuacji"
+ 2: "{N} jednostki na terenie ewakuacji"
+ STR_UNITS_OUTSIDE_EXIT_AREA:
+ 0: "Brak jednostek poza terenem ewakuacji"
+ 1: "{N} jednostka poza terenem ewakuacji"
+ 2: "{N} jednostki poza terenem ewakuacji"
-
Hmmm I guess we'll have to wait until they add proper pluralization support or come up with some dodgy workaround. :-\
-
add a empty string to en-US.yml ? If it can act.
STR_UNITS_IN_EXIT_AREA:
0: "No Units in Exit Area"
1: "{N} Unit in Exit Area"
2: "{N} Units in Exit Area"
3: ""
STR_UNITS_OUTSIDE_EXIT_AREA:
0: "No Units outside Exit Area"
1: "{N} Unit outside Exit Area"
2: "{N} Units outside Exit Area"
3: ""
etc.
-
A filter to show strings that have two or more translations whould be great. That way it should be easy to spot translations that are debated, and people could vote for the best. For example, right now there are two (https://www.getlocalization.com/openxcom/editor/15107/#3593114) translations (https://www.getlocalization.com/openxcom/editor/15107/#3594262) that, although are better, they ranked as 2nd.
I admit, this happend due to inertia on my part, when voting for strings (I voted first for the original translation, then proposed a new translation and voted it) - maybe a botton for canceling my vote would be good too.
As a side note, what are the attributes after which the list is sorted? Right now it seems to be completely random. That makes it somehow difficult to determine where exactly the string is used. It was easier before, when consecutive strings where somewhat related.
I will try find some time to identify where are the strings used, and maybe make a page on the wiki.
-
Just sent out a big update that fixes most problems translators have been having with the strings, so be sure to review all changed strings so they work correctly in-game.
Pluralization fixes will come later.
-
I'm not sure if this was asked before, but how about gender support? Take this line for example:
{0}{NEWLINE}has become unconscious
This works well in English, but in Romanian the translation is a bit different, depending on if the unit/soldier in question is a male or female
Note:
There is a workaround, that works by modifying the translation a bit, something along these lines:
The soldier{NEWLINE}{0}{NEWLINE}has become unconscious
This way, the subject is changed, and the line remains the same regardless if there is a male or female involved. This raises the question about handling alien units under your control though...
-
im on my way to completet the german translation on getlocalization.com :)
-
I'm not sure if this was asked before, but how about gender support? Take this line for example:
This works well in English, but in Romanian the translation is a bit different, depending on if the unit/soldier in question is a male or female
Note:
There is a workaround, that works by modifying the translation a bit, something along these lines:
This way, the subject is changed, and the line remains the same regardless if there is a male or female involved. This raises the question about handling alien units under your control though...
There already is gender support. ;) Look for the strings with _MALE and _FEMALE (they will look the same in English).
-
Hey there. My first post ever, so, again, Hey there!
I took the liberty of adding another language at the GetLoc site. Is there any way to export the language files so that we could test the translations locally? Nevermind, they are sync'ed with the Git now. Thanks.
-
There already is gender support. ;) Look for the strings with _MALE and _FEMALE (they will look the same in English).
Oh, my bad. I will.
Question: How do I search for a certain "key" on GL?
-
It seems that in the UFOpedia description there are two white spaces after each dot. At least in the Live/Alien Autopsy & XCom Craft Weapons descriptions.
-
just started looking into GetLocalization and trying to improve the German translation... is there an easy way to find in which context the strings are used? Probably not, eh? I guess the "easiest" way is to search for the string in github...
-
I'm actually working on that, finished with ~half of the strings.
First, I started taking screenshots of the various screens and noting the strings used in each, but that is too time consuming, so I took the english language file in excel and put notes beside each string on where it is used.
I'll post it when it's done.
-
I'm actually working on that, finished with ~half of the strings.
First, I started taking screenshots of the various screens and noting the strings used in each, but that is too time consuming, so I took the english language file in excel and put notes beside each string on where it is used.
I'll post it when it's done.
way cool! wait... didn't SupSuper say that he has screenshots of every screen? maybe those two reference systems could be combined?
on another note: I think the "STR_GENERAL_STORES_UFOPEDIA" needs to be updated throughout localizations. it says "All equipment, weapons systems, munitions, recovered material and Heavy Weapons Platforms are placed in stores, with the exception of equipment assigned to craft in hangars.", but AFAIR the craft-assigned equipment actually does count into base storage space now that the 80-item-limit has been removed.
So now it should probably be "All equipment, weapons systems, munitions, recovered material and Heavy Weapons Platforms are placed in stores, including reserved space for equipment assigned to craft in hangars." 8)
-
Here's all the screenshots I've used to make OpenXcom, they're from the vanilla game so a lot might have changed, but they should at least save you some trouble.
-
Thanks, i'll think at how to present all this info. Probably in html.
-
SupSuper, is it possible for me to propose more than one translation for a string? sometimes I'm kinda torn between two possible translation and would like to propose both, so others can vote on them. but every time I try to add another translation, it overwrites my previous one instead.
-
A filter to show strings that have two or more translations whould be great. That way it should be easy to spot translations that are debated, and people could vote for the best. For example, right now there are two (https://www.getlocalization.com/openxcom/editor/15107/#3593114) translations (https://www.getlocalization.com/openxcom/editor/15107/#3594262) that, although are better, they ranked as 2nd.
I admit, this happend due to inertia on my part, when voting for strings (I voted first for the original translation, then proposed a new translation and voted it) - maybe a botton for canceling my vote would be good too.
As a side note, what are the attributes after which the list is sorted? Right now it seems to be completely random. That makes it somehow difficult to determine where exactly the string is used. It was easier before, when consecutive strings where somewhat related.
Sadly GetLocalization seems to scrap the original file order. :( When in doubt you can always dig out the Language files.
The sorting setting seems to be controlled by the "filter" option at the top. "Sorted by Quality" (however that's measured) seems to list strings with multiple translations first, so you can try that. There's also filters for strings you've voted on or not.
Oh, my bad. I will.
Question: How do I search for a certain "key" on GL?
You can't seem to search by key as a translator, though you can see it in the Context.
way cool! wait... didn't SupSuper say that he has screenshots of every screen? maybe those two reference systems could be combined?
on another note: I think the "STR_GENERAL_STORES_UFOPEDIA" needs to be updated throughout localizations. it says "All equipment, weapons systems, munitions, recovered material and Heavy Weapons Platforms are placed in stores, with the exception of equipment assigned to craft in hangars.", but AFAIR the craft-assigned equipment actually does count into base storage space now that the 80-item-limit has been removed.
So now it should probably be "All equipment, weapons systems, munitions, recovered material and Heavy Weapons Platforms are placed in stores, including reserved space for equipment assigned to craft in hangars." 8)
Nice catch, it's fixed now. Let me know if there are any other major inaccuracies in the game text, as I remember the original had a few which confused players.
SupSuper, is it possible for me to propose more than one translation for a string? sometimes I'm kinda torn between two possible translation and would like to propose both, so others can vote on them. but every time I try to add another translation, it overwrites my previous one instead.
I'll have a look.
-
Changes in the file en-US (string ID or string Desc) = all translations this string is deleted and there is no sign on it (it is impossible to check - getlocalization.com - the previous version of the translation). Comments can not be recovered. The new proposals - are also lost.
Only view the Git history, efficiently helps and allows fix it (translate again).
This probably causes some complete-translations becomes a incomplete.
-
Yeah, been through that and looked at the git hub history. This will probably be a "one time only" thing - due to the transition from sentence composed of multiple strings to single string containing whole sentence.
-
Thanks, i'll think at how to present all this info. Probably in html.
If you want, GetLocalization lets you attach screenshots and text to a string's context. Though a html page might still be nice for an overview.
unexpected changes: https://github.com/SupSuper/OpenXcom/commit/658a3c44a4f571854ce52af12111f4114ce2a940
Ok I've updated the pluralization system now and added blank strings to English so hopefully they should reach every language now. I made it follow the Unicode standard (https://unicode.org/repos/cldr-tmp/trunk/diff/supplemental/language_plural_rules.html), where "_zero", "_one", "_few", "_many" and "_other" define the plural strings.
Just leave strings that don't apply to your language blank or a space or whatever, as they won't be used anyways.
-
Empty strings "_few" and "_many" in en-US is not visible for translators (getloc.com).
Name them (desc.) "<few>" and "<many>", or something.
-
Empty strings "_few" and "_many" in en-US is not visible for translators (getloc.com).
Name them (desc.) "<few>" and "<many>", or something.
Ok I just copy-pasted the plural strings so translators won't miss what the original string is.
-
How about something like this: strings.html
Edit: Updated the string list in this thread: https://openxcom.org/forum/index.php/topic,1561.msg15054.html#msg15054
-
nice string list... maybe we could just put it onto a wiki page? that way it would be nicely available and the screenshots could be added by everybody... collaboratively. :)
-
Where do we report string errors/bugs? The bug tracker?
A missing string: the ruleset specifies STR_ARMOR_PIERCING as the weapon of the basic Tank/Cannon, but it's not in the translation templates. It's displayed on the UFOpedia page, though.
-
Where do we report string errors/bugs? The bug tracker?
A missing string: the ruleset specifies STR_ARMOR_PIERCING as the weapon of the basic Tank/Cannon, but it's not in the translation templates. It's displayed on the UFOpedia page, though.
Normally the bug tracker, but I've fixed it now.
Anyways with the help of _michal, you can now get the latest translations here (https://openxcom.org/translations/latest.zip). :) They are automatically updated from GetLocalization on an hourly basis, so just extract it to your Data\Language whenever you wanna test your changes. They're also included in the nightly builds.
-
.ZIP 17-10-2013 15:00
bin/data/Language/pl-PL.yml (compare locally)
@@ -80,14 +80,12 @@ pl-PL:
STR_BUILD_NEW_BASE: "Buduj nową bazę"
STR_CANCEL: "Anuluj"
STR_COST_UC: "KOSZT>"
STR_CONSTRUCTION_TIME_UC: "CZAS BUDOWY>"
STR_DAY:
- one: "{N} dzień"
- few: "{N} dni"
- many: "{N} dni"
- other: "{N} dnia"
+ 1: "{N} dzień"
+ 2: "{N} dni"
STR_MAINTENANCE_UC: "UTRZYMANIE>"
STR_OK: "OK"
STR_INSTALLATION: "Instalacje"
STR_CURRENT_RESEARCH: "AKTUALNE BADANIA"
STR_SCIENTISTS_AVAILABLE: "Naukowców dostępnych>{ALT}{0}"
@@ -179,12 +177,12 @@ pl-PL:
STR_FINANCE: "Finanse"
STR_ST: "{0}."
STR_ND: "{0}."
STR_RD: "{0}."
STR_TH: "{0}."
- STR_NOT_ENOUGH_SPECIAL_MATERIALS_TO_PRODUCE_ITEM_AT_BASE: "Brakuje specjalnych materiałów by wyprodukować{NEWLINE}{0}{NEWLINE}w bazie{NEWLINE}{1}"
- STR_NOT_ENOUGH_MONEY_TO_PRODUCE_ITEM_AT_BASE: "Brakuje pieniedzy by wyprodukować{NEWLINE}{0}{NEWLINE}w bazie{NEWLINE}{1}"
+ STR_NOT_ENOUGH_SPECIAL_MATERIALS_TO_PRODUCE_ITEM: "Niewystarczająca ilość materiałów specjalnych, by produkować:{NEWLINE}{0}"
+ STR_NOT_ENOUGH_MONEY_TO_PRODUCE_ITEM: "Za mało pieniędzy, by produkować:{NEWLINE}{0}"
STR_PRODUCTION_OF_ITEM_AT_BASE_IS_COMPLETE: "Produkcja{NEWLINE}{0}{NEWLINE}w bazie{NEWLINE}{1}{NEWLINE}zakończona"
STR_CONSTRUCTION_OF_FACILITY_AT_BASE_IS_COMPLETE: "Budowa{NEWLINE}{0}{NEWLINE}w bazie{NEWLINE}{1}{NEWLINE}zakończona"
STR_OK_5_SECS: "OK - CZAS: 5 s"
STR_RESEARCH_COMPLETED: "Badania zakończone"
STR_VIEW_REPORTS: "ZOBACZ RAPORT"
@@ -267,12 +265,12 @@ pl-PL:
STR_READY: "GOTOWY"
STR_OUT: "WYSŁANY"
STR_REPAIRS: "NAPRAWIANY"
STR_REFUELLING: "TANKOWANY"
STR_REARMING: "UZBRAJANY"
- STR_TARGET: "CEL: {0}"
- STR_WAY_POINT: "PUNKT ORIENTACYJNY"
+ STR_TARGET: "CEL: "
+ STR_TARGET_WAY_POINT: "PUNKT KONTROLNY"
STR_ARE_YOU_SURE_CYDONIA: "Jesteś pewien, że chcesz wysłać ten samolot na misję do Cydonii?"
STR_YES: "TAK"
STR_NO: "NIE"
STR_SELECT_DESTINATION: "WYBIERZ CEL"
STR_CYDONIA: "CYDONIA"
@@ -286,13 +284,12 @@ pl-PL:
STR_PATROLLING: "PATROLUJE"
STR_TAILING_UFO: "ŚLEDZI UFO"
STR_INTERCEPTING_UFO: "PRZECHWYTUJE UFO-{0}"
STR_RETURNING_TO_BASE: "WRACA DO BAZY"
STR_DESTINATION_UC_: "CEL: {0}"
- STR_BASE_UC: "BASE>{ALT}{0}"
STR_SPEED_: "PRĘDKOŚĆ>{ALT}{0}"
- STR_MAXIMUM_SPEED_UC: "PRĘDKOŚĆ MAKSYMALNA>{ALT}{0}{ALT}"
+ STR_MAXIMUM_SPEED_UC: "PRĘDKOŚĆ MAKSYMALNA>{ALT}{0}"
STR_ALTITUDE_: "PUŁAP>{ALT}{0}"
STR_VERY_LOW: "BARDZO NISKO"
STR_LOW_UC: "NISKO"
STR_HIGH_UC: "WYSOKO"
STR_VERY_HIGH: "BARDZO WYSOKO"
@@ -307,11 +304,11 @@ pl-PL:
STR_COMMITTED: "LOJALNY"
STR_GAME_OPTIONS: "OPCJE GRY"
STR_LOAD_GAME: "ZAŁADUJ GRĘ"
STR_SAVE_GAME: "ZAPISZ GRĘ"
STR_INTERCEPTION_CRAFT: "SAMOLOTY"
- STR_BASE_: "Baza>{0}"
+ STR_BASE_: "Baza>"
STR_NAME_UC: "NAZWA"
STR_AMMO_: "AMUNICJA>{ALT}{0}"
STR_CREW: "ZAŁOGA"
STR_EQUIPMENT_UC: "SPRZĘT"
STR_ARMOR: "PANCERZ"
@@ -629,11 +626,11 @@ pl-PL:
STR_LABORATORY_UFOPEDIA: "W bloku laboratoriów może pracować do 50 naukowców. Laboratoria są wyposażone w najnowszą aparaturę do badań materiałowych, biochemicznych i kosmologicznych. Zapewniony jest też ułatwiony dostęp do najlepszych laboratoriów naukowych na całym świecie, włącznie z instytutami wojskowymi."
STR_WORKSHOP_UFOPEDIA: "Warsztaty posiadają całe potrzebne wyposażenie służące do produkcji sprzętu zaprojektowanego lub przebadanego{NEWLINE}w laboratoriach naukowych. W warsztatach może pracować do 50 inżynierów, ale konstruowane przedmioty również wymagają trochę miejsca."
STR_SMALL_RADAR_SYSTEM_UFOPEDIA: "Radar krótkiego zasięgu jest efektywny w promieniu ponad 550 km i jest połączony z systemami satelitarnymi do poszukiwań obiektów naziemnych. Każdy radar ma 5% szans na wykrycie obiektu średniej wielkości w ciągu 10 minut."
STR_LARGE_RADAR_SYSTEM_UFOPEDIA: "Radar dalekiego zasięgu jest efektywny w promieniu ponad 830 km{NEWLINE}i jest połączony z systemami satelitarnymi do poszukiwań obiektów naziemnych. Każdy radar ma 5% szans na wykrycie obiektu średniej wielkości w ciągu 10 minut."
STR_MISSILE_DEFENSES_UFOPEDIA: "Obrona rakietowa stanowi jakąś ochronę przed wrogim statkiem, który próbuje lądować w pobliżu bazy."
- STR_GENERAL_STORES_UFOPEDIA: "Cały sprzęt, broń, amunicja, zdobyte materiały i Ciężkie Działa Samobieżne, są przechowywane w magazynach. Również sprzęt przydzielony samolotom w hangarach."
+ STR_GENERAL_STORES_UFOPEDIA: "Cały sprzęt, broń, amunicja, zdobyte materiały i ciężkie działa samobieżne, z wyjątkiem sprzętu na pokładach samolotów, są przechowywane w magazynach."
STR_ALIEN_CONTAINMENT_UFOPEDIA: "Cele dla obcych posiadają specjalne środowisko utrzymujące ich procesy życiowe. Instalacja ta może utrzymywać przy życiu do 10 obcych form życia przebywających w oddzielnych celach."
STR_LASER_DEFENSES_UFOPEDIA: "Obrona laserowa, dzięki promieniowaniu laserowemu, jest dobrą ochroną przed wrogim statkiem."
STR_PLASMA_DEFENSES_UFOPEDIA: "Obrona plazmowa, dzięki rozpędzonym cząstkom, zapewnia mocną i skuteczną ochronę przed wrogim statkiem."
STR_FUSION_BALL_DEFENSES_UFOPEDIA: "Obrona fuzyjna zapewnia najskuteczniejszą ochronę przed atakiem obcych. Dzięki antymaterii pociski wytwarzają implozję, która niszczy wszystko w obrębie określonego promienia."
STR_GRAV_SHIELD_UFOPEDIA: "Tarcza grawitacyjna odpycha statek obcych próbujący lądować w pobliżu bazy. Wystarczająco długo, by wszystkie systemy obronne mogły wystrzelić ponownie. W praktyce podwaja to skuteczność każdego systemu obronnego bazy."
@@ -655,10 +652,11 @@ pl-PL:
STR_HIGH_EXPLOSIVE_UFOPEDIA: "Ten materiał wybuchowy powinien być używany tylko do wyburzania. Trzymaj żołnierzy z daleka od wyburzanych obiektów."
STR_MOTION_SCANNER_UFOPEDIA: "To nowoczesne urządzenie wykorzystuje różnorodne detektory i zaawansowane algorytmy komputerowe do wykrywania ruchu jednostek (wroga, własnych itp.). Efektywne używanie tego urządzenia wymaga jednak pewnej praktyki. Podczas misji kliknij na ikonę skanera ruchu trzymanego w ręku. Z menu wybierz 'Skanuj'. Wyświetlacz skanera pokaże w centrum strzałkę wskazującą kierunek, w którym jest zwrócona twarz żołnierza (północ będzie na górze). Pulsujące plamy będą odpowiadać jednostkom, które ostatnio się ruszały. Większe lub szybciej poruszające się jednostki wygenerują większe plamy. Nieruchome jednostki w ogóle nie zostaną wykryte."
STR_MEDI_KIT_UFOPEDIA: "Apteczką można leczyć, znieczulać oraz stymulować. Aby jej użyć, trzeba stanąć twarzą przodem do żołnierza wymagającego leczenia. Jeśli żołnierz jest ogłuszony, trzeba stanąć nad jego ciałem. Następnie trzeba kliknąć na ikonę apteczki i wybrać z menu 'Użyj apteczki'.{NEWLINE}LECZENIE> Części ciała z ranami śmiertelnymi będą czerwone. Kliknij na zranioną część ciała. Kliknij na przycisk 'Leczenie'. Zostanie wyleczona jedna rana śmiertelna i zostanie przywrócone trochę zdrowia.{NEWLINE}STYMULACJA> Zwiększa wytrzymałość i ocuca nieprzytomnego (ogłuszonego) żołnierza. Aby ocucić nieprzytomnego żołnierza, musisz stać dokładnie nad jego ciałem.{NEWLINE}ZNIECZULANIE> Przywraca morale zranionego żołnierza, nie więcej jednak niż stracone przez niego zdrowie."
STR_PSI_AMP_UFOPEDIA: "Wzmacniacz psioniczny (PsiAmp) może być używany tylko przez żołnierzy ze zdolnościami psionicznymi. Podczas walki kliknij na ikonę PsiAmpa, wybierz typ, a potem kursorem obiekt ataku. Dostępne są dwa typy ataku psionicznego:{NEWLINE}PANIKA> Jeśli atak się powiedzie, zmniejszy się morale obiektu, co może spowodować jego panikę.{NEWLINE}HIPNOZA> Jeśli się powiedzie, to zyskasz bezpośrednią kontrolę nad jednostką przeciwnika tak, jakby była Twoją własną. Ten typ ataku trudniej jest przeprowadzić pomyślnie niż poprzedni."
STR_STUN_ROD_UFOPEDIA: "To urządzenie może być użyte tylko w bezpośrednim kontakcie. Wstrząsem elektrycznym ogłuszy żywy organizm bez zabijania go."
+ STR_THE_SUBJECT_HAS_DIED: "Podczas 'przesłuchiwania' jeniec zmarł z powodu urazów."
STR_MIND_PROBE_UFOPEDIA: "Próbnik myśli jest urządzeniem komunikacyjnym obcych, który pobiera informacje bezpośrednio z fal mózgowych. Jednostki XComu mogą używać tego urządzenia w walce do wyświetlania charakterystyk obcych. Kliknij na próbniku myśli, a potem wybierz opcję 'Użyj próbnika'. Następnie kliknij kursorem na obcego."
STR_PLASMA_PISTOL_UFOPEDIA: "Broń plazmowa jest śmiercionośną bronią obcych bazującą na przyśpieszaniu cząstek we wnętrzu słabego pola antygrawitacyjnego."
STR_PLASMA_RIFLE_UFOPEDIA: "Jest to porażająco potężna broń bazująca na przyśpieszaniu cząstek we wnętrzu nikłego pola antygrawitacyjnego."
STR_BLASTER_LAUNCHER_UFOPEDIA: "To jest wyrzutnia rakiet kierowanych, który strzela rakietami fuzyjnymi o dużej sile rażenia. Gdy klikniesz na rakietnicy fuzyjnej, będziesz mógł ustalić punkty kontrolne, przez które będzie miała przelatywać rakieta fuzyjna. Jeśli masz ustawioną wystarczającą ilość punktów kontrolnych, kliknij na specjalną ikonę odpalenia."
STR_SMALL_LAUNCHER_UFOPEDIA: "Mała wyrzutnia bomb ogłuszających. Bardzo przydatny do chwytania żywych okazów obcych."
@@ -689,12 +687,12 @@ pl-PL:
STR_COUNTRIES_COMMA: "{0}, {1}"
STR_COUNTRIES_AND: "{0} i {1}"
STR_COUNTRY_IS_UNHAPPY_WITH_YOUR_ABILITY: "{0} - kraj ten jest niezadowolony z Twojej zdolności do radzenia sobie z działalnością obcych na jego terytorium i zdecydował się obniżyć swoje dotacje."
STR_COUNTRIES_ARE_UNHAPPY_WITH_YOUR_ABILITY: "{0} - kraje te są szczególnie niezadowolone z Twoich zdolności do radzenia sobie z działalnością obcych na ich terytoriach i zdecydowały się obniżyć swoje dotacje."
STR_KNOTS: "{0} km/h"
- STR_COUNTRY_HAS_SIGNED_A_SECRET_PACT: "{0} - kraj ten podpisał tajny pakt z nieznanymi siłami obcych i wycofał się z projektu XCom."
- STR_COUNTRIES_HAVE_SIGNED_A_SECRET_PACT: "{0} - kraje te podpisały tajne pakty z nieznanymi siłami obcych i wycofały się z projektu XCom."
+ STR_COUNTRY_HAS_SIGNED_A_SECRET_PACT: " - kraj ten podpisał tajny pakt z nieznanymi siłami zbrojnymi obcych i wycofał się z projektu."
+ STR_COUNTRIES_HAVE_SIGNED_A_SECRET_PACT: " - kraje te podpisały tajne pakty z nieznanymi siłami zbrojnymi obcych i wycofały się z projektu."
STR_MONTHLY_RATING: "Ocena miesięczna> {ALT}{0}{ALT} {1}"
STR_FUNDING_CHANGE: "Zmiana funduszy> {ALT}{0}"
STR_COUNCIL_REDUCE_DEBTS: "Rada krajów sponsorujących projekt nie jest zadowolona z Twojego położenia finansowego. Musisz zmniejszyć swoje długi poniżej jednego miliona dolarów, inaczej projekt zostanie zakończony."
STR_HYPER_WAVE_TRANSMISSIONS_ARE_DECODED: "ZDEKODOWANO TRANSMISJĘ HIPERFALOWĄ"
STR_CRAFT_TYPE: "STATEK"
@@ -880,11 +878,11 @@ pl-PL:
STR_NOT_ENOUGH_EQUIPMENT_TO_FULLY_RE_EQUIP_SQUAD: "Za mało sprzętu, aby w pełni uzbroić oddział."
STR_MARS_CYDONIA_LANDING: "Mars: Lądowanie w Cydonii"
STR_MARS_CYDONIA_LANDING_BRIEFING: "Twój Mściciel wylądował na powierzchni Marsa na terenie Cydonii. Nasze informacje wskazują na to, że piramidalne konstrukcje zawierają zielone windy dostępu do podziemnego kompleksu. Skoro tylko zgromadzisz wszystkich swoich żołnierzy na zielonych obszarach, kliknij na ikonę ewakuacji, by uruchomić windy i dostać się do podziemi."
STR_MARS_THE_FINAL_ASSAULT: "Mars: Szturm ostateczny"
STR_MARS_THE_FINAL_ASSAULT_BRIEFING: "Windy piramid zabrały Twoich znużonych walką żołnierzy głęboko pod powierzchnię planety. Żołnierze dotarli do serca wielkiego kompleksu tuneli i sal. 'Mózg' obcych jest ukryty gdzieś w labiryncie. Musi zostać zniszczony, jeśli Ziemia ma być uratowana przed zniewoleniem ze strony obcych.{NEWLINE}{NEWLINE}Powodzenia!"
- STR_YOU_NEED_TO_RESEARCH_ITEM_TO_PRODUCE_ITEM: "Musisz zbadać{NEWLINE}{0}{NEWLINE}by móc produkować:{NEWLINE}{1}"
+ STR_YOU_NEED_TO_RESEARCH_ITEM_TO_PRODUCE_ITEM: "Musisz zbadać{NEWLINE}{0}{NEWLINE}by używać lub produkować:{NEWLINE}{1}"
STR_THE_ALIENS_HAVE_DESTROYED_THE_UNDEFENDED_BASE: "Obcy zniszczyli niebronioną bazę {0}"
STR_XCOM_AGENTS_HAVE_LOCATED_AN_ALIEN_BASE_IN_REGION: "{0} - w tym kraju szpiedzy XCom'u wyśledzili bazę obcych."
STR_STANDOFF: "ŚLEDZENIE"
STR_CAUTIOUS_ATTACK: "ATAK OSTROŻNY"
STR_STANDARD_ATTACK: "ATAK STANDARDOWY"
@@ -1036,21 +1034,17 @@ pl-PL:
STR_UNDER_ARMOR_UC: "PANCERZ DOLNY"
STR_TIME_UNITS_RESERVED_FOR_SNAP_SHOT: "Zarezerwowano PR dla strzału szybkiego."
STR_TIME_UNITS_RESERVED_FOR_AUTO_SHOT: "Zarezerwowano PR dla krótkiej serii."
STR_TIME_UNITS_RESERVED_FOR_AIMED_SHOT: "Zarezerwowano PR dla strzału celowanego."
STR_UNITS_IN_EXIT_AREA:
- zero: "Brak jednostek na terenie ewakuacji"
- one: "{N} jednostka na terenie ewakuacji"
- few: "{N} jednostki na terenie ewakuacji"
- many: "{N} jednostek na terenie ewakuacji"
- other: "{N} jednostki na terenie ewakuacji"
+ 0: "Brak jednostek na terenie ewakuacji"
+ 1: "{N} jednostka na terenie ewakuacji"
+ 2: "{N} jednostki na terenie ewakuacji"
STR_UNITS_OUTSIDE_EXIT_AREA:
- zero: "Brak jednostek poza terenem ewakuacji"
- one: "{N} jednostka poza terenem ewakuacji"
- few: "{N} jednostki poza terenem ewakuacji"
- many: "{N} jednostek poza terenem ewakuacji"
- other: "{N} jednostki poza terenem ewakuacji"
+ 0: "Brak jednostek poza terenem ewakuacji"
+ 1: "{N} jednostka poza terenem ewakuacji"
+ 2: "{N} jednostki poza terenem ewakuacji"
STR_ABORT_MISSION_QUESTION: "Przerwać misję?"
STR_CORPSE: "Zwłoki"
STR_UNLOAD: "Rozładuj"
STR_NEW_SAVED_GAME: "<Nowy Zapis Gry>"
STR_NEW_BATTLE: "Nowa potyczka"
wtf? xD
once again many translation strings is gone (getloc.com)
-
They seem fine here (https://openxcom.org/translations/latest.zip). Note that translations are no longer included in the codebase, so you might be looking at old files.
-
STR_UNITS_OUTSIDE_EXIT_AREA_2
???
https://www.getlocalization.com/openxcom/editor/15103/#3593339
edit
login on getloc.com before click link
-
compare en-US <> latest pl-PL (zip)
-
That is very weird, I downloaded the latest translations just yesterday and they were working fine. I'll give GetLoc a call.
P.S. Use Alt-Printscreen to only take a screenshot of your active window. Nice wallpaper though. ;)
-
P.S. Use Alt-Printscreen to only take a screenshot of your active window. Nice wallpaper though. ;)
thx for a tip:)
https://en.wikipedia.org/wiki/%C5%81eba
-
if I will choose the en-US instead of ALL then see the correct version of the translation. But ZIP is that some inappropriate. Previously, did not matter what's chosen.
-
at this moment everything is ok
-
is anybody else getting a lot of GetLocalization e-mail-notifications about somebody commenting this or that string in his/her language?
I thought those comments and notifications only go out to those people working on the same language (because that would make sense), but I'm getting a load of them in languages foreign to me. am I using some kind of wrong setting or is there something else going on?
-
I think the emails go to anyone working on the same project. I thought also that it should only be for those working on that speific language, but yes i am getting e-mails all the time. I am about to block it :) or listed as spam or something :D
-
If you prefer you can disable emails in your profile: https://www.getlocalization.com/accounts/profile/notifications/
There's no way for GetLocalization to know which "language" you're interested in since you can technically contribute to any of them. I will ask them if they can improve this.
-
Hi, guys. What do you think about https://www.transifex.com ? :) I think this site is better for translating than GetLocalization I guess.
-
hmmm.... that actually looks nice, but jumping from place to place may not be the best strategy :) just saying, but if SUp likes it and it works well or better why not
hmmm but is not free you only get a 30 day trial :(
-
hmmm.... that actually looks nice, but jumping from place to place may not be the best strategy :) just saying, but if SUp likes it and it works well or better why not
hmmm but is not free you only get a 30 day trial :(
Seems to be free for open-source projects. I also found https://crowdin.net/
Of course these all look similar to GetLocalization (voting system and all), there's no telling which is better without trying each one. :P Maybe someone can find public projects to try them with.
-
I have projects in Transifex (tx). Translation workflow is different than GetLocalization. First at all, tx is hierarchy - you have lead of project, coordinator of translation team, reviewer and translator roles. There is no voting system, only suggestions. Tx has translation memory, glossary and history of translation.
One most best parts of tx is API and console tx-client that relies on it. You can even rollback and mass-import in that client.
Tx used by Fedora as platform for entire translation efforts for that distributive. XFCE uses own (pretty outdated 0.8 ) instance.
-
There is no voting system, only suggestions.
Lol? You can vote of course if there's any suggestions to translated strings.
-
No, in Transifex there no "Vote" button for available suggestions. You can only pick up available or suggest new one.