11-11-2020, 02:13 PM | #1 |
Connoisseur
Posts: 77
Karma: 10
Join Date: Aug 2010
Location: Murcia/Spain
Device: Android 12
|
newbie: weird char display problem
I have an epub2 file, which displays fine with Foliate on Linux, but on Moon+Reader on Android, displays weird char for single quote. Sigil tells me that the encoding and charset are both UTF-8. How can i go to fix this problem? I tried to change it to ISO-8859-1 (I saw in the internet that this sometime fix the problem), but not in my case.
|
11-11-2020, 03:27 PM | #2 |
Running with scissors
Posts: 1,552
Karma: 14325282
Join Date: Nov 2019
Device: none
|
It sounds like the font is missing that glyph. Try using a different font and see what happens, e.g., one from google.
|
11-12-2020, 01:12 AM | #3 | |
Wizard
Posts: 2,297
Karma: 12126329
Join Date: Jul 2012
Device: Kobo Forma, Nook
|
Quote:
Many times, people accidentally use ` GRAVE ACCENT (the little key to the left of '1') instead of ‘ LEFT SINGLE QUOTE. Code:
This is an `example´ of grave and acute accent. (Wrong) This is an ‘example’ of left and right single quote. (Correct) Grave -> Left Single Quote Search: ` Replace: ‘ Acute -> Right Single Quote Search: ´ Replace: ’ To Spot Other Strange Characters In Sigil, Press Tools > Reports > Characters in HTML Files. Scroll through the list, and look for anything that looks like a "weird" apostrophe. Then you could double-click on a character in the list, and Sigil should jump you to its location in the code. These 3 are correct:
If dealing with double quotes, these 3 are correct too:
Any other quote-looking characters should probably be inspected. Last edited by Tex2002ans; 11-12-2020 at 01:17 AM. |
|
11-13-2020, 03:41 AM | #4 |
Connoisseur
Posts: 77
Karma: 10
Join Date: Aug 2010
Location: Murcia/Spain
Device: Android 12
|
Thanks all for your reply, I'll try out your suggestions during this weekend to see if it'll fix the problem.
@Tex2002ans, thanks for the tips for Sigil, learned something new today. |
11-15-2020, 02:28 PM | #5 |
Connoisseur
Posts: 77
Karma: 10
Join Date: Aug 2010
Location: Murcia/Spain
Device: Android 12
|
Here's an update, I'm afraid I messed up pretty good the file I was working on, I think when I tried to change from UTF-8 to ISO-8859-1, I did not reverse back the changes I made, so the weird char got worse and it took me several hours trying to fix it, at the end I gave up. Got a back up file and now everything is fine. Thanks so much for your suggestions.
|
11-15-2020, 02:33 PM | #6 |
Running with scissors
Posts: 1,552
Karma: 14325282
Join Date: Nov 2019
Device: none
|
|
11-15-2020, 05:17 PM | #7 | ||
Wizard
Posts: 2,297
Karma: 12126329
Join Date: Jul 2012
Device: Kobo Forma, Nook
|
Quote:
But what was the weird character? Can you copy/paste it here? Quote:
You see this pretty often when characters like the: — (EM DASH) turn into: – Good tools like Calibre should be able to convert to UTF-8 properly. But if you already mangled your original beyond repair... usually it's best to do what you did—start from your last good backup. |
||
Tags |
charset, encodings, epub 2 |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
regex newbie search end of string char problem | michaelbr | Sigil | 6 | 10-15-2020 01:54 PM |
Problem with char encoding | sse450 | Calibre | 7 | 12-02-2019 12:57 AM |
Display Char Value | phossler | Editor | 2 | 05-05-2014 05:27 PM |
Weird, temporary, display bug | zartemis | Amazon Kindle | 1 | 11-26-2007 05:59 AM |