For example, if I create an SVG and use an externally referenced font file, and if that font files has 100 glyphs, but my SVG only uses 10 of the glyphs, do the 90 unused glyphs gets stripped out of the font file before Base64 encoding? This is essentially my work flow with some other tools, doing the steps manually. Results are good but the process is tedious. Looking for a pure C program to portably compile on Android (Termux, Clang, NDK, BIONIC), Windows, and Linux, install as a Node.js package, and automate the process. I may have to write it myself and release as open source.
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.
The plugin examples that are provided seem very simple although I understand this is the beta phase I was looking to do something similar to the already integrated vecta layers functionality.
Where I could either add my own add to something which could represent a list of board objects same as in layers or some other functionality. And then handle these objects in a small UI pop-up such as the layers pop-up.
So generally my question is, could I technically with the current documentation and support develop something similar to current vecta layers in the form of a plugin? If so could you please link me to the part of documentation that has this, because I couldn't find this part.
I ran the attached SVG file through the web portal for nano. In the original you'll note there are two instaces of "2020" on the X-axis for each graph, but after running through nano (and having the fonts compile et cetera) the 2020s are no longer there (and there is a 2020 in the upper left-hand corner of the resulting SVG)
I tried opening it in Vecta and the "original" looks good, but the "minified" version shows the difference (this is why I suspect the minifier)
I tested just adding a @font-face rule with the base-64 encoded fonts directly into the source file and do not observer this issue (sadly this makes my file much bigger ).
(Edit: I don't see how to get at attached files, so including the SVG source for reference)
Welcome SVG fans! Stay updated and connected with us (Vecta and Nano team) in this community. This community is the place for
Sharing announcements on latest Vecta & Nano updates
Feature requests (Make sure to include some context)
Bug catching (We'd appreciate a screenshot)
Any Vecta, Nano or SVG related questions
General - Everything about SVG (tips & tricks, discussions, showcase)
Vecta - Announcement, feature request, or bug in Vecta.io
Nano - Announcement, feature request, or bug in Nano
Code of Conduct
Be Clean, No harassment, No spam.
We will remove or block anyone who we believe does not have good intentions to engage with the community