[LSC] File Format Restrictions for Official Parts

[William Howard]

> 1) Co-planar angle

I'll happily defer to better mathmaticians / rendering software authors than 
me, but how about a maximum angle of 5 degrees with a strong recommendation 
for 2 degress (and a comment that parts already in the library or certified 
on the tracker are not to be re-submitted just to fix any violations)


> 2) Overlapping/intersecting polygons

How about adding a comment that overlapping primitives, provided that the 
overlap is small, are considered acceptable.  My intention was not to force 
authors to in-line primitives.  However,  there may be some cases where it 
is better to use (say) a 3-8cyli and a quad than a 1-2cyli, but I think the 
PT review process is already very good at handling these cases


> 3) Line / cond line overlap

Change must not overlap to strong recommendation not to.  This could be 
relocated into the official 1.0 file format spec (but for some reason I'm 
loathed to edit that file just now - perhaps in 4 months time ;-) )


> 4) File naming - sections for patterned parts and parts without a known 

> Lego number.

Include the necessary text into this spec


> 5) File naming - move to a seperate file?

I was hoping that we could dispense with all the individual and dispersed 
files (specs, lugnet posts, PT FAQ, etc) and gather all the information into 
one place, so this to me seems counter-productive


> 6) Leading zero before decimal point

If we are going to allow 3) to reduce file size, adding unnecessary zeros 
could easily outweigh those gains.  There are already files that do / do not 
have leading zeros before the decimal point.  My vote is to leave it as it 
is (ie optional)