Megapack tech tree - language corrections (English) and Polish translation

[filux]

I decided to do a translation to main tech tree that participates actively in 90% of the battles -> Megapack  .

Before starting work (on the secret project ) I have read all related with this topics available on the forum and found that my opinion support "both opposite parties in conflict" .
Is it possible to do that both sides were satisfied?

Yes of course! it must be possible! 

E.g.

Code: [Select]

[img]http://imgius.com/photos/20130601137008947274542.png[/img]    [img]http://imgius.com/photos/20130601137008947931906.png[/img]

[img]http://imgius.com/photos/20130601137008947204765.png[/img]    [img]http://imgius.com/photos/20130601137008947113111.png[/img]
But during the translation came to light fact, that the original strings contains some errors,
(one of them probably is here at least since glest v.3.2 because I found old description on the wiki )
so on the occasion of sometimes looking to the history and mythology I introduced some patches to English strings.

Summary: package is useful to everyone, especially when you play a lot in version 3.8 because only this version supports the translation of all strings.

Pack contains a translation to Megapack tech tree (very much tested) and also partial translation (contain Megapack section of course) to all of the other official tech trees containing something from Megapack .

From now the game is much more polonized, which is highly encouraging and important especially for beginners.

link:

Code: [Select]

[url=http://s000.tinyupload.com/?file_id=53643710891761967169]Megapack tech tree - language corrections (English) and Polish translation [/url]

[GunChleoc]

That's a good idea for a workaround

I still think the best way to handle this would ne to separate game language from interface language and have the person starting a multiplayer game decide on the game language. I am currently trying to figure out how to use multiple textdomains in gettext. Mayrkign strings in the code is easy, but I have failed generating separate PO files so far.

[tomreyn]

Filux:
I'll be happy to look at the English language changes you suggest for Megapack (and thus Magitech and Ultrapack) if you can provide a patch or replacements for the existing XML files. Then, however, unless Titi says differently, this will have to be limited to orthographic and grammatical errors.

I would also like to point out that I personally like the compromise you are suggesting reagarding translations of unit and structure names in Megapack.

[filux]

... for Megapack (and thus Magitech and Ultrapack)...

... and east_vs_mega and imperial_m_g too

...unless Titi says differently, this will have to be limited to orthographic and grammatical errors ...

Meanings' errors are really only a few though they are a bit annoying.
I think that we'll agree on determine whether the new name is apposite or should be different.