Geoff the Medio wrote:
The FOOT page about it describes FreeOrion as "a clone of Master of Orion (II)". This is incorrect. FreeOrion is inspired by MOO(2), but is not a clone (of any game) and incorporates ideas from various other games besides MOO(2) and has many new ideas not copied from another game as well.
I will change it
Some other suggestions:
Have some built-in capacity to deal with changes to the base english stringtable that need to be propegated to the translations. The most important changes are probably the addition of new strings that need translations, and modifications to existing strings. Any translations of modified strings should probably be marked as incomplete. Deleted strings could be just removed from the translations, but saving them might be useful, in case the string was just renamed in the english version.
I will manage it myself (it will be not public) or I will create public root accounts in the future, because I do not want any one to make something not compatibile with the game. There will be no string deletion feature. Instead, I will allow to generate stringtables for different versions of FO - now it is latest stable.
You might also want to have multiple versions of translations possible. Right now, there are differences that make stringtable for the latest point release and the SVN version incompatible.
I will think about it. I mentioned it above. I will add a relation between translations and version of FO - but I have to think how to do it the best way.
Additionally, some strings contain special sequences of characters like %1% (where the 1 can be another number) that need to be present in the translated string... They're replaced with some other string or number in the rendered text, and might cause crashes if there are different number (total) or number (within the %'s) of these in the translated string from what is expected. I suspect this is the cause of crashes some people have been recently reporting with out-of-date translations that are in the point release or SVN. ... Anyway, the point was that you might want to have some built-in consistency check for the translated string, to ensure it has all the same %1% type flags as the english string, so that someone translating won't accidentally (or intentionally?) submit a broken string.
OK. I will add this feature - FOOT will search for %d% and check if they exist in translated version, and if the number of %d%'s is correct. Incorrect strings will be checked as errorous (?) and will be not used in stringtable generation proccess.
And as i mentioned above - all changes on aliases, original strings, really important data I will do myself - for comaptibility.
I will add changes as soon as posible (possible? posibble? posiblle? sorry
Thank you for suggestions