[protobuf] Re: Issue 196 in protobuf: Python: Ascii output is not assured to be in utf-8

2010-12-14 Thread protobuf
Updates: Status: Fixed Labels: FixedIn-2.4.0 Comment #5 on issue 196 by ken...@google.com: Python: Ascii output is not assured to be in utf-8 http://code.google.com/p/protobuf/issues/detail?id=196 Cool, it sounds like it is indeed fixed. -- You received this message because y

[protobuf] Re: Issue 196 in protobuf: Python: Ascii output is not assured to be in utf-8

2010-12-08 Thread protobuf
Comment #4 on issue 196 by liuj...@google.com: Python: Ascii output is not assured to be in utf-8 http://code.google.com/p/protobuf/issues/detail?id=196 I see, this was actually fixed by another CL that always encodes unicode string field to utf8 to fix this bug in our internal branch(s/142

[protobuf] Re: Issue 196 in protobuf: Python: Ascii output is not assured to be in utf-8

2010-12-07 Thread protobuf
Updates: Status: Accepted Labels: -FixedIn-2.4.0 Comment #3 on issue 196 by ken...@google.com: Python: Ascii output is not assured to be in utf-8 http://code.google.com/p/protobuf/issues/detail?id=196 Jisi, I'm not convinced that this is fixed. The as_utf parameter simply p

[protobuf] Re: Issue 196 in protobuf: Python: Ascii output is not assured to be in utf-8

2010-12-06 Thread protobuf
Updates: Status: Fixed Labels: FixedIn-2.4.0 Comment #2 on issue 196 by liuj...@google.com: Python: Ascii output is not assured to be in utf-8 http://code.google.com/p/protobuf/issues/detail?id=196 Now the text_format.PrintMessage has a parameter "as_utf", which I believe fi

[protobuf] Re: Issue 196 in protobuf: Python: Ascii output is not assured to be in utf-8

2010-07-02 Thread protobuf
Updates: Status: Accepted Comment #1 on issue 196 by ken...@google.com: Python: Ascii output is not assured to be in utf-8 http://code.google.com/p/protobuf/issues/detail?id=196 (No comment was entered for this change.) -- You received this message because you are subscribed to the G