In the context of automatic parsing of a CSS value against a value definition, the initial field of the negative descriptor should be defined with a value that can be parsed against the value field. But the initial field is defined with "\2D" ("-" hyphen-minus).
I suggest using "\2D" or just "-" (I believe tokenization will replace \\2d by -) and to define in prose that it corresponds to ("-" hyphen-minus), or to use some kind of markup (containing ("-" hyphen-minus)) that provides additional details that w3c/reffy can read to separate it from the initial value.
FYI, @tidoust.
EDIT: the same issue applies to prefix, defined with "" (the empty string), and suffix, defined with "\2E\20" ("." full stop followed by a space).
In the context of automatic parsing of a CSS value against a value definition, the
initialfield of thenegativedescriptor should be defined with a value that can be parsed against thevaluefield. But theinitialfield is defined with "\2D" ("-" hyphen-minus).I suggest using
"\2D"or just"-"(I believe tokenization will replace\\2dby-) and to define in prose that it corresponds to ("-" hyphen-minus), or to use some kind of markup (containing ("-" hyphen-minus)) that provides additional details thatw3c/reffycan read to separate it from theinitialvalue.FYI, @tidoust.
EDIT: the same issue applies to
prefix, defined with "" (the empty string), andsuffix, defined with "\2E\20" ("." full stop followed by a space).