Unicode data is largely limited to (person) names and extended text fields. There are no plans to allow keys, usernames, etc. And of course "unicode woes" is a contradiction in terms.

Working Services

Service Comments
roles -v OK - Renders names correctly
alpine Alpine itself handles UTF-8 fine, and LDAP lookups (where supported) are also fine.

Known Bugs

Known issues with the Unicode data originating in Theon

Service comments / steps to reproduce Fix?
finger Renders UTF-8 chars as ??  
getent passwd Renders UTF-8 chars as ??  
alpine - default lookup believed to use finger / getent. Reconfigure to use infdir for composer lookups.
mailman - sync_members fails with unicode errors, used when syncing db lists to mailman lists turns out it is only failing at a part that is echo'ing out the email address to stdout. I've manually removed the attempt encode things to ascii before echo'ing in sync_members. need to patch mailman RPM
mailman - subscription through web fails with unicode errors having added an English (UTF8) language option, if the list is now set to default to that, subscript via web works
Topic revision: r4 - 11 Jul 2013 - 16:07:53 - NeilBrown
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies