View Single Post
Old 01-30-2014, 12:03 PM   #7
skreutzer
Software Developer
skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.
 
skreutzer's Avatar
 
Posts: 190
Karma: 89000
Join Date: Jan 2014
Location: Germany
Device: PocketBook Touch Lux 3
You are right, nobody writes a book directly in XML. However, no processing workflow will be based on AsciiDoc. So the way to go is to convert AsciiDoc format to XML or XHTML in order to feed the text (retaining its semantic markup) into the automated processing workflow. I'm perfectly fine with it, and as AsciiDoc provides (hopefully well-formed) XML and (hopefully valid) XHTML out of the box, it could be quite usable as front end for semantic writing, especially because it is a valuable goal to encourage semantic markup instead of direct formatting right from the beginning. As AsciiDoc is free software, I might look into supporting it as front end. Do you use AsciiDoc or do you know somebody who writes files in AsciiDoc and wants automated output creation?
skreutzer is offline   Reply With Quote