Thanks. I've been trying to get into visual studio, cpp, and so far, so good. I can programmatically generate svg code - lines, circles, text. I can generate text as g-code for machining, and that can be relatively easily parsed to svg path statements. Hoverer, there are  few snags, a minor one is related to the different x,y origins, and I have to dig in a bit more to get better rendering .I've been experimenting with a simple vector font - just a single line. It renders differently in openscad compared to a browser. I think different defaults are applied. I think it may be easier to use true type fonts, which seem to produce g code as an outline of the character, not single lines. On 27/03/2022 12:18, Torsten Paul wrote: > On 26.03.22 14:30, Raymond West wrote: >> How far had you got? > Really just started parsing the svg file, so it's still > far off anything that could produce actual output. > > ciao, >   Torsten.

I think my g-code text conversion to svg text is worth pursuing for my purposes, (and also it will get any g code into svg , although z height will be ignored, other than cutting/ non cutting)  changing the style, now allows openscad to show the shapes the same as in a browser. Not sure if I'll write software to separate each character, or possibly manually separate the 80 or so groups of paths that may be required. I've attached a test of the characters 'ABC' below (upside down for the time being) - just a proof of concept of my conversion program so-far. I guess I'll have to get to grips with more c++, since  then I can more easily change fonts (It should work with any true-type font, although I'll only bother with monospaced, I expect. Obviously there could be some tidying up, reduce the number of dp's, etc., but that can come later if needed. On 27/03/2022 13:18, Raymond West wrote: > Thanks. > > I've been trying to get into visual studio, cpp, and so far, so good. > I can programmatically generate svg code - lines, circles, text. > > I can generate text as g-code for machining, and that can be > relatively easily parsed to svg path statements. > > Hoverer, there are  few snags, a minor one is related to the different > x,y origins, and I have to dig in a bit more to get better rendering > .I've been experimenting with a simple vector font - just a single > line. It renders differently in openscad compared to a browser. I > think different defaults are applied. I think it may be easier to use > true type fonts, which seem to produce g code as an outline of the > character, not single lines. > > On 27/03/2022 12:18, Torsten Paul wrote: >> On 26.03.22 14:30, Raymond West wrote: >>> How far had you got? >> Really just started parsing the svg file, so it's still >> far off anything that could produce actual output. >> >> ciao, >>   Torsten. > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org