Invitation to connect on LinkedIn

Good News For UOF Project

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 

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&   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!
--

-- 
anhongyun

RedFlag Chinese 2000

2010-11-3

2010-11-03 

anhongyun 

store additional data in oo xml file

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

--

-- 

GnuPG key 0xCFD04A45: 8822 057F 4956 46D3 352C 1A06 4E2C AB40 CFD0 4A45

xforms list menu submission failure

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.

<?xml version="1.0" encoding="UTF-8"?>
<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"><office:scripts/><office:font-face-decls><style:font-face
style:name="Liberation Serif" svg:font-family="&apos;Liberation
Serif&apos;" style:font-family-generic="roman"
style:font-pitch="variable"/><style:font-face style:name="Liberation
Sans" svg:font-family="&apos;Liberation Sans&apos;"
style:font-family-generic="swiss"
style:font-pitch="variable"/><style:font-face style:name="DejaVu Sans"
svg:font-family="&apos;DejaVu Sans&apos;"
style:font-family-generic="system"
style:font-pitch="variable"/></office:font-face-decls><office:automatic-styles><style:style
style:name="P1" style:family="paragraph"><style:paragraph-properties
fo:text-align="start"/></style:style><style:style style:name="P2"
style:family="paragraph"><style:paragraph-properties
fo:text-align="center"/></style:style><style:style style:name="gr1"
style:family="graphic"><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"/></style:style><style:style
style:name="gr2" style:family="graphic"><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"/></style:style></office:automatic-styles><office:body><office:text><office:forms
form:automatic-focus="false"
form:apply-design-mode="false"><xforms:model><xforms:instance><purpose>
                                                       <analysis
value="ewbrl">epc england</analysis>
                                                       <analysis
value="sbrl">epc scotland
                                                       </analysis>

</purpose></xforms:instance><xforms:bind id="analysis"
nodeset="analysis" type="xsd:string"/><xforms:submission
id="savepagegeneralinformation" bind="analysis"
action="file://~/tmp/testsubmit.xml" method="put" indent="false"
omit-xml-declaration="false" standalone="false"
replace="instance"/><xsd:schema/></xforms:model><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=""><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"><form:properties><form:property
form:property-name="DefaultControl" office:value-type="string"
office:string-value="com.sun.star.form.control.ListBox"/><form:list-property
form:property-name="DefaultSelection"
office:value-type="float"/></form:properties></form:listbox><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"><form:properties><form:property
form:property-name="DefaultControl" office:value-type="string"
office:string-value="com.sun.star.form.control.CommandButton"/></form:properties></form:button></form:form></office:forms><text:sequence-decls><text:sequence-decl
text:display-outline-level="0"
text:name="Illustration"/><text:sequence-decl
text:display-outline-level="0" text:name="Table"/><text:sequence-decl
text:display-outline-level="0" text:name="Text"/><text:sequence-decl
text:display-outline-level="0"
text:name="Drawing"/></text:sequence-decls><text:p
text:style-name="Standard">General information</text:p><text:p
text:style-name="Standard"/><text:p text:style-name="Standard">Purpose
of analysis: <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"/> </text:p><text:p
text:style-name="Standard"/><text:p
text:style-name="Standard"><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"/>
</text:p></office:text></office:body></office:document-content>

<?xml version="1.0"?>
<analysis value="ewbrl">epc scotland
                                                       </analysis>
<?xml version="1.0"?>
<analysis value="sbrl">epc scotland
                                                       </analysis>

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&   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!
--

-- 

LiHeng

RedFlag Chinese 2000

Re: odf2xhtml

At 2010-04-12 13:42 +0200, Martynas Jusevicius wrote:
>I can point out several of the main advantages of switching to 2.0:

Thank you for doing so!

>* 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)

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.

>* loads of new constructs, functions and more convenient operators (in
>XPath 2.0)
>* multiple result documents

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.

>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?

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 <at> CraneSoftwrights.com
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/i/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

Saving additional style:paragraph-properties attributes

Hi,

I am new to open office development and am looking for some help/guidance on
how to save additional paragraph property attributes into an XML document.

I want to associate a security classification (e.g. "unclassified",
"restricted") with a style in Writer.
I have successfully updated the user interface to allow the setting of the
classification but now want the value to be saved/restored into the
XML document (specifically "styles.xml").

My understanding (or mis-understanding) is that this is done with property
names.

I have defined the name "SecLblClass" in
sw/source/core/unocore/
unoprnms.cxx:

       /* 0739 UNO_NAME_SECLBL_CLASS */ {MAP_CHAR_LEN("SecLblClass")},

which is mapped to the associated attribute in
sw/source/core/unocore/unomap.cxx:

       #define COMMON_CRSR_PARA_PROPERTIES_WITHOUT_FN_O1
       ...
       SW_PROP_NMID(UNO_NAME_SECLBL_CLASS), RES_PARATR_SECLBL_CLASS,
CPPUE2T(CPPUTYPE_INT16), PropertyAttribute:MAYBEVOID, 0

The attribute is defined in sw/source/core/bastyp/init.cxx:
       _InitCore()
       ...
       aAttrTab[ RES_PARATR_SECLBL_CLASS - POOLATTR_BEGIN] = new
SfxUInt16Item (RES_PARATR_SECLBL_CLASS, 0);

Then to get this attribute saved into the document, I have just added the
name to the list of paragraph properties in xmloff/source/text/txtprmap.cxx:

       aXMLParaPropMap[]
       ...
       MP_E ("SecLblClass", X841, X841_LABEL, XML_TYPE_NUMBER16, 0)

The X841 namespace is also configured and can be successfully written to the
style.xml.

