poire-z

> the good thing is that it is already quasy-toggleable because the reference pages can/must be enabled manually Oh, right. Forgot about how it works :) But there are still...

And here we go with the complications :/ Reference pages, as they can be strings (ie. roman numerals, `xviii`) can't really get involved in arithmetics (substractions for "pages left"). But...

> Reference pages, as they can be strings (ie. roman numerals, `xviii`) can't really get involved in arithmetics (substractions for "pages left"). So, I guess if substractions are not possible,...

A few tweaks done to the footer and the alt/top status bar with #11873 - which may make things a bit better for you synthetic people using synthetic page numbers...

I have no real idea how/what [gperf](https://www.gnu.org/software/gperf/) really does :/ But looking at the mupdf patch: - they replaced some late string comparisons with some id/hash comparisons - we already...

Pinging some KOReader contributors, that some PRs show you must be at ease with some of these languages I'm not: @frankyifei @houqp @chrox who did some CJK work on crengine,...

> I doubt UAX line-breaking rules deal with those kinds of grammatical/typographical conventions, do they I was hoping it would :) so we wouldn't have to bother with all these...

https://german.stackexchange.com/questions/117/what-is-the-correct-way-to-denote-a-quotation-in-german I figure that if german uses `»quoted stuff«` , in a sentence like `he said »this« and went away`, my french rules would prevent line breaking after `said` and...

> libunibreak in FBInk for line-breaking purposes [...] What you do with that information is left to you ;). libunibreak is probably the easiest stuff to integrate. I had some...

Another note related to the use of fonts: - crengine only gets to work with 2 fonts: the main one and a fallback one. We allow users to select both...