Leading or trailing white space characters in file names

[Roland Melkert]

The current spec says: "The whitespace characters allowed for keyword and parameter separation include spaces and tabs". I don't think this is clear and or complete at all.

So maybe replace:

Every line of the file contains one command. With few exceptions, every command is independent of other lines. The exceptions are the BFC meta-commands which modify the behaviour of one or more following command lines. There is no line length restriction. The whitespace characters allowed for keyword and parameter separation include spaces and tabs. Every command starts with a number, called a line type. The function and format of the line is determined by the line type.

with

Every line of the file contains one command. With few exceptions, every command is independent of other lines. The exceptions are the BFC meta-commands which modify the behaviour of one or more following command lines. There is no line length restriction. Every command starts with a number, called a line type. The function and format of the line is determined by the line type.

And add a section below it (just like "text based", "text encoding", etc)

Whitespace

The whitespace used to separate tokens throughout the document may only exist out the following: used to separate tokens may be any of the following:

- space
- horizontal tab
- vertical tab
- form feed

I've removed the 'new line' and 'carriage' return from that list because of the line orientated nature of LDraw.

And as a result of the above we can adjust the line:

<file> is the filename of the sub-file referenced and must be a valid LDraw filename.

to

<file> is the filename of the sub-file referenced and must be a valid LDraw filename. Any leading and/or trailing whitespaces must be ignored.

Although some native speaking English person could probably word all of this better.