You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2002/06/27 01:51:49 UTC
DO NOT REPLY [Bug 10242] -
[DOC] Text serializer is not documented
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10242>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10242
[DOC] Text serializer is not documented
vgritsenko@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Text silently dropped |[DOC] Text serializer is not
| |documented
------- Additional Comments From vgritsenko@apache.org 2002-06-26 23:51 -------
J,
> The workaround is to enclose the
> transformation result in an element:
This is not a workaround, this is how TextSerializer is *supposed* to work.
Unfortunately, this is not documented well. Thus, I'm changing bug title.
> If possible, character() SAX events outside any elements
> should generate log entries.
I don't think it is of value, because Cocoon does *not* perform any validation
of XML, and it is not Cocoon's responsibility. And text nodes before any
element is clear indication of invalid XML.
Solution can be to write a WellformednessCheckTransformer or
WellformednessCheckSAXConnector (proposed recently on cocoon-dev).
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org