Date: prev next · Thread: first prev next last


Hi :)
Yeh i think Sophie did such a brilliant job of summarising all the
points that no-one had anything to argue against.

My main concern was about automating the bits that could be automated
in some sensible way - preferably some way that each language could
select to opt into or out of.  In wiki-editing people are encouraged
to write a summary, like a subject-line in an email, for changes
beyond just a couple of characters.  Something like that might help
with the automation.

I really liked the point about having some way of identifying trivial
but frequent changes and minor grammer corrections that most
translators will already have dealt with in order to make sense in
their own language(s).

There was a lot of other interesting things in Sophie's post but i
just agree with all of them and that makes it difficult to discuss ;(
It seems like just about everyone here feels the same way.

Regards from
Tom :)



On 26 January 2015 at 09:32, Sveinn í Felli <sv1@fellsnet.is> wrote:
Þann mán 26.jan 2015 09:25, skrifaði Mihovil Stanić:

Not sure what can we add here?

You summed it up nicely in those 3 points.
As far as I'm concerned, en_us can be changed/improved as much as anyone
wants... only if they provide script for automatic update for all other
affected languages.

New strings - OK
Edited strings with changed meaning, fixed typos - OK
Cosmetic changes (~ to _ or "Status" to "Status:" or ... to … or those
different quote styles I don't even have on my keyboard) and anything
similliar - NOT OK if you don't script it for all languages
Cosmetic changes ("Big brown fox" -> "Big Brown Fox") - NOT OK at all,
change just for en_us, don't change my strings and don't even notify me
you did it in en_us


May I add here:

XML/HTML entities and such (<a href...> to <link>) - NOT OK, scripted for
all languages (if possible)

Sveinn í Felli

Mihovil


26.01.2015 u 09:33, Sophie je napisao/la:


To conclude, what l10n team would like to see is:
- a review process of the strings before they are committed and make
sure they respect the en_US standards (capitals, grammar, punctuation,
typography). Maybe adding the Gnome HIG book to our pages [like 2] if
not already.

- if there is a way to script changes, script them otherwise wait until
there is a script available to commit them

- any time there are heavy changes that pop up in someone's mind (like
changing ... for …) discuss it with the l10n team before committing
those changes.






--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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

-- 
To unsubscribe e-mail to: projects+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/projects/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.