Hi,
Changing the default encoding of python shouldn't be necessary, if you
have to
do it, it means that you have errors in your code (or in some code
you're using).
I would suggest to remove the default encoding setting and try to find
from where the error is coming. Leaving this setting can be bad since
you won't see errors you could make about encodings and your code may
not work where the default encoding is different.
Can you describe with more details what you are doing, what type of
vocabulary you're using,
and what is the traceback of the UnicodeDecodeError?
On May 8, 2:07 pm, supasate <
kaizerw...@...> wrote:
> Now I can avoid these problems by changing i18n domain to plone.
>
> However, for vocabulary, it still has a problem about encoding
> (UnicodeEncodeError).
>
> I searched the list archives and follow many advices that change default
> encoding of python to utf-8. By following this instruction, the
> UnicodeEncodeError is gone, however, I got "Value ต่างชาติ is not allowed
> for vocabulary of element ${label}." ต่างชาติ is a word in my language. I
> saw the word ต่างชาติ is correct and it's in my allowed vocabulary list.
>
> For more details,
> 1. I created .po file using utf-8 encoding.
> 2. Results of using Vocabulary words with unicode _(u"word") and not unicode
> _("word") are not different.
>
> Thank you in advance.
>
> Supasate
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________
Plone-i18n mailing list
Plone-i18n@...
https://lists.sourceforge.net/lists/listinfo/plone-i18n
