ISSUE-327: 'Fallback' encoding

'Fallback' encoding

State:
CLOSED
Product:
css-syntax
Raised by:
Richard Ishida
Opened on:
2013-12-19
Description:
3.2 The input byte stream
http://dev.w3.org/csswg/css-syntax/#input-byte-stream

Why refer to the 'fallback' encoding? Why not just say, "determine the encoding:"?

I guess this might be a question for the Encoding spec, but it's not clear to me why you would go to all the trouble of determining a fallback encoding before testing whether there is a byte order mark, since if there is you just throw all that work away anyway.

It would also be much clearer if the steps simply said
1. test for http...
2. check for bom
3. check for @charset
4. look for environment encoding
5. use utf-8

Related Actions Items:
No related actions
Related emails:
  1. [minutes] Internationalization telecon 2013-12-19 (from ishida@w3.org on 2014-01-14)
  2. [css-syntax] CR publication, Encodings and @charset (from simon.sapin@exyr.org on 2014-01-07)
  3. I18N-ISSUE-327: 'Fallback' encoding [.prep-css3-syntax] (from sysbot+tracker@w3.org on 2013-12-19)

Related notes:

I think the change makes this clearer. Recommend close.

Richard Ishida, 15 Jan 2014, 14:09:16

satisfied

Addison Phillips, 16 Jan 2014, 17:01:17

Display change log ATOM feed


Addison Phillips <addison@amazon.com>, Chair, Richard Ishida <ishida@w3.org>, Fuqiao Xue <xfq@w3.org>, Atsushi Shimono <atsushi@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $