--- as-events.pod 2003/03/06 16:24:27 1.1
+++ as-events.pod 2003/03/06 17:02:57 1.2
@@ -42,13 +42,13 @@
amounts, remarks, and other values. This data tuple is termed an I<event>, and
may either be transmitted to a B<AS> server or stored to a local file. Should
it be stored to a local file, the file name is arbitrary and is shown in the
-title bar of B<as-gui>. In most cases the postfix B<.as> is appended to the
-file name, although this behaviour can be turned on or off through the user
-preferences.
+title bar of B<as-gui>. Typically, the file is called F<events.as>. In most
+cases the postfix B<.as> is appended to the file name, although this behaviour
+can be turned on or off through the user preferences.
=head1 FILE FORMAT
-The B<events.as> file contains ASCII text. The first line consists of an
+The B<as-events> file contains ASCII text. The first line consists of an
identifier to associate the file type and version. Following text may contain
white space, comments, and data tuples.
@@ -58,10 +58,12 @@
B<eventsid> ::= "%!AS-EVENTS-" [0-9] '.' [0-9]
-B<tuplelist> ::= B<tuplelist> | B<tuple> | EMPTY
+B<tuplelist> ::= B<tuplelist> | B<tuple> | B<comment> | EMPTY
B<tuple> ::= B<user> B<uuid> B<crc> B<revision> B<date> B<begin> B<end> B<amount> B<account> B<remark>
+B<comment> ::= ($#.*)
+
(* user field *)
B<user> ::= [a-zA-Z][a-zA-Z0-9]+
@@ -116,7 +118,7 @@
B<accsep> ::= '/'
-B<acctext> ::= [a-zA-Z0-9_-]+
+B<acctext> ::= [a-zA-Z0-9_-]*
(* remark field *)
@@ -124,7 +126,7 @@
=head1 EXAMPLE
-A typical F<events.as> file might look like this:
+A typical B<as-events> file might look like this:
%!AS-EVENTS-0.6
harvey 0ccf1d42-743b-43df-9b5d-202451b3c26f e8f212b6 0 2002-09-30 00:00 00:00 02:00 /it/development/meeting/weekly "Code review"
@@ -133,7 +135,8 @@
=head1 SEE ALSO
-as-gui(1)
-as-gui.conf(5)
+as-gui(1),
+as-gui.conf(5),
+as-accounts(5),
=cut
|
