- From: <bugzilla@jessica.w3.org>
- Date: Sun, 21 Dec 2014 21:08:49 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27616 --- Comment #2 from Michael Kay <mike@saxonica.com> --- Personal response: Character maps are a pretty ugly feature; they were introduced as a slightly cleaner alternative to the disable-output-escaping feature, but they still have the architectural disadvantage of creating an unwanted coupling between the transformation and the serialization of its results. We wouldn't want to encourage people to do semantic transformations of the data in the serialization phase, so I personally wouldn't welcome any feature-creep in this area. The most common use cases for character maps is to generate entity or character references, or other serialization artefacts such as DOCTYPE declarations or CDATA sections that have no direct representation in the XDM data model. I haven't come across any users who have problems that would be solved by allowing substitution of anything more than a single character. Substituting arbitrary strings could become very expensive, and could lead to users attempting to use the feature for tasks that are properly done in the transformation phase. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 21 December 2014 21:08:50 UTC