[xmlroff] Usability issues

[Stefan S. <se...@sy...>]

Hi Tony,

as we talked about xmlroff's usability a while ago, here is an example I just ran into:

Processing some input file I just generated, I get this output:

(process:29504): libfo-CRITICAL **: fo_expr_eval: assertion `IS_CHAR (g_utf8_get_char (string))' failed

(process:29504): libfo-CRITICAL **: fo_property_id_validate: assertion `datatype != NULL' failed



I don't find this output particularly helpful, because:

* It isn't clear whether this is a warning or an error (though 'CRITICAL' certainly hints
   at an error).

* It isn't clear whether this is due to invalid input, an unimplemented feature
   in xmlroff, or something entirely different.

* It isn't clear whether there is anything I (as a user) can do to prevent this
   problem, by making changes to the input.


I'm not sure how these points should be addressed, and, whether this could
happen in the 0.4 timeframe.

Thanks,
		Stefan