Hi Tony,
Ralph hold that position for all time... his book is fantastic and I use it
regularly... he is the guru...
HTML is like a subset of XML except XML rules are a little tighter.. XHTML is
HTML conforming to XML rules.
HTML is more concerned with the presentation of data, where XML is the data and
the description of data... but it can be far more than that... .
HTML has predefined elements... such as <b> and <body> and <table> and <form>
and those elements have their own syntax... When XML is used like this it is
called a vocabulary...
XML however can be defined anyway you want it... I can just slap this out
<login>
<success>No</success>
</login>
and you would instantly have an idea what it meant and what the information was
that it was carrying...
since it is is all text then DP is great at manipulating it, and it can extend
DP into new areas...
For example, Vector graphics seem something that DP ws never designed for,
however SVG (Scaleable Vector Graphics) are just another XML application or
vocabulary... so for instance,
<svg xmlns="http://www.w3.org/2000/svg"; width="467" height="462">
<rect x="80" y="60" width="250" height="250" />
<rect x="140" y="120" width="250" height="250" />
</svg>
would generate a two overlapped rectangles in a SVG capable program, (The
xmlns thing which looks like a web link tell the application the context or
namespace that svg refers to... so it know to rended it as a vector graphic
and not in some other context. ) If you copy that to a file and gave it a name
such as test.svg and then opened it with Firefox you would see the two
rectangles.
But it doesn;t take much imagination to realise that DP could easily produce
that file, or more complex files. MusicML is a music vocabulty, and so DP could
stored information about music scores and produce MusicML files which could be
used with compatible instruments to play sounds, or in sheet music programs to
display a score... When you web enable DP delivering XML means you can power
all kinds of applications and devices dynamically... XML become the glue for
transmitting data from one system to another.
Because XML is so popular there are many merging standards and things you can
do with it... For example, you can use XSLT to convert XML into an HTML
webpage... its like merging data and a template together... which means for DP
you are relieved of any need to think aobut presentation. Making major changes
to HTML in DP can be a chore, but with XSLT you can style the data anyway you
like all externally to DP
So just as you can produce HTML from DP you can with the same ease produce XML,
which can be used for creating HTML, or for many other applications
Regards
Brian
----- Original Message -----
From: Tony Perez
To: Dataperfect Users Discussion Group
Sent: Wednesday, March 05, 2008 9:55 PM
Subject: RE: [Dataperf] Code Page
Hello Michael and Brian,
Interesting discussion. I am somewhat lost in the definition of XML. Is that
the same as HTM or HTML? It suggests it's some kind of a mark-up language, but
how does it differ from HTML?
Brian, keep this up and you'll replace Ralph as the DP guru!! :)
Regards to all,
Tony
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brian Hancock
Sent: Wednesday, March 05, 2008 2:27 AM
To: Dataperfect Users Discussion Group
Subject: Re: [Dataperf] Code Page
Hi Michael,
The command "CHCP 437" will set the code page, but I am not sure that that
will have any effect on the problem of your record delimiter and memo fields.
Whenever I export data I use either WP format or XML. generally text file
exports produce the sort of problems you refer to. Mind you I think
Export data out in XML... and use a CDATA section for the memo fields.
Yuio will need to create a Schema (actually the easiest way is to create the
target tables in Access and then export a couple of records as XML, and use
that nd the schema as a template for bringing data from DP.
Creating XML in DP is a piece of cake.
Another way of exporting the data so that you avoid the problem of embedded
lines feeds is to create a report to do the export, and to format memo fields
with the Print Mode Indicator of ;;Q... so you format for the output memo
field might look something like A0A0;;Q
The ;;Q converts embedded CR or CRLF to \n so the text
The quick brown fox CRLF
jumps over the laxy dog
becomes
The quick brown fox\njumpsover the lazy dog"
which overcomes the record delimter problems. (Note that embedded "\"s
become "\\")
Once you get the data into Access it is relatively simple to search and
replace \n to be a CRLF and \\ to be a \
Regards
Brian
----- Original Message -----
From: Michael Iannantuoni
To: Dataperfect Users Discussion Group
Sent: Wednesday, March 05, 2008 6:36 PM
Subject: Re: [Dataperf] Code Page
Hi Brian,
Thanks for the info about CHCP but I'm not sure what I need to set it to.
It currently shows 850.
The problem I had was exporting data from a very simple DataPerfect
application to experiment with in Access. I use a delimited file export using |
for field delimiter and ~ for record delimiter only to find that Access doesn't
allow a record delimiter other that a HRt (!!!!! so much for memo fields in
Access!!!) and that within the Windows environment, my | had changed to a Y
with an acute accent. I seem to recall using Code Page 437 in the past so might
experiment a little.
Regards,
Michael
Brian Hancock wrote:
Hi Michael,
Although I have never had to change a code page from the default 457 on
oz version of Windows , you can do it from the command window before running
DP, eiher inteactively or in a batch file, or by setting it in the autoexec
file for the MS-DOS shortcut.
The utility to change Code page is CHCP, which if executed without a
parameter returns the code page or if executed CHCP xxx set the code page to
the parameter.
When you set up a Shortcut to an MS-DOS program, within its Properties,
from the Advanced Button on the Program tab, you can set the Config.sys and
Autoexec.bat files. By default on WINNT and derivatives it will use two default
files CONFIG.NT and AUTOEXEC.NT located in the Windows\System32 folder. You can
either edit the Autoexec.NT file directly or if you only want to change the
codepage (or other setting) for that instance you can specify a different
autoexec which you have added the necessary CHCP xxx setting. Probably easiest
is it to copy the original AUTOEXEC.NT edit the copy and seting the properties
in the shortcut to use it instead.
Regards
Brian
----- Original Message -----
From: Michael Iannantuoni
To: Dataperfect Mailing List
Sent: Tuesday, March 04, 2008 8:11 PM
Subject: [Dataperf] Code Page
Can someone remind me where I set the Code Page for DataPerfect on a
Windows XP system please.
Thanks,
Michael
----------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
--------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
------------------------------------------------------------------------------
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
_______________________________________________
Dataperf mailing list
[email protected]
http://lists.dataperfect.nl/mailman/listinfo/dataperf
