Hi Wiebe,

I am not exactly sure... I can;' remember where I got this information from... but I put it into my DP Cheatsheet for times like this... However I do seem to remember that in many cases whitespace is ignored so

#C:
=1=*1"Kirk"*3 BO "Boldly"
BF "go where no man has"
UO "tread" UF
CR "--------------------------------------"**

gives the same result (I think) as

#C:
=1=*1"Kirk"*3 BO "Boldly" BF "go where no man has" UO "tread" UF CR "--------------------------------------"**

whitespace being newlines or spaces...

Now the really nice thing about this in Ruby is that you have PERL-like Regular Expressions, so you should readily be able to either check its validity or parse it into its components

Regards
Brian

----- Original Message ----- From: "Wiebe Cazemier" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, July 20, 2007 11:33 PM
Subject: [Dataperf] Re: Transaction log markup


Hmm, that is more complicated than I thought.

About the bold and underline; in my tests, the BO and BF (etc) codes are always on a new line. Is a memo field something else than a a multiline textfield,
and hence the reason those codes are not on new lines?


On Friday 20 July 2007 07:08, Brian Hancock wrote:

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

_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf


_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf

Reply via email to