Assuming the licensing is ok , why don't we import this extension this
extension, make it an official extension and then start improving it.
Note that I see from a discussion on the Apache OO list that their copy if
this extension is incomplete and bits of it are lying around in another git
repo.
On Sunday, 17 August 2014, Olivier Hallot <olivier.hallot@libreoffice.org>
wrote:
Hello guys...
AFAIK we have no tool to edit the help pages for LibreOffice. The tools
scattered here and there that I tested are broken and I end up having to
edit the XML text file with great pain, limiting the possibilities to
add/improve content.
A feature with no help page is a hidden feature/secret for most users.
OTOH, discussions on a new help system are stalled, some hickups once a
while, since LO birth.
The extension I am told to investigate is HelpAuthoring.oxt, + a SUN
Help2 Reference Guide in PDF available in the net. The extenstion is
broken and debate will rise to fix it or design a new help system with
no foreseable future.
So, is there *anywhere* a version of OpenOffice.org + Helpauthoring.oxt
known to work in Linux/windows(*) that I can install and edit
LibreOffice Help pages?
Thank you
(*) W7 or Win XP
--
Olivier Hallot
Comunidade LibreOffice
http://ask.libreoffice.org/pt-br
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org <javascript:;>
http://lists.freedesktop.org/mailman/listinfo/libreoffice
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.