From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: using modeset
Date: Mon, 15 Jun 2020 20:23:14 +0200 [thread overview]
Message-ID: <35CEE372-48A6-4EA0-BCF6-310349688EEC@fiee.net> (raw)
In-Reply-To: <2DC545CA-C12B-4C1F-B8B2-C7022C32F114@hxcore.ol>
> Am 12.06.2020 um 11:26 schrieb Jan Willem Flamma <register12c@gmail.com>:
>
> Thank you Wolfgang, BPJ and Robert for your answers and feedback. Much appreciated.
>
> I will explorer the solutions that have been offered to extend my knowledge on using ConTeXt but at the same time I value the advice of not going down that route for large document.
The project that pays my bills is technical documentation in several languages (in LaTeX3, setup by Marei). Each manual is constructed from many small building blocks of text. Each block is in its own file.
That makes editing one whole manual somewhat tedious, but pays off if you recycle the same blocks. E.g. each block is only translated once, even if it appears in several manuals (think of security instructions or legal stuff that is the same in all). Each block has an explicite change date to keep track of the state of the different translations.
The two main files of each product are one that contains just a few settings and one that pulls in all the needed building blocks.
In this case all blocks with the same content in different languages are kept together in one directory (files have a language code). Another approach would be same structures and file names below a main language directory.
If you have only one translation, the latter might be better. If you need to keep several translations in sync, the first approach might make more sense.
Hraban
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-06-15 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 8:41 Jan Willem Flamma
2020-06-11 9:34 ` Wolfgang Schuster
2020-06-11 18:53 ` BPJ
2020-06-12 5:29 ` r.ermers
2020-06-12 9:26 ` Jan Willem Flamma
2020-06-15 18:23 ` Henning Hraban Ramm [this message]
2020-06-17 12:13 ` Jan Willem Flamma
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=35CEE372-48A6-4EA0-BCF6-310349688EEC@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).