On 01/13/2015 08:59 PM, Idris Samawi Hamid ادريس سماوي حامد wrote:
Dear gang,
I'm currently writing a paper with very basic typographical needs: blockquotes, emphasis, bibliography, perhaps a graphic or two. The publisher wants the thing in Word, naturally. The last time I did something like this I set up a markdown document and just exported it to both docx and to context. For simple documents this is at least workable, but I'd prefer to write in context, not markdown.
Hi Idris, I think it is better to use a markdown source with pandoc. It is the closest model to its native format. I have written a small book from a markdown source. The PDF document was generated by ConTeXt, previously converted with pandoc. I think this is the wrong way to go. Mainly because conversion to ConTeXt doesn’t rettain language information and special attributes. I had to edit the ConTeXt source to add the missing features. [pandoc’s internal document format only allows attributes for certain elements, not for all of them. A workaround is to wrap then in divs an spans.] In my opinion, the right way to go is to convert the markdown source to HTML and to parse it with an environment. Otherwise, updating the source is not straightforward (either you have two sources: markdown and ConTeXt). Why do you prefer to avoid markdown as a source document format?
Now it's been a while since I've experimented with ConTeXt and epub. From lightly perusing the list it seems that there has been considerable movement on this front. So my question: Has anyone here succeeded in the following workflow:
context -> xml -> docx
[perhaps via pandoc]?
I don’t have any samples of this workflow, since I never worked this way. pandoc doesn’t even have a ConTeXt reader (https://github.com/jgm/pandoc/issues/1423). You will need a way to generate a document in an XML format that pandoc understands. XHTML is an option. And I guess that would be easy to generate with ConTeXt (I have never done it). Just in case it helps, Pablo -- http://www.ousia.tk