- From: David Dailey <ddailey@zoominternet.net>
- Date: Wed, 12 Nov 2014 06:36:59 -0500
- To: "'Rik Cabanier'" <cabanier@gmail.com>, "'Bogdan Brinza'" <bbrinza@microsoft.com>
- Cc: "'www-svg'" <www-svg@w3.org>, <yanli@scnu.edu.cn>
- Message-ID: <000001cffe6c$f8af39f0$ea0dadd0$@net>
On Tuesday, November 11, 2014 6:03 PM To: Bogdan Brinza Cc: www-svg Subject: Re: SVG Hinting requirements proposal published Rik replied to Bogdan Brinza: On Mon, Nov 10, 2014 at 3:43 PM, Bogdan Brinza <bbrinza@microsoft.com> wrote: Hi SVG WG, Thanks again for having us on last TPAC meeting! I’ve published SVG hinting requirements first draft on Proposals wiki here: https://www.w3.org/Graphics/SVG/WG/wiki/Proposals/SVG_hinting - I’ll keep this updated as new input data, proposed solutions, informational links and options come. Let me know if you have any immediate comments. I’ll follow up with other related actions this week, hopefully by this week’s telecon to discuss action for taking SVG 2 LCWD. Thanks for writing this up! The article on pixel fitting [1] is similar to my proposal to always round path points and line widths so they land on whole screen pixels. Flash had something similar to avoid fuzzy strokes [2]. CSS already rounds lines to whole pixels to avoid AA artifacts so there must already be some platform support for this. 1: http://dcurt.is/pixel-fitting 2: http://blog.kaourantin.net/?p=21 I believe that there are many in the cartographic community who share a sense of the importance of such things. I’m not part of that community but tried presenting some of Professor Li’s perspectives on the subject at SVG Open one year: http://cs.sru.edu/~ddailey/svg/2011/maps.html . Sorry that my notes are so sketchy but it matches my memory;) I do know that non-scaling stroke, knowing at what zoom level to hide labels of landmarks, and providing display-based positioning guidelines of features and labels are all of interest. Regards David
Received on Wednesday, 12 November 2014 11:37:41 UTC