21728 2013-04-17 04:28:37 +0000 [HTML] editorial: 4.10.20: "either are greater" 2013-07-15 22:28:07 +0000 1 1 1 Unclassified WHATWG HTML unspecified All All CLOSED FIXED P2 trivial Unsorted 1 jmdyck ian ian mike contributor oldest_to_newest 86324 0 jmdyck 2013-04-17 04:28:37 +0000 In 4.10.20 "APIs for the text field selections", in the algorithm for setRangeText(...), step 3 says: If either start or end are greater than the length of ... Change "are" to "is". 86325 1 jmdyck 2013-04-17 05:14:06 +0000 Similarly in 5.4.1.1 "Conversion to vCard", step 12 says: If either of sex or gender-identity have a value ... 86402 2 ian 2013-04-19 23:36:51 +0000 Hmm. Is there a grammatical argument to be made that this is short for "either or both of", and would that get the plural conjugation? I want to avoid implying that if both cases match the criteria, that the condition is not met, without being overly verbose about it. 86409 3 jmdyck 2013-04-20 05:35:41 +0000 (In reply to comment #2) > Hmm. Is there a grammatical argument to be made that this is short for > "either or both of", and would that get the plural conjugation? That might be a bit subtle for some readers of the spec, especially those who aren't native speakers of English. Moreover, that argument might suggest that the *singular* form is short for "either but *not* both", which you probably don't want. E.g.: either its horizontal dimension or its vertical dimension is zero either dirtyWidth or dirtyHeight is negative or zero either x or y is less than 0 either name, http-equiv, or itemprop is specified either of the arguments is infinite or NaN If either fails In some of those, it *can't* be both, but in some it probably can, and I'm guessing you want to implicitly include the "or both". > I want to avoid implying that if both cases match the criteria, that the > condition is not met, without being overly verbose about it. Maybe the best thing is to just say so somewhere in the introductory material. You could also point out that in cases where you *do* want to exclude the "or both" case, the spec uses explicit constructions such as: -- If just one of either w or h is zero -- either a rel attribute or an itemprop attribute, but not both. 88659 4 ian 2013-06-04 20:47:23 +0000 Yeah, fair enough. 88660 5 contributor 2013-06-04 20:48:53 +0000 Checked in as WHATWG revision r7898. Check-in comment: Improve grammar. http://html5.org/tools/web-apps-tracker?from=7897&to=7898