<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>RE: [Westernmontana-pm] Welcome</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I work at a hospital. Soon, I'm to be working with XML in a medical setting - translating messages from HL7 to XML, and working with Mirth Channel exports to assist in automatic listener setup for feeds to a Xapian search engine. Whenever I work with XML, my first choice is to try out XML::Twig for my application, and if that fails, use search.cpan.org to find the most recent release of whatever module I want.<BR>
<BR>
As I get into this project more, I'll work at being more proactive on communication of it.<BR>
<BR>
Jack Downes<BR>
Health Information Technology, KRMC<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: westernmontana-pm-bounces+jdownes=krmc.org@pm.org on behalf of Jon Pielaet<BR>
Sent: Sat 4/30/2011 8:22 PM<BR>
To: westernmontana-pm@pm.org<BR>
Subject: Re: [Westernmontana-pm] Welcome<BR>
<BR>
-- NOTICE --<BR>
<BR>
The following message is part of the Western Montana Perl Mongers group Mail list. When you hit 'REPLY', the e-mail message that you compose and then 'SEND' shall be sent to EVERYONE on the list. NOTHING is private.<BR>
<BR>
Un-subscribe information is located at the end of this message.<BR>
<BR>
-- NOTICE --<BR>
<BR>
<BR>
Sure Tomas,<BR>
<BR>
Well, I am responsible for all of the alternatively formatted<BR>
materials at Disability Services for Students at the University of<BR>
Montana.<BR>
<BR>
For the most part, this means producing DAISY Digital Talking Books<BR>
(DTBook XML is at the core of that standard) but we also emboss some<BR>
Braille from time to time.<BR>
<BR>
Right now, we convert paper books to UTF-8 text using production<BR>
scanners and OCR software then, student employees mark-up that text in<BR>
Microsoft Word and export it to DTBook XML using an Open Source<BR>
Plug-in. I would love to get rid of Word but teaching students the<BR>
inner working of this XML is not really realistic for the most part.<BR>
<BR>
I am basically the only one who ever looks at the XML, and there are<BR>
common fixes that I would like to automate.<BR>
<BR>
Perl seems like a good choice for this task. I am just starting to<BR>
learn the basics of Perl, but I have been using Unix\Linux for years.<BR>
More recently, I begun studying extended RegEx. In fact, that is what<BR>
has attracted me to Perl. I already have some useful expressions<BR>
written for egrep, sed, and awk, so scripting in Perl seems like the<BR>
next logical step.<BR>
<BR>
I am working my way through "The Llama" (Learning Perl - O'Reilly) right now.<BR>
<BR>
If anyone has any tips for working with XML in Perl, I would love to hear them.<BR>
<BR>
I like to talk about what I do, so let me know if you have questions.<BR>
<BR>
Thanks,<BR>
<BR>
Jon Pielaet<BR>
KD7SWH<BR>
_______________________________________________<BR>
Westernmontana-pm mailing list<BR>
Westernmontana-pm@pm.org<BR>
<A HREF="http://mail.pm.org/mailman/listinfo/westernmontana-pm">http://mail.pm.org/mailman/listinfo/westernmontana-pm</A><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>