However, this does not seem to be sufficient for the classification to be
written to the styles.xml.

Can anyone point me at any appropriate examples/documentation, or point out
any steps I am missing?

Thanks,

Graeme

Fw: Web Pages and Linked Meta Data

OO Writer is the word processor

--- On Tue, 3/23/10, Gannon Dick <gannon_dick <at> yahoo.com> wrote:

> From: Gannon Dick <gannon_dick <at> yahoo.com>
> Subject: Web Pages and Linked Meta Data
> To: public-egov-ig <at> w3.org
> Date: Tuesday, March 23, 2010, 5:23 PM
> When the web was young, there was a
> very good reason that HTML was structured so.  With
> just a few minutes instruction, one could produce a rich
> text web page.  Meta Data, was made optional, and
> "hidden" in a browser because it was only critical for
> engineering.  E-Mail "Full Headers" are still a mystery
> to some.  Lest we forget, Web Pages were designed to
> make certain people piles of money. This hidden headers
> model helps that process along too.  The assumption is
> that you don't own what you can't see.
> 
> Several ways of dealing with the special requirements of
> Meta Data have been developed in the meantime, RDF, RDFS,
> DC, SKOS, OWL, FOAF, etc..  Today, there is a different
> sort of "critical engineering" problem, and this time it
> affects web page authors.  The hidden header model is
> not such a good way to look at a web page any more. 
> Privacy issues lead to a reluctance to add linking data and
> the lack of connection to the abstractions OWL, SKOS etc.
> makes them less "author friendly". 
> 
> I have a word-processor to web page meta data centric model
> with an end to end validation test (by XSD). Since the
> "backbone" is HTML, the browser display is mostly unchanged.
> The document is a dctype "Dataset" the head is a
> skos:Collection of rdf:Properties and the body elements
> cite,address,abbr, etc. are all styled in a "Citation" class
> (or a "Redaction" class, because some people talk too
> much).  "Working" elements are marked as owl:sameAs to
> their respective rdf:Property or rdfs:Class, or DC Term in
> both the <head> and <body>.  This is a
> necessary first step to the solution of the Semantic Web
> Engineering problem now that Internet Web Pages are a fact.
> 
> 
> HTML 5, as proposed, uses the same basic hidden header
> document model.  And each section has particular
> instructions for conversion to RDF.  It is still
> solving the other web architecture engineering problem.
> 
> Normally I would just post this and let people find
> it.  However, since this is a fork from one of the
> earliest assumptions of the Internet ...
> 
> A fully worked example is available for the asking:
> gannon_dick AT yahoo.com
> 
> --Gannon
> 
> 
>  
> 
> 
>       
> 

      

Generic @font-family in CSS (another odf2xhtml patch)

Hey agin,

another annoyance I came across in odf2xhtml today is missing output
of generic @font-family declarations in the generated CSS.
They are described in CSS2:
http://www.w3.org/TR/CSS2/fonts.html#generic-font-families

They are also described in ODT as
style:font-face/@style:font-family-generic and
style:font-face/@style:font-pitch, although widht different values --
'roman' instead of 'serif', 'swiss' instead of 'sans-serif' etc.
http://books.evc-cit.info/OD_Essentials.pdf

That makes a mapping pretty trivial, and I wonder why it wasn't
included in odf2xhtml.

Anyhow, here is my version. Modified @style:font-name template in
style_mapping_css.xsl:

<xsl:template match="@style:font-name">
        <xsl:param name="globalData" />

        <xsl:text>font-family:</xsl:text>
        <xsl:variable name="content" select="."/>
        <xsl:variable name="quote">'</xsl:variable>
        <xsl:variable name="fontName"
select="$globalData/office:font-face-decls/style:font-face[@style:name=$content]/@svg:font-family"
/>
        <xsl:variable name="fontFamily"
select="$globalData/office:font-face-decls/style:font-face[@style:name=$content]/@style:font-family-generic"
/>
        <xsl:variable name="fontWidth"
select="$globalData/office:font-face-decls/style:font-face[@style:name=$content]/@style:font-pitch"
/>
        <xsl:value-of select="translate($fontName, $quote, '')"/>
        <xsl:choose>
            <xsl:when test="$fontFamily = 'roman'">
                <xsl:text>, serif</xsl:text>
            </xsl:when>
            <xsl:when test="$fontFamily = 'swiss'">
                <xsl:text>, sans-serif</xsl:text>
            </xsl:when>
            <xsl:when test="$fontWidth = 'fixed'">
                <xsl:text>, monospace</xsl:text>
            </xsl:when>
        </xsl:choose>
        <xsl:text>; </xsl:text>
</xsl:template>

Martynas
odt2epub.com

odf2xhtml

Hey list,

I've been working with odf2xhtml XSLT filter a lot lately, in relation
to ePub e-books. It does its job but it's really showing its age. I
wonder if there are plans for a new version? It could really benefit
from many of XSLT 2 features.

One of the most annoying things is the generated CSS. If style A
defines bold text and style B is inherited from A and additionally
defines right alignment, odf2xhtml generates such code:

.A { font-weight: bold; }
.B { font-weight: bold; text-align: right; }

<p class="A"> ... <p class="B">

That shows up OK in the browser, but removes the relationship between
A and B in the XHTML/CSS output. For example, if I need to select all
elements with style inherited from A, I cannot do that without looking
into the original ODT and examining the styles.

I think much better output could be achieved using multiple classes in XHTML:

.A { font-weight: bold; }
.B { text-align: right; }

<p class="A"> ... <p class="A B">

What do you think?

Martynas
odt2epub.com