<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.openoffice.devel.xml">
    <title>gmane.comp.openoffice.devel.xml</title>
    <link>http://blog.gmane.org/gmane.comp.openoffice.devel.xml</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2857"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2856"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2855"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2854"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2853"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2852"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2851"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2850"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2849"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2848"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2847"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2846"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2845"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2844"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2843"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2842"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2841"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2840"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2839"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2838"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2857">
    <title>Invitation to connect on LinkedIn</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2857</link>
    <description>&lt;pre&gt;I'd like to add you to my professional network on LinkedIn.

- Hirano

Hirano Kazunari
I18n/L10n Community Contributor at OpenSolaris
Japan

Confirm that you know Hirano Kazunari:
https://www.linkedin.com/e/-vbc24i-gt47wzm7-3h/isd/4381515296/Q_q8FKMT/?hs=false&amp;amp;tok=3RxAYmTuv2-QU1

--
You are receiving Invitation to Connect emails. Click to unsubscribe:
http://www.linkedin.com/e/-vbc24i-gt47wzm7-3h/dFaWMWH_2q4wAFQYOVdeyNnl0-_w33OuR0D/goo/dev%40xml%2Eopenoffice%2Eorg/20061/I1517856227_1/?hs=false&amp;amp;tok=29oYt5vgL2-QU1

(c) 2011 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.
&lt;/pre&gt;</description>
    <dc:creator>Hirano Kazunari</dc:creator>
    <dc:date>2011-09-28T11:14:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2856">
    <title>Re: Re: Good News For UOF Project</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2856</link>
    <description>&lt;pre&gt;
Harold:

http://en.wikipedia.org/wiki/Uniform_Office_Format

TomW
&lt;/pre&gt;</description>
    <dc:creator>TomW</dc:creator>
    <dc:date>2010-12-07T02:23:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2855">
    <title>Re: Good News For UOF Project</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2855</link>
    <description>&lt;pre&gt;
"anhongyun" &amp;lt;anhongyun&amp;lt; at &amp;gt;redoffice.com&amp;gt; wrote in message 
news:201011091736457638298&amp;lt; at &amp;gt;redoffice.com...
Congratulations. Now, what is UOF?

&lt;/pre&gt;</description>
    <dc:creator>Harold Fuchs</dc:creator>
    <dc:date>2010-11-09T09:46:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2854">
    <title>Good News For UOF Project</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2854</link>
    <description>&lt;pre&gt;hello everyone:

Here is a  good news: we have created the UOF project, uof.openoffice.org.

If you are interested in it,please pay close attention to this.
Welcome to UOF lists.

thank you very much!

best wishes!

2010-11-09 



anhongyun 
&lt;/pre&gt;</description>
    <dc:creator>anhongyun</dc:creator>
    <dc:date>2010-11-09T09:36:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2853">
    <title>Re: Fw: Proposal of new project for UOF</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2853</link>
    <description>&lt;pre&gt;
UOF is a Chinese document format,Promote it is conducive to the promotion things cultural exchanges and I hope in the future to have more Chinese people into the OOo to participate in them.

I strongly support and I will also spare no effort in this project.




温搏
2010-11-03



发件人： anhongyun
发送时间： 2010-11-03 12:44:30
收件人： dev; dev
抄送： 
主题： [xml-dev] Proposal of new project for UOF

Hi ALL,
     UOF is a Chinese document format developed by Chinese
government and all elements of UOF with Chinese tag-name and it is
updated frequently in current period, a lots of new feature would be add
into this standard. To launch a separate project of UOF may focus on
special features of China and Chinese market, and all of office software
provider who based on OpenOffice.org in China can maintain only one
project of UOF interoperability for OpenOffice.org, and we can get the
best interoperability of UOF in China.
     *There are 2 products, RedOffice&amp;amp;   CS2C, based OpenOffice.org
have supported UOF format.
     *And IBM Symphony has supported UOF too.
     *Several universities are also focus on UOF, OOXML and ODF
converters.
Proposal of UOF Interoperability Project
Summary
     UOF is a Chinese developed open standard for 'office'
