On 26 October 2016 at 06:38, Nigel Tao <nigel...@golang.org> wrote: > On Wed, Oct 26, 2016 at 12:45 AM, Sean Russell <seaneruss...@gmail.com> wrote: >> How did you calculate the SVG sizes? When I download the the icons from the >> material design github, the collection of the *_48px.svg icons weighs in at >> 3.8MB. > > You may be double counting the design/ and production/ versions of the > same icons, although that shouldn't explain a 10x difference. There > may be other factors. How did you make your calculation? > > >> So, one question and one suggestion: the question is what were you measuring >> for the SVG size, and the comment is that you might want to address the svgz >> aspect. As in, "yes, svgz is smaller, but more expensive to decode," with >> benchmarks, or whatever other technical merits you're aware of. > > The SVG size was measured by this program: > https://go.googlesource.com/exp/+/master/shiny/materialdesign/icons/gen.go > which generated this file (look at the final lines): > https://go.googlesource.com/exp/+/master/shiny/materialdesign/icons/data.go > > SVGZ is indeed smaller, and more expensive to decode, but I don't have > numbers at hand. > > Even so, there's still the point that a spec-compliant SVG renderer is > a _lot_ of code, and XML brings its own complexities.
This cannot be understated. A well known tool generates SVGs that the Go XML parser cannot parse because it uses XML directives to create XML entities that contain XML elements when they're expanded. This meant we couldn't process them at all (we wanted to adjust the view box parameter). -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
