[skreutzer]

Originally Posted by SBT

What about TEI? Popular, loads of tools, XSLT for EPUB Conversion?

Yes, TEI is fine for automated processing workflows, but neither is TEI an input format (I never received TEI from anybody, also word processors don't support it as output format), nor an output format (no TEI readers). But TEI could be used as intermediate format, so I'll certainly look into the TEI processing tools. It might save the time to implement PDF and EPUB generators, and if TEI tools can be integrated into an automated workflow which is easy to set up and to use, I guess it could be quite advantageous.

Originally Posted by Arios

So my request is just to asking you to point out shortly the main elements of your project.

1. Background: C/C++, Java, Web (PHP, JavaScript) and other stuff.
2. I plan to license exclusively under free software licenses (GNU AGPL3 or later for software, CC BY-SA 4 for non-software which I write initially, usage of and contributions to FSF-approved free software licenses.
3. The main goal of my project is to develop an automated digital publishing workflow, mostly based on XML processing. It is intended to eliminate the current practice of setting type by hand in the digital age, which is caused by direct formatting for each desired output format.
4. I haven't submitted my project here on mobileread, but requested some hints in the forum regarding tools which can be used for such a workflow. I started to generalize the methods of my Bible digitalization and reproduction project 1 2 3, with some results published in my public personal git repository.

Note: as mentioned, this freely licensed software can also be used (with no or little adjustments) in non-free, proprietary environments (which is part of the digital freedoms a user deserves), while it could be hard or even impossible to integrate non-free, proprietary tools into the free workflow or free environment, if it doesn't at least support some open formats, protocols, etc.

Originally Posted by Tex2002ans

While looking through some articles, I stumbled upon these two, which I thought might be of interest in the case of automating book workflows.

Thank you very much, I'll read them and maybe comment. There's a lot going on in the field of digital publishing, so I'm glad that you've pointed me to those articles, which I otherwise certainly would have missed.



In the meantime I've started a little Java GUI programming, so there's now a metadata editor for the configuration file of my EPUB generator. I plan to add another GUI helper for the configuration file, so that the entire EPUB conversion can be managed not only by an automated processing workflow, but also by ordinary users. I would like to set up a basic processing workflow, both usable automatically and by GUI, so that real texts can be processed with it.

I found out that OpenOffice/LibreOffice can be configured in a way that semantic markup can be applied quite conventiently. Further, I'm involved in automatically processing output generated by a tool which reads a Wiki software, so Wikis as online front-ends seem to be pretty convenient, probably semantic, text editors for special kinds of writing activity.

I also found a freely licensed automated processing workflow called Booktype, which I will investigate as well as the TEI processing tools. Probably it is easier than expected to provide an freely licensed automated processing workflow, by just combining what's already there to some kind of a "single installer", and by making easy to use for everybody (both ordinary users as well as professional formatters/typesetters). And sorry, no new River Valley TV video link, my progress is too slow and the videos are too interesting for me personally, even when not directly related to the topic of automated digital publishing.