I created this PDF using PDFSharp.
When I print it (to my Brother HL 5140 laser printer, or to the XPS printer, but not to PDFCreator) it ends up looking like this XPS document does does when viewed with the XPS viewer built in to Windows 7. I've also taken a pair of screenshots.
The printed copy contains an extra line segment (actually two, a skinny white one atop a wider black one in a style commonly used to depict roads) that runs from top center to bottom left.
Does anyone know why this happens, whether it is a bug in PDFSharp or a problem with my geometry, or have any idea how to go about debugging something like this?
Related
I have a document that was created from a scanned document, after using the Acrobat XI pro's text recognition tool, with parameters language: Spanish; PDF output: clear scan; downsample to 600 dpi.
It worked rather well, with only small problems, which can be easily overlooked. Except that I use foxit PDF reader to actually read PDF (I have a slow PC), and there is an "a" glyph that in Adobe looks normal, but in foxit it looks filled, without the empty space at its center (the problem exists only in italics lowercase "a")
(example of problem). There are lots of lower case italics a's, almost in every other page. I use this book to study for a central course for my degree, it's the best we have at our school's library in Spanish, so I read it almost every day, and it's quite annoying (example 2).
There are examples of that italics lowercase "a" that show up fine in foxit the a's in "plantación" are normal.
Sample pages, the first page has normal a's, the second has filled a's
Could I copy the normal looking a glyph and replace the one that causes the problem? if so, what software would I need?
Thanks for reading this.
Yes it is possible to change the ClearScanType (Fd1428390-Identity-H) to conventional font here changed to 11pt Times Roman Italic. Also messed with colour, size and bold to demonstrate effects, but you just need to use one combination.
This change is allowed in the Free version of Tracker PDF-XChange Editor but beware if not done cautiously text edits could trigger demo watermarks.
Select the edit text only from buttons then select text, with properties pane active (on the right) and make changes, if you see the demo banner appear then Ctrl-Z and try a different approach.
Morning, everyone,
Quick question about PS2PDF. I use it to convert graphics that I produce directly in postscript to PDF. While there is no visual problem on PS files, I see a grid on my PDF viewer. At first I thought the problem was in the viewer, but it remains present when I compile my TeX files containing the figures with PDFLaTeX. Do you have any ideas for settings that can "fix" this display? Thanks in advance :)
Evince is independent of Ghostscript as far as PDF files are concerned, but I don't know how it can be viewing PostScript files.
I believe what you are seeing is an artefact of the PDF rendering engine in use, and the way the PDF file is constructed (which is itself dependent on the way the PostScript is constructed).
Much of the content is drawn by creating little rectangles which are intended to butt up against each other (and basically do). However, depending on the resolution, the precise numerical accuracy of the calculations and the accuracy of the co-ordinates, it can be the case that these rectangles do not quite touch ideally. There is a theoretical gap between them.
You can see this occur with Adobe Acrobat, and zooming in and out changes where the lines appear (it changes the effective resolution, thereby changing the calculations from user space to device space, ie to the actual pixels on screen).
I cannot say for sure that the same problem exists with Evince, but I expect it does. Withh Acrobat I can turn off anti-aliasing, which is where the problem really arises. Acrobat is attempting to insert an anti-aliased pixel between the two rectangles, which leads to these faint lines. Turning it off (In Acrobat X Edit->Preferences->PageDisplay->Smooth Line art) makes the lines disappear.
Ghostscript doesn't apply anti-aliasing by default, so these lines don't appear when rendering either the PostScript or the PDF files, but if I turn on anti-aliasing (-dGraphicsAlphaBits=4) then Ghostscript renders the lines in both the PostScript and the PDF file.
Essentially I think the problem is that your PDF viewer is using anti-aliasing and your PostScript viewer isn't, so they don't look the same.
I've got the following problem:
I want to print a PDF file as a booklet, using Adobe Acrobat Reader (in a copy shop, they got no better printing software). Unfortunately, Adobe shrinks my file down to the printable area. Instead I want to have it printet 50%(cause it'a a booklet, every page shrinked down by half) the original size, without shrinking any further, the margins simply cut off (just the egde of some pics etc, not important, the size matters)
My idea was, to use a software to create a white margin around every page, covering the stuff in the not-printable-area. Then adobe would not shrink anything down.
Does anyone know a tool for my problem? I couldnt find one. (running on either Windows or Ubuntu)
I would prefer a command line tool, cause I got a bunch of files to print.
Or is there a way to tell adobe Reader to not shrink anything (I know it works with normal printing, just couldnt figure it out with booklet printing)
Or are there any other ideas out there?
thanks in advance
Nevermind, i found a solution:
I created a PDF template with a white margin, transparent in the middle.
Using 'pdftk' I can easily set my original file als background of my template.
Done.
I've been trying to create PDF files from my Visio drawings. My current method is very simple, just "Save As" pdf in Visio. One issue I have is that the inter-character spacing becomes uneven after the drawing is converted to pdf. I've attached two images here. The first one shows the original font in Visio and the other shows the distorted font in PDF.
Has anyone experienced this problem before? How would you suggest on fixing this?
Thanks!
I observed the same spacing problem with Visio 2013's export to PDF feature, but not when outputting a PDF using Adobe Acrobat XI Pro. It also appeared when pasting a Microsoft Visio drawing object or pasting and EMF from Visio into Word 2013; however, inserting a WMF from the same Visio drawing does not have the problem. I had just started using 2013 although 2016 versions were already available. I did not have the problem with Visio/Word 2007. -- 7/2016: I left most of my prior observations, but this, the issue appears to have been fixed by Microsoft Update.
The PDF generator is using a similar, but not the same font as Visio. The stroke weights of the examples you posted are not the same (note the horizontal lines in the 'e' and 't').
Try a different font.
Posting the PDF output itself would be very helpful, but from what you have said already, coupled with what you have shown in images, it appears that the Visio output is setting each character individually and getting the character widths wrong, thus the placement of each following letter is too far beyond the preceding one.
I'm not too sure of the baseline positioning, either, because the endpoint of that curving blue line below the "c" in the screenshots you posted is significantly closer to the text in the rendered PDF than in the initial screenshot above it.
See if Visio can deal with Courier first, as that is a monospace font (i.e. each glyph occupies the same width on the line). If it generates text in Courier that still shows wandering letterspacing, I would begin to wonder whether there's a newer/updated Visio release to seek out before continuing to fight with this.
This is apparently a long lasting bug in Visio. I still see it in my Visio 1708, build 8431.2250). The bug is at least 4 years here already.
The working fix to avoid kerning problems for single diagrams is to export them in any bitmap format (e.g. png) or Windows Metafile Format (WMF) or use screen snipping tools to copy diagrams from the screen.
From that, may be the solution can be in tuning the PDF renderer to produce set of raster images instead of using the embedded vector graphics.
Bug report on Microsoft Answers:
https://answers.microsoft.com/en-us/office/forum/office_2013_release-word/font-spacing-kerning-issues-after-cut-paste-from/e930ec40-507f-4b25-9d72-c6c41b9d70cf
Using the following process:
A PDF is been created by PDFCreator, when a user prints something to the virtual printer
The PDF gets further processed with integrated VBScript handler and passed over to JAVA which does some processing with the PDF content
In the middle of the process an external application is called with the PDF that adds black text and graphics to the PDF
The PDFs are collected and once a week handed over to a print shop that uses a plate for each CMYK
The problem is: the print shop needs a color seperated CMYK PDF, but the added black text & graphics from the external app should be the only content on the K plane (because we want to make a special print effect). All other content which has been printed via PDFCreator should be on CMY plates only, so black must be emulated with those colors.
At the moment we are manually braking the process before calling the external application and seperate the colors via Adobe Creator Pro, but that is no future option because the whole process should work automated.
So basicly I need a way to convert the CMYK PDFCreator PDF to a CMY version only so the external app can throw in as many black K content as needed.
Is the PDF conversion the right direction I'm heading to? Is there any way w/ ghostscript how this can be done? I read the gs documentation but got nowhere as I only saw RGB to CMYK conversion but no CMYK to CMY with empty B...
I believe that PDFCreator is simply a wrapper around ghostscript, so you may have some joy on the ghostscript mailing lists. It seems that gs does support some printers that just ouput CMY so this functionality is likely to be available in there.
Wouldn't you be better off using a new separation called Black? Can't the print shop handle that?