![]() |
#1 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 55
Karma: 392326
Join Date: Feb 2023
Device: Kobo Libra 2
|
Koreader UI and font/character display issues
I've been using Koreader to connect my Kobo to Calibre via my home wifi, the name of which contains the letter "ä" - when connecting to the network, Koreader displays that as "\xc3\xa4". Having looked a bit into it, it has something to do with string conversion - is there anything that I can do about it to fix it on my reader, or should it be something that would need to be handled in the source code? It's not a showstopper by any means, but it just looks a bit odd.
Also, sometimes when I'm trying to look up a word in a dictionary, it might display them quite oddly: for example, I was trying to look up the word "eclair" in an English-language book (I know it's French), and it brought up the English language explanatory dictionary (main) I had installed separately, and displayed the word as "÷clair" - is this an issue with that particular dictionary, or am I possibly missing some font (it is probably trying to display it as "éclair", but fails because it hasn't got the correct font; or the dictionary has the wrong encoding...) |
![]() |
![]() |
![]() |
#2 |
BLAM!
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
The broken UTF-8 handling for the Wi-Fi SSIDs is known, nobody's bothered looking into it in years given how low priority it is (at least for LGC, if we had an active CJK contributor, that'd be another kettle of fish ^^).
The dictionary issue is *probably* a dictionary issue, you'll have to give more details about how it's coded. |
![]() |
![]() |
Advert | |
|
![]() |
#3 | |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 55
Karma: 392326
Join Date: Feb 2023
Device: Kobo Libra 2
|
Quote:
And it seems the second issue is due to the dictionary - I looked around some more and extracted the dictionary to take a look at it, and it's wrong there as well. Notepad++ says the file is utf-8, but some of the characters are certainly something else - maybe it was converted from some other character set in the past and the errors remained. I tried to fix it by manually changing the character and recompressing the file, but then it just ceased to work altogether, so I just deleted and redownloaded the dictionary. I think I'll leave it be - the errors are slightly annoying, but fixing it is getting to be too much work just to see "éclair" written properly... |
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
wrong character in koreader | tartanpion | KOReader | 6 | 08-21-2020 05:42 PM |
Character detection issues | jgoguen | Development | 1 | 02-12-2013 07:58 PM |
Formatting folders...character cut-off issues? | trianglekitty | Library Management | 0 | 07-30-2012 08:11 PM |
PRS-T1 Font display issues (bold letters) | martingUSA | Sony Reader | 3 | 12-07-2011 04:53 PM |
Cannot display this Character | ghostyjack | Workshop | 3 | 08-18-2010 02:45 AM |