Mercurial > hg > batmud > maputils
changeset 795:21e148e89bcc
Some improvements and clarifications in LOC format v3 documentation.
| author | Matti Hamalainen <ccr@tnsp.org> |
|---|---|
| date | Sun, 12 Jul 2009 02:26:53 +0000 |
| parents | 0b42f2952bde |
| children | 3504e24e3de2 |
| files | README.loc |
| diffstat | 1 files changed, 5 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/README.loc Wed Jun 17 21:25:55 2009 +0000 +++ b/README.loc Sun Jul 12 02:26:53 2009 +0000 @@ -6,6 +6,7 @@ fileformat v2 to v3: * Records are no longer line-based, but can span multiple lines. + A new record can only start after a newline, though. * String fields can have escaped sequences inside them. * Name field can now contain optional alternative names, separated by pipe ('|'). First name, is still used as the @@ -31,9 +32,10 @@ * Empty lines (this includes lines with whitespace only) are IGNORED. * Lines where the first non-whitespace character is a hash (#), are considered comments and are thus IGNORED. Processing software MAY - preserve and add comments, if wished. - * String-type fields can contain ESCAPED sequences (escape character is - slash '\'), which MUST be parsed into literals. + preserve and add comments, if wished. Comment lines CAN NOT be + continued with the above mentioned line continuation method. + * String-type fields can contain ESCAPED sequences (escape character + is slash '\'), which MUST be parsed into literals. Example: foo\;bar would be parsed to "foo;bar" Each record is divided to fields 8 fields via semicolons (;). Fields MAY