ISSUE-152: New content and formats must exclusively use the utf-8 encoding
New content and formats must exclusively use the utf-8 encoding
- State:
- CLOSED
- Product:
- encoding
- Raised by:
- Richard Ishida
- Opened on:
- 2012-03-21
- Description:
- "New content and formats must exclusively use the utf-8 encoding."
We need to examine the ramifications of this. Should it say must or should wrt content?
- Related Actions Items:
- No related actions
- Related emails:
- RE: Comments on: W3C Process2015 (from szilles@adobe.com on 2015-04-13)
- Re: Comments on: W3C Process2015 (from singer@apple.com on 2015-04-06)
- RE: Comments on: W3C Process2015 (from addison@lab126.com on 2015-04-06)
- RE: Comments on: W3C Process2015 (from szilles@adobe.com on 2015-04-06)
- Re: Comments on: W3C Process2015 (from singer@apple.com on 2015-04-06)
- Re: Comments on: W3C Process2015 (from chaals@yandex-team.ru on 2015-04-06)
- RE: Comments on: W3C Process2015 (from szilles@adobe.com on 2015-04-06)
- Comments on: W3C Process2015 (from addison@lab126.com on 2015-04-03)
- [minutes] Internationalization telecon 2014-07-17 (from ishida@w3.org on 2014-07-17)
- I18N-ISSUE-152: New content and formats must exclusively use the utf-8 encoding [Encoding-prep] (from sysbot+tracker@w3.org on 2012-03-21)
Related notes:
I'm happy that this has received discussion elsewhere, and so am closing this issue.
Richard Ishida, 19 Aug 2014, 07:36:25Display change log