16 Describe the applicant's efforts to ensure that there are no known operational or rendering problems concerning the applied-for gTLD string
|gTLD||Full Legal Name||E-mail suffix||Detail|
|.كيوتل||Qatar Telecom (Qtel)||centralnic.com||View|
The string ʺ.كيوتلʺ is an Internationalized Domain Name (IDN) label that according to the IDNA standards has two forms. The A-label form ʺ.xn--pgb3ceojʺ consists exclusively of ASCII characters and does not appear to present any rendering problems whatsoever.
The U-label form ʺ.كيوتلʺ consists of Arabic language characters and is supposed to be primarily used in Arabic language environment. According to the applicable standards this string is classified as having a right-to-left (RTL) display order.
As demonstrated below, the Applicant has made a comprehensive review of sources of information regarding rendering issues, and is taking the steps outlined below to mitigate those issues.
16.1. Mixed context rendering
While use of the string in a fully RTL context does not pose any rendering problems, certain complexities may arise when the string is rendered in a mixed environment that uses both RTL and LTR display order.
To address these complexities Applicant will adhere to the recommendations given in RFC 5893. In particular, application of the Bidi rule (para. 2 of RFC 5893) results in the following additional constraints that the Registry will enforce for second level domain registrations:
1.Labels must start with an Arabic letter.
2.If Arabic numbers are present in the label, no European numbers may be present, and vice versa.
Bidi rule guarantees that different strings will not be rendered in the same way regardless of the display order of the characters that constitute the string and the display order of the context in which the string appears.
Applicant will limit the registrations in the TLD exclusively to IDNs with RTL display order. Therefore, at least with regards to second-level domain names under the TLD no mixed context rendering issues will occur.
16.2. TLD string rendering by the browsers
Different browser engines use different approaches to decide whether the domain name part of an IDN-based URL should be rendered in its U-label form or in its A-label form.
Some browsers, such as Mozilla, maintain a white list of IDN-enabled TLDs, giving certain level of control over the rendering mechanism to the Registry Operator. Including a TLD as a entry in the white list triggers rendering the domain name in the address bar in its U-label form rather then in the A-label form. Applicant will work with Mozilla to ensure the TLD is white-listed for Mozilla browsers.
Besides, we will address the browser-related rendering issues in several other ways.
Where browsers are found to incorrectly render Arabic language TLDs we will report this to the browser manufacturers and ask them to update the view for IDNs
We will provide a list of “preferred browsers” on our website for the viewers for consistent viewing.
We will support initiatives of ICANN and other industry bodies to address the issue of Universal Acceptance of IDN TLDs and contribute where possible.
Similar gTLD applications: (3)
|gTLD||Full Legal Name||E-mail suffix||z||Detail|
|.اتصالات||Emirates Telecommunications Corporation (trading as Etisalat)||centralnic.com||-3.31||Compare|
|.موزايك||Qatar Telecom (Qtel)||centralnic.com||-3.25||Compare|
|.بيتك||Kuwait Finance House||centralnic.com||-3.25||Compare|