Hi On Tue, Jun 26, 2012 at 03:18:14PM -0700, Ryan Kaldari wrote:
Anti-aliasing is a feature, not a bug. As long as your SVG is going to be displayed on a monitor that uses pixels, you have to code it with this in mind. There is no such thing as a "correct" thumbnail size. All
Yes. Somehow I thought rendering is done with infinte solution and then scaled down to the needed pixel discretisation of the to-be-displayed image. :-/ Sorry for my misconcept.
thumbnails are going to have anti-aliasing unless they consist of nothing but flat squares that are all multiples of the same dimensions, i.e. virtually never.
Moreover, I e.g. use height and width in the SVG-code which matches as good as possible to the design. E.g. for this flag I choosed the width to be a multiple of 225, such that clones of one "Allah Akbar" pattern might be easily copied from the rendered ONE pattern, which may save a lot of time! Thus I expected an intelligent renderer noticing integer-translations in the final raster. ;) This is the reason I tried to use integer numbers to allow the renderer to re-use already rendered substructures! Maybe I expect too intelligent algorithms. :-/
I fixed the rendering issue with the Iranian flag by making the tekbirs slightly overlap the central field. Now it will look correct no matter what thumbnail resolution you request. The fix took a total of 10 minutes to figure out and implement, which is probably a lot less time than has been spent on writing emails to argue about it.
Yes, you fix this special issue (as I was successful in the special mirror-split) Thanks. But both are only workaround. Further artifacts show up if the flag's width is not a perfect muliple of 225. And regarding your needed real time: yes, it is a big problme to get competent help on wikimedia. Most people use thought- less tools and can not give you help / hints :-( Only reupload wrongly designed flags. :-( With my proposal: render in the given SVG-size and then use a (bug-free or much better known) render from png or jpeg only for scaling down this rendered image, would have also solved the issue. I don't know why the SVG-renderer don't work internal so?
On wikimedia you must argue to convince or not, that this is a bug in their constrcution resulting in wrong geometries. Thus much talk results in very few (or no) chnaging to the better on wikimedia. Thus I'm here VERY POSITIVELY SURPRISED to get the other relation: very less talk/discussion needed but promptly get a practical/pragmatic solution from this wikimedia-developers. How often did I asked for the correct people to ask? And get no or false answer.
Achim