From: jbf <roma83537@gmail.com>
To: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: dictionary example
Date: Sun, 13 Jun 2021 08:49:55 +1000 [thread overview]
Message-ID: <27dfb869-5ac7-8112-5f67-4b9b2cb7c355@gmail.com> (raw)
In-Reply-To: <a017e454-e246-4d67-f9b1-894b17a256d4@gmail.com>
Indeed, Wolfgang, the whole idea is to use whatever head (I chose
subsubject, but am not tied to that) to be able to get headers which
show me the first and last item on each page, as dictionaries usually
do. So my next question would be... is there another way I can get a
mark entry of this kind without using heads that automatically have
spaces before and after (which is what I tried to get rid of with my
before=, after= keys). Could I, for example, use \getmarking with
specifically designed paragraphs?
BTW, I can do exactly what I need to do in LaTeX (have already produced
a working model), but I want to be able to do it in ConTeXt. Maybe the
approach I've taken thus far is the completely wrong one, which I why I
was wondering if someone has already produced a standard dictionary
format with ConTeXt.
Julian
On 12/6/21 11:25 pm, Wolfgang Schuster wrote:
> jbf schrieb am 12.06.2021 um 12:39:
>> I am wondering if someone has tried a two-column dictionary layout
>> with ConTeXt. What is confounding me at the moment is the gap between
>> entries in the columns. My MWE is below. Try as I may, I seem unable
>> to get rid of those gaps! I obviously want each entry to follow on
>> from the other. I'm obviously not doing things right! If someone has
>> already set up a dictionary and has a model they could share I'd be
>> grateful. I'm attaching a screenshot of the result from the code below.
>
> The gaps between the entries are the subsubject titles where you omit
> the title. Omitting the title for a heading doesn't mean no space is
> inserted, to change this you can use the 'placehead=hidden' setting
> but I guess your goal is to add a mark entry for each description.
>
> Wolfgang
>
> ___________________________________________________________________________________
>
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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:[~2021-06-12 22:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 10:39 jbf
2021-06-12 13:25 ` Wolfgang Schuster
2021-06-12 22:49 ` jbf [this message]
2021-06-12 23:52 ` jbf
2021-06-13 7:48 ` Hans Hagen
2021-06-13 9:09 ` jbf
2021-06-13 9:33 ` Hans Hagen
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=27dfb869-5ac7-8112-5f67-4b9b2cb7c355@gmail.com \
--to=roma83537@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=wolfgang.schuster.lists@gmail.com \
/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).