Subject: Re: Using AbiWord for HTML
From: January Weiner 3 (jweiner1@ix.urz.uni-heidelberg.de)
Date: Thu Feb 07 2002 - 03:12:36 CST
Hello,
> Sounds like a good idea. If I understand correctly, currently importers
> return UT_OK for success, anything else being failure, why not add a
> third, "fuzzy" option (e.g., UT_IE_INTERRUPTED)? - In which case, the
> "bogus or invalid document" dialog is still displayed but a document
> exists and is processed normally.
This would have an additional advantage: Abiword would be *forwards
compatible* :-), like HTML browsers. Imagine you add a tag in a future
release of Abiword; the older versions will not be able to open such a
document, even if the tag is really not important for the whole text.
Abiword, instead of ignoring unknown tags in the native abw format,
complains that file is corrupted (or compatible) and aborts reading the
text. This was an obstacle for me while writing a perl script for adding
bibliography. It would be nice if it (i) did not complain about unknown
tags / formattings (ii) preserved it upon file saving.
> Or maybe this should be up to individual importers and AbiWord doesn't
> care? For example, the (X)HTML importer could append
>
> <p><b>Transfer Interrupted!</b></p>
>
> to what has been read successfully, and return UT_OK - AbiWord is none the
> wiser.
Hm, I think the former would be better, because it could allow better user
interaction.
Best regards,
j.
----)-\//-///-----------------------------------January-Weiner-3-------
"You can't trample infidels when you're a tortoise. I mean, all you
could do is give them a meaningful look."
-----------------------------------------------
To unsubscribe from this list, send a message to
abiword-user-request@abisource.com with the word
unsubscribe in the message body.
This archive was generated by hypermail 2b25 : Thu Feb 07 2002 - 03:12:42 CST