Re: [w3c/payment-request] editorial: mark languageCode at risk (#764)

The challenge here is having a clear algorithm to identify the language of content - in this case, an address. Does [0] provide the algorithm? Apologies if it does and I missed it. Without such an algorithm, none of us can implement `languageCode` Interoperability (current situation, why it’s now marked at risk). 

At the risk of getting circular, if there is such an algorithm, whereby a string is give and out comes a language tag(s), then IMO, it should be part of `Intl`, because it would be univesally useful to the web platform. 

-- 
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-418908806