I'd like to see someone consider using one of the many UI frameworks available these days rather than coming up with another - I guess to try to avoid another guiguts situation. One-man software tools have such obvious shortcomings no matter what their technical merit. The first that comes to my mind is Eclipse but there are dozens of others in the general category.. The CMS packages (django, wordpress, joomla, etc.) have a lot of what's needed and are variously easy to adapt. Epubmaker could be plugged in. But so much of this has already been done that it's likely we can avoid reinventing some major wheels. On Sun, Feb 5, 2012 at 11:23 AM, <hmonroe.pglaf@huntermonroe.com> wrote:
Sorry to repeat myself but you can get the RST and PGTEI tools sets (Epubmaker and Gnutenberg Press) installed easily on Windows systems as bundled with guiguts-win here http://sourceforge.net/projects/guiguts/files/guiguts/.
There are many interesting development opportunities here: fleshing out a GUI interface to these tools, making it easier for users to generate Epub friendly HTML while provideing warnings when they have not, tweaking the code used to create HTML so it creates PGTEI. Contact me with a sourceforge ID and I can add you as a developer. On the last idea, the first step would be to modify lib\Guiguts\HTMLConvert.pm to replace a line like
[code]$textwindow->ntinsert( "$step.0", '<h1>' );[/code]
with
[code]$textwindow->ntinsert( "$step.0", $chapterheader);[/code]
then create a file html.rc with lines like
[code]$chapterheader='<h1>';[/code]
which gets read in at the start of htmlautoconvert(). Then you create pgtei.rc
[code]$chapterheader='<header>';[/code]
You would then have a routine to produce TEI that is already far better than the one on the dp web site. A minor change to another routine (is_paragraph_open) could ensure that the <div> for the previous chapter is closed.
Hunter _______________________________________________ gutvol-d mailing list gutvol-d@lists.pglaf.org http://lists.pglaf.org/mailman/listinfo/gutvol-d