writes: I recently tried to make simple QuickRef document for GNU/Arch. QuickRef in theory is simple document which encompass list of often used commands of specific tool. I wanted to create such one in ODT using OpenOffice.org 2.0 under (sorry) Windows.
It's all started Okay. But after typing few lines, I got tired of OO.o2 bug: one-two minute freezE when opening fonts dialog (It happens sometime when you have several documents open in OO.o for long period of time.)
I bravely decided that KOffice 1.5 would do better job, so I fired up VMware Player (we are not allowed to have Linux in office - free VMware is Ok) with Debian. First problem appeared - fonts. Windows and Linux do not have same fonts. Document with Times New Roman and Courier New looked ugly, until I replaced M$Windows fonts with native Linux ones - Bitstream Serif/Sans/Mono.
Then second problem surfaced: KOffice 1.5 apparently doesn't support character styles, but only paragraph styles. I used such style in comments intermixed in meta-code I were adding to QuickRef.
Okay. KOffice is really more pleasant to work with, compared to OO.o1/2. And bit later job was done. Now I was going to enjoy the results. "Print" > "Print to PDF" ... Oops. That looks ugly. Apparently GhostScript didn't like fonts I have used and all labels in PDFed QuickRef were misrendered: readable, but ugly. Nevermind - let's try another fonts. No luck: the same ugly result.
Okay. Nevermind. Let's bring my QuickRef back to Windows and OO.o2 - if it's inconvenient to edit document, printing/exporting framework of OO.o is definitely more stable compared to KOffice one.
FTP, copy document, fire up OO.o2 ... Holy crap. Fonts - OO.o seems used some randomization algorithm picking font substitution. Font sizes - some paragraphs or parts of them displayed with font size two times (or so) smaller than standard (and no apparent problem is visible in paragraph style dialog - all sizes globally set to 11pt, reapplying style didn't help). Italic I have used for comments got partially removed... Needless to say that next-to-perfect PDF export function of OO.o have produced exact replica of the ugly mess I have had on screen.
No matter how raw and unstable KOffice 1.x, OO.o2 dumbly breaks on document created in alternative application. The only way I have come up to fix the observed in OO.o weirdnesses - reimport thru plain text file (select all, copy to notepad, reselect in notepad and then back from notepad into OO.o) what is bogus. Does anybody ever tested OO.o with ODF generated by other tools, me wonders.
I wonder if I am only one who is trying interoperability of ODF suits. Have anybody else tryed to move ODF documents around between ODF capable suits (OO.o and KOffice are the only I know and have) with positive results? Moving documents from Windows to Linux and back?