Any thought to storing links to the docs in a db rather than the data
itself, maybe with some keywords you can search on?



Joel

Headline- Apathy Runs Rampant; But Noone Seems to Care

> -----Original Message-----
> From: Timothy Johnson [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 19, 2002 1:27 PM
> To: 'Kevin Old'; [EMAIL PROTECTED]
> Subject: RE: Storing Newsletter in Database
> 
> 
> 
> I think the last time I tried to make a webpage with 
> Publisher it made the
> whole document into a picture background with links on top.  
> That might put
> a dent in your plan if that's still the way it's set up.
> 
> -----Original Message-----
> From: Kevin Old [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 19, 2002 1:11 PM
> To: [EMAIL PROTECTED]
> Subject: Storing Newsletter in Database
> 
> 
> Hello all,
> 
> I have a challenge that has been put on me.  I have built a 
> website for my
> church and we are now wanting to put our newsletter online.  
> It is currently
> being done in Microsoft Publisher.
> 
> I would like to take the MS Publisher file and extract the 
> data and insert
> it into a database (PostgreSQL) and then display it via 
> PHP/Perl.  Catch is,
> the data is not that consistent.
> 
> The only thing I can think of is to have MS Publisher save it 
> as HTML, and
> then go through and parse everything and get it put in the 
> database.  I know
> that would still involve some kind of consistency with the 
> data.  If there
> was a way for me to apply an XML DTD to the HTML, that would 
> automate the
> process more.
> 
> On the other hand, I could just have the entire newsletter 
> HTML dumped in
> the database and then have it displayed like that (modifying 
> the HTML of
> course).  But that defeats the entire purpose of "automating" data.
> 
> Any ideas on how this can be done, even if I don't have 
> consistency in the
> data?
> 
> Any help is appreciated,
> Kevin
> 
> 
> 
> -- 
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> --------------------------------------------------------------
> ------------------
> This email may contain confidential and privileged 
> material for the sole use of the intended recipient. 
> If you are not the intended recipient, please contact 
> the sender and delete all copies.
> 
> -- 
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to