at PaymentItems dictionary, product name can be included which are from merchant can be encoded as non-unicode charset. at PaymentAddress interface, languageCode is defined but that is not enough, the merchant possibly will receive broken shipping address. 2016년 9월 23일 (금) 오전 10:53, ianbjacobs <notifications@github.com>님이 작성: > @mountielee <https://github.com/mountielee>, > > I don't believe that payment request API specifies any encoding. I believe > the surrounding context (e.g., HTML) is where the character set is defined, > and one can specify different character encodings. > > Am I missing something? > Ian > > — > You are receiving this because you were mentioned. > > > Reply to this email directly, view it on GitHub > <https://github.com/w3c/webpayments/issues/181#issuecomment-249150644>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ADvzYLwwNcc_mXC78D2aSdg0vo6Rkd1sks5qs6GggaJpZM4KEy6W> > . > -- 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/webpayments/issues/181#issuecomment-249151833Received on Friday, 23 September 2016 10:00:28 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:19 UTC