Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SGML to XML

Status
Not open for further replies.
radugb

radugb

Technical User
Dec 28, 2006
12
US
I have a whole lot of files in .sgm format that I need to convert over to XML so the new version of the program they go with will recognize them. I have no idea how to write XML or SGML and am hoping that there may be some sort of GUI conversion tool (of the drag and drop method) that can do it for the most part automatically. Any ideas? Thx, RaduG

ps: when I mean a lot, I mean about 21000 file each about 1.5kb
 
Sort by date Sort by votes
Can you provide an example, or a representative fragment, of the SGML files?

Also, does the 'new version of the program' come with an XML Xchema description of the XML documents it expects? If so, that might be helpful, too.

Tom Morrison
 
Upvote 0 Downvote
Here is an example of what the 2.8 version data files are (the SGML format ones):

<!DOCTYPE VCESI PUBLIC "-//Volvo Construction Equipment//DTD VCESI03//EN"[
]>
<VCESI lang="GB"><PRODUCT-SPECIFIC><SERVINFOTYPE><INTRO-PARTINFO><SERVINFO><TITLE>Preface</TITLE><SUBTITLE>EXCAVATOR VOLVO EC210</SUBTITLE><PARA><PTXT><EMPH ETYPE="BOLD">BASIC MACHINE</EMPH></PTXT><PTXT>PROD NO DD00A001 EC210</PTXT></PARA><PARA><PTXT><EMPH ETYPE="BOLD">ENGINE</EMPH></PTXT><PTXT>Part No. 1111-00013 Typ, B 5,9 - C</PTXT><PTXT>Part No. 1111-00313 Typ, B 5,9 - C for tropics</PTXT></PARA><PARA><PTXT><EMPH ETYPE="BOLD">BUCKETS</EMPH></PTXT><PTXT>Bucket GP. ESCO. 0,86/0,95 - F24</PTXT><PTXT>Description:</PTXT></PARA><TABLE FRAME="NONE"><?Pub Dtl><TGROUP COLS="3" COLSEP="0" ROWSEP="0" ALIGN="LEFT" CHAROFF="50" CHAR=""><COLSPEC COLNUM="1" COLNAME="SQCOLUMN1" COLWIDTH="0.88in"><COLSPEC COLNUM="2" COLNAME="SQCOLUMN2" COLWIDTH="0.40in"><COLSPEC COLNUM="3" COLNAME="COL3" COLWIDTH="4.21in" COLSEP="0"><TBODY VALIGN="TOP"><ROW><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>GP</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT"><PTXT>=</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>General purpose. (RB)= Rock bucket.</PTXT></ENTRY></ROW><ROW><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>ESCO</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT"><PTXT>=</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>Type of bucket tooth, Esco.</PTXT></ENTRY></ROW><ROW><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>0,86</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT"><PTXT>=</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>Volume CECE cubic meter.</PTXT></ENTRY></ROW><ROW><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>0,95</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT"><PTXT>=</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>Volume SAE cubic meter.</PTXT></ENTRY></ROW><ROW><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>S1</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT"><PTXT>=</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>Quick fit bucket.</PTXT></ENTRY></ROW><ROW><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>F24</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT"><PTXT>=</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>Direct-mounted (pin-on) bucket.</PTXT></ENTRY></ROW></TBODY></TGROUP></TABLE><PARA><PTXT><EMPH ETYPE="BOLD">TRACK ASSEMBLY</EMPH></PTXT><PTXT>Track TRK 600SR X 49</PTXT><PTXT>Description:</PTXT></PARA><TABLE FRAME="NONE"><?Pub Dtl><TGROUP COLS="3" COLSEP="0" ROWSEP="0" ALIGN="LEFT" CHAROFF="50" CHAR=""><COLSPEC COLNUM="1" COLNAME="SQCOLUMN1" COLWIDTH="0.88in"><COLSPEC COLNUM="2" COLNAME="SQCOLUMN2" COLWIDTH="0.40in"><COLSPEC COLNUM="3" COLNAME="COL3" COLWIDTH="4.21in" COLSEP="0"><TBODY VALIGN="TOP"><ROW><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>TRK</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT"><PTXT>=</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT> Track</PTXT></ENTRY></ROW><ROW><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>600</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT"><PTXT>=</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>Width of track</PTXT></ENTRY></ROW><ROW><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>S</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT"><PTXT>=</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>Symmetrical track</PTXT></ENTRY></ROW><ROW><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>R</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT"><PTXT>=</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>Clearing hole</PTXT></ENTRY></ROW><ROW><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>49</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT"><PTXT>=</PTXT></ENTRY><ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT"><PTXT>Number of track shoes</PTXT></ENTRY></ROW></TBODY></TGROUP></TABLE></SERVINFO></INTRO-PARTINFO></SERVINFOTYPE></PRODUCT-SPECIFIC></VCESI>


