The PVMM handles text in a way that can be converted back and forth between XML & PVM & HTML formats with ease. Examples are: Holy Redeemer Episcopal Church.....
The XML version is how we store text data in APL files. This makes the text string self-documenting.
We can store whatever properties we want with each text string and only pull out those we need for whatever reference or search table we want. Also we can recreate the table whenever we want, so we're not at risk with regard to it getting out of kilter with the data.
We can edit this text string with notepad as long as we're alert to the XML structure, but that shouldn't be difficult to teach someone. And, of course, we can create a form for editing the data so that even a careless person can't mess things up too easily.
The only difficulty found with this so far is that the properties each need some kind of separator. Bracket "br" close-bracket is used for some of the fields, quad-tcnl twice for others. We'll have to give that some more thought, but XML, HTML and a PVM are wonderful ways of handling text. The use of separators can be handled in the "Field Gallery" (FieldGallery). Davin Church's utilities make all this possible and easy.
Davin offers the following comment.
XML is a good way of storing arbitrarily-structured text. However, you must be aware of some limitations in the process...
For one thing, you should keep your data as text-only, because when converting XML back to PVMs, a general utility won't know when something is supposed to be numeric.
XML is good for a general data repository, but it isn't fast enough to use for a database or other speed-intensive needs (in case you were thinking that). It's fine for storing configuration information and other reference data.
Casually putting HTML inside XML is problematic, as they both use the same syntax of
, and HTML isn't as strict in structure. This can really mess up trying to parse it out of XML tags. The way you fix this is to convert the HTML "<" & ">" characters to special codes so they don't end up looking like bad XML. The XMLItem function will do this for you if you call it an extra time with only a right argument.
As for your problem with separators, I think you're approaching it wrong. If you need to separate data units, just use XML itself to do that. Get rid of all the TCNLs and
s that aren't part of your actual data. And from your text file, it doesn't look like you're using my XML utilities properly - aren't you using XMLItem and BuildXML to create that string?
Do you need some more help working with my XML tools?