I imagine it is difficult to anticipate such texts, and even more difficult to correct it without inducing different mistakes. So, I am just submitting it for consideration:
1 Like
Good thought but no. I used the Roon preference as follows:
I also examined the title using the edit option, and there is no space there. For this example, space or no space, Roon chose to use two lines for the title, when one line would easily suffice (4 more characters on the first line). Thatâs the mystery to me.
I think it has to do with the (). Try editing the album name to be Ravel: Influen(ces) and see if it splits out the parans to a different line.
No joy:
Like most topics on a music blog, itâs no big deal. Just making mgmt aware should they want to improve things.
So, my guess was right, the text parser is splitting out the parentheses and its contents to a different line. That means if you remove the () from around the âsâ it should keep it as one line.
Yeah but then itâs not the album title anymore.
I would err towards correctness of metadata vs. pleasing the UI.
2 Likes
If the algorithm had something like âuse as few lines as possible for the titleâ near the top of the IF statements, it would fix this issue.
Line breaking within a word where there is no space, even if there is a parenthesis, is pretty daring behavior if the UI doesnât have a hard limit in this case such as a fixed screen width.
Even if there is a space, a line break should not be enforced if the screen width allows for keeping one line. Having to enter non-breaking UTF-8 codes to get around it should not be necessary 
1 Like
I guess, sure.
Given the options between having
Ravel: Influence
(s)
or
Ravel: Influences
I would just edit the title to the second option as it is less bothersome, to me. I understand why the split happens, even if I donât agree with it. I can understand Johnâs complaint and I am not defending Roonâs design choices.
What is more annoying for me are the cases like thisâŚ
Where the title is split even though it doesnât need to be. This happens all the time unfortunately. And, it is a pain in the rear to fix each instance.
2 Likes
May I ask how you can fix this? I have several instances of this behavior and it just looks uglyâŚ
See Suedkiez post right above mine and follow the link.
2 Likes
@John_V I just remembered that my above linked post may have a workaround for you as well. Havenât tried it, though. The solution there does not mention it, but in addition to the 202F and 2007 character codes that produce non-breaking spaces of two different widths, there is also this one (follow the link from the solution post):
U+2060 U+2060 WORD JOINER (â ¡
WJ)Encoded in Unicode since version 3.2. The word-joiner does not produce any space and prohibits a line break at its position.
If you enter this before the parenthesis in your album title, following the approach in the solution post, it might prevent the line break there.
1 Like
Related to the line break topic in general, I find it curious how Roon so often creates these early line breaks, as discussed in this topic as well, although on PC there is ample space to the right (and I think most of us have arrived at the conclusion that this may simplify things for portrait mode on mobiles), but then suddenly this can be done, so one wonders why @Rugbyâs The Shirts has to be on two lines
