Hi,
I've asked the same question some time ago, but as far as I can see, the
problem still exists in the latest cps ...
We have translated cps to bulgarian (cyrillic) some time ago, and the
all non ascii chars in the translated messages in all layout_* page
templates have been replaced with '?????'. I have spend some time on the
problem, but the only acceptable, and very strange workaround was to insert
<tal:block define="dummy python: request.RESPONSE.setHeader('Content-Type',
'text/html;; charset=windows-1251')" /> to all of them. This way it
works, but it's very annoying to do that every time I upgrade to new
version ...
Thanks for your help in advance.
--
Vladimir Iliev
_______________________________________________
cps-users mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/cps-users
