I started trying out the unicode feature since the 08-18 nightly. Not all 
unicode characters are being displayed correctly. A large proportion of 
characters are represented by weird looking symbols.

Attachment "screen_v6.1.jpg" illustrates web UI of v6.1.1, which I have been 
using. This version does not support unicode at the SB2. However, the unicode 
support at the web UI is near perfect, if not for the lack of unicode support 
in ��Browse file folders��. It did not bother me because I do not usually use 
��Browse file folders��. In all other Browsing functions, all unicode 
characters are being rendered correctly.

Attachment "screen_v6.2.x.jpg" shows the web UI of v6.2.x 08-18 nightly, which 
supposedly supports unicode at the SB2. You can see from the web UI some 
unicode chars are not being displayed correctly. The good thing is, those 
Unicode characters being rendered correctly in web UI will also be displayed 
correctly at SB2. Incorrectly rendered chars in web UI gets displayed 
incorrectly at the SB2 as well. It is basically WYSIWYG. What you see on web 
UI is what you get in SB2.

Another observation is that v6.2.x seems to be able to pick up the number of 
albums correctly but the index (see screen capture) is about one row shorter 
than v6.1.1. I believe this could be related to the unicode feature.

Closing in on the 6th album in the screen capture, I am attaching the cuesheet 
for this album. 

Note:
Firmware update�� OK
ARIALUNI.TTF in graphics folder�� OK
SlimServer on WinXP SP2 Pentium 4 2.6G 1GB RAM
Wireless SB2