Hi, i would like to mention at this point of the discussion, a lot of string in the source code are not marked as translatable text.
For example if you open the addons/web/controllers/main.py at line 900 there is a string "You cannot leave any password empty." what isn't disappear anywhere else in the source code. Or another one: addons/web/static/src/js/chrome.js line 645: "No database selected !". A lot of strings, if not most of them are not marked well. I think at first this should be fixed, because than we will have tons of new strings to translate. Thanks, Csaba 2012.11.28. 1:05 keltezéssel, "Lionel Sausin, de la part de l'équipe informatique Numérigraphe" írta: > Dear community, > > For now the urgency is v7, but beyond that I really encourage the native > English speakers in the community to gather as a team and tackle the > task of reviewing *all* the strings. > > This *is* a lot of work, but only a bit harder than reviewing a whole > translation. > I'm sure Olivier and other technical wizards will help ease the pain. > Translation teams can also help you find a method, and check proposals > for consistency and ease of translation. > From watching the translators I'm confident a complete review can be > done by a team of 6~10 experienced contributors, maybe in time for v7.1, > certainly before v8.0. > > All it takes right now is a volunteer to create a team and a mailing > list, and recruit contributors. > Who will take up the gauntlet? > > Lionel Sausin. > > Le 27/11/2012 18:19, Olivier Dony a écrit : >> On 11/26/2012 07:06 PM, Ray Carnes wrote: >>> It is clear many of the terms in OpenERP were decided/writtenby >>> non-native >>> English speakers. For people in English speaking markets, this can >>> make the >>> product look unnecessarily amateurish. >> >> We realize this is the case, and for v7 we have done a bit of >> reviewing/cleaning up of the master terms with the help of native >> english speakers. >> Of course we did not cover all 18k terms, and a few thousands new >> terms were also introduced with v7.0, not all of them reviewed. >> >> Any feedback from our translator community would be very much >> appreciated in this regard. And now is probably the best time to >> collect this feedback, especially on the newly introduced terms >> (before too much effort is wasted on translating them). See below... >> >> >>> *_What is the best way to have community translation efforts_**_for >>> American >>> English?_**_ Create another language?_* I understand you need one >>> anchor >>> language for terms. You have a community in the USA that would love >>> to help >>> translate but from what I can tell, everyone does it on their own and >>> doesn't >>> collaborate very well. >> >> Creating another language is pretty tedious and I would suggest to >> only use "en_US" translation entries as a workaround, when it is >> really necessary for a customer project. For the future it is always >> be best to try to fix the master terms in the "trunk" version. It may >> sometimes cause a bit of translation loss, but when done for good >> reasons it will also make the job of international translators easier >> in the future. >> >> As we indeed use US English as anchor/master language, we should not >> alter the terms too much on stable versions, but we can use the >> opportunity of a new release to improve them. >> >> In order to make some progress on this, we can start a collaborative >> pad (as already suggested by some people) where native english >> speakers can suggest corrections to the "master terms" that are used >> for v7.0 (i.e. the current terms in trunk). >> I created a pad where you could start, and we'll see how it works out: >> http://pad.openerp.com/english-review >> >> Please keep in mind that this is a continuous improvement process and >> we will not be able to change hundreds of terms for v7.0 (not to >> mention the extra burden it would create for translators). So let's >> concentrate on the most important/confusing terms and obvious typos, >> and not waste time with terms that are not 100% wrong or confusing. >> For example don't waste your time on variations (e.g. "team" vs "sales >> team", "manufacturing" vs "production"); we will ignore them unless >> it's clear that the term is 100% wrong in that context and creates a >> lot of confusion. >> >> If the contents of this pad contains a manageable amount of good >> suggestions I will make sure they get corrected before the final 7.0 >> release. >> >> Let me know what you think... >> >> Thanks for your invaluable contributions! >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openerp-expert-localization >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~openerp-expert-localization >> More help : https://help.launchpad.net/ListHelp > > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
