I personally see this as a very low prioritized problem. While it can be annoying that the text gets outputted as paths and not text, there is a workaround as I earlier mentioned:
And honestly, the workaround is EASY: you don't even need to open InkScape graphically
- Export page as SVG
- Run the command inkscape --export-type="pdf" --export-filename="page.pdf" page.svg
I don't see any advances in using the KiCad template format rather than SVG:
- SVG is close to unlimited in terms of function of what is needed
- While InkScape (to some users) can be difficult to use, it is no different from making a KiCad template: a plain SVG takes as much effort to code manually as a KiCad template
(Also, if it has been possible for the user to use FreeCAD with bodies, sketches, workbenches, and pockets, then making a simple template with lines and a logo in InkScape should be to overcome - and templates by FreeCAD is even provided)
To create templates as FreeCAD objects seems like a heavy coding job. I believe it would be easier to implement the workaround I mentioned above into FreeCAD (so FreeCAD internally creates the PDF from a Qt exported SVG.
So while I recognize that it is an issue to users, I consider this a very low prioritized issue by making templates FreeCAD objects and using KiCad style templates instead:
- There is a workaround (first SVG, then convert to PDF)
- Implementing the workaround internally is easier than converting all templates to FreeCAD objects (I believe)
- SVG got all needed functions - KiCad style has limits
- SVG is equivalent to code as Kicad style - only difference is syntax. Meanwhile, SVG can also be edited graphically in InkScape