You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The paths in SVG can be written in various ways. The ruleset is really loose, so different tools might export the path very differently.
It even makes me consider a non-SVG format instead of a simplified SVG for storage.
We should also have a rule about where each path starts and consider reversing it to be consistent (for example: of the start/end point, the top-left point could be chosen, to get consistent ordering).
For now, we can probably use https://pypi.org/project/svg.path/ to parse and rewrite the path for our simplified SVG.
However, that library is very limited in the choices is offering for rewriting and I don't think it follows the SVG spec exactly. It's just a lightweight choice which can be used so we don't bikeshed over tooling.
The text was updated successfully, but these errors were encountered:
The paths in SVG can be written in various ways. The ruleset is really loose, so different tools might export the path very differently.
It even makes me consider a non-SVG format instead of a simplified SVG for storage.
We should also have a rule about where each path starts and consider reversing it to be consistent (for example: of the start/end point, the top-left point could be chosen, to get consistent ordering).
For now, we can probably use https://pypi.org/project/svg.path/ to parse and rewrite the path for our simplified SVG.
However, that library is very limited in the choices is offering for rewriting and I don't think it follows the SVG spec exactly. It's just a lightweight choice which can be used so we don't bikeshed over tooling.
The text was updated successfully, but these errors were encountered: