change the regional setting - now my chinese music works! thanks!
but my japanese ones still don't... not sure why cuz some do and some
don't... just sorta gets ignored even tho they were ripped from the
same CD
--
rwong
I found a workaround. Go to control panel -> Regional and Language
Options -> Advanced, and set the langauge to Chinese (PRC). Then you
should be able to see your Chinese, Japanese or Korean songs in
slimserver or slimbox.
--
raylpc
--
I opened a bug: http://bugs.slimdevices.com/show_bug.cgi?id=3739
However, progress seems to have stalled.
I hope someone will contact me soon to continue troubleshooting this.
--
dailofan
dailofan's Profile: http://forum
I have this probelm too.
It also extends to Japanese and Korean.
Windows XP, NFTS, UTF8 tags.
Very occasionally, it will recognise a song but it's very rare and I
have no idea why it works when it does.
--
monkie
monkie'
This looks like a real bug to me. I'd encourage you to file it at
http://bugs.slimdevices.com so we can keep track of it more easily.
Thanks!
--
ChrisOwens
Christopher Owens
QA Manager
[EMAIL PROTECTED]
(510) 743-1152 x717
-
The F:drive is a local drive (USB) on an XP Pro workstation. File
system is NTFS, I believe(will verify). The system has OS support for
both Chinese and Japanese. I have no problem in Windows Media Player
reading, displaying or playing these files.
--
dailofan
---
On 11-Jul-06, at 9:50 PM, snarlydwarf wrote:
I have plenty of both latin1 and utf8 directories and file names and
they both work fine, but that's as ext3 on linux.
utf16 could be problem, however.
-kdf
___
discuss mailing list
discuss@lists.slimdev
What sort of filesystem is your drive F:?
Is it a local drive? Is it a mounted share? If a share, what sort of
machine is it on? What OS are you running your server on?
I have plenty of both latin1 and utf8 directories and file names and
they both work fine, but that's as ext3 on linux.
--
dailofan Wrote:
> I have a number of Chinese and Japanese CDs in my collection. Slim will
> always skip their directories claiming they are invalid and not include
> them in the library.
> I've tried this on versions 6.2x, 6.3, and now 6.5x. Same problem.
>
> The files were ripped using WMP an