#1389: Allow control over value literalization and whitespace handling in
parameters and settings
-------------------------+--------------------------------------------------
Reporter: david | Owner: david
Type: enhancement | Status: reopened
Priority: normal | Milestone: 1.1
Component: config | Version:
Severity: normal | Resolution:
Keywords: | Has_patch: 0
-------------------------+--------------------------------------------------
Changes (by david):
* status: closed => reopened
* resolution: fixed =>
Comment:
Reopening this as I missed something in the [http://www.w3.org/TR/REC-xml
/#sec-white-space White Space Handling section of the XML specification]:
The value "default" signals that applications' default white-space
processing modes are acceptable for this element; the value "preserve"
indicates the intent that applications preserve all the white space. This
declared intent is considered to apply to all elements within the content
of the element where it is specified, unless overridden with another
instance of the xml:space attribute. This specification does not give
meaning to any value of xml:space other than "default" and "preserve". It
is an error for other values to be specified; the XML processor may report
the error or may recover by ignoring the attribute specification or by
reporting the (erroneous) value to the application. Applications may
ignore or reject erroneous values.
We must fix this accordingly, but the question is whether or not the
{{{literalize}}} attribute should behave the same.
--
Ticket URL: <http://trac.agavi.org/ticket/1389#comment:6>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
