Skip to content

Conversation

dankohn
Copy link
Contributor

@dankohn dankohn commented Feb 24, 2018

Signed-off-by: Dan Kohn dan@dankohn.com

All of these SVGs were corrupted.

Signed-off-by: Dan Kohn <dan@dankohn.com>
Copy link
Member

@ldemailly ldemailly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thx for spotting this !

@ldemailly
Copy link
Member

cc @geeknoid

@ldemailly ldemailly merged commit 58fce9d into istio:master Feb 24, 2018
@geeknoid
Copy link
Contributor

In what way were the SVG files corrupted?

The front-matter was intentionally added so that the SVG gets compressed before being emitted in the main site. In usage, as far as I can tell, these SVGs were fine and being loaded by browsers.

Did the compression mess something up that browsers just overlook?

@ldemailly
Copy link
Member

ah glad it didn't break on the site, but that header makes them uneditable
also I don't think compression for a 3k long cached file is really that important ? it should be done by the webserver config if we needed

@geeknoid
Copy link
Contributor

geeknoid commented Feb 24, 2018 via email

@ldemailly
Copy link
Member

ldemailly commented Feb 24, 2018

most (all?) the human editable content is in MD / jekyll format, not plain html (yes lots of html fragments too)

but more relevant: you can't exactly draw in text mode when opening the files; if one needed to edit the icons (yes I have a couple hand coded svg too but that's not quite the common case)

@dankohn
Copy link
Contributor Author

dankohn commented Feb 24, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants