ho-dev
[eFEAT] i18n
There are my thoughts about project translation:
- [ ] Each unclear or ambiguous sentence-to-translate MUST be commented.
- [ ] Some items should be splitted (For ex: shortened abbr for a column header and a regular term). Maybe it'll lead to the extreme redundancy, but any new translator would clearly understand what the sentence exactly means and where it will be visible.
- [x] Plurals. "X years Y day(s)" looks already ugly in English (as in most Germanic and Romanic languages). But in all Baltic, Celtic and most of Slavic languages this sentence is definitely incorrect (they have more than two plural forms). As a translator I'd prefer Mozilla's indices with GNU gettext's Plural-Forms `formulas:
# Get the index of the plural rule for your language
# from https://developer.mozilla.org/docs/Mozilla/Localization/Localization_and_Plurals
PluralRule=1
# Player age. Requires plural form. The semicolon sign (";") is a delimiter
years=year;years
# Player age (days). Requires plural form.
days=day;days
Foxtrick is a good example.
- [ ] Documentation for devs. The procedure to add/split/rename translation keyword must be documented. Maybe we need a neutral stub with our English - it also gives opportunity to issue en-uk and en-us translations if anybody interests in it.
- [ ] Credits. It's bad idea to lose previous translators' names. The old "Autor" field for every translation have to be retained.
- [x]
item names' deboschification? :) - [ ] Warcry! Once three first items are done/in the work, we'll need some spam into national HT forums with asking for help in translation and informing about "HO is alive" with new url's instead of outdated ho1@sf. Should be made in contact with HT-staff.
Seems to me this issue is one more to hold 2.0 release.
I like those, they are interesting. I had to look terms up in code to translate ambiguous lines, so that would be helpful for people. Mozilla's indices with GNU gettext Plural-Forms formulas sounds lovely. Some nice docs would be nice too. Lastly, credits. I mentioned that earlier but got nowhere. @akasolace is in charge of translations/POEditor.
@konved I think we should try to keep things simple (in the sense of low efforts). Hence, I am all in the removal of German terms (personally almost every time I touch part of the code I try to translate it to English) and the introduction of comments to guide translators.
However, I believe that introduction of US and UK English would be unnecessary. For the treatment of plural form I also believe your proposal is very ambitious but if you want to implement this, please feel free to take the lead on this one.
For credits: if you all think it is a good idea I will reintroduce them.
Regarding your last point, I believe that if we manage to deliver 2.0 with all the features, it will definitely help promote HO again. It will be the first release with new features in many years. That is why we really need to complete the minute base rating and the feedback plugin.
@konved I recieved 3 demands from new contributors this afternoon, have you posted on HO forum or is it just a coincidence ?
@akasolace no, I've put it only here. Just to hear thoughts on it before starting any work.
French
@konved nice ! I also suggest that I modify PoEditor to not export not translated term. It should not change anything behaviour wise, because HO automatically revert to English if term not available in requested language. In the future however, that would allow to change directly translation in properties files and import them back in PoEditor. What we could not do yesterday for example.
What do you think ?
@konved are you still working on this one ? do you know when you will have it finished ?
@konved are you still working on this one ? Are you planning to close it anytime soon? Should I remove the 2.0 milestone?
