On 17/3/03 0:16, "Vadim Gritsenko" <[EMAIL PROTECTED]> wrote:
>> - String getCharsetEncoding() [or getCharacterEncoding]:
>>
>> Returns the default character encoding configured for the specified
>> AbstractTextSerializer (or the default one for the sitemap if none
>> was specified).
>> This can be usefult (for example) in the HtmlSerializer so that a new
>> <meta http-equiv="Content-Type" content="text/html; charset=???"/>
>> tag can be added automagically to the output, or to the "XMLSerializer"
>> so that the "<?xml version="1.0" encoding="???"?>" initial processing
>> instruction can be constructed appropriately.
>>
>
> It (<?xml?> instruction) done via
> format.put(OutputKeys.ENCODING,encoding.getValue()) in abstract
> serializer itself.
That gets the value out of the serializer configuration itself... So, per
se, we cannot have a per-pipeline text serializer with different encodings
per different sitemaps...
Hmm... I don't know why but it doesn't feel right.
Pier
