04-21-2017, 05:16 PM | #16 | ||
Wizard
Posts: 1,611
Karma: 724945
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
I can't find anything in the EPUB spec (although I'm not familiar with it, so that's based just on some skimming and Ctrl+F-ing) that would suggest going against letter and spirit of the HTML5 spec like that.
It sounds like Sigil is merely implementing a workaround against an internal bug (source): Quote:
Quote:
Last edited by Frenzie; 04-21-2017 at 05:18 PM. |
||
04-22-2017, 01:43 AM | #17 | |
Librarian
Posts: 346
Karma: 72225
Join Date: Apr 2015
Location: Liège - Belgium
Device: kobo gloHD - KA1
|
Quote:
@Frenzie : I was probably taking my experience with xml to xhml... Thanks for the advice with dtd ! Last edited by cramoisi; 04-22-2017 at 02:02 AM. |
|
Advert | |
|
04-22-2017, 03:23 AM | #18 | |
Wizard
Posts: 2,608
Karma: 3000161
Join Date: Jan 2009
Device: Kindle PW3 (wifi)
|
Quote:
Last edited by roger64; 04-22-2017 at 03:25 AM. |
|
04-22-2017, 05:17 AM | #19 |
Wizard
Posts: 1,611
Karma: 724945
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
In general I would agree. Just because the spec says something doesn't mean I agree with it, but it's still the spec. Why type & mdash ; when you can just type and see —? And what's the point of the aforementioned bigodot anyway? But characters like non-breaking space, thin space, and hair space are slightly different.
Sure, I could set up an easy way to type them. Besides which, Compose, space, space for nbsp is already there, or I could just use a Unicode character table. The problem is that I still couldn't really see them unless I paid extremely close attention — heck, non-breaking space is completely invisible in most circumstances. Is it there? Is it missing? Is it there by accident? Ah, so just use & # 160 ; Well, I'd suspect anyone who thinks that's better than & nbsp ; of being a computer failing the Turing test. Last edited by Frenzie; 04-22-2017 at 05:23 AM. |
04-22-2017, 06:43 AM | #20 |
Wizard
Posts: 2,608
Karma: 3000161
Join Date: Jan 2009
Device: Kindle PW3 (wifi)
|
I never had any problem reading EPUB with Koreader using utf-8 characters in EPUB3 format.
Another reason I dislike using nbsp (as such) as well as & # 160 for French text is because as there are really thousands of them (if you wish to abide by the French typography rules), it makes proofreading even a part of text unpleasant. Compare it using the Calibre editor with the plain UTF-8. The appearance is cleaner and Turing can't help you on this... |
Advert | |
|
04-22-2017, 08:32 AM | #21 |
Wizard
Posts: 1,611
Karma: 724945
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
Sure, that's understandable. There's a reason I prefer to write Markdown when I can and not XML, LaTeX or HTML. I think it's slightly odd that line-breaking algorithms would all do the wrong thing on "« " and " »". It seems like something that should be easy to automate, even if only in French… But anyway, my point all along has been about HTML5, not personal preferences.
Btw, what do you use to protect against accidental "« " over "«*"? (Assuming those came out correctly.) [Edit: I just noticed that this forum seems to have changed all of my non-breaking spaces into asterisks.) PS In LibreOffice I just noticed that non-breaking spaces come with a gray background. Not bad. I wonder if I can make Geany do something like that, because obviously nobody would actually prefer an ugly nbsp… it's just that sometimes ugly beats invisible. |
04-25-2017, 03:47 AM | #23 | |
Wizard
Posts: 2,608
Karma: 3000161
Join Date: Jan 2009
Device: Kindle PW3 (wifi)
|
A recent comment from one of the the authors of Sigil that maybe of interest:
Quote:
Congratulations. Koreader is making great progress every single day. Last edited by roger64; 04-25-2017 at 03:55 AM. |
|
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Non-breaking space | JSWolf | ePub | 38 | 06-09-2020 09:00 PM |
Non breaking space (possible) bug | rferran | Sigil | 3 | 12-02-2016 12:33 PM |
Non-Breaking space | drago87 | Conversion | 0 | 01-20-2016 05:52 AM |
Why the non-breaking space? | Notjohn | Sigil | 2 | 06-08-2015 05:24 AM |
Non-breaking space (doubled) bug | Camelot | Sigil | 49 | 02-13-2015 04:20 PM |