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


On 18/09/12 21:01, Michael Stahl wrote:
hi Stephan,

On 18/09/12 20:46, Libreoffice Gerrit user wrote:
  officecfg/registry/cppheader.xsl      |   18 +++++++++---------
  officecfg/registry/files.mk           |    3 ++-
  sd/source/ui/remotecontrol/Server.cxx |    6 ++++--
  3 files changed, 15 insertions(+), 12 deletions(-)

New commits:
commit ee5403b98bf0e89693a14f7a1ae5658d9e5eb730
Author: Michael Stahl <mstahl@redhat.com>
Date:   Tue Sep 18 20:41:56 2012 +0200

     officecfg: generate header for Impress-sdremote, handle "-" in xcs name
this was an urgent change to fix a non-building master, to handle the
newly introduced "Office/Impress-sdremote.xcs"; but i wonder, is it
perhaps intentional that schema files aren't allowed to have "-" in
their names, considering that there are a bunch of .xcu files with names
like Foo-bar.xcu where a Foo.xcs exists; should the
Office/Impress-sdremote.xcs simply be renamed instead, and the xslt
change reverted?
I should mention that the new config file fails to work (NoSuchElementException trying to access the config): while trying to fix it I renamed to ImpressSdRemote.xcs (which didn't fix things, but fits in better with the general naming scheme -- it seems that adding the file to postprocess/packregistry/makefile.mk was the key step).

I've commited the renaming, meaning the xslt changes can be reverted if needed.


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.