applications. It includes word processing, presentation, and spreadsheet
modules, and is made up of GUI, API, and format specifications. The
document format described uses XML contained in a compressed file
container.  This project improve the interoperability of UOF, include
all features, GUI and API and solve the problems in Chinese office
application system.
     UOF is not in same structure of ODF, some features(such as
Media Object and Conditional format of Spreadsheet ) can not transform
well only with XSLT, so we need to develop a set of extensions to
transform them into a friendly structure first. For UOF API we must bind
a bundle of interfaces and services on OpenOffice.org in order to
OpenOffice.org can be integrated into office system with UOF API.
The mission of this project is improving the interoperability of
UOF.We're going in for transforming the format between UOF and ODF with
XSLT.There's an UOF filter including an extension to solve some
very important problems with Calc and OLE.
Scope
1.To develop and maintain the filters for every UOF version. Include
XSLT template and a set extensions.
2.To develop and maintain all IDL and services of  UOF APIs
3.To Implement the Chinese special features of UOF in OpenOffice.org
4.To collect the suggestions on UOF from community and participate in
editing of UOF
5.To propose the special features of ODF to UOF community
  
     We will open all XSLT and filter(now as a extension) source
code we have done. And to work on new version of UOF with all contributors.
     Now we are working on transforming the format between UOF2.0
and ODF with XSLT stylesheet, and the new features about media object.
     UOF2.0 is multiple documents construction and will be a kind of
compression format. Each document is a XML file using  Chinese tags. The 
other documents are the multimedia objects such as media files,image files and so
 on. We should convert all documents into a FlatXML which could present all tags
of different documents,and then convert the FlatXML file into ODF with
XSLT stylesheet. And in the other conversion direction ,firstly,ODF will
be converted into multiple documents with XSLT stylesheet,and then the
multiple documents will be packed into UOF2.0 format.
Best regards!
&lt;/pre&gt;</description>
    <dc:creator>温搏</dc:creator>
    <dc:date>2010-11-03T07:28:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2852">
    <title>Re: Proposal of new project for UOF</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2852</link>
    <description>&lt;pre&gt;Glad to hear this good news. 
And I am looking farward for to see this project.


Best regards!


Hua Shuran
  
System Analyst

Beijing Redflag Chinese 2000 Software Co., Ltd.
Building No.2, Block A, Huilongsen, 18 Xihuan Nanlu
Beijing Economic-Technological Development Area
100176 Beijing - P.R.China
Tel: +86-10-51570010 ext.6139
e-mail： huashuran&amp;lt; at &amp;gt;RedOffice.com
http://www.RedOffice.com




发件人： anhongyun
发送时间： 2010-11-03 12:44:30
收件人： dev; dev
抄送： 
主题： [xml-dev] Proposal of new project for UOF

Hi ALL,
     UOF is a Chinese document format developed by Chinese
government and all elements of UOF with Chinese tag-name and it is
updated frequently in current period, a lots of new feature would be add
into this standard. To launch a separate project of UOF may focus on
special features of China and Chinese market, and all of office software
provider who based on OpenOffice.org in China can maintain only one
project of UOF interoperability for OpenOffice.org, and we can get the
best interoperability of UOF in China.
     *There are 2 products, RedOffice&amp;amp;   CS2C, based OpenOffice.org
have supported UOF format.
     *And IBM Symphony has supported UOF too.
     *Several universities are also focus on UOF, OOXML and ODF
converters.
Proposal of UOF Interoperability Project
Summary
     UOF is a Chinese developed open standard for 'office'
applications. It includes word processing, presentation, and spreadsheet
modules, and is made up of GUI, API, and format specifications. The
document format described uses XML contained in a compressed file
container.  This project improve the interoperability of UOF, include
all features, GUI and API and solve the problems in Chinese office
application system.
     UOF is not in same structure of ODF, some features(such as
Media Object and Conditional format of Spreadsheet ) can not transform
well only with XSLT, so we need to develop a set of extensions to
transform them into a friendly structure first. For UOF API we must bind
a bundle of interfaces and services on OpenOffice.org in order to
OpenOffice.org can be integrated into office system with UOF API.
The mission of this project is improving the interoperability of
UOF.We're going in for transforming the format between UOF and ODF with
XSLT.There's an UOF filter including an extension to solve some
very important problems with Calc and OLE.
Scope
1.To develop and maintain the filters for every UOF version. Include
XSLT template and a set extensions.
2.To develop and maintain all IDL and services of  UOF APIs
3.To Implement the Chinese special features of UOF in OpenOffice.org
4.To collect the suggestions on UOF from community and participate in
editing of UOF
5.To propose the special features of ODF to UOF community
  
     We will open all XSLT and filter(now as a extension) source
code we have done. And to work on new version of UOF with all contributors.
     Now we are working on transforming the format between UOF2.0
and ODF with XSLT stylesheet, and the new features about media object.
     UOF2.0 is multiple documents construction and will be a kind of
compression format. Each document is a XML file using  Chinese tags. The 
other documents are the multimedia objects such as media files,image files and so
 on. We should convert all documents into a FlatXML which could present all tags
