View Single Post
Old 03-19-2021, 05:53 PM   #88
murraypaul
Interested Bystander
murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.murraypaul ought to be getting tired of karma fortunes by now.
 
Posts: 3,726
Karma: 19728152
Join Date: Jun 2008
Device: Note 4, Kobo One
Quote:
Originally Posted by stevenaleach View Post
Plus, reflowable text would mean having rendered characters in a set of sizes in a set of fixed-width fonts (at least a serif and non-serif in regular, bold, italic, and bold-italic) -- a route I'd started to go down, generating three-bit (to free a bit as a run-length repeat flag) packed-pixel font pixmaps... but if I were to cover all the characters I'd like to support (basic and extend Latin, Greek characters, mathematical symbols and operators) in a range of sizes useful on the e-ink display... well... yikes... that's a lot of data just for fonts.
I think you are working more directly with the hardware, rather than using the M5 development stack?
Because the board API they supply already has code for the device to render arbitrary TTF fonts at different sizes and display them. They don't have to be fixed-width either.
I have a toy-working text + basic bold/italic display with full justification with non-fixed-width fonts, the API does most of the work already.
murraypaul is offline   Reply With Quote