From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Typing efficiency
Date: Fri, 4 Sep 2020 15:51:46 +0200 [thread overview]
Message-ID: <3E8EE726-5A29-48EE-BE8D-DAE1612FFBB6@elvenkind.com> (raw)
In-Reply-To: <9A39F242-5579-4FCB-A29C-FC6C728480E1@hxcore.ol>
Hi,
Sounds like a job for the blocks mechanism more so than buffers:
\defineblock[entext]
\defineblock[nltext]
\defineselector [language] [max=2,n=1]
\startmode[en]
\setupselector[language][n=1]
\keepblocks[entext]
\stopmode
\startmode[nl]
\setupselector[language][n=2]
\keepblocks[nltext]
\stopmode
\starttext
\startsection[title=\select{language}{English title}{Dutch title}]
\beginentext
This is English text.
\endentext
\beginnltext
This is Dutch text.
\endnltext
\stopsection
\stoptext
Best wishes,
Taco
> On 4 Sep 2020, at 14:02, Jan Willem Flamma <register12c@gmail.com> wrote:
>
> Dear list member,
>
> Following up from:
> https://www.mail-archive.com/ntg-context@ntg.nl/msg94719.html
>
> The below MWE works but how can I avoid having to type
> \startmode[en]
> \getbuffer[en]
> \stopmode
> \startmode[nl]
> \getbuffer[nl]
> \stopmode
>
> after every block of text?
>
> I tried to define a new start/stop pair as follows:
> \definestartstop[Bufen][
> before={\startmode[en]
> \startbuffer[en]},
> after={\stopbuffer
> \getbuffer[en]
> \stopmode}]
>
> but that fails.
>
> No doubt a clever solution exists that minimizes the typing.
>
> Kind regards,
> Jan Willem
>
>
> ===
> \setupinteraction[state=start]
>
> %\enablemode[nl]
> \enablemode[en]
>
> \defineselector [language] [max=2,n=1]
> \startmode[en]
> \setupselector[language][n=1]
> \stopmode
> \startmode[nl]
> \setupselector[language][n=2]
> \stopmode
>
> \starttext
>
> \startsection[title=\select{language}{English title}{Dutch title}]
>
> \startbuffer[en]
> This is English text.
> \stopmode
> \stopbuffer
> \startbuffer[nl]
> This is Dutch text.
> \stopbuffer
>
> \startmode[en]
> \getbuffer[en]
> \stopmode
> \startmode[nl]
> \getbuffer[nl]
> \stopmode
>
> \stopsection
>
> \stoptext
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
Taco Hoekwater
Elvenkind BV
___________________________________________________________________________________
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-09-04 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 12:02 Jan Willem Flamma
2020-09-04 13:51 ` Taco Hoekwater [this message]
2020-09-04 14:26 ` Wolfgang Schuster
2020-09-06 11:28 ` 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=3E8EE726-5A29-48EE-BE8D-DAE1612FFBB6@elvenkind.com \
--to=taco@elvenkind.com \
--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).