From: Hans Hagen <j.hagen@xs4all.nl>
To: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: composing commands
Date: Sun, 7 Feb 2021 20:40:34 +0100 [thread overview]
Message-ID: <285aca9b-b8a1-f4a0-f4eb-5113b64d8291@xs4all.nl> (raw)
In-Reply-To: <725a4491-daaa-df10-2b3c-d784c232701d@uni-bonn.de>
Hi Thomas,
> On 2/5/21 5:38 PM, Hans Hagen wrote:
>> etc ... the ones that make 'composed characters'. I think that anyone
>> who needs them uses utf . They can be in (say) m-oldschool.mkxl or so.
>>
>> Objections? Hurt feelings? Sentiments?
>
> No hurt feelings, but I know that in my bib files, there are a couple of
> old entries that still have these weird composed characters. So I'm fine
> with upgrading, but it would be nice if this could fail gracefully, with
> a nice and informative error message...
Okay, here is a secret. When your bib fils is read, those magic accent
placement commands are not used at all:
\starttext
\startbuffer[bib]
@article{test,
title = {\"Articl\`e \O n\k{e}},
author = {Th\^omas},
year = {2001},
}
\stopbuffer
\usebtxdataset[bib.buffer]
\ctxlua{inspect(publications.datasets.default.luadata.test)}
\placebtxrendering[method=dataset,pagestate=start]
\stoptext
They have magically disappeared. Thanks to the fact hat Alan and I spent
quite a bit of time on brewing the magic potion when we redid the bib
stuff. So, although we will keep the shortcuts you'd probably never
noticed them being gone.
Now the question is: what can we expect in old bib files that we {\em
don't} handle.
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 / 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-02-07 19:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 16:38 Hans Hagen
2021-02-05 16:49 ` Jairo A. del Rio
2021-02-05 21:28 ` Hans Hagen
2021-02-05 17:19 ` Thomas A. Schmitz
2021-02-05 21:30 ` Hans Hagen
2021-02-05 22:25 ` Otared Kavian
2021-02-05 22:39 ` Hans Hagen
2021-02-05 23:01 ` Thomas A. Schmitz
2021-02-05 23:49 ` Hans Hagen
2021-02-05 22:29 ` Hans Hagen
2021-02-06 22:41 ` T. Kurt Bond
2021-02-08 9:53 ` Hans Hagen
2021-02-08 21:42 ` Richard Mahoney
2021-02-09 10:03 ` Otared Kavian
2021-02-09 13:08 ` Hans Hagen
2021-10-11 11:06 ` Marcus Vinicius Mesquita via ntg-context
2021-02-07 19:40 ` Hans Hagen [this message]
2021-02-05 22:21 ` Otared Kavian
2021-02-05 22:47 ` Hans Hagen
2021-02-05 23:45 ` luigi scarso
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=285aca9b-b8a1-f4a0-f4eb-5113b64d8291@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=thomas.schmitz@uni-bonn.de \
/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).