iLiad FBReader problem: files with Korean file names

wagnerian · 05-14-2007, 03:29 AM

The "add to library dialog" does not list files with Korean file names as if the files do not exist at all. FBReader for Windows XP does not have this problem. Any idea?

wallcraft · 05-14-2007, 10:03 AM

I suggest providing a tar bundle (with an english filename) containing one or two of the problematic files. That way, I can test whether the problem exists in the Desktop Linux version.

I am assuming that tar will preserve the filenames, one check would be to untar them in a different directory first to confirm this. If there is a better way to attach files that preserves filenames (and works under Linux) then please use it.

wagnerian · 05-14-2007, 11:23 AM

Quote:

Originally Posted by wallcraft

I suggest providing a tar bundle (with an english filename) containing one or two of the problematic files. That way, I can test whether the problem exists in the Desktop Linux version.

I am assuming that tar will preserve the filenames, one check would be to untar them in a different directory first to confirm this. If there is a better way to attach files that preserves filenames (and works under Linux) then please use it.

http://wagnerian.new21.org/pub/temp.tar

wallcraft · 05-14-2007, 11:30 PM

I get the same behavior under Desktop Linux, and I have reported it this fact on FBReader's Google Group.

wallcraft · 05-15-2007, 12:58 AM

I think I have worked this out. The filenames are in euc-kr and need to be in utf-8. When I use convmv to convert the filenames to utf-8, Desktop FBReader works as it should. I found out about convmv here. This is a Linux utility (actually a perl script). The command I used was:

Code:

convmv -f euc-kr -t utf8 --notest *

where "--notest" should be used only after testing that the conversions are appropriate. Note that convmv (particularly its -r --notest option) might be a brick your iLiad command if you run it in the wrong directory. So the safest approach would be to run it on some other machine under a standard user account and then transfer the files.

wagnerian · 05-15-2007, 10:04 PM

That's too much inconvenient!

I'd rather take the risk of modifying the er_registry.txt to associate .txt files with FBReader.
There's no problem on the iLiad content lister to process euc-kr file names if a Korean font is installed on the device.

wagnerian · 05-16-2007, 08:15 AM

Successfully modified the er_registry.txt file. Thank God my iLiad did not brick!

05-14-2007, 03:29 AM	#1
wagnerian Musicology Student Posts: 55 Karma: 45 Join Date: Oct 2006 Location: Seoul, Korea (R.O.K.) Device: iLiad, BlackBerry Bold 9000, Zaurus C1000	FBReader problem: files with Korean file names The "add to library dialog" does not list files with Korean file names as if the files do not exist at all. FBReader for Windows XP does not have this problem. Any idea?

05-15-2007, 12:58 AM	#5
wallcraft reader Posts: 6,979 Karma: 5183568 Join Date: Mar 2006 Location: Mississippi, USA Device: Kindle 3 and Fire	I think I have worked this out. The filenames are in euc-kr and need to be in utf-8. When I use convmv to convert the filenames to utf-8, Desktop FBReader works as it should. I found out about convmv here. This is a Linux utility (actually a perl script). The command I used was: Code: convmv -f euc-kr -t utf8 --notest * where "--notest" should be used only after testing that the conversions are appropriate. Note that convmv (particularly its -r --notest option) might be a brick your iLiad command if you run it in the wrong directory. So the safest approach would be to run it on some other machine under a standard user account and then transfer the files. Last edited by wallcraft; 05-15-2007 at 01:12 AM.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kindle File Names	Captain Skurvy	Amazon Kindle	2	08-14-2010 02:22 AM
File Names	Vulcan	Sony Reader	4	01-02-2009 04:03 PM
iLiad Mobipocket problem with documents in Korean language.	wagnerian	iRex Developer's Corner	0	07-14-2007 03:49 PM
iLiad Enabling Korean encoding (EUC-KR) with FBReader (0.8.2b) for iLiad	wagnerian	iRex Developer's Corner	2	05-11-2007 10:03 PM
PRS-500 RTF file names	phigdon	Sony Reader Dev Corner	2	05-01-2007 11:46 PM

05-14-2007, 10:03 AM	#2
wallcraft reader Posts: 6,979 Karma: 5183568 Join Date: Mar 2006 Location: Mississippi, USA Device: Kindle 3 and Fire	I suggest providing a tar bundle (with an english filename) containing one or two of the problematic files. That way, I can test whether the problem exists in the Desktop Linux version. I am assuming that tar will preserve the filenames, one check would be to untar them in a different directory first to confirm this. If there is a better way to attach files that preserves filenames (and works under Linux) then please use it.

05-14-2007, 11:30 PM	#4
wallcraft reader Posts: 6,979 Karma: 5183568 Join Date: Mar 2006 Location: Mississippi, USA Device: Kindle 3 and Fire	I get the same behavior under Desktop Linux, and I have reported it this fact on FBReader's Google Group.

05-15-2007, 10:04 PM	#6
wagnerian Musicology Student Posts: 55 Karma: 45 Join Date: Oct 2006 Location: Seoul, Korea (R.O.K.) Device: iLiad, BlackBerry Bold 9000, Zaurus C1000	That's too much inconvenient! I'd rather take the risk of modifying the er_registry.txt to associate .txt files with FBReader. There's no problem on the iLiad content lister to process euc-kr file names if a Korean font is installed on the device.

05-16-2007, 08:15 AM	#7
wagnerian Musicology Student Posts: 55 Karma: 45 Join Date: Oct 2006 Location: Seoul, Korea (R.O.K.) Device: iLiad, BlackBerry Bold 9000, Zaurus C1000	Successfully modified the er_registry.txt file. Thank God my iLiad did not brick!


Advertisement Enthusiast