Adding full UTF-8 support

Zrgwa

Member
Joined
Oct 8, 2024
Messages
8
I have recently switched from Eversolo DMP-A6 to Ultra and noticed the display UI has trouble processing some of the more obscure characters (shows only empty squares). On mobile app it works fine. Hopefully this isn't something too hard to fix. Example sources with such characters:


IMG_6033.jpeg
 
Is it? Found it accidentally and really like it:))
Yep just checked again. Love the stuff he pushes under this alias! Much more eclectic & experimental. How do you rate the Ultra vs the Eversolo? Have you made a definitive switch or kept both?
 
Yep just checked again. Love the stuff he pushes under this alias! Much more eclectic & experimental. How do you rate the Ultra vs the Eversolo? Have you made a definitive switch or kept both?
Eversolo UI, knob and overall feel is way better. Didn’t do side by side DAC comparison. Settled for the Ultra due to more I/O options and that for the same price I can get Ultra + Topping DAC with superior performance and headphone amp.
 
Eversolo UI, knob and overall feel is way better. Didn’t do side by side DAC comparison. Settled for the Ultra due to more I/O options and that for the same price I can get Ultra + Topping DAC with superior performance and headphone amp.
I think you are writing in the wrong thread? This is about character support.
 
It looks like UTF-8 is fully supported but the font used by the Ultra do not contain these very special characters.
Well, if the font doesn't support these printable UTF-8 characters then the Ultra does not fully support UTF-8, pretty much by definition, right? :)

It's not enough to not crash the device to call it "support". 😁
 
UTF-8 is a Unicode character encoding method. The Unicode defines more than 100000 character points, so to cover all in a font definition will be a big task. I am not even sure that the example in this thread show the correct font?
 
The standard Microsoft fonts (even if not genuine from a historical point of view) are good examples for very wide coverage of available glyphs. Most freeware fonts are not, many still leaving out most everything beneath 8 bit ASCII.

What's the point in "supporting UTF-8“ if the font you provide cannot display the glyph?
 
As said, UTF-8 is an Unicode encoding method. There are others including UTF-16 and UTF-32.

The UTF-8 method maps the provided bytes (1 to 6) into a Unicode code point. This is used to look up in the available font definition to render the displayed character. If the current font don't define the Unicode character you may try to download more of the font mapping pages or another font that do. Many apps uses OS APIs to help with this.

But as said, the current Unicode definition is about 120000 characters, so that will be a lot to define and load. It looks like WiiM Ultra covers the most important language characters in the used fonts.

To me the provided example do look like it was encoded with another method than UTF-8.

See https://en.m.wikipedia.org/wiki/Unicode_block for a list of Unicode blocks that needs to be covered if all UTF-8 encoded glyphs shall be supported. This includes e.g. Egyptian hieroglyphs.
 
Last edited:
All that is important here is that app can easily show these characters and the Ultra cannot. I think there should be feature parity and support told me that it has been forwarded to the devs.
 
Back
Top