Skip to content
This repository has been archived by the owner on Feb 12, 2023. It is now read-only.

qtox.svg is corrupted #4114

Closed
Vort opened this issue Feb 1, 2017 · 8 comments
Closed

qtox.svg is corrupted #4114

Vort opened this issue Feb 1, 2017 · 8 comments
Labels
M-ui Affected Module: User Interface

Comments

@Vort
Copy link
Contributor

Vort commented Feb 1, 2017

qtox.svg logo differs in shape from qtox.png
Here is the difference visualization:
qtox_diff

@antis81
Copy link
Contributor

antis81 commented Feb 1, 2017

I'd rather say "png is corrupted" in this case… 😄

@zetok
Copy link
Contributor

zetok commented Feb 1, 2017

@Vort would you be interested in fixing it?

@zetok zetok added help wanted M-ui Affected Module: User Interface labels Feb 1, 2017
@Vort
Copy link
Contributor Author

Vort commented Feb 1, 2017

@zetok, I don't really know which version should be preferred and why they are different.
My first thought was that asymmetry is a mistake, but it is better to find out what exactly happened here.

@antis81
Copy link
Contributor

antis81 commented Feb 1, 2017

@Vort When looking at the pattern it might come down to an applied antialiasing "filter" or something like that. It might even be a bug inside the rendering engine… nothing to be worried about too much, but interesting to investigate… have fun 👍

@Vort
Copy link
Contributor Author

Vort commented Feb 1, 2017

@antis81, the one-pixel differences are not a problem, look at the middle of keyhole.

@Vort
Copy link
Contributor Author

Vort commented Feb 1, 2017

Screenshot from Inkscape:
qtox_key

@antis81
Copy link
Contributor

antis81 commented Feb 1, 2017

Ok, just wanted to answer, but you been quicker. You know how to use inkscape?

  1. Convert the corner "dot" on the right into… well… a corner (like on the lefft).
  2. Probably align the new corner on the right vertically to the one on the left.

So you are right the SVG is "broken" and just has not been exported. Congrats! 👍 💯

@Vort
Copy link
Contributor Author

Vort commented Feb 1, 2017

I have found the source of problem: this optimization was done not carefully enough.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
M-ui Affected Module: User Interface
Projects
None yet
Development

No branches or pull requests

3 participants