If your intent is to get text from a to b, then there won't be a problem.
Protobuf uses utf-8, but that is an implementation detail that you should
never see. If your concern is that it may take more bytes in utf-8 than
utf-16 (for the codepoints in question), the you can always use a "bytes"
type and handle the text encoding yourself.
On 14 Nov 2013 17:26, "NotoriousAl" <timm.mei...@googlemail.com> wrote:
> Hey everyone. I`m glad to join the group.
> I have a project where I have to deal with diferent languages,one of them
> being Chinese. I don`t know yet if I will need UTF-16, but the question is:
> Can I get into trouble just using UTF-8, as this is supported by PBs or
> would I be fine with this choice. I read other posts in this forum where
> people suggest to use a library like ICU or UTF8 CPP to map from UTF16 to
> UTF8 and back on the other side of the wire.
> Could someone please tell me from his/her own experience with protocol
> buffers if either of the mentioned ways (just UTF8 or UTF16 with
> conversion) is feasible and produces correct results.
> Thanks in advance for your effort.
> Greetings, Al
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to protobuf+unsubscr...@googlegroups.com.
> To post to this group, send email to firstname.lastname@example.org.
> Visit this group at http://groups.google.com/group/protobuf.
> For more options, visit https://groups.google.com/groups/opt_out.
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/groups/opt_out.