[Emu] Revised sections for Issue #18 (Internationalization)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emu] Revised sections for Issue #18 (Internationalization)
"4.3.6. Internationalization of Display Strings
The payload MAY provide a standard attribute format that supports
international strings. This attribute format MUST support encoding
strings in UTF-8 [RFC3629] format. Any strings sent by the server
intended for display to the user MUST be sent in UTF-8 format and
SHOULD be able to be marked with language information and adapted to
the user's language preference as indicated by RFC 4646 [RFC4646].
Note that in some cases, such as when transmitting error codes, it
is acceptable to exchange numeric codes that can be translated by the
client to support the particular local language. These numeric codes
are not subject internationalization during transmission. "
"4.5.2. Internationalization
The password authentication exchange MUST support user names and
passwords in international languages. It MUST support encoding of
user name and password strings in UTF-8 [RFC3629] format. The method
MUST specify how username and password normalization is performed in
reference to SASLPrep [RFC4013] or Net-UTF-8 [RFC5198].
Any strings sent by the server during the password exchange and
intended
for display to the user MUST be sent in UTF-8 format and SHOULD be
able to be marked with language information and adapted to the user's
language preference as indicated by RFC 4646 [RFC4646]. Note that in
some
cases, such as when transmitting error codes, it is acceptable to
exchange
numeric codes that can be translated by the client to support the
particular local language. These numeric codes are not subject
internationalization during transmission. "
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.