-
Notifications
You must be signed in to change notification settings - Fork 44
Problems with UTF8 characters as text value #258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Also got the same problem while showing my calendar entrys from the google calendar. Programmed a little workaround that deletes these ugly square-placeholders but emojis and some german characters like ä will not be shown correctly while ö is shown. The ttf-font has the öäü etc. included but the display doesn't show them.
|
I just tested those symbols with multiple fonts, and none of those seemed to support it - type: text
value: ppb 🢃 🢆 🢂 🢅 🢁 ⮽ ä ü ö
x: 10
y: 10
font: ppb.ttf
- type: text
value: rbm 🢃 🢆 🢂 🢅 🢁 ⮽ ä ü ö
x: 10
y: 30
font: rbm.ttf
- type: text
value: GothamRnd 🢃 🢆 🢂 🢅 🢁 ⮽ ä ü ö
x: 10
y: 50
font: GothamRnd-Bold.ttf
- type: text
value: SpaceMono 🢃 🢆 🢂 🢅 🢁 ⮽ ä ü ö
x: 10
y: 70
font: SpaceMono-Bold.ttf
- type: text
value: ClearSans 🢃 🢆 🢂 🢅 🢁 ⮽ ä ü ö
x: 10
y: 90
font: ClearSans-Bold.ttf
- type: text
value: DejaVu 🢃 🢆 🢂 🢅 🢁 ⮽ ä ü ö
x: 10
y: 110
font: dejavu-sans.bold.ttf
- type: text
value: SF-Pro 🢃 🢆 🢂 🢅 🢁 ⮽ ä ü ö
x: 10
y: 130
font: SF-Pro-Rounded-Bold.ttf
- type: text
value: Unifont 🢃 🢆 🢂 🢅 🢁 ⮽ ä ü ö
x: 10
y: 150
font: unifont-16.0.03.ttf
So it seems to be a font problem (According to this Website only some obscure paid fonts seem to include those symbols). As for german umlauts, those (should) work with drawcustom. If by google calendar you mean the content type that would be an issue for the main OEPL repo. |
I noticed a feature of Windows and most likely Linux called Font Substitution... If a font does not have a glyph, a fallback is used as it seems. So my claim with all these fonts having the arrows most likely is completely wrong indeed ... Will look into the available arrows later today |
Maybe the arrows are shown from the wingings font with a lot of special characters. As for the german umlauts I think you are right. It must be something with my automation that makes this problem. The trash-calendar is shown correctly and here we have "Biomüll" for example that shows the ü without any problems (same font). Gonna ask chatgpt if I can do something with the umlauts and my google calendar script. |
BTW: I've uploaded wingding.ttf into my home assistant and used the following script:
This should show a few different arrows but it only shows squares ... (The german umlauts seem to work fine - so it must be something with my google calendar script.) |
The question is, if you copied that selection into your script or used the UTF8 arrows there. WingDings most likely is not really UTF8 compliant as its just a collection of symbols. That's what I wanna go and try at home later. Checking "Zeichentabelle" for arrows in the default fonts and then copy them out of "Zeichenauswahl:" |
I've used value: "èåâÜðòÁÁ for the arrows. That's what I would normally do for example in a word-document. When you change the font to something else you get those letters. If you change it back to wingding it shows the arrows. |
I think I found a font to test. But not from work. Later... And if things fail, I will use plan B. Use the MDI Icon instead. |
OK, as this is no real bug from the integration, I bypassed it in a nice way.
|
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
I created a automation that portraits my current blood sugar values, days left until the sensor is to be replaced and an tendency of the sugar value. All works fine except the tendency as it uses UTF-8 based arrows that result in a ⮽ on the Tag. (see photo)
To Reproduce
This is the automation:
Expected behavior
Showing the arrows and no ⮽ instead. And yes, I replaced the ⮽ in the else part and it still is shown, so it's no problem on my if else endif.
Screenshots

Additional context
I guess it's a font problem? Maybe we need a more powerful font here... If some arrows are a problem, then I wonder what CJK glyphs will do
EDIT: I tried DejaVuSans-Bold and SourceSansPro-Bold instead and both have these arrows according to LibreOffice and my source code showing fine there. So... The problem is not just the font.
The text was updated successfully, but these errors were encountered: