From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Documentation of change / Evolving documents
Date: Sun, 29 Sep 2019 10:36:59 +0200 [thread overview]
Message-ID: <AFD4AFA0-4F18-4F64-85A6-E52878741523@fiee.net> (raw)
In-Reply-To: <588C9B26-325C-4A5E-BFFF-2B8B1E6A7DC1@axelkielhorn.de>
> Am 2019-09-29 um 08:59 schrieb Axel Kielhorn <tex@axelkielhorn.de>:
>
> But I would prefer to write
>
> \startChangeA{V. 2.0}
> Mit den Befehlen \type{\Changea}, \type{\Changer} und \type{\Changec} werden hinzugefügte, gelöschte oder geänderte Satzteile gekennzeichnet. Der Befehl \type{\Changec} hat zwei Argumente: alter Text und neuer Text.
> \stopChangeA
See https://wiki.contextgarden.net/Command/definestartstop
> Or maybe:
> \startChangeA[version={V. 2.0}]
This could help: https://wiki.contextgarden.net/System_Macros/Handling_Arguments
> Once this is fixed I’d like to translate it to english and put it into the Wiki.
Looking forward to it.
Grüßlinge, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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:[~2019-09-29 8:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 8:06 Axel Kielhorn
2019-09-29 6:59 ` Axel Kielhorn
2019-09-29 8:36 ` Henning Hraban Ramm [this message]
2019-09-29 8:50 ` Wolfgang Schuster
2019-09-29 12:34 ` Axel Kielhorn
2019-10-11 8:18 ` Axel Kielhorn
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=AFD4AFA0-4F18-4F64-85A6-E52878741523@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).