[quicktips/index] UTF-8 mentioned in two different places

[xfq]

[source] (https://www.w3.org/International/quicktips/index) [en]

UTF-8 is mentioned in both Encoding and Forms. I think it's a bit repetitive, and IMHO we can just mention it in Encoding. In Form, we can mention stuff that is only related to forms (name, address, time, date, etc.).

[r12a]

It's mentioned also in Forms because that (certainly when this was written) used to be one of the main problem areas for ubiquitous language support: the back end software crushed the multilingual input coming from the web page. Probably not so much the case for Chinese and Japanese, which have always had to support large language encodings, but for other languages.

[r12a]

Remember also that this is not a spec. Content authors are human (so far) and often need reminding of things at particular junctures.

[xfq]

Is this problem still common now?

If it is not common, I think eliminating some duplicate text can make this "Quick Tips" document simpler.

[aphillips]

It's still a distinct problem. Page encoding has to do with how the page generator (or content) is generated. Form encoding as to do with how form data is decoded at the server (and, to a far lesser extent, how the page is set up and encoded). It's good to call out the problem of decoding form data because errors in this space still cause data corruption problems for users.

[xfq]

I am more inclined to think that both of them are encoding problems. We can specifically point out the form problem in the description of the Encoding section, rather than mentioning encoding problem again in the Form section.