Hi Wiebe,
I can only add this
Transaction Log
Transaction
Syntax
Create
#C: date yyyy/mm/dd time 99:99:99
=panel= *field1"val1"*field2"val2"...**
Edit
#E: date yyyy/mm/dd time 99:99:99
=panel=index+field"keyvalue"++
*field"newvalue"*field2"newvalue"**
Delete
#D: date yyyy/mm/dd time 99:99:99
=panel=index+field"keyvalue"++
Run Report
#R:
=reportnumber=
Note: date yyyy/mm/dd time 99:99:99 is optional
For Memo fields - embedded:
Carriage Return
*field"Line1" CR "Line two"**
Bold (paired)
*field"Text" BO "Bolded" BF "text"**
Underline (paired)
*field"text" UO "UndLn" UF "text"**
#C:
=1=*1"Kirk"*3 BO "Boldly"
BF "go where no man has"
UO "tread" UF
CR "--------------------------------------"**
Regards
Brian
----- Original Message -----
From: "Wiebe Cazemier" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, July 19, 2007 10:37 PM
Subject: [Dataperf] Transaction log markup
Hi,
I want to write an importer/writer for DP transaction logs in ruby, and to
do
that, I need to know the markup of the file. Is there anything more I need
to
know besides:
- Line begins with: =<panelnr>=
- Field seperator is: *<fieldnr>
- Record seperator is: **
- Field contents is in quotes: "name"
- Quoted text in fields is double quoted, like: ""hello""
And some questions I have:
New lines in multiline fields, both have \r\n and the string CR. I don't
quite
see the logic which is used when.
What exactly is the character encoding? I started DP with the /w flag,
which
causes reports to be written in latin1, but it doesn't seem to help with
transaction logs. Is this a conscience choice, seeing as how importing
back
from a WP merge file containing latin1 fails?
Any help is appreciated.
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
