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


Hi,
just thinking loud (hope it is not too loud): is it possible to* make help
packs into extensions* (oxt files)? Could this also be done with the
lang-packs?

The benefits:
- *smaller file size*: extensions are great, because they are not
executables and all the execution/installation code already lies within
LO/OOo;
- *lower cost of building/hosting*: a help pack would need to be built just
once for all supported (and unsupported) operating systems;
- *user-friendly*: a help pack can be dropped onto Extension Manager,
double-clicked etc. It can also be downloaded at the last phase of the
installation process with an installer on Windows and Linux etc. (an
installer downloading and running another installer seems not so nice).
- *localizer-friendly*: maybe Pootle server could be extended to generate
helppacks (langpacks) daily/weekly or by demand - for testing purposes as
well as for the release purposes;

The drawbacks:
- the extension framework maybe needs to be extended a bit to support help
installation via extensions (but if needed at all that seems a reasonable
investment to me, not knowing how much work that would present :) );

Lp, m.

-- 
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***

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.