XandeKK
commented
3 weeks ago A problem I encountered while using this application involved the rendering of characters that the selected font did not support. To address this, I plan to add a fallback feature that will allow the use of another font if the base font is unable to render the necessary characters.
However, the question arises: which fonts should I use as fallback? I will use the "Comic Type" parameter that the user selects to specify the work they are typesetting (the "Comic Type" is an AI parameter for speech bubble detection, used to select the model, such as manga, manhwa, and manhua). Thus, with the "Comic Type," I will use the corresponding Noto font for the language of the work, which will cover some characters.
Still, there may be some characters that will not be rendered. To address this issue, user feedback will be necessary. For now, I will only add the Noto fonts, but there will also be an option for users to set their own fallback fonts.
Although the title implies code modifications, I didn't make significant changes compared to the previous version since it is already functional. I do have some additions in mind, but they'll only be necessary if they are suggested or if any issues arise.
One change I intended to implement is incorporating Lazy Loading for the fonts. At present, the code loads all user-selected fonts simultaneously. However, with Lazy Loading, fonts would be loaded only when the user actually needs them. As I mentioned earlier, I'll consider it if the need arises.