Architecture issue on Unicode and PC Screen Font #1601
Unanswered
valentinbreiz
asked this question in
Q&A
Replies: 1 comment
-
It may be that it's unrelated to the architecture- many unicode characters are not supported at all. It could also be the font itself. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone I have an architecture design issue
I'm trying to implement unicode with a custom PC Screen Font. It works well but I don't know if I make it the right way. The problem is that the font doesn't support all unicode characters (that is normal unicode is huge), so some characters has differents offsets in the font data and unicode value.
For exemple for a space (' '), unicode is U+0020 and my font offset is 0x20, they are the sames no problem. But for example if I want to use the double bar ('║') which is U+2551 for unicode and at 0xD1 address in my font data: they do not patch.
My technique seems for me a bit tricky: I just search for unicode correspondance in the unicode map (parsed thought the PCScreenFont class) like above:
Do you think is it right like this or should I make an array of chars with the max unicode lenght supported by the font and place the font data in each unicode offset?
Beta Was this translation helpful? Give feedback.
All reactions