|
From: <pl...@pi...> - 2012-10-12 21:53:52
|
On 10/12/12 17:40, sfeam (Ethan Merritt) wrote: > pl...@pi... wrote> >> >The nice thing about SVG is the ability to zoom in to get more detail. >> >Doing this on Allin's example , comparing Firefox to Opera on linux, >> >the U of UNEMP is basically outside the plot with the second upright on >> >the y-axis. >> > >> >With Opera is it perfectly coincident this the y axis, on FF it is just >> >inside the graph with a very fine amount of white separating it from the >> >axis. >> > >> >A more exacting test case could provide some useful metrics on the problem. > But how would that help? Aren't you illustrating that the_same file_ > produces different results when displayed by different viewing programs? Exactly. What I found out by testing was that even on the same platform there are fond rendering differences. That is one thing I wanted to know. I also established that on the face of it , it's so damn small, you need to blow up to x20 to see it. What I was suggesting is that quantifying the problem like this is probably an essential first step to fixing it in the most effective way with a minimum of trial and error loops. I think you have a much better understanding that I do of where the weaknesses lie but I'd expect a test case to have long key titles, be tested with several different types of font and include varying amounts of capitals, and letters like i,l,t against m,a,c,w,o Comparison should probably be made between (wxt, qt ) and pngcairo et al and svg/postscript. This in a matrix with lin/mac/win on the other vector. Hopefully this would find some areas that work fine and determine worst cases aberrations. best regards, Peter. |