Tonight a close friend of mine drove my attention to the open ebook standard and the conference he recently attended to. This make it the issue on standards a very important part to create an opportunity for both OpenOffice.org and OpenDocument to have transformations for this open format.

 Documents and books are something that have similar needs, they need to be open formats, they need to be accesable and human readable. The ebook specs are provided on their site and also have an awesome way to process information.

Read more

we load the content.xml file using pecice of java code.

odfDoc = loadDocument(TemplateName);

odfContent = odfDoc.getContent();

it gives content.xml file.is ther any way to acess the style.xml

i tried in to get style.xml file.i am able to access the file.

while writing and saving time its not reflecting the cahnges.

Pls help ,

Thanks,

Sads

Hi recently I had a conversation with a fellow developer and talk about ODF popularity. The debate centralized between the Open source agenda and the open standard agenda and where it cross.

The idea of empowering ODF across technologies and systems can sometimes be challenging to absorbed by open source people (including myself). 

So an interesting challenging was brought up. Why not have an ODF Viewer in microsoft technology. This means VB and ActiveX. This will be as tactical as having a ODF plugin for Microsoft office.

Read more

The next version of Qt - the cross platform framework most notably used by KDE - will ship with basic ODF write support. More info on the Trolltech Labs blog.

ODFDOM is the name of the upcoming free OpenDocument framework sponsored by Sun Microsystems Inc.

It will be the next evolutionary step after AODL and Odf4j. Designed together with their architects with the intent to provide an easy lightwork programming API for the ODF developer community. ODFDOM is meant to be portable to any object-oriented language.

The first pre-version of the Java 5 reference implementation of ODFDOM is planned to become available under LGPL3 in May 2008.

Read more