Here is a version 4.0 of a different file, for which they use XML now:

<?xml version='1.0' ?><?xml-stylesheet href='..\..\..\stylesheet\vcesi03.xsl' type='text/xsl'?><!DOCTYPE vcesi [ <!NOTATION TIFF SYSTEM ''><!NOTATION CGM SYSTEM ''><!NOTATION BMP SYSTEM ''><!NOTATION WMF SYSTEM ''><!NOTATION GIF SYSTEM ''><!NOTATION JPG SYSTEM ''><!NOTATION PNG SYSTEM ''><!NOTATION SGML SYSTEM ''><!NOTATION XML SYSTEM ''>]><vcesi><product-specific><servcatype servcatnbr=''><title></title><servcat2 servcatnbr='' servcatcomp='VCE'><title></title><servcat3 servcatnbr='' servcatcomp='VCE'><title></title><servinfotype><intro-partinfo><servinfo><title>Foreword</title><subtitle>This catalogue lists the spare parts for attachments for
construction equipment, bearing the name Volvo and Volvo BM/Michigan
with the following designations:</subtitle><para><ptxt><emph>WHEEL LOADERS: Volvo BM / Michigan</emph></ptxt><ptxt>L30</ptxt><ptxt>L50, L50B</ptxt><ptxt>L70, L70B</ptxt><ptxt>L90, L90B</ptxt><ptxt>L120, L120B</ptxt><ptxt>L150</ptxt><ptxt>L160</ptxt><ptxt>L180</ptxt></para><para><ptxt><emph>WHEEL LOADERS: Volvo / Volvo BM</emph></ptxt><ptxt>L50C, L50D</ptxt><ptxt>L60E</ptxt><ptxt>L70C, L70D, L70E</ptxt><ptxt>L90C, L90D, L90E</ptxt><ptxt>L110E</ptxt><ptxt>L120C, L120D, L120E</ptxt><ptxt>L150C, L150D, L150E</ptxt><ptxt> L180C, L180D, L180E</ptxt><ptxt>L220D, L220E</ptxt></para><para><ptxt><emph>EXCAVATOR LOADERS: Volvo BM</emph></ptxt><ptxt>EL70, EL70C</ptxt></para></servinfo></intro-partinfo></servinfotype></servcat3></servcat2></servcatype></product-specific></vcesi>



Both files are part of an interactive parts catalog; I don't see any descriptions of an XML Xchema, nor is there any descriptions of the XML files it looks for. Thx, RaduGB
 
