i've forgotten to specify that this issue about the block element only happens when block is inside an inline element
----- Forwarded Message ----- From: Simone Parotta <[email protected]> To: [email protected] Sent: Thursday, May 27, 2010 12:19:55 PM GMT+0100 Europe/Berlin Subject: Re: [XFC] block ok, but i mean how is it managed? For example in an ODT document, which is my main concern, apparently the block element is ignored if it's empty (no newline is created) while if block contains some text, then is sorrounded with new-lines as expected. I've not investigated on more complex scenarios, anyway it seems that when block is empty is handled differently or even ignored, since i think it should be the standard behaviour of the block element to have new-lines after and before if not otherwise specified. is my guess wrong? ----- Original Message ----- From: Hussein Shafie <[email protected]> To: Simone Parotta <[email protected]> Cc: [email protected] Sent: Thursday, May 27, 2010 10:15:36 AM GMT+0100 Europe/Berlin Subject: Re: [XFC] block Simone Parotta wrote: > i've read here > > http://www.xmlmind.com/foconverter/support.html#xfc_support_policy > > that block element has some support limitation: > > "Not supported inside inline-level objects (output format limitation)." > > > what do you mean for "output format limitation"? > It means that the output format, for example RTF, makes it very difficult to implement the described XSL-FO feature. -- XMLmind FO Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xfc-support
