Hi Andrew,

at the first glance everything seems to be alright in your created ODF.

Can you please submit an issue in IssueZilla for OpenOffice.org. You can attach your created ODF files to this issue. You should assign this issue directly to me ([email protected]) - I will do some deeper investigations.

Best regards, Oliver.

On 12/08/10 01:39, Andrew Buza wrote:
I'm creating ODF text documents using Python's XML libraries and am
running into a little snag. The documents I'm creating seem to be
working when opened in OpenOffice.org, with the exception of the
next-style-name attribute. If I have a style with a next-style-name
defined it won't be applied to that style when opened. For example, in
the included style definitions, "Style1" should have a next style of
"Block Text", but when opened it will be "Style1" instead.
I've gone through the ODF specification and compared what I have with
ODT files generated by OO.o, but I haven't been able to determine where
I'm going wrong. What might the problem be?
My content and styles XML defintions should be attached to this message.



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


--
ORACLE http://www.oracle.com
Oliver-Rainer Wittmann | Oracle Open Office and ODF Standardization
Phone: +49 40 23646 500
Oracle Office GBU

ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Rijnzathe 6, 3454PV De Meern, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven

http://www.oracle.com/commitment
Oracle is committed to developing practices and products that help
protect the environment

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to