of different documents,and then convert the FlatXML file into ODF with
XSLT stylesheet. And in the other conversion direction ,firstly,ODF will
be converted into multiple documents with XSLT stylesheet,and then the
multiple documents will be packed into UOF2.0 format.
Best regards!
&lt;/pre&gt;</description>
    <dc:creator>滑淑然</dc:creator>
    <dc:date>2010-11-03T06:33:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2851">
    <title>Re: Proposal of new project for UOF</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2851</link>
    <description>&lt;pre&gt;That seems  a good news to ODF and UOF,especialy the user of ODF and UOF . And I will focus on this project.
Many thanks!


2010-11-03 



chenhao 



发件人： anhongyun
发送时间： 2010-11-03 12:44:30
收件人： dev; dev
抄送： 
主题： [xml-dev] Proposal of new project for UOF

Hi ALL,
     UOF is a Chinese document format developed by Chinese
government and all elements of UOF with Chinese tag-name and it is
updated frequently in current period, a lots of new feature would be add
into this standard. To launch a separate project of UOF may focus on
special features of China and Chinese market, and all of office software
provider who based on OpenOffice.org in China can maintain only one
project of UOF interoperability for OpenOffice.org, and we can get the
best interoperability of UOF in China.
     *There are 2 products, RedOffice&amp;amp;   CS2C, based OpenOffice.org
have supported UOF format.
     *And IBM Symphony has supported UOF too.
     *Several universities are also focus on UOF, OOXML and ODF
converters.
Proposal of UOF Interoperability Project
Summary
     UOF is a Chinese developed open standard for 'office'
applications. It includes word processing, presentation, and spreadsheet
modules, and is made up of GUI, API, and format specifications. The
document format described uses XML contained in a compressed file
container.  This project improve the interoperability of UOF, include
all features, GUI and API and solve the problems in Chinese office
application system.
     UOF is not in same structure of ODF, some features(such as
Media Object and Conditional format of Spreadsheet ) can not transform
well only with XSLT, so we need to develop a set of extensions to
transform them into a friendly structure first. For UOF API we must bind
a bundle of interfaces and services on OpenOffice.org in order to
OpenOffice.org can be integrated into office system with UOF API.
The mission of this project is improving the interoperability of
UOF.We're going in for transforming the format between UOF and ODF with
XSLT.There's an UOF filter including an extension to solve some
very important problems with Calc and OLE.
Scope
1.To develop and maintain the filters for every UOF version. Include
XSLT template and a set extensions.
2.To develop and maintain all IDL and services of  UOF APIs
3.To Implement the Chinese special features of UOF in OpenOffice.org
4.To collect the suggestions on UOF from community and participate in
editing of UOF
5.To propose the special features of ODF to UOF community
  
     We will open all XSLT and filter(now as a extension) source
code we have done. And to work on new version of UOF with all contributors.
     Now we are working on transforming the format between UOF2.0
and ODF with XSLT stylesheet, and the new features about media object.
     UOF2.0 is multiple documents construction and will be a kind of
compression format. Each document is a XML file using  Chinese tags. The 
other documents are the multimedia objects such as media files,image files and so
 on. We should convert all documents into a FlatXML which could present all tags
of different documents,and then convert the FlatXML file into ODF with
XSLT stylesheet. And in the other conversion direction ,firstly,ODF will
be converted into multiple documents with XSLT stylesheet,and then the
multiple documents will be packed into UOF2.0 format.
Best regards!
&lt;/pre&gt;</description>
    <dc:creator>chenhao</dc:creator>
    <dc:date>2010-11-03T06:22:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2850">
    <title>Proposal of new project for UOF</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2850</link>
    <description>&lt;pre&gt;Hi ALL,
     UOF is a Chinese document format developed by Chinese
government and all elements of UOF with Chinese tag-name and it is
updated frequently in current period, a lots of new feature would be add
into this standard. To launch a separate project of UOF may focus on
special features of China and Chinese market, and all of office software
provider who based on OpenOffice.org in China can maintain only one
project of UOF interoperability for OpenOffice.org, and we can get the
best interoperability of UOF in China.
     *There are 2 products, RedOffice&amp;amp;   CS2C, based OpenOffice.org
have supported UOF format.
     *And IBM Symphony has supported UOF too.
     *Several universities are also focus on UOF, OOXML and ODF
converters.
Proposal of UOF Interoperability Project
Summary
     UOF is a Chinese developed open standard for 'office'