Upvote 0 Downvote
Well, by eliminating the improperly terminated processing instructions (start with <?) and by self terminating the COLSPEC elements, I get a well-formed XML document as follows.
Code: 
<VCESI lang="GB">
	<PRODUCT-SPECIFIC>
		<SERVINFOTYPE>
			<INTRO-PARTINFO>
				<SERVINFO>
					<TITLE>Preface</TITLE>
					<SUBTITLE>EXCAVATOR VOLVO EC210</SUBTITLE>
					<PARA>
						<PTXT>
							<EMPH ETYPE="BOLD">BASIC MACHINE</EMPH>
						</PTXT>
						<PTXT>PROD NO DD00A001 EC210</PTXT>
					</PARA>
					<PARA>
						<PTXT>
							<EMPH ETYPE="BOLD">ENGINE</EMPH>
						</PTXT>
						<PTXT>Part No. 1111-00013 Typ, B 5,9 - C</PTXT>
						<PTXT>Part No. 1111-00313 Typ, B 5,9 - C for tropics</PTXT>
					</PARA>
					<PARA>
						<PTXT>
							<EMPH ETYPE="BOLD">BUCKETS</EMPH>
						</PTXT>
						<PTXT>Bucket GP. ESCO. 0,86/0,95 - F24</PTXT>
						<PTXT>Description:</PTXT>
					</PARA>
					<TABLE FRAME="NONE">
						<TGROUP COLS="3" COLSEP="0" ROWSEP="0" ALIGN="LEFT" CHAROFF="50" CHAR="">
							<COLSPEC COLNUM="1" COLNAME="SQCOLUMN1" COLWIDTH="0.88in"/>
							<COLSPEC COLNUM="2" COLNAME="SQCOLUMN2" COLWIDTH="0.40in"/>
							<COLSPEC COLNUM="3" COLNAME="COL3" COLWIDTH="4.21in" COLSEP="0"/>
							<TBODY VALIGN="TOP">
								<ROW>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>GP</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT">
										<PTXT>=</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>General purpose. (RB)= Rock bucket.</PTXT>
									</ENTRY>
								</ROW>
								<ROW>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>ESCO</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT">
										<PTXT>=</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>Type of bucket tooth, Esco.</PTXT>
									</ENTRY>
								</ROW>
								<ROW>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>0,86</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT">
										<PTXT>=</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>Volume CECE cubic meter.</PTXT>
									</ENTRY>
								</ROW>
								<ROW>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>0,95</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT">
										<PTXT>=</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>Volume SAE cubic meter.</PTXT>
									</ENTRY>
								</ROW>
								<ROW>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>S1</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT">
										<PTXT>=</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>Quick fit bucket.</PTXT>
									</ENTRY>
								</ROW>
								<ROW>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>F24</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT">
										<PTXT>=</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>Direct-mounted (pin-on) bucket.</PTXT>
									</ENTRY>
								</ROW>
							</TBODY>
						</TGROUP>
					</TABLE>
					<PARA>
						<PTXT>
							<EMPH ETYPE="BOLD">TRACK ASSEMBLY</EMPH>
						</PTXT>
						<PTXT>Track TRK 600SR X 49</PTXT>
						<PTXT>Description:</PTXT>
					</PARA>
					<TABLE FRAME="NONE">
						<TGROUP COLS="3" COLSEP="0" ROWSEP="0" ALIGN="LEFT" CHAROFF="50" CHAR="">
							<COLSPEC COLNUM="1" COLNAME="SQCOLUMN1" COLWIDTH="0.88in"/>
							<COLSPEC COLNUM="2" COLNAME="SQCOLUMN2" COLWIDTH="0.40in"/>
							<COLSPEC COLNUM="3" COLNAME="COL3" COLWIDTH="4.21in" COLSEP="0"/>
							<TBODY VALIGN="TOP">
								<ROW>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>TRK</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT">
										<PTXT>=</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>Track</PTXT>
									</ENTRY>
								</ROW>
								<ROW>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>600</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT">
										<PTXT>=</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>Width of track</PTXT>
									</ENTRY>
								</ROW>
								<ROW>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>S</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT">
										<PTXT>=</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>Symmetrical track</PTXT>
									</ENTRY>
								</ROW>
								<ROW>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>R</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT">
										<PTXT>=</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>Clearing hole</PTXT>
									</ENTRY>
								</ROW>
								<ROW>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>49</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="RIGHT">
										<PTXT>=</PTXT>
									</ENTRY>
									<ENTRY MOREROWS="0" ROTATE="0" VALIGN="TOP" ALIGN="LEFT">
										<PTXT>Number of track shoes</PTXT>
									</ENTRY>
								</ROW>
							</TBODY>
						</TGROUP>
					</TABLE>
				</SERVINFO>
			</INTRO-PARTINFO>
		</SERVINFOTYPE>
	</PRODUCT-SPECIFIC>
