+++ This bug was initially created as a clone of Bug #683200 +++ http://www.icann.org/en/announcements/announcement-30oct09-en.htm From article: "The coming introduction of non-Latin characters represents the biggest technical change to the Internet since it was created four decades ago," said ICANN chairman Peter Dengate Thrush. "Right now Internet address endings are limited to Latin characters – A to Z. But the Fast Track Process is the first step in bringing the 100,000 characters of the languages of the world online for domain names." More info at: https://fedorahosted.org/spacewalk/wiki/Features/NonLatinCharacters Requirements Client tools need to make sure that all host names are in Pune encoding before sending to rhnParent. Client tools should accept non latin domains as entry (eg. serverURL) and encode it to Pune, before connect() or before it is send to rhnParent. We will store host names in DB in Pune encoding. We will have to go through WebUI and anytime we present hostname (SDC, device info, monitoring...) we will decode Pune string to UTF-8. We will modify JavaDoc for API calls and whenever hostname is used, we will note that we accept/return hostname in Pune encoding. --- Additional comment from msuchy on 2011-05-04 09:04:54 EDT --- changes in webui has been done in spacewalk.git in commits: d3bf18726d0117f44214b2914a3e71693edac0c3 4b4b1650ef4cd40b491764a949dee44506bcaf04 0d6d46f29e666cff294689b471a6a363f83c9077 f7eefed0ea337a932bc9d8ce88950026b4a2962e d6902867cad5a94f5c91884237d0387812b42f4c e0d234c0dea61fda4f7c992d03705dbf48a76bbc 3e738c0ce75fe4e4e21cf8959d775cfef4648603
cherrypicked to satellite.git as commits: d2afae68cd0387c2501f6449e4b8be2e9776ec61 3f1757b1b6ae838af12eec292203b98844534193 6ce13740cfdb224eeb044915247fe29a01b01f77 cbc71d9ccd30be3c712aae73b6cbf1d4356d5598 f8bb89b084dfa15ac254f293fb966388b96d5925 05d5f6e471aead5674b5ffb5bfabd4b7f35c3668 273894cc5e8822887f9b0a8ed3e86aa86900ff0a 3c54188a8c36af69886b0166b92051f3c8c170bc
Affected pages: /rhn/systems/details/Overview.do?sid=1000041669</p> /rhn/systems/details/SystemHardware.do?sid=1000041669</p> /rhn/admin/config/GeneralConfig.do</p> /rhn/admin/config/MonitoringConfig.do? /rhn/admin/config/BootstrapConfig.do?</p> /rhn/systems/DuplicateHostName.do?</p> /rhn/systems/Search.do
Taking for QA.
(In reply to comment #2) > Affected pages: > /rhn/systems/details/Overview.do?sid=1000041669</p> > /rhn/systems/details/SystemHardware.do?sid=1000041669</p> > /rhn/admin/config/GeneralConfig.do</p> > /rhn/admin/config/MonitoringConfig.do? > /rhn/admin/config/BootstrapConfig.do?</p> > /rhn/systems/DuplicateHostName.do?</p> > /rhn/systems/Search.do VERIFIED in spacewalk-java-1.2.39-80. IDN on all affected pages are handled correctly. I.e., system names (aka profile names) are displayed in Pune encoding and hostnames are translated into UTF. Example: You have system with hostname 'xn--luouk-k-z2a6lsyxjlexh.example.com' (Pune encoded) registered into Satellite. In Sat. WebUI you will see the System Name still in original Pune encoding as 'xn--luouk-k-z2a6lsyxjlexh.example.com'. But the Hostname is always translated into UTF8 and displayed as 'žluťoučký-kůň.example.com'.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. https://rhn.redhat.com/errata/RHSA-2011-0879.html