New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

saving pdf in MS word doesn't subset Korean characters #51

anemochore opened this Issue Dec 7, 2015 · 4 comments


None yet
3 participants

anemochore commented Dec 7, 2015

First, my MS Word 2010 file:

When i save this file into a PDF file using 'Save as' menu, I got the below PDF file.
(I unchecked 'Bitmap text when fonts may not be embedded' option)

As you see in 'Document Properties' in Acrobat or Reader,
Noto Sans Mono CJK KR Regular wasn't subset or at least not subset as TrueType.
And when copying the 4th line, Korean characters "한글" is not copied at all. It's just a bitmap, I guess.

I don't know whose problem this is (maybe MS Word?) but
I think the font itself should be easier to use universally, ie independent of applications.
Any idea or similar problem?

@anemochore anemochore changed the title from saving pdf in MS word doesn't subset some Korean characters to saving pdf in MS word doesn't subset Korean characters Dec 7, 2015


This comment has been minimized.

kenlunde commented Dec 8, 2015

According to this Microsoft article, this is expected behavior if the font doesn't include outlines in TrueType format.


This comment has been minimized.

anemochore commented Dec 9, 2015

Thank you for your reply. So the problem seems to be with MS Word '2010.'

Now I see. Under my Windows 7, Word 2010, Acrobat XI, and Chrome altogether were not successful to create a PDF file subsetting Noto Sans Mono CJK correctly(ie OpenType). Only Indesign CC 2014 was able to do that.

I understand. But a bit disappointed too.

@anemochore anemochore closed this Dec 9, 2015


This comment has been minimized.

kenlunde commented Dec 9, 2015

InDesign has the best overall PDF export functionality of any authoring application.


This comment has been minimized.

jungshik commented Dec 9, 2015

@anemochore As for Chrome, you can file a bug at ? After filing a bug with details, let me know the bug number and I'll follow up there. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment