SVG conformance ?
See original GitHub issueHi, currently writing a LaTeX package to add smcat
support, it appears Inkscape
(and inkview.exe
) cannot interpret correctly the produced svg
output, ie. from your own example :
initial,
doing: entry/ write unit test
do/ write code
exit/ ...,
# smcat recognizes initial
# and final states by name
# and renders them appropriately
final;
initial => "on backlog" : item adds most value;
"on backlog" => doing : working on it;
doing => testing : built & unit tested;
testing => "on backlog" : test not ok;
testing => final : test ok;
The svg
output “features” something like <polygon fill="transparent" stroke="transparent" ...
where "transparent"
is not recognized.
Check this out :
https://tools.ietf.org/html/draft-brownlee-svg-rfc-13 <- https://tools.ietf.org/id/svg
Did you meant stroke-opacity
instead of stroke
?
Please check the result not just in web browsers, but also with more conformant and less forgiving tools.
Btw you’re not the only one to produce “strange” svg
files, https://github.com/mermaid-js/mermaid is also pretty “lazy” regarding svg
conformance and Inkscape
compatibility…
Anyway, good job overall…
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (5 by maintainers)
Top GitHub Comments
Updated https://github.com/Kochise/latex-smcat to reflect your changes.
Many thanks again.
OK, let’s call it a success…
smcat_test.smcat.txt smcat_test.eps.txt smcat_test-eps-converted-to.pdf