widths

There is a fundamental reason for the difference: in standard CSS block/inline layout, widths depend on parent widths, but heights depend on child heights.

Certainly seen this used for different widths of spaces, and different widths of dashes, even though the keyboard has only the space bar and the hyphen.

And while you're at it, help convince those web developers that required 1024+ pixel widths on pages are counterproductive.

It's not a 1:1 correspondence but it's a pretty close correlation to the actual widths of things.

But ideally this is something that should be decided by each developer's personal editor config, like tab widths for indentation.

You still have widths expressed in pixels which still limits the chance of your text being readable on some smaller devices.

Although, maybe if you prefer narrow column widths, you should resize your browser window.

It's probably a personal aesthetic, but the variable stroke widths make it look cartoony.

Two structures share acommon initial sequenceif corresponding members havecompatible types (and, for bit-fields, the same widths) for a sequence of one or moreinitial members.

I just wanted some sense of the continuing extent of each language indicated, (that is, the labels should have variable widths).

I have a couple of the results here[1] (my boxes are off in terms of size, but the flow widths should be correct).

There's not much guessing going on here, you are either able to define the viewport, or it will render the page at the widths specified in the page styles.

Wouldn't this "pre-calculated" version work only for a certain combination of text size, line-height, element widths, and zoom settings?

There are different allowed widths and heights ("loading gauge") for train cars in different countries.