[Bug 29831] [FO31] fn:transform and serialization to string

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29831

--- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Re comment#1:

I think you are right. I now vaguely remember having seen that paragraph
before, and perhaps even asking this question before (which in itself may be an
indication that a Note could be helpful).

I used d-o-e as an example. I would have done better using character-maps as an
example (they have similar semantics but are interoperable). 

You write "However, a serializer MAY provide an option that allows the encoding
phase to be skipped". 

That suggests that applying character maps (which happens before encoding) has
effect. It also suggests that the output method has effect (which, I agree,
makes sense, otherwise one should use "raw" if you just needed a tree).

All in all: everything *except* (optionally) encoding takes place and the
result is given back as a string (that is, a series of characters, not octets).
If encoding takes place, you may get the string "&#x416;" (7 characters)
instead of the string "Ж" (Cyrillic Zhe, 1 character).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 21 September 2016 00:17:06 UTC