Le 04/12/2014 00:58, Jesper Hertel a écrit :
2014-12-01 14:57 GMT+01:00 Sophie <email@example.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 discuss together how to handle that in our workflow.
Some changes are necessary and the en_US version has to be maintained
too but that shouldn't have an impact or at least, as limited as
possible on the l10n work.
For some reason I don't completely catch what you are saying, but I guess
it is something along the lines that we should have a specific discussion
forum for the en_US (American English, the "original" text) version? Or
maybe a discussion about whether we should have a separate discussion forum?
I do believe discussing the English strings are somewhat related to the
translation of them, so maybe because of that I fail to see a very sharp
division between them and the localization. The English strings are, in
principle, also a type of localization, I would say. They just have a much
higher authority, as they become the authoritative source for the rest of
English strings come from different teams in the community, mostly from
developers and UX/Design teams, sometimes QA when they see small things
to fix quickly. The l10n team is the one who review the English strings
and who is the most impacted by their quality (before the user) and the
workload when they are changed.
When we want to discuss something that has an interest for several
teams, we have a cross team list, the projects@ list. I believe that the
developer should be aware, as well as the UX team that if they want to
make large changes to the English string, that will have a huge impact
on the l10n team and they have to take care of how those changes are
applied (spread over the branches, create scripts, etc.)
I'm not sure it's the good moment to open the discussion now because we
are all catching dead lines,
Yeah, and maybe what I wrote above is in some way also part of that
discussion that we probably should not take now? If so, you don't have to
respond to my comment now.
but I propose to do it
Does "do it" mean start the discussion, or are you referring to something
yes, that mean starting the discussion on the projects@list
on week 2 next year,
after the hard code freeze for 4.4.0.
Is it ok for you all?
Fine with me. :-)
if yes, I'll open a ticket on Redmine.
Très bien, Sophie!
Sophie Gautier firstname.lastname@example.org
Co-founder - Release coordinator
The Document Foundation
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy