Jeremy, the tool I'm playing with converts a directory of RTF files into clean HTML, but then performs a second step of parsing each file into a format that can be pulled into a SQL database -- hence the CSV format for the lowest common denominator DB format...
Yes, you can cut and paste HTML into Wordpress pretty easily. One file at a time. You have several hundred or thousand to do, it could be a little wearing... Art Campbell ? ? ? ? ? ? ? art.campbell at gmail.com ? "... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl." -- Richard Thompson ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? No disclaimers apply. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? DoD 358 I support www.TheGrotonLine.com, hyperlocal news for Groton MA. On Thu, Jul 14, 2011 at 3:21 PM, Jeremy H. Griffith <jeremy at omsys.com> wrote: > On Thu, 14 Jul 2011 10:23:18 -0400, Art Campbell <art.campbell at gmail.com> > wrote: > >>The workflow seems to be (unstructured): >> >>1. From Frame, SaveAs (I'm using MIF2Go) as RTF. >>2. Batch-convert the RTF to clean HTML or XHTML. > > That doesn't make sense to me. ?Why have Mif2Go make > RTF, with very different requirements than HTML, and > then use something else to make the clean HTML/XHTML > you can have Mif2Go make in the first place? > > I hope the intermediate step isn't using Word, which > produces horrible HTML. ?But Word is what our RTF is > tuned for... > >>3. Save/export into a comma-separated value (CSV) file. >>4. Import the CSV into WordPress, assigning tags, categories, post >>types and other bits and pieces on import. > > WordPress doesn't import HTML? ?CSV is a very old and > limited format... ?Does WordPress use it internally, > or does it use its own XML format, as I'd expect? > > -- Jeremy H. Griffith, at Omni Systems Inc. > ?<jeremy at omsys.com> ?http://www.omsys.com/ >