</VCESI>

It would seem a straightforward programming situation to preprocess the SGML documents to create well-formed XML, then apply an XSLT stylesheet to the well-formed XML version of the SGML to arrive at the new XML version.

There exist GUI tools for creating the XSLT stylesheet, of which my favorite is Stylus Studio (available on a trial basis on the web). Another would be the Altova toolset.

Tom Morrison
 
Upvote 0 Downvote
You've lost me somewhat..I know of XML, but not how to preprocess it into an SGML document, nor do I know anything of XSLT stylesheets. Radug
 
Upvote 0 Downvote
Download sp of J Clark.
In particular, look into sx.exe utility. A rudimentary command line would be something like this adding some switch to draw your attention to some more capability.
[tt]sx.exe -butf-8 -ferrfile.txt orgfile.sgml>translatedfile.xml[/tt]
 
Upvote 0 Downvote
So tsuji has shown how to get your SGML to XML.

You now need to have a look at XSLT. XSLT is a 'language' for describing the transformation of an input XML document (such as would be produced by SX) into another XML document (i.e. the desired new XML document format illustrated in your original post). For this there are GUI tools, as I mentioned above. There is an XSLT tutorial here.

Once you have the XSLT then you will be able to transform your 21000 documents programatically. Perhaps you could share what computing environment you intend to use for this conversion, as that will dictate somewhat the XML processor that will be used for the second step.

Tom Morrison
 
Upvote 0 Downvote
Each time I put that command line into sx.exe, it tells me "character "-" not allowed in prolog
 
Upvote 0 Downvote
Probably complaining about the following. You need to experiment a bit...
Code: 
<!DOCTYPE VCESI PUBLIC "[COLOR=red][b]-[/b][/color]//Volvo Constru

Tom Morrison
 
Upvote 0 Downvote
>Each time I put that command line into sx.exe, it tells me "character "-" not allowed in prolog.
If I use the sample sgml and "put that command line into sx.exe", whatever it means, it generates quite a bit of warnings and errors, basically related to the unavailability of the DTC for sx to use, and produces a decent translated xml source. But not one error mentions the cited message in the error file. So how comes "each time"?
 
Upvote 0 Downvote
Nope still gives me this message everytime, and I changed all the "-"'s in the file to "_"'s. C:\Documents and Settings\Radu\Desktop\bin\sx.exe:<OSFD>0:1:0:E: character "-" not allowed in prolog
 
Upvote 0 Downvote
As you continue to show irrelevant data, go to your IT-guy and/or vendor to ask for advice. We are no voyeur.
 
Upvote 0 Downvote
I dont think its anything in the file. I think I am typing the command line in wrong in sx.exe.

I put in "-butf-8 -ferrfile.txt VCESI03.sgm>VCESI03.xml" and first it will give me the message:

C:\Documents and Settings\Radu\Desktop\bin\sx.exe:<OSFD>0:1:0:E: character "-" not allowed in prolog

So I took the first "-" out of the command line and got this:

C:\Documents and Settings\Radu\Desktop\bin\sx.exe:<OSFD>0:1:0:E: character "b" not allowed in prolog

I then took out the "b" and it told me: C:\Documents and Settings\Radu\Desktop\bin\sx.exe:<OSFD>0:1:0:E: character "u" not allowed in prolog

It did this all the way down the line til there was nothing left in the command line. Maybe I'm giving it a bad command or something?
 
Upvote 0 Downvote
OK - this is probably me putting in the wrong command line. What is the EXACT command line I need to enter after I open sx.exe. No matter what I type in it still tells me that whatever character, NOT CONTENT, it not allowed in prolog. Thx, RaduG
 
