02-19-2019, 02:07 PM | #61 |
Gentleman and scholar
Posts: 10,994
Karma: 108312789
Join Date: Jun 2015
Location: Space City, Texas
Device: Clara HD; Nook ST w/Glowlight, (2015) Glowlight Plus, Paperwhite 3
|
I've tried that and still don't see it, using Georgia, Noto Serif or Bookerly. Did I maybe do something wrong?
|
02-19-2019, 02:41 PM | #62 | |
Grand Sorcerer
Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
It'll take me a little while but later I'll come back and add some screenshots showing ligatures using those 3 fonts in a test kepub. ETA: As I mentioned earlier it's only going to look as good as the font you're using allows ... As @ps67 says, it looks like the Kobo built-in Georgia hasn't actually got any ligatures. Either the glyphs are missing or there is no ligature lookup table defined. My copy of Noto Serif only has 4 ligatures: fi, fl, ffi, ffl, but they are displayed below. My copy of Bookerly has 6: fi, fl, ffi, ffl, ff, ft The sideloaded font I use most often is MinionPro which has 27 ligatures defined, but only 8 of them are much use to me: fi, fl, ffi, ffl, ff, ft, fj, Th Perhaps the rest are more relevant to other languages. Last edited by jackie_w; 02-19-2019 at 04:14 PM. Reason: ETA & added screenshots |
|
02-19-2019, 03:09 PM | #63 |
Guru
Posts: 732
Karma: 7025494
Join Date: Aug 2017
Location: Italy
Device: Kindle Paperwhite, Kobo Elipsa, Pocketbook Color PB633, Inkpad Color
|
Georgia has no ligatures (no fi ligature) also in Epub. I don't know if there is a way to have ligatures with Georgia (of course You can use Georgia Pro if You own it).
@jackie_w: Did You note any drawback, like a lesser precision When You return in the previous position (may be You return on the span, not on the correct paragraph?) Last edited by ps67; 02-19-2019 at 03:25 PM. Reason: Did You note any drawback... |
02-19-2019, 04:11 PM | #64 | |
Grand Sorcerer
Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
However, it doesn't necessarily mean that a problem doesn't exist, it just means I've never registered it or it hasn't bothered me enough to get irritated by it. This is the problem when a hack only has an audience of one |
|
02-19-2019, 04:58 PM | #65 | ||
Gentleman and scholar
Posts: 10,994
Karma: 108312789
Join Date: Jun 2015
Location: Space City, Texas
Device: Clara HD; Nook ST w/Glowlight, (2015) Glowlight Plus, Paperwhite 3
|
Quote:
Quote:
|
||
02-19-2019, 05:03 PM | #66 | |
Guru
Posts: 732
Karma: 7025494
Join Date: Aug 2017
Location: Italy
Device: Kindle Paperwhite, Kobo Elipsa, Pocketbook Color PB633, Inkpad Color
|
Quote:
I was wondering if Kobo ever thought about solving the ligature problem in Kepub. If they consider it a problem. Because otherwise the format is quite good, I really like the images that can be enlarged. Also pop up notes work quite well even if they are even better in the Kindle because it handles very long notes too, while Kobo provides a preview but if the note is too long you have to click on "see more" and go to the position of the note. |
|
02-19-2019, 06:05 PM | #67 | |
Grand Sorcerer
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
Putting the trailing spaces outside the spans shouldn't be a problem with the reading position. Except maybe if the end of a sentence was the end of a page. The stored position is the first character on a page. If that was to be the spaces after a sentence, I don't know what would happen. There is a problem with highlighting. If you highlight so that it starts or ends on the spaces outside the span, and save that, when you reopen the book the highlight isn't displayed properly. An early version of the extended driver did this. I remember discussing it in the driver's thread. |
|
02-19-2019, 06:50 PM | #68 | ||
Grand Sorcerer
Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
I never risked trying one koboSpan per paragraph because currently Kobo's method for koboSpans only seems to contain text not other tags. I wasn't sure what the consequences might be. I don't really have much use for highlighting, but if I did and starting/ending a highlight on a space caused problems then I think I'd use the same approach as that old Doctor-Patient joke ... Quote:
|
||
02-19-2019, 06:55 PM | #69 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@jackie_w: I'm game to take this for a span^Wspin for a while if you have an up-to-date patch laying around .
(NB: I stand by that terrible pun .) |
02-19-2019, 07:31 PM | #70 | |
Grand Sorcerer
Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
I don't have a copy of the official KTE with only the koboSpan hacks added, but I know you're a smart lad where Python is concerned I'll send you a PM shortly with a link to my fully hacked KTE with a few notes on where to find the relevant bits. I think you should find it easy to extract what you need. Perhaps you'll come up with a better way of doing it? |
|
03-24-2019, 06:15 PM | #71 |
Enthusiast
Posts: 36
Karma: 10
Join Date: Mar 2019
Device: Kobo Clara HD
|
Hi,
I am new in the forum, while lately having a KOBO Clara (earlier I had a Kindle Keyboard) I try to make eBooks, my method is creating a clean html from word, then clean it in a way remove all spans, in sigil build this code with my CSS file to an epub, finally in calibre convert it to azw... I was happy to have my first KOBO but sending my first epub to the device - using KTE - I was a bit (lot) disappointed. I didn’t read it earlier but kepub parser is not handling the "page-break", so I must split all the books before breaks.... I thought, can be handle... But next: not handling the “aligns” as well. Reading in forum a lot realized two way, either hack or touch again all the books what I want to send my device and place the "*" and the important! into all my CSS’s lines which are including "align". As I am living in Hungary, readying Hungarian language books. Here in our typography we have different layout like for ex. in English part of the word. And here comes the biggest issue. Sending the above mentioned "re-created" test book to device it looks UGLY. (and it comes how the dialogues are handled in our typography. Here is a sample: "– Semmi újság? – kérdezte." EnDash Semmi..... I learned here that the body-tag "text-rendering : optimizedspeed/legibility…" and the kobo.spans placement are responsible for the layout a lot. So, my problem with the above sentence: We start dialogues with a dash, the following nbsp is NOT a fix length space so dialogues in a row (each is in new line) looks ugly. I have read here that there is an issue with dash handling as well... Plus, in the above example the "?" is NOT the end of the sentence so making the span around just resulting worse layout. I would like to have some help from experts. In the "container „of KTE I know there is a line with regexp where finds the sentence ends for putting kobo.spans around. Can I "jump" those "! ", "? ",". " situations where the following letter IS NOT a capital? I would like to have the kepub where kobo.spans are only at the sentence start and end, and not splitting a sentence with several kobo.spans Last edited by Gorcsev; 03-24-2019 at 06:26 PM. |
03-24-2019, 07:43 PM | #72 | |||
Wizard
Posts: 2,736
Karma: 6990705
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
|
Quote:
Quote:
Quote:
|
|||
03-24-2019, 09:46 PM | #73 |
Grand Sorcerer
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
@Gorsev: There has been some discussion of these problems in the past. Some of them are inherent in kepub parser or the underlying controls used. There isn't any real way to fix them. From memory, using a non-break space was one of the suggestions to improve things. But, I think if you don't justify the text it probably works better.
One thing to do is look at what Kobo does with books from them. If you can find a Hungarian book in the Kobo store and look at it, you can get a clue. I don't know if they have them, but, I don't see it listed as a choice for the store. And I don't know how to search for one. There are other languages that do dialog in a similar manner (and, of course, which ones escapes me completely at the moment). Maybe looking at samples in those would help work out the best thing to do. As @geek1011 said, and is sort of discussed further up, the KoboTouchExtended driver or kepubify could be modified to use different strategies for placing the spans. The KoboTouchExtended driver should match what Kobo does reasonably well, unless something has changed recently. The simplest alternative would be one span per paragraph. I know that works for most situations, but I don't know what happens if there are tags inside the paragraph. |
03-25-2019, 03:57 AM | #74 | |||
Enthusiast
Posts: 36
Karma: 10
Join Date: Mar 2019
Device: Kobo Clara HD
|
Thank you all of your replies
Quote:
Quote:
Quote:
Thank you, your reply most probably I will make a comparison with sample text what is the difference between KTE-kepubify spanning. |
|||
03-25-2019, 04:06 AM | #75 | |
Enthusiast
Posts: 36
Karma: 10
Join Date: Mar 2019
Device: Kobo Clara HD
|
Quote:
Unfortunately you are right it was discussed earlier, but as I read through that post it was not a settled down solution. As I searched the net, the non-break space is not 100% means "not-variable length space". Better solution (I tried in kepub) would be the fix length "1/4 em-space" but the device displays a □ when the "text-rendering: optimezedlegibility/speed" is used in body tag. Interim solution a fix length "en-space" but again, it means should be touched all the books what I sideload to KOBO . |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
3.26.1 not converting Kepub format | RZetlin | Conversion | 2 | 06-26-2018 02:47 AM |
Aura H2O trying kepub and have questions | Shadowjack | Kobo Reader | 25 | 12-26-2017 04:30 AM |
Glo Question regarding kepub format | user2178319 | Kobo Reader | 18 | 05-14-2015 12:48 PM |
Kepub format and Koreader | gontofe | Kobo Reader | 4 | 08-20-2014 09:10 AM |
Harry Potter KePUB format | Gazella | Conversion | 19 | 04-13-2014 06:54 AM |