At 5:17 PM -0500 1/10/01, John L. Clark wrote:
>CSS (and to a lesser degree) XSL do it because there is no specified
>interface to {X,HT}ML and the associated style sheet languages. That
>is, authors are completely free to edit the code by hand. In my mind,
>however, AbiWord documents are by definition interface based;
EXACTLY what I am trying to fix! I want to use the AbiWord
format for something OTHER than AbiWord.
I suspect that my users will either use AbiWord as a starting
point to create "template files", or they will generate the file
ENTIRELY on the fly from some database/cgi/etc. process. Therefore,
I am trying to find those places where AbiWord had made assumptions
about things in the format that it new implicitly but that other
clients of the format (like me ;), wouldn't.
>Furthermore, RGB
>format is not hard to understand, and is pretty universal across tools.
True, HOWEVER, RGB sucks for prepress work.
>I think color word support in our Abi export is unnecessary for these
>reasons.
I wouldn't expect Abi to export colors by name or even
support CMYK color spaces (at least not any time soon), BUT I do want
to make sure that a user of my system could happily round trip a
document from my "extended" Abi format.
LDR
--
----------------------------------------------------------------------------
You've got a SmartFriend� in Pennsylvania
----------------------------------------------------------------------------
Leonard Rosenthol Internet: [EMAIL PROTECTED]
America Online: MACgician
Web Site: <http://www.lazerware.com/>
FTP Site: <ftp://ftp.lazerware.com/>
PGP Fingerprint: C76E 0497 C459 182D 0C6B AB6B CA10 B4DF 8067 5E65
