W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2007

[whatwg] Serialising HTML to Files in Non-Unicode Encodings

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Thu, 16 Aug 2007 02:40:13 +1000
Message-ID: <46C32C6D.4000200@lachy.id.au>
K?i?tof ?elechovski wrote:
> Any serializer that needs an exotic character set should also have a way of
> retrieving the character set.  This character set need not be specified
> within the fragment stored because it would probably be the same for many
> fragments.  The serializer should rather store it elsewhere without
> modifying the original HTML text: as a record attribute, a column property,
> an optional parameter or built-in configuration parameter.

That doesn't work if the serialiser is saving it as a file that is 
intended to be viewed from the local file system, or put onto a server 
where the author can't (or doesn't know how to) configure the 
Content-Type header properly.  It depends entirely on the use case and 
environment for which the serialiser is designed and configured.

Lachlan Hunt
Received on Wednesday, 15 August 2007 09:40:13 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:57 UTC