Closed qissue-bot closed 5 years ago
Original Redmine Comment Author Name: Alister Hood (Alister Hood) Original Date: 2010-11-23T21:56:22.000Z
Wait... Exporting to PDF always behaves as described. Printing doesn't seem to now, although I'm pretty sure it did before I restarted QGIS...
Original Redmine Comment Author Name: Marco Hugentobler (Marco Hugentobler) Original Date: 2010-11-24T03:19:15.000Z
Cannot reproduce this. Exporting a line layer to PDF and opening in inkspace showed the lines to be vector. Note that point marker symbols are sometimes printed as raster (new symbology svn markers should be vector though)
Original Redmine Comment Author Name: Alister Hood (Alister Hood) Original Date: 2010-11-24T12:52:29.000Z
It is with line and polygon layers. I'm getting the same results on two different computers, with 1.5, 1.6 and trunk, and with new and old symbology. Both machines are running Windows. I guess I'd better find a machine to do a clean install on... maybe that will show up a setting that affects it.
Original Redmine Comment Author Name: andskog - (andskog -) Original Date: 2010-12-07T11:36:54.000Z
Also an issue here. Running 1.6 on two computers (W7 and XP). Same result with QG 1.5. It workes just fine in 1.4, however.
Original Redmine Comment Author Name: Alex Mandel (Alex Mandel) Original Date: 2011-05-02T19:50:37.000Z
I have done further testing on this issue under QGIS 1.6 and QGIS Trunk commit:e5863992 (SVN r15131). I can confirm that this bug happens on windows and not linux. I tried both new and old symbology, but have not yet tried only point, line or polygon one at a time yet.
Here's a link to an easy to use simple dataset and example pdfs made on windows and linux. http://blog.wildintellect.com/files/qgisbug/
I think this issue would be more minor if the SVG export was better, though I think fixing he pdf export might be more realistic. I am changing the Priority, for several Windows users I know this is a major deal breaker as it really impedes their ability to make quality maps without pdf as vector or svg that clips to extent and preserves scale.
Original Redmine Comment Author Name: Alister Hood (Alister Hood) Original Date: 2011-05-02T22:19:45.000Z
without pdf as vector Have you tried printing to a virtual pdf "printer"? That produces vector output for me now...
svg that clips to extent and preserves scale
Scale should be preserved now - see #3224
Is clip-to-extent necessary simply to minimise file size? Personally I'm quite happy now with exporting to svg and then printing the svg to PDF. But of course it would be much better not having to do a two-step process...
Original Redmine Comment Author Name: Alister Hood (Alister Hood) Original Date: 2011-05-02T22:45:38.000Z
Have you tried printing to a virtual pdf "printer"? That produces vector output for me now...
Sorry, no, I'm wrong. It doesn't anymore - printing rasterizes everything. So my original description for this bug is accurate again.
have not yet tried only point, line or polygon one at a time yet I've tried that, but only with new symbology. It is always rasterised.
Original Redmine Comment Author Name: Alister Hood (Alister Hood) Original Date: 2011-05-02T22:55:24.000Z
Ah. But it is affected by other things on the layoout e.g. if an arrow overlaps the map then part of the map is rasterised. If a basic shape overlaps the map then the whole map is rasterised. Also svg images are partly rasterised (I guess it depends on the layers inside the svg). See attached example.
Original Redmine Comment Author Name: Alister Hood (Alister Hood) Original Date: 2011-05-02T23:03:54.000Z
Sorry, no. It is more complicated than that.
If a basic shape overlaps the map then the whole map is rasterised. No, this isn't correct - see document2.pdf
Also svg images are partly rasterised (I guess it depends on the layers inside the svg). I see this wasn't demonstrated in document1.pdf - more of the svg was rasterised than I expected (I guess due to the svg being in line with the basic shape or something). See document2.pdf instead.
I don't think I'm achieving anything here ;)
Original Redmine Comment Author Name: Alister Hood (Alister Hood) Original Date: 2011-05-02T23:07:12.000Z
This should possibly be marked as duplicate of #3480
Also IIRC there is a bug where map labels cause any vector layers they overlap to be rasterised (or partly rasterised).
Original Redmine Comment Author Name: Alex Mandel (Alex Mandel) Original Date: 2011-05-03T08:12:52.000Z
Replying to [comment:6 Alister]:
without pdf as vector Have you tried printing to a virtual pdf "printer"? That produces vector output for me now...
I will double check but the last time I did so to PDF Creator it was still rasterized.
svg that clips to extent and preserves scale
Scale should be preserved now - see #3224
Is clip-to-extent necessary simply to minimise file size? Personally I'm quite happy now with exporting to svg and then printing the svg to PDF. But of course it would be much better not having to do a two-step process...
I need to go back and check more about Labelling since we also need labels to come out as Text objects in both SVG and PDF unless a user explicity chooses to convert text to paths. Either way it should never be rasterized.
Original Redmine Comment Author Name: Alister Hood (Alister Hood) Original Date: 2011-05-03T12:27:56.000Z
I need to go back and check more about Labelling since we also need labels to come out as Text objects in both SVG and PDF unless a user explicity chooses to convert text to paths. Either way it should never be rasterized.
"new" labelling is always rasterized - this is not a glitch, but the way it is designed. I'm pretty sure there is a ticket requesting it to be output as text, but I can't find it in a hurry.
Original Redmine Comment Author Name: Alister Hood (Alister Hood) Original Date: 2011-12-15T19:22:55.000Z
Alister Hood wrote:
I need to go back and check more about Labelling since we also need labels to come out as Text objects in both SVG and PDF unless a user explicity chooses to convert text to paths. Either way it should never be rasterized.
"new" labelling is always rasterized - this is not a glitch, but the way it is designed. I'm pretty sure there is a ticket requesting it to be output as text, but I can't find it in a hurry.
Sorry, I meant they are not currently designed to be text. They aren't rasterized in current Trunk.
Original Redmine Comment Author Name: Alister Hood (Alister Hood) Original Date: 2011-12-15T19:43:12.000Z
Does anyone still have a problem with this, or can we close the ticket? On current trunk I only have a problem when using the map book function of the easy print plugin: http://code.google.com/p/cataisrepository/issues/detail?id=6
Original Redmine Comment Author Name: Victor Axbom (Victor Axbom) Original Date: 2013-02-06T21:49:22.000Z
Not sure if it's the same problem. But I can't get layers with the line pattern fill to render as vector when I export to pdf. Anybody else experience the same issue? Both master and 1.8 is affected for me on Win XP.
Alister Hood wrote:
Does anyone still have a problem with this, or can we close the ticket? On current trunk I only have a problem when using the map book function of the easy print plugin: http://code.google.com/p/cataisrepository/issues/detail?id=6
Original Redmine Comment Author Name: Davide Pascutti (Davide Pascutti) Original Date: 2013-03-06T02:41:16.000Z
Victor, I have exactly the same problem: line fills are rasterized when exporting to pdf. I tried exporting to other vector format (pdf, svg, eps), I also tried using an external pdf printer but had no luck. Any idea? I'm using QGIS 1.8.0 on Win XP.
Original Redmine Comment Author Name: Victor Axbom (Victor Axbom) Original Date: 2013-03-19T00:11:10.000Z
Guess the problem is not really a bug as the line pattern fill seems to be implemented to create a raster fill. The function creates a texture with lines to be used as a Qt::TexturePattern custom brush. I'm not sure, but I guess it's not possible to get a vector line pattern fill with the current implementation then.
Original Redmine Comment Author Name: Alister Hood (Alister Hood) Original Date: 2013-03-19T11:24:23.000Z
the line pattern fill seems to be implemented to create a raster fill
Then that is a bug.
See discussion at #3430 and https://github.com/qgis/Quantum-GIS/pull/210
As Marco said: "Qt brush styles aren't suitable for printouts because they can't be scaled". I guess it might make sense to close this ticket and open a new one about the line pattern file.
Original Redmine Comment Author Name: Victor Axbom (Victor Axbom) Original Date: 2013-03-19T22:36:49.000Z
Hmm, you are right. That don't seem to be the intention then There is already a ticket for the problem #6996
Alister Hood wrote:
the line pattern fill seems to be implemented to create a raster fill
Then that is a bug.
See discussion at #3430 and https://github.com/qgis/Quantum-GIS/pull/210
As Marco said: "Qt brush styles aren't suitable for printouts because they can't be scaled". I guess it might make sense to close this ticket and open a new one about the line pattern file.
Original Redmine Comment Author Name: Alister Hood (Alister Hood) Original Date: 2013-03-20T10:49:29.000Z
I think we might as well close this ticket.
Author Name: Alister Hood (Alister Hood) Original Redmine Issue: 3250, https://issues.qgis.org/issues/3250
Print or export to PDF from the composer: Any vector layers will be rasterized in the output.
Perhaps the current behaviour is a workaround for the bug in QT (or whatever it was) that prevented layers from being clipped to the visible region... Is it?