-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What does "space-separated" mean? #870
Comments
I guess the right answer is that whatever XML allows as separating terms is valid here. After all, this is an XML attribute. Ie, the right terminology is probably to say 'white space separated terms', where white space is defined here: https://www.w3.org/TR/xml/#NT-S https://www.w3.org/TR/xml/#NT-S this means that yes, CR and LF are valid indeed. But none of the special space characters listed in the page you referred to are.. My two cents… |
That's my guess too, but we need more explicit words. |
In real production world, I've never seen someone using something else than a regular space character (0x20) in separating attributes values. |
Proposed Solution Add reference to XML white space. |
#870 - clarify white space in epub:type #866 - clarify hyperlinks outside container do no get listed in manifest #855 - remove normative keyword from informative discouraged constructs #853 - separate/clarify rdfa and microdata usage and support #847 - improve media overlays purpose and scope description #844 - remove "user" as a defined term #842 - clarify meaning of element "value" as text content #834 - remove html processing model from relationship description Also include minor wording clarifications suggested as part of the content documents review in issues #880, #879, #878, #877, #876, #875, #874, #868, #867, #864, #863, #860, #857, #856, #852, #849 and a few issues reported by via the mailing list.
In the definition of epub:type, we have a phrase "space-separated terms". What does it mean? There are many space characters in Unicode. Does it allow CR and LF?
The text was updated successfully, but these errors were encountered: