![]() |
#16 |
Enthusiast
![]() Posts: 34
Karma: 10
Join Date: Dec 2012
Location: Italy
Device: Kindle
|
In other words, who will fix it?
|
![]() |
![]() |
![]() |
#17 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
|
There is no one actively working on Sigil code so what you have may be the last version although someone might do something someday.
Dale |
![]() |
![]() |
Advert | |
|
![]() |
#18 |
Enthusiast
![]() Posts: 34
Karma: 10
Join Date: Dec 2012
Location: Italy
Device: Kindle
|
I had a dream... but Sigil 0.8.1 (built Windows x64, loaded Qt 5.3.2) does not fix the issue. Ciao
|
![]() |
![]() |
![]() |
#19 |
Sigil Developer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 8,485
Karma: 5703586
Join Date: Nov 2009
Device: many
|
Hi,
I did not even know about this bug so there was most likely no one working on it. That said code in xhtml files must be "normalized" NFC unicode according to the spec. See this Wikipedia article for a description of what NFC text means for unicode: http://en.wikipedia.org/wiki/Unicode_equivalence So if you have input correct "NFC" - Normalized Form Canonical Composition that still shows a bug in code view please post a the smallest example epub that shows the issue and I will see what I can do about it. If the problem is in Qt, not Sigil, then a bug report should be filed with Qt. Thanks, KevinH |
![]() |
![]() |
![]() |
#20 |
A curiosus lector!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 463
Karma: 2015140
Join Date: Jun 2012
Device: Sony PRS-T1, Kobo Touch
|
@pgfiore
And what happen if you get rid of all Calibre classes and span? With something like this (in an epub file): Code:
<?xml version="1.0" encoding="utf-8" standalone="no"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="it"> <head> <title></title> </head> <body> <h3>Ciao!</h3> <p>è acquistabile <em>accessibilità</em> alle".</p> <p> etc., etc... La forêt ambiguë est bête, là où l'ombre s'estompte</p> </body> </html> |
![]() |
![]() |
Advert | |
|
![]() |
#21 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 5,683
Karma: 24031401
Join Date: Dec 2010
Device: Kindle PW2
|
Quote:
IMHO, this is a non-issue, since there's no advantage in coding accented characters as two sequential characters. On the contrary, it will slightly increase the file size of ePubs in languages that use lots of accented characters. Also in my experience some diacritics are not correctly displayed above or below the base character, depending on the font and the rendering engine. For these reasons precomposed diacritics are almost always the better choice. |
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kindle Touch - Book titles acting weirdly | Katdragon | Amazon Kindle | 2 | 01-01-2013 07:57 AM |
Speakin' of weird: Linux build eating accented chars. | Hitch | Sigil | 2 | 12-17-2010 01:24 PM |
iRiver Story managed by Calibre | mareksuski | Calibre | 14 | 02-19-2010 02:45 AM |
Replacing Chars in URL | DAiki | Calibre | 5 | 10-13-2008 09:25 AM |