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


Hi Martin,

Martin Srebotnjak píše v Út 24. 11. 2015 v 15:54 +0100:

Please, once more, do not do any "l'art pour l'art"-istic changes that
might cause any kind of trouble to localizers.

There are many more things to invest time and will in first - to write
missing help content, to edit the help content, to make
wiki-served-help fully localizable, to have manuals (getting started
guides) up-to-date etc.

Exactly!  And to be able to do so, we need to lower the entry barrier,
so that more people can write the help content, update the manuals, etc.

We have just seen a guy interested in editing help, and this was one of
his struggles there - that he just couldn't find the help file he needs
to edit.  Asking him to grep all the main0123.xhp files (and alike) is
just as nice as telling him "go away, we don't want you" :-(

That's why I am interested to learn what are the technical & workflow
difficulties to make the barrier lower, and what is the impact on the
localizers.

We need to do changes to be more open for documentation contributions,
that's something we just cannot avoid, otherwise our help will be
completely outdated soon.  So I'm asking if (and what) we can do in a
way that causes no or only minimal trouble.

Most localizers localize from Pootle and I am sure that po files there
could be given additional description what part of UI or help they
cover, if really someone feels lost.

"Most localizers localize from Pootle" together with:

2015-11-24 13:22 GMT+01:00 Andras Timar <timar74@gmail.com>:

It is
possible to automatically replace file names in git and in Pootle, but
this can cause disruption for translators who work offline, and
translation memories have to be regenerated.

actually makes me think that only a small fraction of translators would
be actually disrupted, because for those using Pootle, it would be
transparent.  So did I misunderstand?

Thank you for your help!

All the best,
Kendy


-- 
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

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.