Mixing
Ghostscript converted PDF not rendered corectly with pdfium
0
I have a problem with some pdf documents I convert with Ghostsript to pdf/a documents. If the original document contains subseted fonts, the document is not correctly displayed in Chrome (pdfium) after converting. The chars will be displayed as squares.
In Adobe PDF Reader the output will be displayed correctly. Maybe the attached files can help you.
original PDF
converted PDF/A
pdf rendering ghostscript pdfa pdfium
edited Nov 21 '18 at 7:52
barbsan
2,43821223
asked Nov 21 '18 at 7:30
Marco NicaMarco Nica
1
add a comment |
0
I have a problem with some pdf documents I convert with Ghostsript to pdf/a documents. If the original document contains subseted fonts, the document is not correctly displayed in Chrome (pdfium) after converting. The chars will be displayed as squares.
In Adobe PDF Reader the output will be displayed correctly. Maybe the attached files can help you.
original PDF
converted PDF/A
pdf rendering ghostscript pdfa pdfium
edited Nov 21 '18 at 7:52
barbsan
2,43821223
asked Nov 21 '18 at 7:30
Marco NicaMarco Nica
1
That would be a problem with Chrome then, I'd suggest you raise a bug report with Google. Note that the PDF/A standard does not permit fonts to be subset, so Ghostscript won't further subset them, but if you start with a subset font, we cannot undo it. I'd guess the problem with Chrome is that the original contains fonts, while the created file contains CIDFonts.
– KenS
Nov 21 '18 at 8:27
Many thank's for your fast replay Ken. I raised a ticket at Google.
– Marco Nica
Nov 21 '18 at 9:29
FWIW I noticed that Ghostscript has rewritten the TrueType fonts, they are still valid, (and the text has not been re-encoded) but its possible there's 'something' about the regenerated fonts that Chrome doesn't like I've no idea what it would be though.
– KenS
Nov 21 '18 at 9:52
add a comment |
0
0
0
I have a problem with some pdf documents I convert with Ghostsript to pdf/a documents. If the original document contains subseted fonts, the document is not correctly displayed in Chrome (pdfium) after converting. The chars will be displayed as squares.
In Adobe PDF Reader the output will be displayed correctly. Maybe the attached files can help you.
original PDF
converted PDF/A
pdf rendering ghostscript pdfa pdfium
edited Nov 21 '18 at 7:52
barbsan
2,43821223
asked Nov 21 '18 at 7:30
Marco NicaMarco Nica
1
I have a problem with some pdf documents I convert with Ghostsript to pdf/a documents. If the original document contains subseted fonts, the document is not correctly displayed in Chrome (pdfium) after converting. The chars will be displayed as squares.
In Adobe PDF Reader the output will be displayed correctly. Maybe the attached files can help you.
original PDF
converted PDF/A
pdf rendering ghostscript pdfa pdfium
pdf rendering ghostscript pdfa pdfium
edited Nov 21 '18 at 7:52
barbsan
2,43821223
asked Nov 21 '18 at 7:30
Marco NicaMarco Nica
1
edited Nov 21 '18 at 7:52
barbsan
2,43821223
asked Nov 21 '18 at 7:30
Marco NicaMarco Nica
1
edited Nov 21 '18 at 7:52
barbsan
2,43821223
edited Nov 21 '18 at 7:52
barbsan
2,43821223
edited Nov 21 '18 at 7:52
barbsan
2,43821223
2,43821223
asked Nov 21 '18 at 7:30
Marco NicaMarco Nica
1
asked Nov 21 '18 at 7:30
Marco NicaMarco Nica
1
asked Nov 21 '18 at 7:30
Marco NicaMarco Nica
1
1
That would be a problem with Chrome then, I'd suggest you raise a bug report with Google. Note that the PDF/A standard does not permit fonts to be subset, so Ghostscript won't further subset them, but if you start with a subset font, we cannot undo it. I'd guess the problem with Chrome is that the original contains fonts, while the created file contains CIDFonts.
– KenS
Nov 21 '18 at 8:27
Many thank's for your fast replay Ken. I raised a ticket at Google.
– Marco Nica
Nov 21 '18 at 9:29
FWIW I noticed that Ghostscript has rewritten the TrueType fonts, they are still valid, (and the text has not been re-encoded) but its possible there's 'something' about the regenerated fonts that Chrome doesn't like I've no idea what it would be though.
– KenS
Nov 21 '18 at 9:52
add a comment |
That would be a problem with Chrome then, I'd suggest you raise a bug report with Google. Note that the PDF/A standard does not permit fonts to be subset, so Ghostscript won't further subset them, but if you start with a subset font, we cannot undo it. I'd guess the problem with Chrome is that the original contains fonts, while the created file contains CIDFonts.
– KenS
Nov 21 '18 at 8:27
Many thank's for your fast replay Ken. I raised a ticket at Google.
– Marco Nica
Nov 21 '18 at 9:29
FWIW I noticed that Ghostscript has rewritten the TrueType fonts, they are still valid, (and the text has not been re-encoded) but its possible there's 'something' about the regenerated fonts that Chrome doesn't like I've no idea what it would be though.
– KenS
Nov 21 '18 at 9:52
That would be a problem with Chrome then, I'd suggest you raise a bug report with Google. Note that the PDF/A standard does not permit fonts to be subset, so Ghostscript won't further subset them, but if you start with a subset font, we cannot undo it. I'd guess the problem with Chrome is that the original contains fonts, while the created file contains CIDFonts.
– KenS
Nov 21 '18 at 8:27
That would be a problem with Chrome then, I'd suggest you raise a bug report with Google. Note that the PDF/A standard does not permit fonts to be subset, so Ghostscript won't further subset them, but if you start with a subset font, we cannot undo it. I'd guess the problem with Chrome is that the original contains fonts, while the created file contains CIDFonts.
– KenS
Nov 21 '18 at 8:27
Many thank's for your fast replay Ken. I raised a ticket at Google.
– Marco Nica
Nov 21 '18 at 9:29
Many thank's for your fast replay Ken. I raised a ticket at Google.
– Marco Nica
Nov 21 '18 at 9:29
FWIW I noticed that Ghostscript has rewritten the TrueType fonts, they are still valid, (and the text has not been re-encoded) but its possible there's 'something' about the regenerated fonts that Chrome doesn't like I've no idea what it would be though.
– KenS
Nov 21 '18 at 9:52
FWIW I noticed that Ghostscript has rewritten the TrueType fonts, they are still valid, (and the text has not been re-encoded) but its possible there's 'something' about the regenerated fonts that Chrome doesn't like I've no idea what it would be though.
– KenS
Nov 21 '18 at 9:52
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53407166%2fghostscript-converted-pdf-not-rendered-corectly-with-pdfium%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53407166%2fghostscript-converted-pdf-not-rendered-corectly-with-pdfium%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
That would be a problem with Chrome then, I'd suggest you raise a bug report with Google. Note that the PDF/A standard does not permit fonts to be subset, so Ghostscript won't further subset them, but if you start with a subset font, we cannot undo it. I'd guess the problem with Chrome is that the original contains fonts, while the created file contains CIDFonts.
– KenS
Nov 21 '18 at 8:27
Many thank's for your fast replay Ken. I raised a ticket at Google.
– Marco Nica
Nov 21 '18 at 9:29
FWIW I noticed that Ghostscript has rewritten the TrueType fonts, they are still valid, (and the text has not been re-encoded) but its possible there's 'something' about the regenerated fonts that Chrome doesn't like I've no idea what it would be though.
– KenS
Nov 21 '18 at 9:52