From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Max Chernoff via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: Re: characters.tex.toutf bug
Date: Thu, 30 Mar 2023 13:58:55 +0200 [thread overview]
Message-ID: <d342099b-bf98-1a57-9950-3834f66c2c31@freedom.nl> (raw)
In-Reply-To: <7fea603a649f15c5adeba0b19659e094036b2e76.camel@telus.net>
On 3/30/2023 7:57 AM, Max Chernoff via ntg-context wrote:
> Hi Hans,
>
> "characters.tex.toutf" only works if there is a backslash somewhere in
> its input string. This leads to some really surprising behaviour in the
> following example:
>
> \definefontfeature[default][tlig=no, trep=no]
>
> \startbuffer[test-bib]
> @article{one,
> author = {``Author---\v{O}ne''},
> }
> @article{two,
> author = {``Author---Two''},
> }
> \stopbuffer
>
> \usebtxdataset[test-bib.buffer]
>
> \starttext
> \placelistofpublications[method=dataset]
> \stoptext
>
> Removing the following lines
>
> elseif not find(str,"\\",1,true) then
> return str
>
> from the definition of "characters.tex.toutf" in "char-tex.{lmt,lua}"
> fixes this issue for me.
it is more side effect of removing the (declared obsolete some years
ago) `` '' input which catched it later
i tend to remove
for k, v in next, ligaturemapping do
hash[k] = v
end
in favor of an explicit 'tquo' feature that one can enable if wanted
\definefontfeature[default][default][tlig=yes,tquo=yes,trep=yes]
\startbuffer[test-bib]
@article{one,
author = {``Author---\v{O}ne''},
}
@article{two,
author = {``Author---Two''},
}
@article{three,
author = {Author---Two},
}
@article{three,
author = {,,Author---Two''},
}
\stopbuffer
so I tested that with the above which seems to work.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-03-30 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 5:57 Max Chernoff via ntg-context
2023-03-30 11:58 ` Hans Hagen via ntg-context [this message]
2023-03-30 21:30 ` Max Chernoff via ntg-context
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=d342099b-bf98-1a57-9950-3834f66c2c31@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.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).