[OpenTAL-checkins] opental/PlacelessTranslationService README.ZPT

[Fernando Lalo Martins]

CVSROOT:        /cvsroot/opental
Module name:    opental
Branch:         
Changes by:     Fernando Lalo Martins <address@hidden>  03/08/28 16:09:49

Modified files:
        PlacelessTranslationService: README.ZPT 

Log message:
        updating this file - now we are known to work in almost all situations 
with zpt

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/opental/opental/PlacelessTranslationService/README.ZPT.diff?tr1=1.3&tr2=1.4&r1=text&r2=text

Patches:
Index: opental/PlacelessTranslationService/README.ZPT
diff -u opental/PlacelessTranslationService/README.ZPT:1.3 
opental/PlacelessTranslationService/README.ZPT:1.4
--- opental/PlacelessTranslationService/README.ZPT:1.3  Thu Feb 27 20:41:06 2003
+++ opental/PlacelessTranslationService/README.ZPT      Thu Aug 28 16:09:49 2003
@@ -2,7 +2,7 @@
 
   This product was originally written for use with OpenTAL.  It has
   since been refactored to become compatible with ZPT; however,
-  "compatible" doesn't (yet) mean very reliable.
+  "compatible" doesn't mean guaranteed.
 
   PlacelessTranslationService is fully unicode-based, so that you may
   write your potfiles in any encoding you want.  ZPT, on the other
@@ -11,6 +11,8 @@
   encodings, you may get UnicodeError.  This problem is not exclusive
   of Placeless; it also happens with Localizer.
 
-  The workaround is to set the default python encoding, but that means
-  other encodings won't work (therefore, some languages will be
-  unusable).  The proper fix requires fixing ZPT.
+  As of more recent releases, this problem seems to have disappeared,
+  thanks to tireless effort of a few contributors.  However, if your
+  setup is peculiar enough that you still get UnicodeError, now you
+  know why.  The fix?  Either fix ZPT, or (shameless plug) switch to
+  OpenPT which is a bit slower but works ;-)