Bug 695263 - can not open some pdf file
Summary: can not open some pdf file
Status: RESOLVED DUPLICATE of bug 694409
Alias: None
Product: MuPDF
Classification: Unclassified
Component: mupdf (show other bugs)
Version: 1.3
Hardware: Android Phone Android
: P4 normal
Assignee: MuPDF bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-05-25 20:47 UTC by beasonshu
Modified: 2014-06-26 09:20 UTC (History)
3 users (show)

See Also:
Customer:
Word Size: ---

Attachments
the file cannot be open in mupdf (v1.4 0r v1.3) (2.86 MB, application/pdf)
2014-05-25 20:47 UTC, beasonshu 		Details
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 beasonshu 2014-05-25 20:47:36 UTC 
Created attachment 10931 [details]
the file cannot be open in mupdf (v1.4 0r v1.3)

the attachement file cannot open in mupdf of android
Comment 1 Tor Andersson 2014-05-27 03:10:05 UTC 
What happens if you rename the file to something with only ASCII characters? I suspect this is the same problem as in bug 694409.
Comment 2 beasonshu 2014-05-27 18:47:18 UTC 
After renaming it ,i can open it in mupdf.
But i found a new problem that i can not annotate on that file .
Could you help me.
Comment 3 beasonshu 2014-05-27 18:50:53 UTC 
Comment on attachment 10931 [details]
the file cannot be open in mupdf (v1.4 0r v1.3)

3q, that's it;
i found a new problem that the file of attachement can not be annotated;
Comment 4 beasonshu 2014-05-28 18:56:22 UTC 
3q, that's it;
i found a new problem that the file of attachement can not be annotated;
Comment 5 Matt Holgate 2014-06-26 09:20:48 UTC 
OK, I've just confirmed that after renaming the file, annotations are able to be drawn, but do not save properly in v1.4.

I repeated the test in v1.5, and it seems that annotations are saved correctly.

Therefore, I think the annotations part of this bug is fixed; please re-test in v1.5 and reopen this bug if you still have problems.

The remaining issue of the filename problem is covered by bug #694409, so I'm going to mark this as a duplicate of that bug.

(Incidentally, I couldn't get the filename bug when transferring the file from a Mac to Android, so I suspect this only happens when using Windows).

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