applications. It includes word processing, presentation, and spreadsheet
modules, and is made up of GUI, API, and format specifications. The
document format described uses XML contained in a compressed file
container.  This project improve the interoperability of UOF, include
all features, GUI and API and solve the problems in Chinese office
application system.
     UOF is not in same structure of ODF, some features(such as
Media Object and Conditional format of Spreadsheet ) can not transform
well only with XSLT, so we need to develop a set of extensions to
transform them into a friendly structure first. For UOF API we must bind
a bundle of interfaces and services on OpenOffice.org in order to
OpenOffice.org can be integrated into office system with UOF API.
The mission of this project is improving the interoperability of
UOF.We're going in for transforming the format between UOF and ODF with
XSLT.There's an UOF filter including an extension to solve some
very important problems with Calc and OLE.
Scope
1.To develop and maintain the filters for every UOF version. Include
XSLT template and a set extensions.
2.To develop and maintain all IDL and services of  UOF APIs
3.To Implement the Chinese special features of UOF in OpenOffice.org
4.To collect the suggestions on UOF from community and participate in
editing of UOF
5.To propose the special features of ODF to UOF community
  
     We will open all XSLT and filter(now as a extension) source
code we have done. And to work on new version of UOF with all contributors.
     Now we are working on transforming the format between UOF2.0
and ODF with XSLT stylesheet, and the new features about media object.
     UOF2.0 is multiple documents construction and will be a kind of
compression format. Each document is a XML file using  Chinese tags. The 
other documents are the multimedia objects such as media files,image files and so
 on. We should convert all documents into a FlatXML which could present all tags
of different documents,and then convert the FlatXML file into ODF with
XSLT stylesheet. And in the other conversion direction ,firstly,ODF will
be converted into multiple documents with XSLT stylesheet,and then the
multiple documents will be packed into UOF2.0 format.
Best regards!
&lt;/pre&gt;</description>
    <dc:creator>anhongyun</dc:creator>
    <dc:date>2010-11-03T04:44:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2849">
    <title>Re: store additional data in oo xml file</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2849</link>
    <description>&lt;pre&gt;
hi Oliver,

the ODF package is basically a ZIP file, so you can add arbitrary files to
it, even in subdirectories (well, with the exception that there are some
reserved names...).

in contrast with ordinary ZIP files, an ODF package contains a file
META-INF/manifest.xml.
every file that is in the package must have an entry in the manifest.xml.
ZIP files that do not have an entry in manifest.xml will be ignored by
OOo; actually iirc in newer versions OOo may even refuse to open an ODF
file if it has a ZIP entry without matching manifest.xml entry.

regards,
 michael

&lt;/pre&gt;</description>
    <dc:creator>Michael Stahl</dc:creator>
    <dc:date>2010-09-30T09:42:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2848">
    <title>store additional data in oo xml file</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2848</link>
    <description>&lt;pre&gt;Hi,

is there a legal way to place custom data into an oo file ?
for example adding a folder with files "custom\test.txt" to an *.ott file ?

i noticed such data will be removed on saving the file...

regards

Oliver

&lt;/pre&gt;</description>
    <dc:creator>Oliver Brinzing</dc:creator>
    <dc:date>2010-09-29T14:46:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2847">
    <title>xforms list menu submission failure</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2847</link>
    <description>&lt;pre&gt;Readers,

I have created a basic xform, but the submission behaviour is broken.
Below is the content.xml file and the submission output file. Please
advise what is my error or if there is a bug with writer.

