2 |
|
|
3 |
This product was originally written for use with OpenTAL. It has |
This product was originally written for use with OpenTAL. It has |
4 |
since been refactored to become compatible with ZPT; however, |
since been refactored to become compatible with ZPT; however, |
5 |
"compatible" doesn't (yet) mean very reliable. |
"compatible" doesn't mean guaranteed. |
6 |
|
|
7 |
PlacelessTranslationService is fully unicode-based, so that you may |
PlacelessTranslationService is fully unicode-based, so that you may |
8 |
write your potfiles in any encoding you want. ZPT, on the other |
write your potfiles in any encoding you want. ZPT, on the other |
11 |
encodings, you may get UnicodeError. This problem is not exclusive |
encodings, you may get UnicodeError. This problem is not exclusive |
12 |
of Placeless; it also happens with Localizer. |
of Placeless; it also happens with Localizer. |
13 |
|
|
14 |
The workaround is to set the default python encoding, but that means |
As of more recent releases, this problem seems to have disappeared, |
15 |
other encodings won't work (therefore, some languages will be |
thanks to tireless effort of a few contributors. However, if your |
16 |
unusable). The proper fix requires fixing ZPT. |
setup is peculiar enough that you still get UnicodeError, now you |
17 |
|
know why. The fix? Either fix ZPT, or (shameless plug) switch to |
18 |
|
OpenPT which is a bit slower but works ;-) |