c2c-oerpscenario team mailing list archive

[Borja López Soilán <borjalopezsoilan@xxxxxxxxx>]

On 2010-11-11 10:46, Geoff Gardiner wrote:
> 2010/11/9 Numérigraphe <327259@xxxxxxxxxxxxxxxxxx 
> <mailto:327259@xxxxxxxxxxxxxxxxxx>>
>
>     ... it may seem strange to refactor  only to fix typos but ...
>
>
> We've been through this before, but I should mention it again:
>
> About 2 years ago I corrected much of the English for Open ERP (I 
> changed only the label strings, not the names). Since then, new 
> strings have been put in with the same old incorrect spellings (there 
> are some favourites, which must be rooted in one language or another - 
> /developper/ is one, /ressource/ is another). So a one-off change does 
> not work for long.
>
> Somebody proposed a new process so that incorrect spelling does not 
> get committed to the published code, but I don't think that process 
> has been implemented.

Maybe they should implement it on the integration server 
(http://test.openobject.com/).
Making a Ruby or Python script that checks for common mistakes 
("childs", "developper") does not look to hard. The server could then 
send those "spelling warnings" to the commiters, just as it does now 
when a commit does not pass the unit/integration tests.

-- 
Borja López Soilán
borja@xxxxxxx

-- 
"Children" not "childs"
https://bugs.launchpad.net/bugs/327259
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Addons Modules: Confirmed
Status in OpenObject Web Client: Fix Released
Status in OpenObject Web Client trunk series: Fix Released
Status in OpenObject Server: Fix Released

Bug description:
English is not my mother tongue, so forgive me if I'm wrong, but : very often on OpenERP we see "childs" written instead of "children" and that's wrong.
You can find field names, in help texts, and in the documentation.

One problem with that is that our English/American users surely won't find it professional looking.

Initially this bug also mentioned spelling errors in the code but now that's Bug #673087.