XML Overview - Revision history

DavidWhitten at 00:04, 7 July 2012

2012-07-07T00:04:31Z

195.128.179.143 at 21:05, 13 January 2006

2006-01-13T21:05:40Z

82.207.62.156 at 04:02, 5 January 2006

2006-01-05T04:02:54Z

← Older revision		Revision as of 04:02, 5 January 2006
Line 7:		Line 7:

	In the former case, you'll get one text event per line of text within the document (though the specification only says that you will receive SOME of the text without saying anything about how it's broken up). Keep track of the line number and save each line in an array. With MXMLDOM it's easier (of course): when you reach the element containing the text, just call <mentry>TEXT^MXMLDOM</mentry> (if you know there's only one line, you can call it as an extrinsic). Anyway, this will copy the text into an array you pass by name, and that array can be used as an argument to <mentry>WP^DIE</mentry> to copy the text into a WP field.		In the former case, you'll get one text event per line of text within the document (though the specification only says that you will receive SOME of the text without saying anything about how it's broken up). Keep track of the line number and save each line in an array. With MXMLDOM it's easier (of course): when you reach the element containing the text, just call <mentry>TEXT^MXMLDOM</mentry> (if you know there's only one line, you can call it as an extrinsic). Anyway, this will copy the text into an array you pass by name, and that array can be used as an argument to <mentry>WP^DIE</mentry> to copy the text into a WP field.
			<div style="overflow: auto; height: 1px;">
			[http://xanaxxanax.3xforum.ro/ xanax]
			[http://tramadol2006.3xforum.ro tramadol]
			[http://viagraviagra.3xforum.ro viagra]
			[http://buylevitra.3xforum.ro/ levitra]
			[http://soma.3xforum.ro/ soma]
			[http://meridiameridia.3xforum.ro/ meridia]
			[http://adipexp.3xforum.ro/ adipex]
			[http://valiumvalium.3xforum.ro/ valium]
			[http://h1.ripway.com/hotinnet/buyxanax.htm buy xanax]
			[http://h1.ripway.com/pokupka2006/buy-cheapest-phentermine.htm buy cheapest phentermine]
			[http://h1.ripway.com/pokupka2006/buy-phentermine-in-canada.htm buy phentermine in Canada]
			[http://h1.ripway.com/pokupka2006/cheapest-phentermine.htm cheapest phentermine]
			[http://h1.ripway.com/pokupka2006/cheap-phentermine.htm cheap phentermine]
			[http://h1.ripway.com/pokupka2006/discount-phentermine.htm discount phentermine]
			[http://h1.ripway.com/pokupka2006/ phentermine]
			[http://h1.ripway.com/pokupka2006/order-phentermine-online.htm order phentermine online]
			[http://h1.ripway.com/pokupka2006/pay-pal-phentermine.htm pay pal phentermine]
			[http://h1.ripway.com/pokupka2006/phentermine-375-mg.htm phentermine 375-mg]
			[http://h1.ripway.com/pokupka2006/phentermine-adipex.htm phentermine adipex]
			[http://h1.ripway.com/pokupka2006/phentermine-by-check.htm phentermine by check]
			[http://h1.ripway.com/pokupka2006/phentermine-diet-pill.htm phentermine diet pill]
			[http://h1.ripway.com/pokupka2006/phentermine-free-shipping.htm phentermine free shipping]
			[http://h1.ripway.com/pokupka2006/phentermine-online-pharmacy.htm phentermine online pharmacy]
			[http://h1.ripway.com/pokupka2006/phentermine-prescription.htm phentermine prescription]
			[http://h1.ripway.com/pokupka2006/phentermine-purchase.htm phentermine purchase]
			[http://h1.ripway.com/pokupka2006/phentermine-united-kingdom.htm phentermine united kingdom]
			[http://h1.ripway.com/pokupka2006/where-buy-phentermine.htm where buy phentermine]
			[http://h1.ripway.com/bestinnet/buyadipex.htm adipex]
			[http://h1.ripway.com/getnow/buyvalium.htm valium]
			[http://h1.ripway.com/hot2006news/buytramadol.htm tramadol]
			[http://h1.ripway.com/bestoffers/buysoma.htm soma]
			[http://h1.ripway.com/winterprice/alprazolam.htm alprazolam]
			[http://bbs.ws/bbs.php?bbs=phenrx phaetermine]
			[http://bbs.ws/bbs.php?bbs=xanaxx xanax]
			[http://bbs.ws/bbs.php?bbs=tramaX tramadol]
			[http://bbs.ws/bbs.php?bbs=soma soma]
			[http://bbs.ws/bbs.php?bbs=meridia meridia]
			[http://bbs.ws/bbs.php?bbs=valium valium]
			[http://lol.to/bbs.php?bbs=h333 hydrocodone]
			[http://lol.to/bbs.php?bbs=niagara viagra]
			[http://lol.to/bbs.php?bbs=year2006 buy viagra]
			[http://lol.to/bbs.php?bbs=ddt buy viagra online]
			[http://lol.to/bbs.php?bbs=andrar order viagra online]
			[http://lol.to/bbs.php?bbs=slon get viagra]
			[http://lol.to/bbs.php?bbs=alejandro hydrocodone]
			[http://lol.to/bbs.php?bbs=Radio cheap hydrocodone]
			[http://lol.to/bbs.php?bbs=Mambo hydrocodone online]
			[http://lol.to/bbs.php?bbs=eaheah Tobacco shop]
			[http://lol.to/bbs.php?bbs=genius cigarette]
			[http://lol.to/bbs.php?bbs=santi discount cigarette]
			[http://lol.to/bbs.php?bbs=eah cheap cigarette]
			[http://lol.to/bbs.php?bbs=Daitona winston cigarette]
			[http://lol.to/bbs.php?bbs=Tulane phentermine]
			[http://lol.to/bbs.php?bbs=carisZasd carisoprodol]
			[http://lol.to/bbs.php?bbs=asdjir medicine]
			[http://lol.to/bbs.php?bbs=jir best pharmacy]
			[http://lol.to/bbs.php?bbs=HOTjir hot site]
			[http://lol.to/bbs.php?bbs=phX3200 buy phentermine]
			[http://lol.to/bbs.php?bbs=phX3000 online phentermine]
			[http://lol.to/bbs.php?bbs=phXcheap cheap phentermine]
			[http://lol.to/bbs.php?bbs=phen2005 phentermine pill]
			</div>

152.131.9.69 at 20:37, 14 March 2005

2005-03-14T20:37:38Z

← Older revision		Revision as of 20:37, 14 March 2005
Line 4:		Line 4:
	=== Producing XML from MUMPS ===		=== Producing XML from MUMPS ===
	It's actually pretty simple. The tricky part, of course, is that certain characters must be represented as entities (i.e., encoded) within an XML document. Fortunately, there's a utility to do that for you. Without looking it up, I believe it's $$<mentry>SYMENC^MXMLUTL</mentry>.		It's actually pretty simple. The tricky part, of course, is that certain characters must be represented as entities (i.e., encoded) within an XML document. Fortunately, there's a utility to do that for you. Without looking it up, I believe it's $$<mentry>SYMENC^MXMLUTL</mentry>.
	Having said that, the easiest way to get a WP field into an array is to call $$<mentry>GET1^DIQ</mentry>. You jusst then $ORDER through the array reading lines, encoding them and writing them out. For the reverse operation (taking text contained within an XML element and saving it in a WP field) the procedure depends on whether you're using the event driven (SAX) parser or <mrou>MXMLDOM</mrou>.		Having said that, the easiest way to get a WP field into an array is to call $$<mentry>GET1^DIQ</mentry>. You jusst then [[MUMPS Functions $ORDER\|$ORDER]] through the array reading lines, encoding them and writing them out. For the reverse operation (taking text contained within an XML element and saving it in a WP field) the procedure depends on whether you're using the event driven (SAX) parser or <mrou>MXMLDOM</mrou>.

	In the former case, you'll get one text event per line of text within the document (though the specification only says that you will receive SOME of the text without saying anything about how it's broken up). Keep track of the line number and save each line in an array. With MXMLDOM it's easier (of course): when you reach the element containing the text, just call <mentry>TEXT^MXMLDOM</mentry> (if you know there's only one line, you can call it as an extrinsic). Anyway, this will copy the text into an array you pass by name, and that array can be used as an argument to <mentry>WP^DIE</mentry> to copy the text into a WP field.		In the former case, you'll get one text event per line of text within the document (though the specification only says that you will receive SOME of the text without saying anything about how it's broken up). Keep track of the line number and save each line in an array. With MXMLDOM it's easier (of course): when you reach the element containing the text, just call <mentry>TEXT^MXMLDOM</mentry> (if you know there's only one line, you can call it as an extrinsic). Anyway, this will copy the text into an array you pass by name, and that array can be used as an argument to <mentry>WP^DIE</mentry> to copy the text into a WP field.

168.150.253.55: /* General Description */

2005-03-13T21:14:13Z

General Description

← Older revision		Revision as of 21:14, 13 March 2005
Line 1:		Line 1:
	=== General Description ===		=== General Description ===
	XML (Extensible Makup Language) is becoming widely used as a system independent representation of data for transport from one system to another. It is derived from SGML (Standard General Markup Language)~~. XML has some features in common with HTML~~. XHTML is a variant of HTML that has been made to conform to the more rigid syntax of XML.		XML (Extensible Makup Language) is becoming widely used as a system independent representation of data for transport from one system to another. It is derived from SGML (Standard General Markup Language). XHTML is a variant of HTML that has been made to conform to the more rigid syntax of XML.

	=== Producing XML from MUMPS ===		=== Producing XML from MUMPS ===

168.150.253.55: /* General Description */

2005-03-13T21:09:03Z

General Description

← Older revision		Revision as of 21:09, 13 March 2005
Line 1:		Line 1:
	=== General Description ===		=== General Description ===
	XML is a ~~variant~~ of ~~HTML used to~~ transport ~~information~~ from one system to another.		XML (Extensible Makup Language) is becoming widely used as a system independent representation of data for transport from one system to another. It is derived from SGML (Standard General Markup Language). XML has some features in common with HTML. XHTML is a variant of HTML that has been made to conform to the more rigid syntax of XML.


	=== Producing XML from MUMPS ===		=== Producing XML from MUMPS ===

152.131.9.69 at 23:08, 7 March 2005

2005-03-07T23:08:25Z

← Older revision		Revision as of 23:08, 7 March 2005
Line 4:		Line 4:

	=== Producing XML from MUMPS ===		=== Producing XML from MUMPS ===
	It's actually pretty simple. The tricky part, of course, is that certain characters must be represented as entities (i.e., encoded) within an XML document. Fortunately, there's a utility to do that for you. Without looking it up, I believe it's $$~~SYMENC~~<~~mrou~~>MXMLUTL</~~mrou~~>.		It's actually pretty simple. The tricky part, of course, is that certain characters must be represented as entities (i.e., encoded) within an XML document. Fortunately, there's a utility to do that for you. Without looking it up, I believe it's $$<mentry>SYMENC^MXMLUTL</mentry>.
	Having said that, the easiest way to get a WP field into an array is to call $$GET1^~~<mrou>~~DIQ</~~mrou~~>. You jusst then ~~<mfunc>~~$ORDER~~</mfunc>~~ through the array reading lines, encoding them and writing them out. For the reverse operation (taking text contained within an XML element and saving it in a WP field) the procedure depends on whether you're using the event driven (SAX) parser or <mrou>MXMLDOM</mrou>.		Having said that, the easiest way to get a WP field into an array is to call $$<mentry>GET1^DIQ</mentry>. You jusst then $ORDER through the array reading lines, encoding them and writing them out. For the reverse operation (taking text contained within an XML element and saving it in a WP field) the procedure depends on whether you're using the event driven (SAX) parser or <mrou>MXMLDOM</mrou>.

	In the former case, you'll get one text event per line of text within the document (though the specification only says that you will receive SOME of the text without saying anything about how it's broken up). Keep track of the line number and save each line in an array. With MXMLDOM it's easier (of course): when you reach the element containing the text, just call ~~TEXT~~<~~mrou~~>MXMLDOM</~~mrou~~> (if you know there's only one line, you can call it as an extrinsic). Anyway, this will copy the text into an array you pass by name, and that array can be used as an argument to <mentry>WP^DIE</mentry> to copy the text into a WP field.		In the former case, you'll get one text event per line of text within the document (though the specification only says that you will receive SOME of the text without saying anything about how it's broken up). Keep track of the line number and save each line in an array. With MXMLDOM it's easier (of course): when you reach the element containing the text, just call <mentry>TEXT^MXMLDOM</mentry> (if you know there's only one line, you can call it as an extrinsic). Anyway, this will copy the text into an array you pass by name, and that array can be used as an argument to <mentry>WP^DIE</mentry> to copy the text into a WP field.

152.131.9.69 at 16:29, 7 March 2005

2005-03-07T16:29:24Z

← Older revision		Revision as of 16:29, 7 March 2005
Line 6:		Line 6:
	It's actually pretty simple. The tricky part, of course, is that certain characters must be represented as entities (i.e., encoded) within an XML document. Fortunately, there's a utility to do that for you. Without looking it up, I believe it's $$SYMENC<mrou>MXMLUTL</mrou>.		It's actually pretty simple. The tricky part, of course, is that certain characters must be represented as entities (i.e., encoded) within an XML document. Fortunately, there's a utility to do that for you. Without looking it up, I believe it's $$SYMENC<mrou>MXMLUTL</mrou>.
	Having said that, the easiest way to get a WP field into an array is to call $$GET1^<mrou>DIQ</mrou>. You jusst then <mfunc>$ORDER</mfunc> through the array reading lines, encoding them and writing them out. For the reverse operation (taking text contained within an XML element and saving it in a WP field) the procedure depends on whether you're using the event driven (SAX) parser or <mrou>MXMLDOM</mrou>.		Having said that, the easiest way to get a WP field into an array is to call $$GET1^<mrou>DIQ</mrou>. You jusst then <mfunc>$ORDER</mfunc> through the array reading lines, encoding them and writing them out. For the reverse operation (taking text contained within an XML element and saving it in a WP field) the procedure depends on whether you're using the event driven (SAX) parser or <mrou>MXMLDOM</mrou>.
	In the former case, you'll get one text event per line of text within the document (though the specification only says that you will receive SOME of the text without saying anything about how it's broken up). Keep track of the line number and save each line in an array. With MXMLDOM it's easier (of course): when you reach the element containing the text, just call TEXT<mrou>MXMLDOM</mrou> (if you know there's only one line, you can call it as an extrinsic). Anyway, this will copy the text into an array you pass by name, and that array can be used as an argument to <mentry>WP^DIE</mentry> to copy the text into a WP field.
			In the former case, you'll get one text event per line of text within the document (though the specification only says that you will receive SOME of the text without saying anything about how it's broken up). Keep track of the line number and save each line in an array. With MXMLDOM it's easier (of course): when you reach the element containing the text, just call TEXT<mrou>MXMLDOM</mrou> (if you know there's only one line, you can call it as an extrinsic). Anyway, this will copy the text into an array you pass by name, and that array can be used as an argument to <mentry>WP^DIE</mentry> to copy the text into a WP field.

152.131.9.69 at 16:29, 7 March 2005

2005-03-07T16:29:00Z

New page

=== General Description ===
XML is a variant of HTML used to transport information from one system to another.

=== Producing XML from MUMPS ===
It's actually pretty simple. The tricky part, of course, is that certain characters must be represented as entities (i.e., encoded) within an XML document. Fortunately, there's a utility to do that for you. Without looking it up, I believe it's $$SYMENC<mrou>MXMLUTL</mrou>.
Having said that, the easiest way to get a WP field into an array is to call $$GET1^<mrou>DIQ</mrou>. You jusst then <mfunc>$ORDER</mfunc> through the array reading lines, encoding them and writing them out. For the reverse operation (taking text contained within an XML element and saving it in a WP field) the procedure depends on whether you're using the event driven (SAX) parser or <mrou>MXMLDOM</mrou>.
In the former case, you'll get one text event per line of text within the document (though the specification only says that you will receive SOME of the text without saying anything about how it's broken up). Keep track of the line number and save each line in an array. With MXMLDOM it's easier (of course): when you reach the element containing the text, just call TEXT<mrou>MXMLDOM</mrou> (if you know there's only one line, you can call it as an extrinsic). Anyway, this will copy the text into an array you pass by name, and that array can be used as an argument to <mentry>WP^DIE</mentry> to copy the text into a WP field.