Thomas DeWeese wrote:
During testing I found out that if there is only one svg element which has one opacity attribute (fill-opacity or stroke-opacity) with a value between 0.0 and 1.0, the generated pdf document is incorrect (ALL colors are wrong).
Do you see changes that are greater than 1-2 code values?
What do you mean with "1-2 code values"?
By code values I mean the set of numbers 0-255 for each color channel. So bright red is (255, 0, 0), there are lots of tools that will tell you what colors are actually on the screen. This is the only way I could tell that the PNG and the PDF had different colors (see below).
Look at this screenshots (BMP) which I made from the two pdf documents (viewed with Acrobat Reader 6.0).
So we seem to have found some of the issue. On my machine (Acrobat 5.0.5) testpdf_1.pdf and testpdf_2.pdf render essentially the same. 'testpdf_1.pdf' doesn't look anything like your 'testpdf_1.bmp'. I'm not quite sure where to go from here, I am not a real PDF specialist (which seems to be the area where the problem is - it isn't in how the SVG is communicated to it).
You may find that the FOP folks (that wrote the PDF part of the transcoder) can help more than I can.
Your SVG content is using 'tspan' elements (although in the given example you sent you don't need to). When this happens the PDF transcoder doesn't try to convert the text as text and falls back to converting it as paths. [...]
I changed it but now I can not see the text in the pdf document.
I do this all the time, so example content that fails would probably be useful, otherwise I don't know how to reproduce your problem.
Here are examples:
Thanks I'll try and take a look and get back to you.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
