Hello, before I open a another (possibly duplicate) issue, I want to try the forum. I have a MRE that may illustrate my point: SVG comes out to “fat” and blurry. Chrome renders same SVG without problems and very readable. Inserting same SVG into Word and exporting that to PDF also results in a very readable PDF. So I suspect, it’s Typst.
Is there something in the SVG, that creates problems, like some filter?
I can’t comment on the issue, but are you talking about an SVG output by Typst, or the PDF output Typst produces when putting an SVG in your document? The title sounds more like the former, but the body more like the latter. Maybe you could edit that a bit.
I suspect it is the font substitution that causes this issue. On your OS, where you generated the svg, you have likely all the fonts installed that are used in the svg. However, the typst app online does not have all the fonts, so you either can use fonts that are available both on your system and inside typst, use typst on the command line on your computer where the fonts are available, or convert the text inside the svg to paths before uploading it.
Edit: Some more detail.
Your svg uses the calibri font, which is not available in the typst online app. Technically, you could likely upload the font into your project folder to use it, but as this is a font that comes with microsoft windows, I am not sure if its license permits this.
Svg files typically do not embed the fonts that are used in the file, as it e.g. is the case in pdf.
Edit 2: You can get a list of available fonts in the typst online app by clicking the leftmost icon with the letters “Ag” here:
I think the real problem here is that there are errors in the SVG file. The style attributes of all <text> nodes contain
stroke:#000000; stroke-opacity:0.00 stroke-width:0
where there is a semicolon missing between the 0.00 and the stroke-width. This makes Typst not recognize that the stroke should be invisible, but instead makes all text be outlined with a black stroke. I suppose that Chrome and Word are more lenient in parsing, and just pretend that there is a semicolon there.
To fix this, you can just add the missing semicolons, or remove all stroke related fields from the text nodes entirely.
It’s the latter: the PDF output Typst produces when incorporating an SVG image.
Thanks a lot! But this means, that the SVG exporter of the tool I’m using (Enterprise Architect) has a bug. Sparx Inc. isn’t known for being too quick with fixes 
But maybe I can post/preprocess the exported SVGs a bit before usage.