&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;
&amp;lt;office:document-content
xmlns:office="urn:oasis:names:tc:opendocument:xmlns:office:1.0"
xmlns:style="urn:oasis:names:tc:opendocument:xmlns:style:1.0"
xmlns:text="urn:oasis:names:tc:opendocument:xmlns:text:1.0"
xmlns:table="urn:oasis:names:tc:opendocument:xmlns:table:1.0"
xmlns:draw="urn:oasis:names:tc:opendocument:xmlns:drawing:1.0"
xmlns:fo="urn:oasis:names:tc:opendocument:xmlns:xsl-fo-compatible:1.0"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:meta="urn:oasis:names:tc:opendocument:xmlns:meta:1.0"
xmlns:number="urn:oasis:names:tc:opendocument:xmlns:datastyle:1.0"
xmlns:svg="urn:oasis:names:tc:opendocument:xmlns:svg-compatible:1.0"
xmlns:chart="urn:oasis:names:tc:opendocument:xmlns:chart:1.0"
xmlns:dr3d="urn:oasis:names:tc:opendocument:xmlns:dr3d:1.0"
xmlns:math="http://www.w3.org/1998/Math/MathML"
xmlns:form="urn:oasis:names:tc:opendocument:xmlns:form:1.0"
xmlns:script="urn:oasis:names:tc:opendocument:xmlns:script:1.0"
xmlns:ooo="http://openoffice.org/2004/office"
xmlns:ooow="http://openoffice.org/2004/writer"
xmlns:oooc="http://openoffice.org/2004/calc"
xmlns:dom="http://www.w3.org/2001/xml-events"
xmlns:xforms="http://www.w3.org/2002/xforms"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:rpt="http://openoffice.org/2005/report"
xmlns:of="urn:oasis:names:tc:opendocument:xmlns:of:1.2"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns:grddl="http://www.w3.org/2003/g/data-view#"
xmlns:field="urn:openoffice:names:experimental:ooo-ms-interop:xmlns:field:1.0"
office:version="1.2"
grddl:transformation="http://docs.oasis-open.org/office/1.2/xslt/odf2rdf.xsl"&amp;gt;&amp;lt;office:scripts/&amp;gt;&amp;lt;office:font-face-decls&amp;gt;&amp;lt;style:font-face
style:name="Liberation Serif" svg:font-family="&amp;amp;apos;Liberation
Serif&amp;amp;apos;" style:font-family-generic="roman"
style:font-pitch="variable"/&amp;gt;&amp;lt;style:font-face style:name="Liberation
Sans" svg:font-family="&amp;amp;apos;Liberation Sans&amp;amp;apos;"
style:font-family-generic="swiss"
style:font-pitch="variable"/&amp;gt;&amp;lt;style:font-face style:name="DejaVu Sans"
svg:font-family="&amp;amp;apos;DejaVu Sans&amp;amp;apos;"
style:font-family-generic="system"
style:font-pitch="variable"/&amp;gt;&amp;lt;/office:font-face-decls&amp;gt;&amp;lt;office:automatic-styles&amp;gt;&amp;lt;style:style
style:name="P1" style:family="paragraph"&amp;gt;&amp;lt;style:paragraph-properties
fo:text-align="start"/&amp;gt;&amp;lt;/style:style&amp;gt;&amp;lt;style:style style:name="P2"
style:family="paragraph"&amp;gt;&amp;lt;style:paragraph-properties
fo:text-align="center"/&amp;gt;&amp;lt;/style:style&amp;gt;&amp;lt;style:style style:name="gr1"
style:family="graphic"&amp;gt;&amp;lt;style:graphic-properties fo:border="solid
#c0c0c0" style:wrap="run-through"
style:number-wrapped-paragraphs="no-limit" style:vertical-pos="middle"
style:vertical-rel="line" style:horizontal-pos="from-left"
style:horizontal-rel="paragraph"
draw:wrap-influence-on-position="once-concurrent"
style:flow-with-text="false"/&amp;gt;&amp;lt;/style:style&amp;gt;&amp;lt;style:style
style:name="gr2" style:family="graphic"&amp;gt;&amp;lt;style:graphic-properties
style:wrap="run-through" style:number-wrapped-paragraphs="no-limit"
style:vertical-pos="middle" style:vertical-rel="line"
style:horizontal-pos="from-left" style:horizontal-rel="paragraph"
draw:wrap-influence-on-position="once-concurrent"
style:flow-with-text="false"/&amp;gt;&amp;lt;/style:style&amp;gt;&amp;lt;/office:automatic-styles&amp;gt;&amp;lt;office:body&amp;gt;&amp;lt;office:text&amp;gt;&amp;lt;office:forms
form:automatic-focus="false"
form:apply-design-mode="false"&amp;gt;&amp;lt;xforms:model&amp;gt;&amp;lt;xforms:instance&amp;gt;&amp;lt;purpose&amp;gt;
                                                       &amp;lt;analysis
value="ewbrl"&amp;gt;epc england&amp;lt;/analysis&amp;gt;
                                                       &amp;lt;analysis
value="sbrl"&amp;gt;epc scotland
                                                       &amp;lt;/analysis&amp;gt;

