Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index

On 12/14/2014 11:07 AM, Sophie wrote:
And I have yet to see those technical marvels we've been promised will
compensate for this problem (promised with lot of eff-ing at silly
localisers, by the way).

Hey, those scripts are done by people to help us, so don't shout on
them. We will discuss these heavy changes after the code/string freeze
with developers and designers. We have to find a way that allow to
maintain the sources without impacting the targets when it's not needed,
let's try to find a solution and keep working in a good mood.

But I do not shout at anybody. Do I?..

Just that I'll believe there are positive changes in this part of workflow, when I'll see an announcement going like (hyperbolised): "We've corrected the fixed space use in 10k worth of strings, but don't worry, your translations won't be kicked out of release, if you'll not redo your 10k worth of translations by tomorrow".

Right now, I'd risk stating that for small teams the task begins to look more trouble than it's worth.


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.