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 http://lachy.id.au/
