On 30.10.2008 15:25 Uhr, Mikko Ohtamaa wrote:

*Trible* check that the encoding of your template is really utf-8. If it
isn't utf-8, you have to specify a different encoding within the
.metadata file of the related template (I think
[default]\ncharset=iso-8859-15 for example).

Got it working, thanks! The problem is that my metadata filename didn't have
a proper name (.metadata instead of .pt.metadata). Talk about DRY
principle... I finally noticed this by feeding garbage into .metadata.

Another question: Why does not .pt default to utf-8? utf-8 is a bit like
standard nowadays, isn't it? :)

UTF-8 is the default afaik or FS-based templates and usually should not require any further metadata files. If this is not the case for you then I would like to see a unittest demonstrating the issue.

-aj
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

Reply via email to