From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: creating a printed book
Date: Sun, 13 Oct 2024 15:50:10 +0200 [thread overview]
Message-ID: <1243e11c-2f10-4f27-bd5b-1b739a04fcab@fiee.net> (raw)
In-Reply-To: <37e3786c-683f-4b20-bc30-e6a483f256b5@freedom.nl>
Am 12.10.24 um 19:59 schrieb Hans Hagen via ntg-context:
> On 10/11/2024 10:16 PM, Hraban Ramm wrote:
>> Am 11.10.24 um 18:19 schrieb David Roderick:
>>> I have created 22 MSword files mainly text with embedded PNG
>>> diagrams. I am seeking to have these converted to Context and to
>>> redo the (simple) diagrams. I was thinking of using MetaPost. I am
>>> seeking to pay a typesetter to assist me in this task. I would be
>>> willing to pay for your time or for the time of a colleague you could
>>> direct me to. I am seeking to have typeset a book. The MSWord files
>>> have already been professionally proof-read, and the subject matter
>>> is political economy from the 18th century and how this translates to
>>> and may contradict conventional wisdom within the field of modern
>>> economics.
>>>
>>> Other typesetters I have contacted have suggested running pandoc to
>>> create a LaTeX file and use Tikz for the diagrams. But I have spent
>>> 3 days reading on advancements in the ConText side of the industry
>>> which I suspect is far more advanced. I would prefer to use better
>>> tools as a longer term solution. Can you advise me?
>>
>> Hi David,
>>
>> I would take your order, but you can also try it yourself with my tools:
>> https://codeberg.org/fiee/context-tools/src/branch/master/docx2ctx
>>
>> Pandoc can also generate ConTeXt code; try which you like better.
>
> I'd never go that route when, as mentioned, a high quality document is
> needed which can involve control (for which one can e.g. use instances
> for specific components). Coding in TeX speak is not that bad. Also, one
> is more likely to get answers for specific problems on the list.
I don’t suggest using DOC(X) to directly create PDF via Pandoc and
ConTeXt, just converting DOC(X) to ConTeXt for further processing.
The direct approach works only with simple and/or very consistently
styled documents.
For my youth novel, I’m writing in LibreOffice, convert ODS to DOCX,
convert that to ConTeXt with my script and finalize the code with an
additional script, so that it doesn’t need further tweaking. This works
only because I control the source and the converter.
My script is not trying to keep the layout, just the structure and some
formatting.
It can extract embedded images (again, since I fixed the bug) and
creates an \externalfigure, but that usually isn’t enough. Similar
situation with embedded tables (the conversion is not good, I’ll
probably enhance it a bit as soon as I need it).
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-10-13 14:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 16:19 [NTG-context] " David Roderick
2024-10-11 20:16 ` [NTG-context] " Hraban Ramm
2024-10-12 17:59 ` Hans Hagen via ntg-context
2024-10-13 12:19 ` angel.of.north
2024-10-13 22:25 ` Hans Hagen via ntg-context
2024-10-13 13:50 ` Henning Hraban Ramm [this message]
2024-10-12 22:32 ` angel.of.north
2024-10-13 13:37 ` Henning Hraban Ramm
2024-10-14 11:12 ` David Roderick
2024-10-14 16:00 ` Henning Hraban Ramm
2024-10-14 16:17 ` Wolfgang Schuster
2024-10-14 19:19 ` David Roderick
2024-10-14 19:32 ` Denis Maier via ntg-context
2024-10-14 19:19 ` Henning Hraban Ramm
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=1243e11c-2f10-4f27-bd5b-1b739a04fcab@fiee.net \
--to=texml@fiee.net \
--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).