View Single Post
Old 12-10-2015, 12:46 PM   #228
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
Quote:
Originally Posted by dgatwood View Post
I think that what the original poster was saying is that if you use CSS to format standardized semantic markup instead of formatting HTML whose semantics are defined only by arbitrary, author-defined classes, then it would be easier for book readers to define alternative styles that override the publisher design in a way that the individual reader prefers. And this is almost certainly true.

With that said, the same thing could also be achieved by convincing the EPUB standards folks to come up with a standard set of CSS classes that should be present in all books, and a standard set of rules for when and how readers can override CSS classes (both those and others). And IMO, the EPUB folks need to do that anyway; right now, it's the Wild West out there.
And content creators need to be able to define the look with more granularity than is allowed by such a rigid XML spec.
So HTML is the best of both worlds unfortunately it relies on people not being utter fools.

Quote:
I'm going to have to agree with the original poster on this one. A paragraph is a unit of text, so a paragraph that contains no text is not a paragraph, and shouldn't be marked up using a paragraph tag. At best, it should be a div, but really, vertical spacing should be handled with CSS instead.
I am going to have to disagree on whether you internalized the meaning of my post that you quoted.

Perhaps it would help if you didn't chop off the second half:
Quote:
Originally Posted by eschwartz View Post
I agree that there are some formatters that use it in the wrong way.
Well, to clarify, what you are saying is exactly the wrong way that I speak of.

But in theme with @Sarmat's suggestions so far, I believe he would rather outlaw the non-breaking-space character entirely.
Why, I don't know. How, I don't know that either. (XML only works with the Sarmat subset of unicode?)

Unless you can propose to me an alternative explanation of his statement, that would fix the non-breaking-space-as-a-paragraph issue, without outlawing the non-breaking-space.
Because, duh, content creators can write <para>&nbsp;</para> just as easily as <p>&nbsp;</p>
Unless that whole line of thought was an irrelevant tangent.
eschwartz is offline   Reply With Quote