jared.olson Posted March 12, 2018 Report Share Posted March 12, 2018 Hi, My company is using uGFX for a project in which we need to translate and display all of our text in a variety of languages. Right now I am working on the Simplified Chinese text, and have encountered a strange bug with MCUFont that I am wondering if anyone else has encountered or is aware of. The problem I am having is that certain, seemingly arbitrary, Chinese glyphs are displaying on my screen as completely different Chinese glyphs. For example, if I attempt to print the string "共2页", on my screen it will appear as "停2页", where the first glyph is different but the rest match correctly. As I said, this only happens with certain glyphs, maybe 1 out of 30, if I had to make rough guess. I am using the MCUFont binary on Linux (Ubuntu running on VMware virtual machine), and the font I am converting is Google's Noto Sans CJK SC - Light. However, I had similar (but worse) issues trying to use Microsoft's SimHei font. The last detail I will note is that some of the glyphs that are of issue seem to be fixed by using a different font size, but the issue isn't isolated to a specific size. So far I have noticed it with sizes 14 and 16. It's possible it is affecting other sizes as well. Has anyone else run into this or know of a potential solution? Thanks! Link to comment Share on other sites More sharing options...
inmarket Posted March 13, 2018 Report Share Posted March 13, 2018 Given that this seems to be font size dependant my guess is that it is the encoder having the problem as the decoder built into uGFX is font size agnostic. Other than saying that, I have not heard of similar problems. Perhaps try using the win32 version of the encoder and also try the online converter to see if they give the same result. There have been minor bugs fixed over time so also check that you are using the latest version from the repository. Link to comment Share on other sites More sharing options...
jared.olson Posted March 14, 2018 Author Report Share Posted March 14, 2018 Thanks for the response, @inmarket. I agree with your assessment that is likely an issue with the encoder. Thanks for the suggestions; we'll look into those. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now