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


Hi Andras, Michael, Caolan!


I would like to share my findings.

1)

https://bugs.freedesktop.org/show_bug.cgi?id=37597 is not related to
my problem. It seems templates are checked only only one level not
recursively in the subdirs.
Maybe a fix need for it.

2) Michael, en-US forlder in added by report designer:

extensions/report-builder/registry/data/org/openoffice/Office/Paths.xcu
<node oor:name="%origin%/../../../../../template" oor:op="fuse"/>
To fix it we should change this path to
%origin%/../../../../../template/en-US/wizard

3) Related to templates path that I would like to change

The current settings are in
officecfg/registry/schema/org/openoffice/Office/Common.xcs:

<prop oor:name="Template" oor:type="oor:string-list">
  <info>
     <author>MBA</author>
     <desc>Specifies the templates originate from these folders and
sub-folders.</desc>
   </info>
  <value 
oor:separator=":">$(insturl)/share/template/$(vlang):$(insturl)/share/template:$(userurl)/template</value>


<prop oor:name="Template" oor:type="oor:string-list">
   <info>
     <desc>Specifies the default directory where all provided
templates are located in folders and sub-folders.</desc>
   </info>
   <value 
oor:separator=":">$(insturl)/share/template/$(vlang):$(insturl)/share/template:$(userurl)/template</value>

(also I did small changes in scp2 module too.

When I set "$(insturl)/share/template/$(vlang):$(insturl)/share/template/common:$(userurl)/template"
in Common.xcs I expected to Settings/Path UI comes up with all three
paths like this:
/opt/libreoffice3.4/basis3.4/share/template/hu (hu is my current UI language)
/opt/libreoffice3.4/basis3.4//share/template/common
/home/kami/.oxygenoffice/3/user/template

but I only get /home/kami/.oxygenoffice/3/user/template

Then I added as
"$(insturl)/share/template/$(vlang)/:$(insturl)/share/template/common/:$(userurl)/template/",
so I  closed I path with "/". then I get this
/opt/libreoffice3.4/basis3.4/share/template/hu (hu is my current UI language)
/opt/libreoffice3.4/basis3.4//share/template/common
/home/kami/.oxygenoffice/3/user/template
/home/kami/.oxygenoffice/3/user/template

So are we confident about leaving closing "/"is the good practice?

So finally I tested with:

  <value 
oor:separator=":">$(insturl)/share/template/$(vlang)/:$(insturl)/share/template/common</value>

And I got the desired path settings:
/opt/libreoffice3.4/basis3.4/share/template/hu (hu is my current UI language)
/opt/libreoffice3.4/basis3.4//share/template/common
/home/kami/.oxygenoffice/3/user/template

What is your opinion? Why closing "/" matters? Can I commit patch for
it in master? Then I would like to get it to 3-4 if this is the good
behavior.

Regards,
KAMI




2011/5/26 Andras Timar <timar74@gmail.com>:
Hi KAMI,

2011/5/26 KAMI911 KAMI911 <kami911@gmail.com>:
Hi Andras!

Thank you for your answer. I will test on master (currently I have
Linux only) Is it possible to use build services for other platforms?
Using share/template folder in path creates a problem: you all subdirs
appear as empty subdir in the templates selector of File - New - From
template.
I would like to fix this issue by moving language independent fulder
to a subfolder (common) and set the path to this share/template/common
folder instead of share/template.


Have you seen this bug?
https://bugs.freedesktop.org/show_bug.cgi?id=37597
It may be related.

Regards,
Andras


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.