In the format section, "Trailing zeros must be removed" is a bit inaccurate. We mean that trailing decimal zeros or unnecessary trailing zeros must be removed. Maybe "trailing zeros to the right of the decimal point must be removed".
Also, there is no requirement to remove the point after a number, i.e. the present text suggests that "10." would be valid.
I'd change "A single leading zero before the decimal point is optional" to "The zero before the decimal point is optional"
Considering the leftmost picture below, suppose we call the next joint/bend to the right of the line ABCD as line HIJK, then I'd prefer a statement either allowing or disallowing a conditional line from H to K, i.e. without any line from I to J which is usually hidden away inside some other geometry. Personally, I'd prefer to require two separate conditional lines, one for HI and another for JK. This practice/preference has been unevenly enforced.
Orientation/Origin
It would be good to mention e.g. the standard expected for wheels.
I'd prefer mentioning the expectation that studless parts have their origin at the bottom of the part if the bottom can be attached to studded parts.
Should the preview keyword be mentioned here?
Why is the origin so late in the text? Since it is about the file rather than single lines, I'd expect it to be before or at the start of the geometry section.
What about
The 'duplicate lines' should be put under 'geometry'.
I also noticed overlap between the 'Header META commands' and the Official Library Header Specification. Do they really need to be two separate pages? Is this some kind of work in progress?
Also, there is no requirement to remove the point after a number, i.e. the present text suggests that "10." would be valid.
I'd change "A single leading zero before the decimal point is optional" to "The zero before the decimal point is optional"
Considering the leftmost picture below, suppose we call the next joint/bend to the right of the line ABCD as line HIJK, then I'd prefer a statement either allowing or disallowing a conditional line from H to K, i.e. without any line from I to J which is usually hidden away inside some other geometry. Personally, I'd prefer to require two separate conditional lines, one for HI and another for JK. This practice/preference has been unevenly enforced.
Orientation/Origin
It would be good to mention e.g. the standard expected for wheels.
I'd prefer mentioning the expectation that studless parts have their origin at the bottom of the part if the bottom can be attached to studded parts.
Should the preview keyword be mentioned here?
Why is the origin so late in the text? Since it is about the file rather than single lines, I'd expect it to be before or at the start of the geometry section.
What about
- file name, encoding, extensions
- origin, orientation
- meta commands
- geometry
- numbers
- colors
The 'duplicate lines' should be put under 'geometry'.
I also noticed overlap between the 'Header META commands' and the Official Library Header Specification. Do they really need to be two separate pages? Is this some kind of work in progress?