From: Francisco Gracia <fgragu023@gmail.com>
To: ntg-context@ntg.nl
Subject: Problem with *lettrine* module in Mk-iv
Date: Thu, 14 Nov 2013 22:53:02 +0100 [thread overview]
Message-ID: <CACiybx5Up95RH1qvx7Xsie9YAHjRH2No=RB66Na0bLFuesKpgg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 725 bytes --]
I am glad to report that the problems that I experienced until recently
with the *lettrine* module have disappeared. At present it works like any
other regular module.
As the *lettrine* source file does not seem to have been modified, I
conclude that the reason of the improvement should be attributed to the
modification of some other unknown piece of the complex *ConTeXt*
machinery. The interpreter at work is
mkiv lua stats > luatex banner: this is luatex, version beta-0.77.0 (tex
live 2013/w32tex) (rev 4645)
This should be good news (at least it has been for me) as *lettrine* is a
more powerful and complete command than *inital* for the intended job and,
above all, is much better documented.
Regards
Francisco
[-- Attachment #1.2: Type: text/html, Size: 839 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2013-11-14 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 21:53 Francisco Gracia [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-09 19:28 Francisco Gracia
2012-09-10 11:43 ` Sietse Brouwer
2012-09-10 13:22 ` Jörg Hagmann
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='CACiybx5Up95RH1qvx7Xsie9YAHjRH2No=RB66Na0bLFuesKpgg@mail.gmail.com' \
--to=fgragu023@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).