On 2023-07-03, at 16:21, Robert Stepanek <rsto=40fastmailteam.com@xxxxxxxxxxxxxx> wrote:
>
> new RFC draft version
Please don’t call Internet-Drafts “RFCs” or “RFC drafts”.
I’m intrigued by the additional text in Section 2.1.5, which now reads:
2.1.5. language
Type: String (optional).
This is the language tag, as defined in [RFC5646], that best
describes the language used for text in the Card, optionally
including additional information such as the script. Note that
values MAY be localized in the localizations property Section 2.7.1.
How to render text is out of scope of this specification, e.g., refer
to [UnicodeBiDi] how to deal with different writing directions.
"language": "de-AT",
Figure 9: language example
The reference to [UnicodeBiDi] is new, referring to https://www.unicode.org/reports/tr9/.
I don’t think that specification will help you divine the LTR/RTL properties of the text; usually, additional input beyond a Unicode text string and a language-tag is required for this (e.g., the “dir” attribute used in examples in TR9).
Grüße, Carsten
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
