MobileRead Forums - View Single Post

ericshliao · 02-03-2008, 06:30 PM

Although contentlister accepts Unicode filename and path (so we can use CJK glyphs in contentlister), Mobipocket format file must be named in ascii character. If not ascii named, the mobi file can not be opened from contentlister.
I think the problem lies in the shell script file "/home/intent/runmobi.sh". The script tries to transfer filename to JVM (Mobi-reader runs on JVM). It's either the script give wrong filename, or JVM wrongly receive the filename string.
I want to use iconv to translate filename string in the shell script, but iLiad busybox doesn't seem to have it. Does anybody have some suggestion for this problem?

02-03-2008, 06:30 PM	#1
ericshliao Guru Posts: 976 Karma: 687 Join Date: Nov 2007 Device: Dell X51v; iLiad v2	A filename encoding problem. Although contentlister accepts Unicode filename and path (so we can use CJK glyphs in contentlister), Mobipocket format file must be named in ascii character. If not ascii named, the mobi file can not be opened from contentlister. I think the problem lies in the shell script file "/home/intent/runmobi.sh". The script tries to transfer filename to JVM (Mobi-reader runs on JVM). It's either the script give wrong filename, or JVM wrongly receive the filename string. I want to use iconv to translate filename string in the shell script, but iLiad busybox doesn't seem to have it. Does anybody have some suggestion for this problem?