&amp;lt;/purpose&amp;gt;&amp;lt;/xforms:instance&amp;gt;&amp;lt;xforms:bind id="analysis"
nodeset="analysis" type="xsd:string"/&amp;gt;&amp;lt;xforms:submission
id="savepagegeneralinformation" bind="analysis"
action="file://~/tmp/testsubmit.xml" method="put" indent="false"
omit-xml-declaration="false" standalone="false"
replace="instance"/&amp;gt;&amp;lt;xsd:schema/&amp;gt;&amp;lt;/xforms:model&amp;gt;&amp;lt;form:form
form:name="Standard" form:apply-filter="true"
form:command-type="table"
form:control-implementation="ooo:com.sun.star.form.component.Form"
office:target-frame="" xlink:href=""&amp;gt;&amp;lt;form:listbox form:name="List Box
1" form:control-implementation="ooo:com.sun.star.form.component.ListBox"
form:id="control1" form:dropdown="true" form:size="20"
form:bound-column="1" xforms:bind="analysis"
form:xforms-list-source="analysis"&amp;gt;&amp;lt;form:properties&amp;gt;&amp;lt;form:property
form:property-name="DefaultControl" office:value-type="string"
office:string-value="com.sun.star.form.control.ListBox"/&amp;gt;&amp;lt;form:list-property
form:property-name="DefaultSelection"
office:value-type="float"/&amp;gt;&amp;lt;/form:properties&amp;gt;&amp;lt;/form:listbox&amp;gt;&amp;lt;form:button
form:name="save page button"
form:control-implementation="ooo:com.sun.star.form.component.CommandButton"
form:id="control2" form:label="save this page"
form:button-type="submit" office:target-frame="" xlink:href=""
form:image-data="" form:xforms-submission="savepagegeneralinformation"
form:delay-for-repeat="PT0.50S"
form:image-position="center"&amp;gt;&amp;lt;form:properties&amp;gt;&amp;lt;form:property
form:property-name="DefaultControl" office:value-type="string"
office:string-value="com.sun.star.form.control.CommandButton"/&amp;gt;&amp;lt;/form:properties&amp;gt;&amp;lt;/form:button&amp;gt;&amp;lt;/form:form&amp;gt;&amp;lt;/office:forms&amp;gt;&amp;lt;text:sequence-decls&amp;gt;&amp;lt;text:sequence-decl
text:display-outline-level="0"
text:name="Illustration"/&amp;gt;&amp;lt;text:sequence-decl
text:display-outline-level="0" text:name="Table"/&amp;gt;&amp;lt;text:sequence-decl
text:display-outline-level="0" text:name="Text"/&amp;gt;&amp;lt;text:sequence-decl
text:display-outline-level="0"
text:name="Drawing"/&amp;gt;&amp;lt;/text:sequence-decls&amp;gt;&amp;lt;text:p
text:style-name="Standard"&amp;gt;General information&amp;lt;/text:p&amp;gt;&amp;lt;text:p
text:style-name="Standard"/&amp;gt;&amp;lt;text:p text:style-name="Standard"&amp;gt;Purpose
of analysis: &amp;lt;draw:control text:anchor-type="as-char" draw:z-index="0"
draw:style-name="gr1" draw:text-style-name="P1" svg:width="4.543cm"
svg:height="0.809cm" draw:control="control1"/&amp;gt; &amp;lt;/text:p&amp;gt;&amp;lt;text:p
text:style-name="Standard"/&amp;gt;&amp;lt;text:p
text:style-name="Standard"&amp;gt;&amp;lt;draw:control text:anchor-type="as-char"
draw:z-index="1" draw:style-name="gr2" draw:text-style-name="P2"
svg:width="3.497cm" svg:height="0.809cm" draw:control="control2"/&amp;gt;
&amp;lt;/text:p&amp;gt;&amp;lt;/office:text&amp;gt;&amp;lt;/office:body&amp;gt;&amp;lt;/office:document-content&amp;gt;

&amp;lt;?xml version="1.0"?&amp;gt;
&amp;lt;analysis value="ewbrl"&amp;gt;epc scotland
                                                       &amp;lt;/analysis&amp;gt;
&amp;lt;?xml version="1.0"?&amp;gt;
&amp;lt;analysis value="sbrl"&amp;gt;epc scotland
                                                       &amp;lt;/analysis&amp;gt;
&lt;/pre&gt;</description>
    <dc:creator>e-letter</dc:creator>
    <dc:date>2010-09-23T11:48:18</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2846">
    <title>Re: [dev] Proposal of new project for UOF</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2846</link>
    <description>&lt;pre&gt;Hi Li Heng,

this is indeed good news. I'm sure, that will make OOo even more 
successful, especially in the Chinese market, of course. :-)

Best regards,
Peter

LiHeng wrote:
&lt;/pre&gt;</description>
    <dc:creator>Peter Junge</dc:creator>
    <dc:date>2010-07-08T07:53:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2845">
    <title>Re: [dev] Proposal of new project for UOF</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2845</link>
    <description>&lt;pre&gt;+1
I think the UOF project will strengthen the OOo adoption in the Chinese 
market.

- Dieter


On 07.07.10 08:03, LiHeng wrote:
&lt;/pre&gt;</description>
    <dc:creator>Dieter Loeschky</dc:creator>
    <dc:date>2010-07-08T07:11:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2844">
    <title>Proposal of new project for UOF</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2844</link>
    <description>&lt;pre&gt;Hi ALL,

     UOF is a Chinese document format developed by Chinese
