When working with an SVG (I will email it as I learned in my last post that long SVGs don't work well in this forum) I found the post-nano file neglected to base64 encode one of the fonts, resulting in a very different final result.

Hi Adam,

We believe that this is solved through the email. Posting our answer here for future reference.

To clarify, your original SVG file does not contain @import or @font-face to the font.

Therefore, Nano will try to get the font file from Google Fonts. In this case, the font in the SVG file is Lato, Lato-Bold and Lato-Semibold.

1. Lato-Bold and Lato-Semibold font-family: Lato-Semibold, Lato; These fonts does not exists in Google Fonts, so Nano will use Lato as a fallback.
2. Failure to embed fonts Based on your SVG file, the CSS is:

.cls-14, .cls-15 {
    font-family: Lato-Semibold, Lato;
    font-size: 19px;
    font-weight: 600;
}

This font will fail to embed because there is no Lato with font-weight: 600. Please refer Lato in Google Fonts https://fonts.google.com/ for more information.

Regards,
The Vecta Support Team