Jordan Brown

Here's how those new elements might be used: ``` f = "Liberation Sans"; size = 20; text = "Hello, world"; fm = fontmetrics(font=f, size=size); tm = textmetrics(text, font=f, size=size); echo(fm=fm);...

Do we want an issue or PR for the addition of those two values?

That last push added underline parameters to the data returned by fontmetrics(): `ECHO: { nominal = { ascent = 12.5733; descent = -2.9433; }; max = { ascent = 13.6109;...

Assuming that the tests run OK (which I expect them to), I think I'm done with this wad, and it's ready for final review and perhaps acceptance.

See #1608. I believe that a common mechanism for multi-color slicers is to give them one STL per color. You would then correspondingly arrange for your OpenSCAD model to have...

You would make one STL of the red parts, one STL of the green parts, et cetera. Then you import them all into your slicer with the same origin so...

So what to do about it? a) Ignore it. Pretend that "size" means "cap height", and pretend the difference between that and reality is because of font design and the...

Ah, duh, yes. I was thinking the new parameter would be `do_scaling_right=true`, but just replacing `size` would be much better. Agree that anything referencing points is wrong. `scale`: OK, `height`:...

But, come to think of it, anything that doesn't include "body" will have the "height of *what*?" problem, so they're all equivalent. And other places in OpenSCAD have `height` or,...

And even if it does include "body", only font geeks will know what that means, as distinct from any of the other perhaps-relevant measurements.