[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: "Smart ASCII" -> XML for authoring?

• To: <xml-dev@l...>
• Subject: RE: "Smart ASCII" -> XML for authoring?
• From: "Paul Brown" <prb@f...>
• Date: Sun, 3 Feb 2002 20:47:36 -0600
• Cc: "Mike Champion" <mc@x...>
• Importance: Normal
• In-reply-to: <PLYXVRWRE0GECBRO3VQM8273GCPNMGSP.3c5c2bc3@MChamp>
• Reply-to: <prb@f...>

> From: Mike Champion
> I'd be interested in hearing others' reactions to this IBM
> DeveloperWorks article and about actual experiences in the field.

Deja vu for me.  About two years ago, we built a text-to-XML converter for a
medical transcription company that uses implicit markup and some (very cool
IMHO) lexicon-driven technology to convert around 25,000 documents per day
from text in a proprietary word processor format (DOS Medrite, for those who
may be familiar) to XML and back.  The XML->text portion includes fancy
formatting that used to waste lots or transcriptionist time, so this was a
big operational win for the transcription provider.

The current incaration of the parser is Java with a SAX back-end (it
implements XMLReader), runs very fast, and generates fewer than 10
exceptions (i.e., documents with indecipherable markup) on an average day.
As an odd parallel to the developerWorks article, the original
proof-of-concept parser (implemented around 3 years ago...) was in Python.

	-- Paul

• References:
  • "Smart ASCII" -> XML for authoring?
    • From: Mike Champion <mc@x...>

• Prev by Date: Re: Architectural Forms: A New Generation (draft 2.1)
• Next by Date: Re: misprocessing namespaces (was Re: There is a meaning, but it's not in the data alone)
• Previous by thread: Re: "Smart ASCII" -> XML for authoring?
• Next by thread: Re: "Smart ASCII" -> XML for authoring?
• Index(es):
  • Date
  • Thread