government and all elements of UOF with Chinese tag-name and it is
updated frequently in current period, a lots of new feature would be add
into this standard. To launch a separate project of UOF may focus on
special features of China and Chinese market, and all of office software
provider who based on OpenOffice.org in China can maintain only one
project of UOF interoperability for OpenOffice.org, and we can get the
best interoperability of UOF in China.
     *There are 2 products, RedOffice&amp;amp;   CS2C, based OpenOffice.org
have supported UOF format.
     *And IBM Symphony has supported UOF too.
     *Several universities are also focus on UOF, OOXML and ODF
converters.

Proposal of UOF Interoperability Project
Summary
     UOF is a Chinese developed open standard for 'office'
applications. It includes word processing, presentation, and spreadsheet
modules, and is made up of GUI, API, and format specifications. The
document format described uses XML contained in a compressed file
container.  This project improve the interoperability of UOF, include
all features, GUI and API and solve the problems in Chinese office
application system.
     UOF is not in same structure of ODF, some features(such as
Media Object and Conditional format of Spreadsheet ) can not transform
well only with XSLT, so we need to develop a set of extensions to
transform them into a friendly structure first. For UOF API we must bind
a bundle of interfaces and services on OpenOffice.org in order to
OpenOffice.org can be integrated into office system with UOF API.
The mission of this project is improving the interoperability of
UOF.We're going in for transforming the format between UOF and ODF with
XSLT.There's an UOF filter including an extension to solve some
very important problems with Calc and OLE.

Scope
1.To develop and maintain the filters for every UOF version. Include
XSLT template and a set extensions.
2.To develop and maintain all IDL and services of  UOF APIs
3.To Implement the Chinese special features of UOF in OpenOffice.org
4.To collect the suggestions on UOF from community and participate in
editing of UOF

     We will open all XSLT and filter(now as a extension) source
code we have done. And to work on new version of UOF with all contributors.
     Now we are working on transforming the format between UOF2.0
and ODF with XSLT stylesheet, and the new features about media object.
     UOF2.0 is multiple documents construction and will be a kind of
compression format. Each document is a XML file using  Chinese tags.  We
should convert all documents into a FlatXML which could present all tags
of different documents,and then convert the FlatXML file into ODF with
XSLT stylesheet. And in the other conversion direction ,firstly,ODF will
be converted into multiple documents with XSLT stylesheet,and then the
multiple documents will be packed into UOF2.0 format.

Best regards!
&lt;/pre&gt;</description>
    <dc:creator>LiHeng</dc:creator>
    <dc:date>2010-07-07T06:03:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2843">
    <title>Re: odf2xhtml</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2843</link>
    <description>&lt;pre&gt;
Thank you for doing so!


In theory, yes, but the version of the Saxon processor that is free 
is not schema-aware.  A conformant XSLT processor is allowed not to 
be schema-aware.


That last one is an important one for my work with OOo.  But I know 
the OOo team is working on a couple of issues I've submitted to 
improve how robust this is in real-world deployment.


Unfortunately not necessarily, as some writers of XML filters may 
have used Saxon extension functions rather than stick solely to the 
XPath function library.  These filters will not work when 
saxon9he.jar (the currently-available free version) is switched for 
the existing saxon9.jar (getting long in the tooth).

But I believe OOo only "advertised" support for XSLT 2, which means 
users going beyond that definition did so at their own risk.

I hope this is helpful.

. . . . . . . . . . . . Ken


--
XSLT/XQuery training:         San Carlos, California 2010-04-26/30
Principles of XSLT for XQuery Writers: San Francisco,CA 2010-05-03
XSLT/XQuery training:                 Ottawa, Canada 2010-05-10/14
XSLT/XQuery/UBL/Code List training: Trondheim,Norway 2010-06-02/11
Vote for your XML training:   http://www.CraneSoftwrights.com/i/i/
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/i/
G. Ken Holman                 mailto:gkholman&amp;lt; at &amp;gt;CraneSoftwrights.com
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/i/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal
&lt;/pre&gt;</description>
    <dc:creator>G. Ken Holman</dc:creator>
    <dc:date>2010-04-12T12:02:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2842">
    <title>Re: odf2xhtml</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2842</link>
    <description>&lt;pre&gt;Hey all,

well I can clearly see that I'm not the top XSLT 2 experts in the
discussion here :) But I think even I can point out several of the
main advantages of switching to 2.0:
* updated data model with sequences and atomic types. No more result
tree fragments and need for node-set()
* schema-aware (variable definitions with XML schema data types or
import of schema)
* loads of new constructs, functions and more convenient operators (in
XPath 2.0)
* multiple result documents

Quite good description here: http://www.altova.com/XSLT_XPath_2.html

If Saxon is already included, then it switching should be a piece of
cake, right?


Martynas
odt2epub.com

