Re: [w3c/webpayments] propose to add encoding attribute to data set (#181)

@ianbjacobs
even well prepared web-based payment apps,
when they received payment request in broken characters, they have no way
to fix it.

web payment standard will encourage many small and non-technical merchants
using web payments.
when merchants receive broken shipping address (we already experienced this
case),
merchants have no way to fix it.

that is the reason charset attribute is added in script tag as part of
standard.

so if merchant is using non-unicode page encodings, with current
expectations, web payment will not work well.


2016년 9월 23일 (금) 오전 11:53, ianbjacobs <notifications@github.com>님이 작성:

> @mountielee <https://github.com/mountielee>, web-based payment apps would
> handle encoding properly. We don't exercise any control over how
> native-based payment apps would work.
>
> 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-249161291>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ADvzYAO_WrVIeHTneZUQqSwQKFwM_KbQks5qs6-PgaJpZM4KEy6W>
> .
>


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