On 28/01/15 12:07, Wols Lists wrote:
3) Who's going to step up to maintain en_US? (I'd love to help, but
I'm working tons of hours as it is)
The same people who are causing all the grief for everybody else by
currently translating/changing all the strings in master? Surely there's
no difference to the amount of work in translating en_us, as there is to
translating master?
I should add, if we go down that route, surely it's not a problem to
script a mass change in master to sync it with en_us, that also flags
all translations as unaffected by that change. Saving loads of
translation grief, but saving the space that Michael Stahl pointed out
would otherwise be taken up.
Cheers,
Wol
Context
- Re: [libreoffice-l10n] Re: Workflow between dev, UX and l10n teams (continued)
Re: [libreoffice-l10n] Re: Workflow between dev, UX and l10n teams · Rimas Kudelis
Re: [libreoffice-l10n] Re: Workflow between dev, UX and l10n teams · Sveinn í Felli
Re: [libreoffice-l10n] Re: Workflow between dev, UX and l10n teams · Jesper Hertel
Re: Workflow between dev, UX and l10n teams · Stephan Bergmann
Privacy Policy |
Impressum (Legal Info) |
Copyright information: 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.