MobileRead Forums - View Single Post

NiLuJe · 06-03-2018, 12:01 PM

AFAICT, the layout is chosen based on the language set in KOReader.

I'm not overly familiar with the layout backend, but that shouldn't be impossible, if possibly rendering the button actually impractical if it ends up switching between 1457 layouts when a random users only needs 2 or 3

.

As for diacritics, while I like the idea in theory (it's basically what any touch aware virtual-keyboard does when shown on an LCD), I'm afraid that in practice, because of the latency of the eInk tech, it'd end up clunky and messy.

06-03-2018, 12:01 PM	#2
NiLuJe 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	AFAICT, the layout is chosen based on the language set in KOReader. I'm not overly familiar with the layout backend, but that shouldn't be impossible, if possibly rendering the button actually impractical if it ends up switching between 1457 layouts when a random users only needs 2 or 3 . As for diacritics, while I like the idea in theory (it's basically what any touch aware virtual-keyboard does when shown on an LCD), I'm afraid that in practice, because of the latency of the eInk tech, it'd end up clunky and messy. Last edited by NiLuJe; 06-03-2018 at 08:36 PM.