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

Hi all,

It is a secret for nobody that the help is a nightmare to maintain for
developers and contributors. However it's an important part for the
quality of our product and we need to find a way that is acceptable for
all of us working on it.

During the last Hackfest in Paris, I discussed with Moggi and Kendy how
we could organize the workflow to enhance and maintain the help and keep
the translation easy for l10n team.

So here is a proposal to discuss about using the wikihelp to maintain it:
- the existing translations would be migrated, so no work is lost (one
of the most important requirement :)

- the translation project is split in 3 parts:
* UI as we have it today
* Extended tooltips - currently in help files, are extracted and get its
own .po project
* Help content, managed in the wiki

- review of the added/modified part on the wiki:
* random people can contribute but *not* directly
* there will be an approval process, like in Pootle or Git

- there is one point that is not optimal, because wiki syntax is
difficult to manipulate via .po files, it would be much safer to use
media wiki to translate, with the help of the translate toolkit (where
you have context, extended syntax, memories).
Note: translating via .po still would be possible, but really at own
The disadvantage that it has too is that we need two tools:
- Pootle for UI + extended tooltips,
- mediawiki for help.

So, this is how we can present the pros and cons maintaining our help
files via the wiki to reach more contributors and quality. Nothing is
set yet, but we need to find a consensus to have our help amended and
maintained, reach a good quality and really serves our users.

Feedback and ideas welcome :)

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.