Marcin Hanclik wrote:
Hi Marcos,
Thanks with remark:
1. deleted the PC's ABNF definition of utf8-char.
OK.
2. added The utf8-char rule is defined in section 4 of [UTF-8].
I think it needs further refinement, since section 4 of [UTF-8] is for the full
range of utf-8, i.e. starting
On Tue, Jul 28, 2009 at 12:04 PM, Marcin
Hanclikmarcin.hanc...@access-company.com wrote:
Hi Marcos,
Unless it's broken (?), I would prefer to leave it as is.
I think that PC should either change the grammar (as suggested in my email)
or specify that the zip-rel-path operates on characters.
-163-8290-646
E-Mail: marcin.hanc...@access-company.com
-Original Message-
From: marcosscace...@gmail.com [mailto:marcosscace...@gmail.com] On Behalf Of
Marcos Caceres
Sent: Monday, July 27, 2009 6:22 PM
To: Marcin Hanclik
Cc: public-webapps@w3.org
Subject: Re: [PC] utf8-char in Zip-rel-path
On Sun, Jul 26, 2009 at 11:29 PM, Marcin
Hanclikmarcin.hanc...@access-company.com wrote:
Hi,
Given the fact that
Rule names are case insensitive.
http://tools.ietf.org/html/rfc5234#section-2.1
it could potentially be better to rename the rule from utf8-char to
something else, since it
Hi Marcos, All,
Following my previous email about Zip-rel-path and concluding that utf8-char
non-terminal is wrongly specified (i.e. it indicates that Zip-rel-path operates
on characters, not bytes, whereas I assume operation on bytes is our target), I
wonder whether Zip-rel-path shouldn't
