.svg and .eps files don't match

Bug #1068188 reported by C B Lucas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
New
Undecided
Unassigned

Bug Description

I though I reported this when concerned about printing problems, but I couldn't find my message, so I will try again.

I make my own pattern which I wish to use for several drawings so I create it as an object is a separate file then use copy | paste. I then use Object | pattern | object to pattern to fill. This works perfectly, but when I save the same file as .eps as well as .svg the two can look very different. I associate this with using my own patten since I have noticed odd effects in development drawings when using my own patterns.

I am preparing drawings to be passed to a printer who requires .eps files, so I need to be certain that I am sending what I think I am.

I have attached the .svg file prepared on Windows X.86.

From the attached SVG file:
   inkscape:version="0.48.2 r9819"

Revision history for this message
C B Lucas (cb-lucas) wrote :
Revision history for this message
su_v (suv-lp) wrote :

Probably like bug #1060402 a duplicate of
Bug #668750 “Patterned SVG can't convert to eps properly (cairo 1.10)”
<https://bugs.launchpad.net/inkscape/+bug/668750>

description: updated
tags: added: eps exporting pattern
Revision history for this message
C B Lucas (cb-lucas) wrote :

I have since found an example which is not dependent on my using my own pattern.

The attached file shows a polka-dot pattern (which I have deliberately distorted) in the upper part and for comparison a polka-dot pattern in a rectangular frame. Both were prepared on a virgin canvas.

When I print the .svg file, the upper parrern is missing.

In the unlikely event that the copy and paste was causing the problem, I copied both into another fresh canvas and the results were the same. I have also had this problem with a diagram that I have shaded.

I haven't been able to see any reason why what appears on the screen should not be printed. If Netscape cannot always print its own .svg files, I am presumably expecting too much for other formats to work pergectly?

Revision history for this message
C B Lucas (cb-lucas) wrote :

I think I have accidentally found one (or possibly the only) cause of the problems I have been having with some files printing incorrectly.

In the developments of my own patterns, I often have several trial versions. Hence I have followed Bah T, 4th edition, page 129 to use File | Vacuum to remove the unused ones. What appears to be happening is that it partially removes those in use. Hence I have lost patterns and also lost a gradient fill when elsewhere in the drawing a pattern was used.

If this is the case, then File | Vacuum has a bug.

I would also recommend that it would be easier to remove unwanted patterns if they could be removed where they are shown in the Fill and Stroke window.

I should welcome comments on my diagnosis.

C B Lucas

Revision history for this message
C B Lucas (cb-lucas) wrote :

After further tests (and a lot more printing), I think that the File ! Vacuuming is probably less to blame than I thought. Since a gradient fill didn't print and unused gradients are claimed to be removed by vacuuming, this seemed the most likely cause.

However, if I have my own pattern in part of a drawing and a gradient fill elsewhere, the .svg file doesn't print the gradient fill, although it is shown on the screen,

If I move my pattern outside the drawing area, but still within the printing area, the gradient fill prints correctly from the .svg file (as does my pattern).

If I use the standard large Polka dot pattern, the drawing prints perfectly.

Hence in conclusion, use of one's own pattern should be undertaken with caution.

I hope these comments are useful, but am I the only one to be concerned about this?

C B Lucas

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.