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


HI Stephan

Em 06/03/2018 13:43, Stephan Bergmann escreveu:
On 06.03.2018 16:13, Olivier Hallot wrote:
The task looks simple: once the new help is built (--with-help=html),
the help files are available in core/instdir/help/6.1 so it must take
the 6.1/ folder and make a package, which is as simple as zipping it. Of
course, replace '6.1' by %PRODUCTVERSION.

Looks odd to me that the help content would be stored in the LO instset
under a %PRODUCTVERSION dir.  Any given LO instset will only contain
help content for the given LO version, anyway, I assume?

It was originally designed for online display, where many LOHelp
versions are hosted in the same server, and the version is passed as
param in the URL by LO.



(If, for example, some subset of the help content would happen to remain
identical across two subsequent LO versions, then intelligent update
processes could exploit that and leave that part of the LO installation
alone.  If, however, there is an artificial difference because of a path
change from .../6.1/... to .../6.2/..., that only makes the intelligent
update process's job harder.)

The version can be removed from the path (need a hack in the XSLT).
Please advise if this is to be done.

Thanks for the comments

-- 
Olivier Hallot
LibreOffice Documentation Coordinator
Comunidade LibreOffice
Rio de Janeiro - Brasil - Local Time: UTC-03:00
http://tdf.io/joinus

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.