gmane.comp.openoffice.devel.xml

Invitation to connect on LinkedIn

Hirano Kazunari — 2011-09-28T11:14:34

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&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&tok=29oYt5vgL2-QU1

(c) 2011 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.

Good News For UOF Project

anhongyun — 2010-11-09T09:36:47

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

anhongyun — 2010-11-03T04:44:19

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!

store additional data in oo xml file

Oliver Brinzing — 2010-09-29T14:46:17

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

Proposal of new project for UOF

LiHeng — 2010-07-07T06:03:15

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!

Saving additional style:paragraph-properties attributes

Graeme Lunt — 2010-03-24T14:09:19

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

Gannon Dick — 2010-03-23T22:29:01

OO Writer is the word processor

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

Generic < at >font-family in CSS (another odf2xhtml patch)

Martynas Jusevicius — 2010-03-23T22:09:48

Hey agin,

another annoyance I came across in odf2xhtml today is missing output
of generic < at >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/< at >style:font-family-generic and
style:font-face/< at >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 < at >style:font-name template in
style_mapping_css.xsl:

<xsl:template match="< at >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[< at >style:name=$content]/< at >svg:font-family"
/>
        <xsl:variable name="fontFamily"
select="$globalData/office:font-face-decls/style:font-face[< at >style:name=$content]/< at >style:font-family-generic"
/>
        <xsl:variable name="fontWidth"
select="$globalData/office:font-face-decls/style:font-face[< at >style:name=$content]/< at >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

Martynas Jusevicius — 2010-03-19T16:29:21

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

DFD this March 30th - What we going to do about it?

Alexandro Colorado — 2010-03-08T22:28:42

On March 30th the Document Freedom day is happening and I think we are
in good time to start to work on a campaign to show our support on the
website.

I think this event is pretty important, and we could be working with
the communities and spread the word about this relevant event. I think
also marketing should put some  money to fund the development.

Some ideas are:
- Showcase the benefits of OpenDocuments
- Show the tools that use ODF
- Push documentation to the forefront about ODF such as adoption, implementation
- Push technical documentation
- Projects like www-at-odf and ODFDOM, XSLT-Tools

I think this is a relevant event to put our support behind and also
OOo does need a more responsive website.

Find content between and

ashok _ — 2010-02-17T14:41:26

I am struggling  a bit with trying to extract inserted text in a
change tracked ODF
document --

since text inserts are recorded in the document using the 2 elements which share
the id attribute : <text:change-start id="an_id" /> and
<text:change-end id="an_id" />
placed arbitrarily in the document depending upon where new text was inserted
 (See example below ).

How do i get the text content contained by these two tags ?


e.g.

<text:section text:style-name="Sect1" text:name="Section2">
      <text:p text:style-name="Standard"/>
      <text:p text:style-name="Standard">Neque porro quisquam est, qui
dolorem ipsum
      quia dolor sit amet, consectetur, adipisci velit, sed quia non
numquam eius
      modi <text:change-start text:change-id="ct472232592"/></text:p>
    ........................
    ........................
    <text:p text:style-name="Standard">Sed ut perspiciatis unde omnis iste natus
        error sit voluptatem accusantium doloremque laudantium, totam
rem aperiam,
        nihil molestiae consequatur, vel illum qui dolorem eum fugiat
quo voluptas
        nulla pariatur?<text:change  text:change-id="ct472209600"/></text:p>
    ........................
    ........................
 </text:section>

Meta Data Round-Tripping & Privacy

Gannon Dick — 2009-12-23T19:36:43

[ANN]  Meta Data Round-Tripping & Privacy

Free White Paper


From the Foreword ...

The trouble with meta data round trips between formats is the same
problem with meta data round trips between “displays” which may hide
meta data from view. While the results are common in real life,
a similar name on a “no fly” list causing a missed flight
(a mis-identification), or a targeted advertisement way off
target ( a mis –re-identificationn), the root cause is simply
that a format conversion confuses the distinction between
“exposed” and “unseen”. In the case of re-identification, the issue
comes up as an identifier deletion when a data redaction was
intended.


The CSVplus Data Base (in OO Base) is a generalized model of a CSV Format
Spreadsheet. Fully exposed meta data elements are added
to the CSV Format to prevent the unintentional deletion of identifiers.

