Bug 694361 - korean file.pdf not support
Summary: korean file.pdf not support
Status: RESOLVED DUPLICATE of bug 694409
Alias: None
Product: MuPDF
Classification: Unclassified
Component: mupdf (show other bugs)
Version: master
Hardware: Android Phone Windows 7
: P4 normal
Assignee: Tor Andersson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-19 01:06 UTC by Jeong Byung Joo
Modified: 2013-07-09 08:36 UTC (History)
0 users

See Also:
Customer:
Word Size: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jeong Byung Joo 2013-06-19 01:06:05 UTC 
choosePDFActivity error.

korean file not support. 


06-18 09:52:24.859: W/dalvikvm(18009): JNI WARNING: input is not valid Modified UTF-8: illegal start byte 0xbe
06-18 09:52:24.859: W/dalvikvm(18009):              string: '??.pdf'
06-18 09:52:24.859: W/dalvikvm(18009):              in Ljava/io/File;.listImpl:(Ljava/lang/String;)[Ljava/lang/String; (NewStringUTF)
Comment 1 Tor Andersson 2013-06-19 08:37:36 UTC 
Can you please attach the file?
Comment 2 Hin-Tak Leung 2013-06-27 22:07:16 UTC 
There is possibly no need to attach a file - the message is about korean file.pdf *name* not support, I think. The reporter was trying to open a file the name of which is not valid utf8.

My guess is that native korean uses the regional encoding KS X 1001, a.k.a. codepage 949, EUC-KR, iso2022-KR, etc before the whole unicode thing comes along, and will possibly continue for some years. just as codepage 932/936/950 persists for the other CJK regions.
Comment 3 Jeong Byung Joo 2013-06-28 00:08:32 UTC 
Hin-Tak Leung. That's right. That's what I am saying.

Is there any way of resolving that problem?
Comment 4 Ken Sharp 2013-07-09 08:36:18 UTC 
The reporter has opened a new report, and attached a specimen file, in #694409

*** This bug has been marked as a duplicate of bug 694409 ***