Skip to content
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

Closed
murata2makoto opened this issue Sep 11, 2016 · 4 comments
Closed

What does "space-separated" mean? #870

murata2makoto opened this issue Sep 11, 2016 · 4 comments
Labels
EPUB32 Issues from 3.0.1 resolved in the EPUB 3.2 specification Topic-ContentDocs The issue affects EPUB content documents
Milestone

Comments

@murata2makoto
Copy link
Contributor

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?

@iherman
Copy link
Member

iherman commented Sep 11, 2016

On 11 Sep 2016, at 07:36, MURATA Makoto notifications@github.com wrote:

In the definition http://www.idpf.org/epub/31/spec/epub-contentdocs.html#sec-xhtml-conf-rsof epub:type, we have a phrase "space-separated terms". What does it mean? There are many space characters https://www.cs.tut.fi/%7Ejkorpela/chars/spaces.html in Unicode. Does it allow CR and LF?

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…

@murata2makoto
Copy link
Contributor Author

That's my guess too, but we need more explicit words.

@laudrain
Copy link

In real production world, I've never seen someone using something else than a regular space character (0x20) in separating attributes values.
As it is XML, the proper terminology is indeed to refer to white-space.

@mattgarrish mattgarrish added Status-Proposed Solution A proposed solution has been included in the issue for working group review Topic-ContentDocs The issue affects EPUB content documents labels Sep 11, 2016
@mattgarrish mattgarrish added this to the EPUB 3.1 milestone Sep 11, 2016
@mattgarrish
Copy link
Member

Proposed Solution

Add reference to XML white space.

mattgarrish added a commit that referenced this issue Sep 14, 2016
#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.
@mattgarrish mattgarrish removed the Status-Proposed Solution A proposed solution has been included in the issue for working group review label Sep 25, 2016
@mattgarrish mattgarrish added the EPUB32 Issues from 3.0.1 resolved in the EPUB 3.2 specification label Aug 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EPUB32 Issues from 3.0.1 resolved in the EPUB 3.2 specification Topic-ContentDocs The issue affects EPUB content documents
Projects
None yet
Development

No branches or pull requests

4 participants