"Cley Faye":
http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#__RefHeading__1415854_253892949
So, somehow arbitrary BASE64-encoded data are fine in ODF yet an obstacle in RTF?
http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#__RefHeading__1417966_253892949
It is not documented there: it says it can be an arbitrary string with no effect defined.
"\cf0\kerning1\dbch\af6\langfe2052\dbch\af7\afs24\alang1081\loch\f4\fs24\lang1036"
\cfN Foreground color (default is 0). N specifies the color as an index of the color table. \kerningN Point size (in half-points) above which to kern character pairs. \kerning0 turns off kerning.
\dbch The text consists of double-byte characters. etc.
RTF was changed on numerous occasion in non-retrocompatible ways,
examples?
accross several MS tools (namely MS Word and Wordpad) you get completely different results for the same file
Different features supported give different results. Yet Arial 10pt red will stay Arial 10pt red everywhere, so the format definitely works.
A RTF file is less "human-readable" than the content.xml file in an ODT
XML isn't more readable than RTF.
-- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