Upvote 0 Downvote
[tt]"C:\Documents and Settings\Radu\Desktop\bin\sx.exe" -butf-8 -ferrfile.txt VCESI03.sgm>VCESI03.xml[/tt]
 
Upvote 0 Downvote
OK - finally got it to convert. Here's what the error file is telling me. Thx, RaduG

sx.exe:V56117001.sgm:1:71:E: invalid formal public identifier "//Volvo Construction Equipment//DTD VCESI03//EN": invalid public text class
sx.exe:V56117001.sgm:1:72:W: cannot generate system identifier for public text "//Volvo Construction Equipment//DTD VCESI03//EN"
sx.exe:V56117001.sgm:2:0:E: reference to entity "VCESI" for which no system identifier could be generated
sx.exe:V56117001.sgm:1:0: entity was defined here
sx.exe:V56117001.sgm:2:0:E: DTD did not contain element declaration for document type name
sx.exe:V56117001.sgm:3:12:E: there is no attribute "LANG"
sx.exe:V56117001.sgm:3:16:E: element "VCESI" undefined
sx.exe:V56117001.sgm:3:25:E: character "_" not allowed in attribute specification list
sx.exe:V56117001.sgm:3:25:E: element "PRODUCT" undefined
sx.exe:V56117001.sgm:3:48:E: element "SERVINFOTYPE" undefined
sx.exe:V56117001.sgm:3:55:E: character "_" not allowed in attribute specification list
sx.exe:V56117001.sgm:3:55:E: element "INTRO" undefined
sx.exe:V56117001.sgm:3:73:E: element "SERVINFO" undefined
sx.exe:V56117001.sgm:3:92:E: element "TITLE" undefined
sx.exe:V56117001.sgm:3:114:E: element "PARA" undefined
sx.exe:V56117001.sgm:3:120:E: element "PTXT" undefined
sx.exe:V56117001.sgm:3:153:E: general entity "ldquo" not defined and no default entity
sx.exe:V56117001.sgm:3:170:E: general entity "rdquo" not defined and no default entity
sx.exe:V56117001.sgm:8:75:E: element "PARA" undefined
sx.exe:V56117001.sgm:8:81:E: element "PTXT" undefined
sx.exe:V56117001.sgm:9:84:E: element "PARA" undefined
sx.exe:V56117001.sgm:9:90:E: element "PTXT" undefined
sx.exe:V56117001.sgm:9:183:E: element "PARA" undefined
sx.exe:V56117001.sgm:9:189:E: element "PTXT" undefined
sx.exe:V56117001.sgm:11:45:E: character "_" not allowed in end tag
sx.exe:V56117001.sgm:11:78:E: character "_" not allowed in end tag
 
Upvote 0 Downvote
You spend 4 posts monologing an error without showing one complete of command line. How about now show the forum what was the wrong command line?
 
Upvote 0 Downvote
Absolutley nothing wrong with the command line...the problem was with me. I was trying to input the command line directly into sx.exe, and not running it through MS-DOS command prompt. In tote, it was me all along. RaduG
 
Upvote 0 Downvote
Any of y'all still willing to help me?
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

smak1
  • Locked
  • Question
add structure to XML
Replies
0
Views
690
smak1
smak1
Bijan Borazjani
  • Locked
  • Question
XML to PDF
Replies
0
Views
786
Bijan Borazjani
Bijan Borazjani
cdr_greg
  • Locked
  • Question
Display XML Line Breaks in Microsoft Word Content Controls
Replies
0
Views
1K
cdr_greg
cdr_greg
P
  • Locked
  • Question
How to re-use a recursive template
Replies
1
Views
775
pdrapeau
P
198709km
  • Locked
  • Question
Grouping XML key value using XSLT
Replies
1
Views
742
atlopes
atlopes

Part and Inventory Search

Sponsor

Back
Top