Wrong disposition of characters on print preview on A4 paper size |
|||||||||||
Issue descriptionChrome Version: 60.0.3112.90 (Official Build) (64 bit, cohort : 60_90_win) Chrome Canary: 62.0.3176.2 OS: Windows 7 professional SP1 32bit and Windows 10 What steps will reproduce the problem? (1) open pdf file attached (2) print preview with Microsoft XPS Document Writer (3) chose A4 Paper size What is the expected result? to see correctly the pdf in the preview What happens instead? Upside down characters and wrong disposition of characters when trying to print preview a PDF file. If is chosen a different paper size (Letter, A4 Extra) I'ts correct with or without "Fit to page" with A4 if the scale is != 100 it's also correct PDF file from customer: https://drive.google.com/open?id=0B01ZVp8vDQocVnZ1WTZlLVl6X0E video https://drive.google.com/open?id=0B01ZVp8vDQocX0hkZWlPeENpSVE
,
Aug 4 2017
Do you know if this is a regression? Did it used to work?
,
Aug 7 2017
Able to reproduce this issue on Windows 10 with chrome stable #60.0.3112.90, Canary #62.0.3178.0 and also in earlier version M45-#45.0.2454.101. This is a non-regression issue, hence marking it as untriaged. Attaching the screen-cast for reference.
,
Aug 8 2017
Seems like a font issue, can you please take a look?
,
Aug 8 2017
Hm ok, I can take a look if this is not a high priority bug. Thankfully, this can also be reproduced on Linux with print preview to Save As PDF.
,
Aug 24 2017
the customer send the procedure used to generate the pdf: 1) connect to this page: https://www.manneken.co.jp/menu/info/allergy/20170912 2) print to save as pdf 3) open the pdf with Adobe (in my case with Adobe Reader) 4) add a comment or highlight some text 5) open the pdf in chrome 6) print preview at 100% file before comment: https://drive.google.com/open?id=0B01ZVp8vDQocSy1nSUdrVFRpZEk file with comment: https://drive.google.com/open?id=0B01ZVp8vDQocYWpMZ1N4QkFTYUk video: https://drive.google.com/open?id=0B01ZVp8vDQocSTcwaVJPUm0zM1U
,
Sep 25 2017
Hi, any news on this issue? Thank you
,
Sep 26 2017
No news yet, I haven't looked into this.
,
Oct 18 2017
npm@ Is there any update that can be shared with us?
,
Oct 18 2017
Yesterday I actually looked at this bug for a bit. I found the part of the PDF concerning the misplaced red text but not entirely sure yet why the text is misplaced. PS: I only work 20% on PDF stuff. If the bug is important, one way to note that is to set the appropriate priority (right now, it is set to 3, which means the bug could be ignored for a long time).
,
Nov 10 2017
I looked at this some more. On Linux, opening the PDF right away works fine. But Control+P and then Save as PDF and then opening the saved PDF exhibits the problem. In the original PDF, there is an "Annots" array, but not in the saved PDF. When rendering the original PDF, in CPDF_Annot::DrawInContext, layers with nontrivial matrices are appended to the CPDF_RenderContext. But these are missing when rendering the saved PDF, which explains the incorrect positioning. It seems, then, that the Page objects are missing this information. I don't see a fast way to fix it (but then again, I haven't worked with annotations). Passing back to hnakashima@ since this seems unrelated to texts/fonts.
,
Nov 30 2017
npm@ Thanks for all your support. hnakashima@ Is there any update?
,
Dec 5 2017
,
Dec 6 2017
jayhlee@ would appreciate it if you could help. The case has not been updated since Nov10 and customer is waiting for update from us.
,
Dec 8 2017
Following Nicolas's steps on #11, I'm also able to repro in Linux. After opening the original PDF in Chrome and printing it, the resulting file has the bug (text inverted at the bottom). It appears in other PDF viewers the same way, so this is a bug in printing rather than in the visualization. Dan, what is the path for printing from the PDF Viewer to a PDF? Who would be a good owner for this?
,
Dec 11 2017
thestig@ to triage for the printing side.
,
Dec 7
Hello! This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time - If you are currently working on this bug, please provide an update. - If you are currently affected by this bug, please update with your current symptoms and relevant logs. If there has been no updates provided by EOD Wednesday, 12/12/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary. Thank you!
,
Dec 13
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by marcore@chromium.org
, Aug 4 2017