Bugzilla – Bug 2609
unicode text in Polish looks very bizarre on sb2/3 display
Last modified: 2009-09-08 09:31:06 UTC
will attach sample images and a sample file
Created attachment 1039 [details] screenshot from web interface of how the font should look
Created attachment 1040 [details] picture of sb display showing how it actually looks on the player
Created attachment 1041 [details] basic comparison of the two
Created attachment 1042 [details] mp3 file that contains the tag that makes this happen
Dan: shouldn't we be rendering the whole string or at least whole words with the same technique?
Yes we should - not quite as easy as it sounds though.
Created attachment 1062 [details] screenshots showing that font does not match in all sizes Kevin requested this information, but did not reply to my emails since Nov 23rd (yes I know bug support is annoying :D ), so I'll include the screenshot here directly. (applet and real Squeezeboxes are identical in this aspect, and I also tried the MS Arial Uni font by now - same problem, just without serifes, that's the only difference).
check your spam filters. Kevin is very good with answering emails and bug support (you'll see his own screenshots posted above), but some spam filters seem to be unfriendly. Attaching here is always a good thing anyway.
AAACK, actually, this was my bad--your message was put in my spam filter. Sorry about that. :(
Regarding the fact that I regard this as a killer of usability, having my mail landing in the spam filter was a good way to stretch this beyong the 30 day money back timeframe :-/ Are there any plans about when this will be fixed?
raising priority. please address--customer is still seeing this issue.
I've checked in a fix for this in subversion change 6517 Make sure he's using the CODE2000 font - it doesn't ship with 6.2.2.
Patrick: did you get a chance to try the new version and see how the Polish now looks? Unfortunately, we don't have any body here who reads Polish right now, so your advice will be very helpful. If it's still not right, please feel free to reopen the bug with comments so we can fix it. Thanks.
@Dan Sully: I've tried Cyberbit, CODE2000, and five different versions of arialuni (0.84, 0.85, 0.86, 1.00, 1.01). Without a Unicode font, the screenshots I showed you wouldn't even be possible ;) @Dean Blackketter The file I just tried was SlimServer_6_2_x_v2006-03-09.tar.gz I apologize for not having this tested earlier, but since the SB so often needs to be re-setup completely when the server software was down, it always takes quite a chunk of time to test this - hey it's annoying enough if you just want some music while shaving, and to get the SB to run takes longer than the shaving. As always, I had to remove/rename the DBI.pm to get it to run at all. arialuni.ttf still existed (I only overwrite the older folder), I even made a copy name ARIALUNI.TTF, but this version doesn't even Unicode characters any more - the question marks are back. So I went and just renamed the whole slimserver folder and created a new one, where I could test this new version without having any left-overs from previous versions in there. Same problem - Unicode characters are still questions marks again. Finally, since Dan Sully mentioned the CODE2000 font, I renamed the arialuni font and put the CODE2000 font back in - without any change. Fonts are 644, so they're world-readable. As a forth attempt, I changed them to user slimserver & group slimserver as well - still question marks. Both your forum and my old installation folders show that the fonts belong into the Graphics folder, where they are. The upper/lowercase is the same as before (just copied them over), and the same as on your forum (arialuni.ttf ARIALUNI.TTF CODE2000.TTF). You replaced the valid letters with invalid question marks, but hey, the question marks at least have the proper size.
PS: Reopening was not successful due to insufficient rights, I guess that was because Kevin had opened it in the first place.
Hi Patrick. Please try moving aside your fonts folder and reinstalling slimserver 6.2.2 from our nightly releases. This will reinstall the CODE2000 font. We recently started including this font with SlimServer (it's very complete and the author has agreed to our redistribution) and the character sizes have been optimized for this font. If you see question marks, then either you have the wrong font there or it can't read the font file.
SlimServer_6_2_x_v2006-03-22.tar.gz simply does not contain a CODE2000.TTF file. The old version I tested (SlimServer_6_2_x_v2006-03-09.tar.gz) had it, but from what you can see from my previous report (hope I wasn't too confusing when describing it), it did not work. So I did now download the 6.5 beta (SlimServer_v2006-03-22.tar.gz), which actually includes CODE2000.TTF. And with this version, it works again - special chars instead of question marks - and even looks quite well and proper-sized now, THANK YOU VERY MUCH! (I would have changed the bug to fixed again already, just didn't have the rights to do so, but please regard this as fixed and me as a happy SB user again :) ) Btw, why didn't you just print the whole text with the font from the TTF? CODE2000 is a font using serifes, and the standard font is not, which creates kind of a mixed typography ;) (no, I'm not complaining again, I'll easily be able to live with that ;-p )
The CODE2000 font is now in the 6.2.2 tree. We want to end up with the same font displayed eventually, but there are some technical issues. Thanks for the report.