Re: Charsets, encodings, http-request, unescape-markup, and convenience, oh my!

Florent Georges <fgeorges@fgeorges.org> writes:

> On 6 October 2011 21:45, Norman Walsh wrote:
>
>>      <c:request method="get" href="http://tests.xproc.org/tests/doc/html-utf8.data"/>
>> [...]
>> It returns a base64 encoded document:
>
>   In my humble opinion, I think those problems wouldn't happen if HTML
> content was parsed as a document node directly by the http-request
> step.  The step can access the HTTP response context (including the
> charset if any) and parse the HTML content directly into a document
> node, e.g. following the same rules as in escape-markup.  Or did I
> miss something?

I share Vojtech's reservations, but I'm inclined to agree.

                                        Be seeing you,
                                          norm

-- 
Norman Walsh
Lead Engineer
MarkLogic Corporation
Phone: +1 413 624 6676
www.marklogic.com