[asterisk-dev] [svn-commits] murf: branch murf/utf8-whatif r89574 - /team/murf/utf8-whatif/

[Johansson Olle E]

>
> I don't see why contexts can't be utf8; extensions, I can understand.

I don't see any reason for contexts in utf8, really. It's an internal  
concept
to Asterisk. We propably need to define what characters we do allow
in a context for external IAX2 libraries as well as Asterisk.
>
> Internally, operations on utf-8 are the same as what they normally  
> are.
> They are non-zero bytes in strings. Nothing special to do, usually.  
> All
> of the current fixed strings we use in asterisk for matching config  
> file
> values/entries are exactly the same in utf8.
>
As long as utilities like strlen and strcmp handle utf8 properly...

Any issues with realtime? Ldap, Radius, databases? CDR records?
Log files?

Conversion will be an issue for caller ID names. Conversion from
Unicode to ASCII isn't easy and depends on language and
culture. As I propose in my branch calleridutf8 we do need
two caller ID names for every device configured in Asterisk.
And we propably need hooks for configurable conversion
tables for incoming calls so that it can be handled in a way the
sysadmin accepts. Imagine automatic conversion from
ancient runes to ascii. Or even something as simple as
"blåbärsmjölk" which can be translated to
"blabarsmjolk", "blaabaersmjoelk" or something unrecognizable.

I'll keep working on a first level of handling utf8 caller ID names
(without conversions) in my branch and test it. When it works
properly for SIP I'll merge it. This is only for caller ID names or
Display Names as we say in the SIP community :-)

/O