On 2010-07-23, Chris Browet wrote: > My point exactly ;) Leaving too much freedom of interpretation will make > MapCSS rendering inconsistent, which is obviously not the goal....
Think of CSS, is the goal absolute consistent rendering? In that case, we might well only use one rendering engine anyway. Just the way html and CSS separates content and design leaving much to the implementor (within the boundaries of the specs), mapcss can leave much to the iplementor too. Some engines might prefer to print road names every inch, some want it once per way... I don't see a problem with inconsistency as long as it is within the bounds of the specs. I don't see a problem with providing a translation table between "zoom levels" and "scale" values either.... Sebastian _______________________________________________ Mapcss mailing list [email protected] http://lists.openstreetmap.org/listinfo/mapcss
