 |
Slovak targeted for 2.06 too: http://forums.thedarkmod.com/topic/17374-slovak-translation-progress-screenshots-etc/#entry415909 |
 |
Also replied in the above thread asking in Petike had manage to fix the broken fonts. |
|
|
I know Petike is working on Slovak. If he's not also working on Romanian, who is? |
 |
I was on Romanian with help from Tels. |
|
|
@Anderson, @NB: Is there more work to be done on Romanian? |
|
|
At the moment I have done everything within my abilities. The Romanian translation should be fully functional as is. |
|
|
@NB, if you agree, can we close this issue? |
|
|
If the latest tdm_base01.pk4 is implemented then yes, it can be closed as far as Romanian is concerned. |
|
|
We need to compare your work to the Slovak translation. Somehow it wasn't fully compliant before. |
|
|
What are the standards to comply with, if I may ask? I coordinated all translation of the GUI, menu, loading tips, inventory description with Tels at the time, as he was the one who started the Internationalisation (I18N) project. |
|
|
Just needs to match the strings in all.lang for 2.06 Every time someone adds new words to the GUI, we need matching string values. |
|
|
I think it's set properly in the tdm_base01.pk4 linked in the description to Google Drive. Did the strings in all.lang for 2.06 change? |
|
|
"Did the strings in all.lang for 2.06 change?" 2.06 has new Graphic menu options for uncapped FPS, multi-core, and soft shadows. They will need corresponding translation updates. |
|
|
@NB, Do we have translators on record for the other languages? They should be contacted to see if they can translate the new strings. Is that something you can take care of? |
|
|
I will take a look. I was thinking that Petike was making is Slovak "2.06 ready" so I could just compare that to Anderson's work. |
|
|
How do I get the all.lang file for 2.06? Beta forums are closed to me. Or you can PM me the words that need translating and I will answer. Atm busy with real life so doing it myself would take longer. At least for the duration of this winter. |
|
|
I attached the current 2.06 all.lang file. |
|
|
2.06 Beta is public: http://forums.thedarkmod.com/topic/19162-beta-testing-206/ |
|
|
Thanks! I will do my best, but I can't guarantee anything at least until February. |
|
|
Sorry, messed up the file name on upload but I revised the characters to exclude all broken cedillas and umlauts. Could you tell me the string numbers for the graphics options you've mentioned? |
|
|
These are the new strings I added for the new graphics features. They're available starting with yesterday's 2.06 package build. // Strings required for new 2.06 features (grayman 0004736) "#str_02930" "Player Field of View" "#str_02931" "Soft Shadow Quality" "#str_02932" "Multi Core Enhancement" "#str_02933" "Uncap FPS" "#str_02934" "HUD Size/Opacity" // Strings for inventory grid "#str_02935" "Inventory Grid" "#str_02940" "Total:" "#str_02941" "Jewels:" "#str_02942" "Goods:" |
|
|
Can you upload the new file here with these strings here? Thank you in advance. |
|
|
Done |
|
|
Also done. |
|
|
Rev 15153 Skina's Russian fixes Rev 15154 Anderson's Romanian fixes |
|
|
Rev 15155 more language fixes and Petike the Taffer's Slovak |
|
|
15156 Russian Unicode to CP1251 fix |
|
|
@NB: I'm trying to get my head around these language changes. When you submitted Russian, Romanian, and Slovak *.lang files, had you added their strings into all.lang, and then used Tels' program to automatically create the 3 *.lang files? Or did these guys create free-standing *.lang files and you submitted them as is, w/o transferring their contents to all.lang first, and then using the process? |
|
|
I copied the (specific, eg. just russian, etc) lang data from the all.lang to it's own document then used compare in Notepad++ to see where the all.lang differed from russian.lang (etc) and updated the child lang files to include additional translation strings. Where there was no translation for some of the new strings, I used google translate then copied the result into an Cyrillic converter and then finally into the child lang file. All tedious manual work. The script would be great if it worked instead of creating a sheet of question marks (due to unrecognized characters). |
|
|
So it looks like we have to remove those three languages from the perl script and instead of creating the individual files automatically, we have to maintain them manually. Right? I'll need to do this, revert the 3 individual files I submitted as part of 15157, and add the single missing line (#str_07221) in each of the 3 files that 15157 is adding. It won't be translated, but at least it'll be present. |
|
|
Sounds like it. Unless Obsttorte has any better idea. Thanks. |
|
|
Is it just Russian I need to handle this way? I don't see the question marks in Romanian or Slovak. |
|
|
You mean if Obs has a better idea along the lines of fixing the perl script? |
|
|
I think russian is the biggest problem. Romanian we just need to watch out for those strange "a" characters that keep coming back somehow. (Probably because I just took Anderson's romanian.lang and didn't backport the changes to all.lang.) Obs seems to know language stuff pretty well. He always gets into the threads. |
|
|
@NB: I just submitted russian. Rev 15164. Can you see if what I did was correct? I commented the russian section in gen_lang.pl and all.lang, and changed russian.lang by hand. |
|
|
Looks good to me. At least as good as what I had, except I'm gonna fix a few character issues in Romanian... Revision 15165 Russian resolution settings fix Revision 15166 |
|
|
Two bad things: 1 - I can't simply comment out the Russian section in all.lang. The syntax inside the section doesn't allow for block comments (/* -> */). I had to delete the entire section to get gen_lang.pl to run. 2 - gen_lang.pl corrupts the romanian.lang and slovak.lang output files. So we have three languages that can't be handled by the gen_lang.pl program. |
|
|
I started a PM with Obs to see if he can help with the script. |
|
|
Rev 15193 should complete the 2.06 work. |
- Anonymous
