Bug 91013 - can't display correctly of Chinese book
Summary: can't display correctly of Chinese book
Status: RESOLVED MOVED
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-18 00:04 UTC by ni shengyue
Modified: 2018-08-21 10:48 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
the book that can't read (1.04 MB, text/plain)
2015-06-18 00:04 UTC, ni shengyue
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ni shengyue 2015-06-18 00:04:40 UTC
Created attachment 116567 [details]
the book that can't read

This is a case cloned from GNOME Bugzilla – Bug 751115
	
the book that can't read

Evince can't display book correcly, just wrong words
but some other tools can display well, such as mupdf, foxit reader (close source software).

 I use mupdf and can read it correcly, and I notice there is print as below:

nisy@nisy-ubuntu:/media/nisy/sda1_WinXP/_Technology/98_my_project/_27_改进开源软件/乱码问题$ mupdf ./1_\[雅舍菁华\].梁秋实.文字版.PDF 
warning: workaround for S22PDF lying about chinese font encodings
warning: ... repeated 2 times ...
warning: workaround for S22PDF lying about chinese font encodings
warning: ... repeated 2 times ...


so I guess mupdf had workaround to avoid font issue, so I checked in mupdf code,find its code should be:

	pdf_load_font
		|__pdf_load_simple_font 
				|__ pdf_load_simple_font_by_name
					|__ 				fz_warn(ctx, "workaround for S22PDF lying about chinese font encodings");


Because evince also have font mechanism, so can evince consider to check mupdf 's mechanism, and merge mupdf 's method to avoid this issue? Thanks.

nishengyue
Comment 1 ni shengyue 2016-02-17 05:15:19 UTC
Does any body can give me some suggestion? Thanks
Comment 2 GitLab Migration User 2018-08-21 10:48:44 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/383.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.