Thinking about this further, I have a question for @aphillips - the answer to which might clear up some of the confusion around the current `languageCode` attribute in the Payment Request API. Right now, `languageCode` defines "the language in which the address is provided", which is "used to determine the field separators and the order of fields when formatting the address for display". But the `PaymentAddress` is a composite of multiple strings (`country`, `region`, `city`, `organization`, etc.). Should each of those strings be flagged with a langtag and base direction? What if the organization name is in kanji or hiragana and the other address fields are in romaji/Latin? It seems that we might be talking about two different things here: (1) the langtag/direction of each string (or potentially a set of strings), and (2) the layout of the set of strings representing an address in the input form of the payment dialog that the browser displays. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-request/pull/764#issuecomment-418915593
Received on Wednesday, 5 September 2018 23:39:52 UTC