From: Nicola <nvitacolonna@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: drop cap (initial) and indentation
Date: Mon, 19 Jul 2021 07:56:19 -0000 (UTC) [thread overview]
Message-ID: <sd3b73$n8g$1@ciao.gmane.io> (raw)
In-Reply-To: <88D4E660-D4F9-4D17-9346-568712110D06@rna.nl>
On 2021-07-18, Gerben Wierda <gerben.wierda@rna.nl> wrote:
> PS. switching \kap and \bf has an interesting result, the first
> character of the words is not in bold. This did not happen with
> lettrine in mkii
I do not have an answer to your question, but I'd like to point out that
you can keep using lettrine with ConTeXt LMTX, if you wish. You just
need to add the modules manually, currently:
https://wiki.contextgarden.net/Modules#ConTeXt_LMTX
Nicola
___________________________________________________________________________________
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-07-19 7:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-18 21:54 Gerben Wierda
2021-07-19 7:56 ` Nicola [this message]
2021-07-21 10:00 ` Use of lettrine module in LMTX Gerben Wierda
2021-07-21 20:38 ` Nicola
2021-07-22 8:05 ` Solution: LMTX initial (drop cap) in combination with indenting Gerben Wierda
2021-07-21 21:10 ` Use of lettrine module in LMTX Wolfgang Schuster
[not found] ` <E7086935-5930-40FD-926A-7B881F56E54A@rna.nl>
2021-07-23 11:04 ` Wolfgang Schuster
2021-07-23 13:10 ` Gerben Wierda
2021-07-23 13:27 ` Arthur Rosendahl
2021-07-25 20:14 ` Nicola
2021-07-25 20:53 ` Modules under LMTX, was " Rik Kabel
2021-07-25 22:20 ` Aditya Mahajan
2021-07-19 13:56 ` drop cap (initial) and indentation Pablo Rodriguez
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='sd3b73$n8g$1@ciao.gmane.io' \
--to=nvitacolonna@gmail.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).