Japanese font display issue in Roon (ref#CGB0OD)[Ticket in]

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Japanese font display issue

Tell us about your home network

· Wifi Network

I previously posted the following in the “Software Discussion : Translations” section, but if this is a problem with how Japanese fonts are displayed, does that mean it is an issue with the Roon program itself?

Since the same issue occurs on the iPad as well, isn’t there a problem with how Roon rasterizes Japanese fonts?
The text formatting breaks on the artist list screen, but it displays correctly on the artist detail screen.

Changing the 1-byte “&” to the 2-byte “&” improves things slightly, but Japanese characters with 濁点 (voicing marks) are positioned too close to the adjacent characters, making them very difficult to read.
Furthermore, the names “Average White Band” and “Vonda Shepard” end with “ト” instead of “ド”;
I consider this a critical bug.

The artist list displays correctly when no filter is applied. It appears to be a bug that occurs only when using the filter.

Hello @Yoshihiro_Kikuchi

You are right that this is ours, and the two problems you describe in the artist list are one bug rather than two.

When a Japanese character carries a voiced sound mark, our text layout separates the mark from the character it belongs to before the text is shaped. The mark then has no base to attach to, so it gets painted over the next character and the base is left bare. That is why ド reads as ト, and why the mark lands on the &. Your finding that the 2-byte & changes the result fits this, and so does the detail screen rendering correctly.

We have reported it to our development team with the specific cause. We do not have a timeframe.

On your question about rasterization: Roon supplies its own fonts rather than using the ones on your device, so Japanese text is drawn the same way on every platform. That matches what you saw on the iPad.

Hi @vadim, thanks for the reply.

I understand the situation; it was pretty much as I had imagined.

Since the issue only occurs when a filter is applied, it’s not entirely unusable, but I would appreciate a fix as soon as possible.

Hello @Yoshihiro_Kikuchi

The ticket is filed and we have everything we need from you on this, so we will close the thread here.

If our development team needs anything further, we will post in this thread and it will reopen.