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

Hi Martin,
Hey, hey :-) this is not the case for the moment. Rob is currently working
on exporting the wiki help content to the sources (if I understand well).
My mail was to make sure that all the aspects of maintaining the help on
the wiki are taken into account. But if the help is better enhanced on the
wiki, it's not a problem on the contrary, the l10n process should not be
changed however.
Kind regards

Le 8 oct. 2013 22:24, "Martin Srebotnjak" <> a écrit :


maintaining and translating LO help via wiki is a no-go for localization

If someone wants to play with that, he/she can do it as one's own pet
project, maybe by creating a fork of LO. But LO should officially stay away
from it. Or it will, quite soon, become an English-only office suite. If
that will be the case, the localization teams should think about forking LO

Lp, m.

2013/10/8 Sophie <>

Hi Rob,

I'm adding the l10n list in copy because they are concerned
Le 08/10/2013 11:16, a écrit :
Hi Sophie,

As I understood the offline help is now hard to maintain.

Yes, this is something complicated for developers
 This should
change that so that the help-wiki will be exported for each release's
offline help. So It should make changing/translating the help easier.

I don't doubt that the wiki would be easier than filling the help .ott
and using the basic macros that was used in the past, I've used it and
it's really complicated.
What is important for us (l10n team) is the possibility to use Pootle to
maintain our translation, because the wiki is not a translation tool (no
glossary, no TM, no way to track changes, no way to mark incorrect/fuzzy
strings, no way to share the files, no xml checks, etc...) and is
impossible to search currently (we need a i18n wiki for that).
That means also that the wiki edition is restrained to the necessary
changes and enhancements that are needed and only those and that changes
are only made in the en_US sources.
I understand that you are currently only working on the process to
export the wiki, but I think that the l10n team may have some input too.
Again (because already expressed to Kendy), my concerns are not about
the changes in the process, I really understand that, but about to make
sure that the l10n team is made aware of the changes in their work if
any, and that the way they are working currently to localize those
important and huge files is taken into account in the process.

Kind regards

Rob Snelders

Sophie schreef op 08-10-2013 09:20:
Hi Markus, Rob,
Le 08/10/2013 01:52, Markus Mohrhard a écrit :
Hey Rob,

2013/10/7 Rob Snelders <>

Hi Markus,

We have spoken about exporting the help-system from the help-wiki.
We will
need a html/javascript framework for that. I don't think a basic
will need more time then a month or 2 for me. But I think we will
also need
to look at how we export the pages from the wiki because how the
pages are
exported is important.

Can you tell me what plugin for mediawiki you had in mind to do the

I found DumpHTML at the mediawiki page. I wanted to try this first
looking for other scripts.

Is there a test-wiki to try it on to see what it does, maybe we'll
need to
change the plugin to fit our needs.

We will get a VM from the infrastructure team soon. We will test all
steps there. I'll tell you more as soon as we get the VM and have it
correctly set up with a wikihelp instance.

If the l10n team is impacted by your project, please tell me, as this
their (huge) work, I would like to keep them in the loop.
Thanks in advance
Kind regards

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

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.