![]() |
#1 |
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? |
![]() |
![]() |
![]() |
#2 | ||
Guru
![]() ![]() ![]() ![]() ![]() ![]() Posts: 976
Karma: 687
Join Date: Nov 2007
Device: Dell X51v; iLiad v2
|
I found the solution. The problem can be solved by setting proper encoding parameter in the shell script that calls JVM to execute.
Take Mobipocket reader for example. In "/home/intent/runmobi.sh", there is a line: Quote:
Quote:
Since iLiad use UTF-8 as its internal encoding scheme. iRex should make this fix in her next software release. Last edited by ericshliao; 02-10-2008 at 07:29 PM. |
||
![]() |
![]() |
Advert | |
|
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Pdf to epub Turkish character encoding problem | blueresistance | Conversion | 1 | 02-25-2011 05:31 PM |
Encoding problem in translation | sbring | OpenInkpot | 1 | 04-29-2010 05:58 PM |
encoding problem with mobi converted to epub | ldolse | Calibre | 5 | 08-14-2009 12:55 PM |
Metadata from filename problem | kad032000 | Calibre | 0 | 05-24-2009 02:26 AM |
FBReader fixes character encoding problem | jbenny | News | 1 | 10-18-2007 10:50 PM |