-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Vladimir Iliev wrote:
> 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,
cool !
> 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 ...
>
can't you just override the
CPSDefault/skins/cps_default/header_lib_header.pt and set the charset
from there as simplier workaround ?
The thing is we are setting the charset to "ISO-8859-15" within the
header...
J.
- --
Julien Anguenot | Nuxeo R&D (Paris, France)
CPS Platform : http://www.cps-project.org
Zope3 / ECM : http://www.z3lab.org
mail: anguenot at nuxeo.com; tel: +33 (0) 6 72 57 57 66
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFC48NkGhoG8MxZ/pIRAs6NAJ9nO8hkR4B6q68NzXccoiszUKc1DwCfcna/
UjSwM78ddmOSBvpBOBa5zPg=
=lat4
-----END PGP SIGNATURE-----
_______________________________________________
cps-users mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/cps-users
