I have forwarded your question to the global translators list in the hope that they can help you.
I really think you need to contact the dev's lists if you want to find out how to build LO from
scratch. It is quite far outside of the type of thing the Users List can help with but it was good
to ask here first so we can try to signpost you to the best places to get the answer from.
Apols and regards from
From: Kolbjørn Stuestøl <firstname.lastname@example.org>
To: LibreOffice brukargruppe <email@example.com>
Sent: Monday, 11 February 2013, 17:42
Subject: [libreoffice-users] Making local help copy?
Is there a (simple) way to build, assemble, or make a local copy of the .po help files?
I am translating the LO Pootle po files and it would help me a lot if I was able to control my
work from time to time instead of waiting weeks or months.
By the way, how often is the build-in help system updated?
I am also translating GIMP which uses HTML for its help files. The clever developers of the
documentation team has created a little program creating the help files from the command "make
html-xx" where xx is the language code. So simple. (Yes, I know LO is using a quite different help
Unsubscribe instructions: E-mail to firstname.lastname@example.org
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
- [libreoffice-l10n] Re: [libreoffice-users] Making local help copy? · Tom Davies
Impressum (Legal Info)
: 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