On Fri, Apr 9, 2010 at 6:32 PM, Dave Pawson &amp;lt;dave.pawson&amp;lt; at &amp;gt;gmail.com&amp;gt; wrote:
&lt;/pre&gt;</description>
    <dc:creator>Martynas Jusevicius</dc:creator>
    <dc:date>2010-04-12T11:42:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2841">
    <title>RE: odf2xhtml</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2841</link>
    <description>&lt;pre&gt;
I was never bitten by any nasty bug with Saxon-B but of course
that's just me. What I'm wondering, though, is whether it is
desirable to have some obscure corner-case bugs solved (small
benefit) at the expense of parting with saxon proprietary
extensions (big cost)?



Temporary trees + modes are a maintenance nightmare: I know, I've
been there. But often, Saxon extensions have a way of making it
into the spec... any hope here?

 

Well, that's a way of looking at the problem, I suppose. Another way
is to say that I'm not, as of this moment, in any kind of situation;
I may have a problem in the distant future -- if:
- I don't find a solution when (if) the problem does arise
- my users have an irrepressible urge to upgrade OOo (and one lets them)
- etc.

In other words, I still think using next-in-chain in this particular
context was very much worth it. As always, YMMV ;-)

Regards,
EB
&lt;/pre&gt;</description>
    <dc:creator>Emmanuel Begue</dc:creator>
    <dc:date>2010-04-09T17:49:10</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2840">
    <title>Re: odf2xhtml</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2840</link>
    <description>&lt;pre&gt;

+1
Some of the oddities that we thought handy are now 'to be paid for'
according to the saxon tax.




+1.

We shouldn't have done it in the first place. Sigh

Even without the extensions, xslt 2.0 is well worth the switch.
Lots of extra functionality that makes complex transformations
that much more easy.

regards



&lt;/pre&gt;</description>
    <dc:creator>Dave Pawson</dc:creator>
    <dc:date>2010-04-09T16:32:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2839">
    <title>RE: odf2xhtml</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2839</link>
    <description>&lt;pre&gt;
My understanding is "has to" because the version of Saxon that 
supports functions costs money, and I don't see OOo putting in 
anything that costs money.

If OOo stayed with saxon9.jar then any faults/improvements would not 
be addressed.


Temporary trees, imported stylesheets and modes ... though admittedly 
not nearly as convenient as "next-in-chain".

But using extensions at any time is risky.  I underscore that in my 
class.  I might start citing your predicament as another example of 
why.  I have three public classes coming up in the next three months 
and I'll see what students have to say about the situation in which 
you find yourself.

. . . . . . . . . . . . Ken


--
XSLT/XQuery training:         San Carlos, California 2010-04-26/30
Principles of XSLT for XQuery Writers: San Francisco,CA 2010-05-03
XSLT/XQuery training:                 Ottawa, Canada 2010-05-10/14
XSLT/XQuery/UBL/Code List training: Trondheim,Norway 2010-06-02/11
Vote for your XML training:   http://www.CraneSoftwrights.com/i/i/
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/i/
G. Ken Holman                 mailto:gkholman&amp;lt; at &amp;gt;CraneSoftwrights.com
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/i/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal
&lt;/pre&gt;</description>
    <dc:creator>G. Ken Holman</dc:creator>
    <dc:date>2010-04-09T16:14:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2838">
    <title>RE: odf2xhtml</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2838</link>
    <description>&lt;pre&gt;Hello,


What does it mean that "the new OpenOffice 3" _has_ to use Saxon HE?
- "new OOo 3": starting with which version?
- "has to": legally? or just "will use", or "may use"...?


I was nearly as careful but not perfectly: I use (extensively)
saxon:next-in-chain to chain stylesheets and have a more
modular code.

What would be the alternative to saxon:next-in-chain when
using Saxon HE?

Thanks,
Regards,
EB
&lt;/pre&gt;</description>
    <dc:creator>Emmanuel Begue</dc:creator>
    <dc:date>2010-04-09T16:08:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2837">
    <title>Re: odf2xhtml</title>
    <link>http://permalink.gmane.org/gmane.comp.openoffice.devel.xml/2837</link>
    <description>&lt;pre&gt;Thanks, for development I was using Saxon9.jar on flat ODF and never noticed that.
--Gannon

--- On Fri, 4/9/10, G. Ken Holman &amp;lt;gkholman&amp;lt; at &amp;gt;CraneSoftwrights.com&amp;gt; wrote:



      
&lt;/pre&gt;</description>
    <dc:creator>Gannon Dick</dc:creator>
    <dc:date>2010-04-09T15:35:29</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.openoffice.devel.xml">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.openoffice.devel.xml</link>
  </textinput>
</rdf:RDF>

