You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I connect the HiFiBerryOS from PC browser, I can see Korean characters but it is not correctly displayed in Raspberry Pi HDMI screen (Maybe font is missing?)
HiFiBerryOS version
20210804
HiFiBerry sound card
DAC+ Pro
To Reproduce
Steps to reproduce the behavior:
Select HiFiBerryOS as DLNA render from mobile app
Play any Korean music with Korean title
The Korean character is not displayed correctly in Raspberry Pi HDMI screen
Expected behavior
Display correct characters
Screenshots
Browser (if applicable)
Additional context
I tried Japanese as well. It is same. I can see correct characters in PC browser, but problem in Raspberry Pi HDMI display.
The text was updated successfully, but these errors were encountered:
Probably missing font. I'm not sure, if we can get the correct fonts, but I'll have a look. As I don't have any files to test: Can you provide a sample file?
There is possible solution. I found moode audio also support HDMI UI out and they have same problem. But I could add the fonts by below (they have web SSH) and I could see the characters properly.
$ sudo apt install -y fonts-unfonts-core
Here is the sample song with Korean character in metadata - I attached the screenshot of Korean string, so that you can know if it is correctly displayed or not
Describe the bug
When I connect the HiFiBerryOS from PC browser, I can see Korean characters but it is not correctly displayed in Raspberry Pi HDMI screen (Maybe font is missing?)
HiFiBerryOS version
20210804
HiFiBerry sound card
DAC+ Pro
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Display correct characters
Screenshots
Browser (if applicable)
Additional context
I tried Japanese as well. It is same. I can see correct characters in PC browser, but problem in Raspberry Pi HDMI display.
The text was updated successfully, but these errors were encountered: