On Thu, 2006-02-16 at 09:36 -0500, [EMAIL PROTECTED] wrote: > Ross, > > Thank you for your help. > > I'm a little confused, though. Do you mean that XML/HTML is the > *only* way to change text options when outputting to an OO file from a > program? > HTML , with variable-length tags and many deprecated options, is a really > messy option for documents generated by a program. I realize I am not running > a > mainstream application :-) but it's not a difficult concept. For an > open-source product, it seems awfully difficult to get this very basic info > on OO. > > And if XML is used, why not allow CSS coding too, and make OO really > flexible and current? > > Among other things, two-sided tags were (sometimes) not carried over > to the next line in the test document. This will be a production application, > so I can't afford a flaky implementation, even if the flakiness might be > caused by user error. > > I am using OO because I don't want to use Word if I can avoid it. I > don't own or know Postscript, and I have a deadline, so I don't want to learn > PS, or XML, or any other package just to format text. Since it is a > production > program for a very small company, I don't want to add more different products > that have to be supported, although the concept of Ghostscript is interesting > down the line. > > Best, > Carl > >
If you are programming this then this is not the place to ask. Please ask programming questions on [email protected] and go from there. -- PLEASE KEEP MESSAGES ON THE LIST. OpenOffice.org Documentation Co-Lead http://documentation.openoffice.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