While this format has an obvious application for Application
User Data and Address Books, it can also be used on other data sets,
for example, Web Forms or Social Networking Site Profiles, Library Catalogs or even Paper Forms.

Download from: http://www.rustprivacy.org/meta/roundtripping.pdf

ODF User Data to vCard 3.0

Gannon Dick — 2009-11-23T09:48:23

I have two XSLT export filters.  They both take the current *.odt user data and export to vCard 3.0. (RFC 2426) One is HTML (tabular) output and the other is RDF/XML output (per a note on this issue from the W3C <http://www.w3.org/TR/vcard-rdf>).

A. Is this in the "issues" ?
B. Does anybody want it ?  The vCard and microformats are all Public Domain, but the filters might come in handy for multi-user installations or where many users would like uniformity.  They would be fairly easy to customize to include Logo's pictures etc..

Passing Parameters to the XSLT Export Filter

Gannon Dick — 2009-10-16T08:57:01

Now (OO version 3.1) that the number of User Defined Properties == Custom Properties is not limited to 4, it is practical to use Properties to pass parameters to the XSLT Export Filter.

File>>Properties>>Custom Properties(tab) Add
e.g. SAX.test = 'Hello World" (text)

(mavens be gone! There are lots of ways to do this)

<xsl:stylesheet version="1.0"
     xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
     xmlns:meta="urn:oasis:names:tc:opendocument:xmlns:meta:1.0"
     xmlns:saxon="http://www.w3.org/1999/XSL/Transform#"
     exclude-result-prefixes="meta">
<xsl:output method="xml" encoding="UTF-8" />

<xsl:param name="SAX.test">
  <xsl:for-each select="//meta:user-defined">
    <xsl:if test="./< at >meta:name = 'SAX.test'">
      <xsl:value-of select="./." />
    </xsl:if>
  </xsl:for-each>
</xsl:param>

 <xsl:template match="/">
  <saxon:param>
    <xsl:value-of select="$SAX.test" />
  </saxon:param>
 </xsl:template>
</xsl:stylesheet>

output is:

<?xml version="1.0" encoding="UTF-8"?>
<saxon:param xmlns:saxon="http://www.w3.org/1999/XSL/Transform#">
   Hello World !
</saxon:param>

Hints:

a) parameter names have to be QNAMES - no spaces
b) the "dot" notation is probably a good idea so you can easily take the parameters out of the list of properties, but it's not required  (Svante, what do you think ? An XSL template for this "protocol" would be nice, in your spare time)
c) tagged Personally Identifiable Information (PII) and other information which should be redacted/deleted (or not) from output documents does not require two transforms **provided** you can pass a (redact/keep) parameter to the stylesheet.  See: http://purl.org/pii/terms/

 --Gannon

ODS Meta Data

Gannon Dick — 2009-10-15T08:14:35

The user-defined meta data in "properties" changed (much for the better) in Open Office version 3.1.  A couple of comments:

1. Don't know if it has been logged as an issue yet, but the "date" data type doesn't work properly.  It error checks the date format, but if that is correct, it takes the field off the list!
2. There is also a "time" datatype in the ODF spec., but not implemented.
3. There are 20 or so fields in a drop down box.  If you want to use GRDDL* you'll have to a) take spaces out of the name and b) include a namespace with the dot notation:  e.g. "Checked By" would have to be typed in as "ODF.Checked_By", with a link to "schema.ODF".

* there might be no reason for GRDDL.  I've only tested it with spread sheets, but this transform should work for *.odt, etc.  It's an export filter from (flat) ODF to RDF/XML.  It uses the OASIS namespace as a default.  (Warning: Don't modify it to work on the ODF file, just the meta.xml component plus two attributes from office:documents gives 295 triples! see: http://www.rustprivacy.org/odf/sstest.zip ).

The transform is :  http://www.rustprivacy.org/odf/ODSmeta2RDFXML.xsl

(the name is case sensitive, download it if you like and change the name)

--Gannon

empty metatypes when generating a ODF

Alexandro Colorado — 2009-08-18T20:36:00

Seems that UNO is generating an empty metafile when creating a new
ODF. A developer notice it first in PyUNO but then create a file from
Basic and experience the same issue. Could this be the best project to
present this bug?