> > I was partly wrong. UTF-8 is the default for pagetemplates on the FS > with content-type text/xml but iso-8859-15 for text/html. You are free > to make the template an xhtml template with a related XML preamble or > you define the encoding using <meta http-equiv...>...check > FSPageTemplate.py if you are interested in implementation details. > Changing the default encoding to utf-8 isn't an option for backward > compatibility.
.metadata is a bit cumbersome way if you have plenty of templates. Also, iso-8859 is sooo 90s and the world is more and more utf-8 based, What could you suggest so that we can make this easy for the future product developers? AFAIK the problem is that TAL and page templates do not have a proper documentation where this thing could be added as a notice and desperate Googling to find this threat is not a very friendly. Could there be a scanner in FSPageTemplate which checks for utf-8 start marker and spits out a warning? -- View this message in context: http://n2.nabble.com/Why-utf-8-characters-in-.pt-files-in-fail--tp1398580p1400654.html Sent from the Product Developers mailing list archive at Nabble.com. _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
