On 2012-04-18 22:34, Glenn Maynard wrote:
(It would be pretty neat if that could be changed to *always* using HTML
escapes for non-ASCII, except when encoding to UTF-8, since that's not
introducing anything new--you can already receivex1234; escapes in POST
data--and it would alleviate the form
This is a decoder error seems odd; it's descriptive language (this thing
must be made true) rather than declarative (do this thing). I'd suggest
the declarative language Emit a decoder error and Emit an encoder error.
If code point is equal or greater than lower boundary is more naturally
On Tue, 17 Apr 2012 14:01:36 +0200, Julian Reschke julian.resc...@gmx.de
wrote:
As a nit, I believe that Character Encoding would make a better title
than just Encoding.
I was thinking maybe Text Encoding given how we're using that for the
API, but I like single-word specs so I'm quite
On Wed, 18 Apr 2012 15:40:33 +0200, Glenn Maynard gl...@zewt.org wrote:
This is a decoder error seems odd; it's descriptive language (this
thing must be made true) rather than declarative (do this thing).
I'd suggest the declarative language Emit a decoder error and Emit an
encoder error.
On Wed, Apr 18, 2012 at 12:12 PM, Anne van Kesteren ann...@opera.comwrote:
If code point is equal or greater than lower boundary is more naturally
greater than or equal to (and less than or equal to). That said,
this would be much clearer with interval syntax:
If code point is in the range
On 19/04/2012 07:34, Glenn Maynard wrote:
On Wed, Apr 18, 2012 at 12:12 PM, Anne van Kesteren ann...@opera.comwrote:
Then we'd first have to introduce interval syntax to the English language.
We could do that I suppose in the Terminology section if you think it would
be better.
It would
I find having the steps incrementing the byte and code point pointers
being before the current byte or code point is processed (except for the
EOF check) confusing but a way to make it less confusing is not obvious.
Regards
-Mark
On 17/04/2012 18:30, Anne van Kesteren wrote:
Hi,
Apart
Hi,
Apart from big5 (which requires some more research) all encoders and
decoders are now defined:
http://dvcs.w3.org/hg/encoding/raw-file/tip/Overview.html
I think it is now ready to be integrated into HTML.
I also think as a next step we might want to define the encoding sniffing
On 2012-04-17 11:30, Anne van Kesteren wrote:
Hi,
Apart from big5 (which requires some more research) all encoders and
decoders are now defined:
http://dvcs.w3.org/hg/encoding/raw-file/tip/Overview.html
...
As a nit, I believe that Character Encoding would make a better title
than just
