Hi Jesper,
Le 04/12/2014 00:58, Jesper Hertel a écrit :
Bonsoir Sophie,
2014-12-01 14:57 GMT+01:00 Sophie gautier.sop...@gmail.com:
Hi all,
Opening a new thread on the changes on the en_US version, I propose to
follow-up on the project@ list so we could associate the developers and
Þann mið 3.des 2014 23:58, skrifaði Jesper Hertel:
Bonsoir Sophie,
2014-12-01 14:57 GMT+01:00 Sophie gautier.sop...@gmail.com:
Opening a new thread on the changes on the en_US version, I propose to
follow-up on the project@ list so we could associate the developers and
design teams and
Hi Sveinn,
Le 04/12/2014 09:21, Sveinn í Felli a écrit :
Þann mið 3.des 2014 23:58, skrifaði Jesper Hertel:
Bonsoir Sophie,
2014-12-01 14:57 GMT+01:00 Sophie gautier.sop...@gmail.com:
Opening a new thread on the changes on the en_US version, I propose to
follow-up on the project@ list so
Bonsoir Sophie,
2014-12-01 14:57 GMT+01:00 Sophie gautier.sop...@gmail.com:
Hi all,
Opening a new thread on the changes on the en_US version, I propose to
follow-up on the project@ list so we could associate the developers and
design teams and discuss together how to handle that in our
I may be completely misunderstanding this, but
it seems to me the point is the en_US strings
should be translations as well. That would put
much needed damper on the changes introduced
just because they can be introduced. As a
secondary gain, translations are (hopefully)
created by folks
IMO bad quality of English strings can be improved by having some l10m teams
work on Master (and spotting these bad strings early enough), and that is being
discussed in parallel.
Also, perhaps requiring string reviews on patches with new or changed strings
could be an option. I'm pretty sure
Hi all,
Opening a new thread on the changes on the en_US version, I propose to
follow-up on the project@ list so we could associate the developers and
design teams and discuss together how to handle that in our workflow.
Some changes are necessary and the en_US version has to be maintained
too
