propose to add encoding attribute to data set

[mountielee]

let me propose to add encoding attribute to data set. currently we only consider unicode(mostly UTF-8) on payment request data set. but at CJK areas non-unicode encodings are widely used at China, GBK (see www.taobao.com) at Japan, EUC-JP or Shift-JIS (see www.rakuten.co.jp) at Korea, EUC-KR (see www.gmarket.co.kr)

we are handling shipping address which is encoding sensitive data. product name is also encoding sensitve data.

[ianbjacobs]

@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

[mountielee]

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 .

[ianbjacobs]

@mountielee,

I think Unicode is a requirement on the Web, but different character encodings may be used within a Githubissues.

Githubissues is a development platform for aggregating issues.