On 30.10.2008 22:51 Uhr, Mikko Ohtamaa wrote:
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
Dealing with a BOM is a pita. We have seem various issue with different
editor when it comes to interpreting the BOM and writing it back
correctly - however there is already BOM support in the underlying ZPT
implementation. So you complained about the documentation: take your
time and create a FAQ or howto on plone.org from the information you
know now :-)
Andreas
begin:vcard
fn:Andreas Jung
n:Jung;Andreas
org:ZOPYX Ltd. & Co. KG
adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany
email;internet:[EMAIL PROTECTED]
title:CEO
tel;work:+49-7071-793376
tel;fax:+49-7071-7936840
tel;home:+49-7071-793257
x-mozilla-html:FALSE
url:www.zopyx.com
version:2.1
end:vcard
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
