ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: context -> docx ??
Date: Wed, 14 Jan 2015 20:58:11 +0100	[thread overview]
Message-ID: <54B6CA53.50509@gmx.es> (raw)
In-Reply-To: <op.xse25m0pfkrasx@ishamid-pc>

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
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2015-01-14 19:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 19:59 Idris Samawi Hamid ادريس سماوي حامد
2015-01-13 21:34 ` Marcin Borkowski
2015-01-14 17:55   ` Alan BRASLAU
2015-01-14 18:58     ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-14 19:58       ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-14 20:03         ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-14 20:15     ` Pablo Rodriguez
2015-01-14 20:29       ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-14 21:25         ` Peter Münster
2015-01-14 21:38         ` Aditya Mahajan
2015-01-14 22:11           ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-14 21:59         ` Pablo Rodriguez
2015-01-14 22:22           ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-15  8:01             ` Alan BRASLAU
2015-01-15 14:43               ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-15 16:03                 ` Wolfgang Schuster
2015-01-14 20:50     ` Marcin Borkowski
2015-01-14 18:44   ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-14 19:58 ` Pablo Rodriguez [this message]
2015-01-17 14:45   ` Idris Samawi Hamid ادريس سماوي حامد
2015-01-17 20:32     ` Pablo Rodriguez
2015-01-17 21:06       ` Idris Samawi Hamid ادريس   سماوي حامد
2015-01-20 17:46         ` Pablo Rodriguez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54B6CA53.50509@gmx.es \
    --to=oinos@gmx.es \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).