Comment #5 on issue 1747 by [email protected]: en_US.UTF-8 problem
(different solution patch)
https://code.google.com/p/ibus/issues/detail?id=1747
Hi,
Thanks.
Either way is fine with me. If one does not find one locale, goes to
check another one as exception. So the same thing on all platforms.
I do not understand your comment. First, C is always available on all
platforms. So if you check C, it return true and processes data under C
locale.
Under C locale, the msgid text containing and marked as UTF-8 data is
converted to C locale possibly changing data. I have no concrete idea
but is this good? If this is good, why even bother to use en_US.UTF-8?
Why not use C over en_US.UTF-8? It does not make sense to me.
Osamu
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
You received this message because you are subscribed to the Google
Groups "ibus-devel" group.
iBus project web page: http://code.google.com/p/ibus/
iBus dev group: http://groups.google.com/group/ibus-devel?hl=en
---
You received this message because you are subscribed to the Google Groups "ibus-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
