El mié, 24 de mar. de 2021 a la(s) 16:47, Hans Hagen (j.ha...@xs4all.nl)
escribió:
> On 3/24/2021 6:33 PM, Jairo A. del Rio wrote:
> > Hi, Hans. Here's my (miserably failing) attempt:
> >
> > \definedataset[nicedata]
> >
> > \starttext
> >
> > \startluacode
> >
> > local name = "nicedata"
> >
> >
So, what's the general recommendation? Which approach is the best in your
opinion? (In case it's the \replaceword approach: do you think you'll have time
to look into this?)
I've seen in an older thread that the best way to deal with this would be in
the hyphenator. What do you think about
On 3/24/2021 8:24 PM, denis.ma...@ub.unibe.ch wrote:
Anything, I've missed? Other aspects to think about here? How about
performance issues? (The blockligatures-mechanism resulted in this: with
a word list of about 2200 words it took a bit more than five seconds to
process 23 A5 pages than
On 3/24/2021 6:33 PM, Jairo A. del Rio wrote:
Hi, Hans. Here's my (miserably failing) attempt:
\definedataset[nicedata]
\starttext
\startluacode
local name = "nicedata"
-- For exposition only
local function dofactorial(n)
local function inner(c,m)
if m<2 then return c end
return
On 3/24/2021 8:20 PM, denis.ma...@ub.unibe.ch wrote:
-Ursprüngliche Nachricht-
Von: Hans Hagen
Gesendet: Mittwoch, 24. März 2021 17:42
An: mailing list for ConTeXt users ; Maier, Denis
Christian (UB)
Betreff: Re: [NTG-context] Another bug with ligature-blocking?
On 3/24/2021 4:48 PM,
No, no actually. I only put a toy example. What I need to solve is related
with storing data in the .tuc file when processes take a long time.
Memoization doesn't work as data is lost with each new run.
Jairo
El mié, 24 de mar. de 2021 a la(s) 15:36, Aditya Mahajan (adit...@umich.edu)
escribió:
Hi,
Trying to sum up what we currently have regarding ligature prevention, it looks
like we have three mechanisms available:
1. \replaceword[set][input][output]
Ex.: \replaceword[ligs][Auflage][Au{fl}age]
Replaces a word input with the corresponding output.
Doesn't work at the moment with LMTX.
> -Ursprüngliche Nachricht-
> Von: Hans Hagen
> Gesendet: Mittwoch, 24. März 2021 17:42
> An: mailing list for ConTeXt users ; Maier, Denis
> Christian (UB)
> Betreff: Re: [NTG-context] Another bug with ligature-blocking?
>
> On 3/24/2021 4:48 PM, denis.ma...@ub.unibe.ch wrote:
>
> >
On 3/23/21 10:12 PM, Alan Bowen wrote:
> Hi, Pablo—
>
> My inquiry concerns the possibility of getting *custom* properties that
> I could specify using \setupinteraction in a way that would output in
> the PDF file (under Document Info or Document Properties) as:
>
> Editor (not Author)
Hi, Hans. Here's my (miserably failing) attempt:
\definedataset[nicedata]
\starttext
\startluacode
local name = "nicedata"
-- For exposition only
local function dofactorial(n)
local function inner(c,m)
if m<2 then return c end
return inner(c*m, m-1)
end
return inner(1,n)
end
local
On 3/24/2021 4:48 PM, denis.ma...@ub.unibe.ch wrote:
\definefontfamily[times][rm][Times New Roman]
don't assume beforehand that something that doesn't work as expected is
a bug
the font just has no ligatures defined which you can remedy (in this
cae) with because it does have the glyphs
Hi,
I just ran into something strange with ligature blocking:
---
\blockligatures[begrif:fl:ich]
\definefontfeature[default][default][dlig=yes,liga=yes,]
Ah, I've now realized that the \blockligatures needs to be activated as a font
feature... So forget about this point.
But, it still looks like ligature prevention with \replaceword is not working
with lmtx, but it works with --luatex.
On 3/24/2021 5:20 AM, Jairo A. del Rio wrote:
Thank you very much. It's useful, indeed. However, what I need is to
bypass TeX (Lua > .tuc) if possible, since all the data I need to handle
is generated with Lua scripts.
datasets-001.tex in the test suite
14 matches
Mail list logo
