From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Selectively supressing ligatures
Date: Tue, 11 Aug 2015 13:22:46 +0200 [thread overview]
Message-ID: <55C9DB06.7000702@wxs.nl> (raw)
In-Reply-To: <55C9D161.2070600@mailbox.org>
On 8/11/2015 12:41 PM, Jan U. Hasecke wrote:
> Am 11.08.2015 um 11:46 schrieb Hans Hagen:
>> On 8/11/2015 11:12 AM, Jan U. Hasecke wrote:
>>
>>> As far as I understood selnoligs works with regular expressions (black
>>> magic!). It is very time consuming, but CPU time is cheap. ;-)
>>
>> sure but life is still short so i prefer less runtime over cheap runtime
>
> Absolutely right:
>
> LuaLaTeX run with selnoligs:
>
> real 18m39.101s
> user 18m40.335s
> sys 0m1.624s
>
>
> LuaLaTeX run without selnoligs:
>
> real 11m50.577s
> user 11m51.438s
> sys 0m1.783s
>
> But as I used pandoc in this project I had no chance to correct the
> ligatures by hand. And if I had I would have needed seven days instead
> of seven minutes more runtime.
a couple of times 7 minutes i guess -)
> But I am offtopic.
Whatever. In Context it's not that slow. In a worst case your 1000 pages
are text only which takes 17.91 sec without and 18.95 sec with
suppression enabled (0.14 s loop overhead), so some 5% extra runtime.
\replaceword[more][slffl][sl{ff}l]
\replaceword[more][slfful][sl{ff}ul]
\replaceword[more][shlfful][shl{ff}ul]
\replaceword[more][shelfful][shel{ff}ul]
\startbuffer
\testfeatureonce{100}{
\dorecurse{10} {
test 1 test 2 test 3 test 4 test 5
shelfful
test 6 test 7 test 8 test 9 test 0
}
\par
}
\stopbuffer
\starttext
\getbuffer \page
\setreplacements[more]
\getbuffer
\stoptext
Btw, a 11 minutes baseline sounds like a lot to me.
> Thanks again for the solution.
>
> juh
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 prev parent reply other threads:[~2015-08-11 11:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 13:10 juh
2015-08-11 6:25 ` Jan U. Hasecke
2015-08-11 8:19 ` Hans Hagen
2015-08-11 9:12 ` Jan U. Hasecke
2015-08-11 9:46 ` Hans Hagen
2015-08-11 10:41 ` Jan U. Hasecke
2015-08-11 11:22 ` Hans Hagen [this message]
2015-08-11 13:00 ` Jan U. Hasecke
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=55C9DB06.7000702@wxs.nl \
--to=pragma@wxs.nl \
--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).