I've been working on creating my own single line fonts lately and I'd like to share with you the workflow that I ended up with. It involves converting all single paths in one go to the glyphs of the svg-font.

Updated version with a lot easier workflow.

Hello,
First of all, congratulations for your work and your tutorial.
Now, It's a complicated issue the font creation.And I'm affraid that even with an extension like yours, it's still a complicated issue. But, some one has to give the first step!.
I think that the process of aligning (Ctrl + A) several times could induce to errors. Just talking about the writen tutorial.
Recently, here on the forum, some one posted an issue involving a cutter and a open path. So, it's posible for a cutter to cut a single, open path, or it depends of the cutter?.

A few years ago, open paths were problematic for some of the consumer grade cutter software applications, but now they can handle open paths. Open paths are desirable for pen plotting, engraving and partial cuts, such as those for creating fold outs or pop-ups.

I'm sure that the workflow is not waterproof, hulf2012. The process of tossing the paths around with ctrl-A and a black fog of paths with little or no visual feedback and control is a fragile procedure, but at least it works if every step is after the recipe and within the family of the bugs I've met

I have now refined the extension to copy the paths to the glyphs and the process is a lot easier than the first approach. There will always be a lot of work designing the paths, but the conversion to the font is pretty compressed with this extension.

You can find the updated tutorial on my blog.

Hei.

Kjempebra Ellen!

Nice code and nice explanation on your blog.

Have to give this a try.

Regarding your blog. Any chance of moving your shared files (like "glassmerker") from 4shared to dropbox?
I don't trust 4shared exe files!

RGDS
Ragnar

Jo takk, Ragnar Thanks for reminding me to update to dropbox. I thought I already had done that. Now its fixed.

Got a feedback that I forgot to remove some lines from the code for debugging which made it crash for others. Now I have updated it on my blog (and I guess I will several times to refine it even more - just for fun).