* ZapfDingbats Unicode differences MKIV vs LMTX
@ 2020-09-18 9:23 Christoph Reller
2020-09-18 14:17 ` Hans Hagen
0 siblings, 1 reply; 9+ messages in thread
From: Christoph Reller @ 2020-09-18 9:23 UTC (permalink / raw)
To: ntg-context
[-- Attachment #1.1: Type: text/plain, Size: 1290 bytes --]
Dear List,
I have the following MWE:
\definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
\usemodule [fnt-10]
\starttext
(1) \getglyphdirect{ZapfDingbats}{61491}\crlf % MKIV log: char (U+0F033)
in font 'ZapfDingbats-4' with id 8: missing
(2) \getglyphdirect{ZapfDingbats}{983059} % LMTX log: char (U+F0013)
in font 'ZapfDingbats-4' with id 8: missing
\ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
\stoptext
In MKIV, line (1) fails to output the requested glyph, while line (2)
produces a "check" (✓). In LMTX, line (2) fails and line (1) produces the
"check" (✓) . The output of "\ShowCompleteFont" reports differing Unicodes
for the same glyphs. Apparently the Unicodes for ZapfDingbats have changed.
I would like to have a "check" (✓) in the output for both MKIV and LMTX.
Options:
A) Is there a way to address the glyph in ZapfDingbats for both MKIV and
LMTX uniformly, e.g. by glyph index? (By glyph name does not seem to work:
MKIV reports glyph names, LMTX does not.)
B) Is there a conditional that I can build into the source to distinguish
between MKIV and LMTX?
C) Is there a font in the distribution for which I can have a
"check"-symbol in both MKIV and LMTX?
Any help is appreciated!
Cheers,
Christoph
[-- Attachment #1.2: Type: text/html, Size: 1566 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: ZapfDingbats Unicode differences MKIV vs LMTX
2020-09-18 9:23 ZapfDingbats Unicode differences MKIV vs LMTX Christoph Reller
@ 2020-09-18 14:17 ` Hans Hagen
2020-09-19 4:18 ` Christoph Reller
0 siblings, 1 reply; 9+ messages in thread
From: Hans Hagen @ 2020-09-18 14:17 UTC (permalink / raw)
To: mailing list for ConTeXt users, Christoph Reller
On 9/18/2020 11:23 AM, Christoph Reller wrote:
> Dear List,
>
> I have the following MWE:
>
> \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
> \usemodule [fnt-10]
> \starttext
> (1) \getglyphdirect{ZapfDingbats}{61491}\crlf % MKIV log: char
> (U+0F033) in font 'ZapfDingbats-4' with id 8: missing
> (2) \getglyphdirect{ZapfDingbats}{983059} % LMTX log: char
> (U+F0013) in font 'ZapfDingbats-4' with id 8: missing
> \ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
> \stoptext
>
> In MKIV, line (1) fails to output the requested glyph, while line (2)
> produces a "check" (✓). In LMTX, line (2) fails and line (1) produces
> the "check" (✓) . The output of "\ShowCompleteFont" reports differing
> Unicodes for the same glyphs. Apparently the Unicodes for ZapfDingbats
> have changed.
>
> I would like to have a "check" (✓) in the output for both MKIV and LMTX.
> Options:
> A) Is there a way to address the glyph in ZapfDingbats for both MKIV and
> LMTX uniformly, e.g. by glyph index? (By glyph name does not seem to
> work: MKIV reports glyph names, LMTX does not.)
> B) Is there a conditional that I can build into the source to
> distinguish between MKIV and LMTX?
> C) Is there a font in the distribution for which I can have a
> "check"-symbol in both MKIV and LMTX?
Dingbats are old school t1 without proper names so we can't use
unicodes. However, there is a goodie that should do that so that in
principle it should work with unicodes but there is some interference
going on (i'll look at that)
For nwo access by 'name' or 'index' (these are kind of stable for such
an old font):
n:a34 : \getglyph{ZapfDingbats}{\tochar{n:a34}} \par
n:a35 : \getglyph{ZapfDingbats}{\tochar{n:a35}} \par
i:48 : \getglyph{ZapfDingbats}{\tochar{i:48}} \par
i:49 : \getglyph{ZapfDingbats}{\tochar{i:49}} \par
n:a104 : \getglyph{ZapfDingbats}{\tochar{n:a104}} \par
n:a105 : \getglyph{ZapfDingbats}{\tochar{n:a105}} \par
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: ZapfDingbats Unicode differences MKIV vs LMTX
2020-09-18 14:17 ` Hans Hagen
@ 2020-09-19 4:18 ` Christoph Reller
2020-09-19 10:04 ` Hans Hagen
0 siblings, 1 reply; 9+ messages in thread
From: Christoph Reller @ 2020-09-19 4:18 UTC (permalink / raw)
To: Hans Hagen; +Cc: mailing list for ConTeXt users
[-- Attachment #1.1: Type: text/plain, Size: 1684 bytes --]
On Fri, Sep 18, 2020 at 4:17 PM Hans Hagen <j.hagen@xs4all.nl> wrote:
> On 9/18/2020 11:23 AM, Christoph Reller wrote:
> > Dear List,
> >
> > I have the following MWE:
> >
> > \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
> > \usemodule [fnt-10]
> > \starttext
> > (1) \getglyphdirect{ZapfDingbats}{61491}\crlf % MKIV log: char
> > (U+0F033) in font 'ZapfDingbats-4' with id 8: missing
> > (2) \getglyphdirect{ZapfDingbats}{983059} % LMTX log: char
> > (U+F0013) in font 'ZapfDingbats-4' with id 8: missing
> > \ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
> > \stoptext
> >
> Dingbats are old school t1 without proper names so we can't use
> unicodes. However, there is a goodie that should do that so that in
> principle it should work with unicodes but there is some interference
> going on (i'll look at that)
>
> For nwo access by 'name' or 'index' (these are kind of stable for such
> an old font):
>
> n:a34 : \getglyph{ZapfDingbats}{\tochar{n:a34}} \par
> n:a35 : \getglyph{ZapfDingbats}{\tochar{n:a35}} \par
> i:48 : \getglyph{ZapfDingbats}{\tochar{i:48}} \par
> i:49 : \getglyph{ZapfDingbats}{\tochar{i:49}} \par
> n:a104 : \getglyph{ZapfDingbats}{\tochar{n:a104}} \par
> n:a105 : \getglyph{ZapfDingbats}{\tochar{n:a105}} \par
>
> Thank you Hans!
Access by glyph index with \tochar{i:19} works well for both MKIV and LMTX.
Access by name with \tochar{n:a39} does not work in LMTX with log
message: char ✓ (U+02713) in font 'ZapfDingbats-4' with id 8: missing. Also
\ShowCompleteFont does not report any glyph names in LMTX.
Cheers,
Christoph
[-- Attachment #1.2: Type: text/html, Size: 2182 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: ZapfDingbats Unicode differences MKIV vs LMTX
2020-09-19 4:18 ` Christoph Reller
@ 2020-09-19 10:04 ` Hans Hagen
2020-09-21 12:55 ` Christoph Reller
0 siblings, 1 reply; 9+ messages in thread
From: Hans Hagen @ 2020-09-19 10:04 UTC (permalink / raw)
To: Christoph Reller; +Cc: mailing list for ConTeXt users
On 9/19/2020 6:18 AM, Christoph Reller wrote:
> On Fri, Sep 18, 2020 at 4:17 PM Hans Hagen <j.hagen@xs4all.nl
> <mailto:j.hagen@xs4all.nl>> wrote:
>
> On 9/18/2020 11:23 AM, Christoph Reller wrote:
> > Dear List,
> >
> > I have the following MWE:
> >
> >
> \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
> > \usemodule [fnt-10]
> > \starttext
> > (1) \getglyphdirect{ZapfDingbats}{61491}\crlf % MKIV log: char
> > (U+0F033) in font 'ZapfDingbats-4' with id 8: missing
> > (2) \getglyphdirect{ZapfDingbats}{983059} % LMTX log: char
> > (U+F0013) in font 'ZapfDingbats-4' with id 8: missing
> > \ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
> > \stoptext
> >
> Dingbats are old school t1 without proper names so we can't use
> unicodes. However, there is a goodie that should do that so that in
> principle it should work with unicodes but there is some interference
> going on (i'll look at that)
>
> For nwo access by 'name' or 'index' (these are kind of stable for such
> an old font):
>
> n:a34 : \getglyph{ZapfDingbats}{\tochar{n:a34}} \par
> n:a35 : \getglyph{ZapfDingbats}{\tochar{n:a35}} \par
> i:48 : \getglyph{ZapfDingbats}{\tochar{i:48}} \par
> i:49 : \getglyph{ZapfDingbats}{\tochar{i:49}} \par
> n:a104 : \getglyph{ZapfDingbats}{\tochar{n:a104}} \par
> n:a105 : \getglyph{ZapfDingbats}{\tochar{n:a105}} \par
>
> Thank you Hans!
> Access by glyph index with \tochar{i:19} works well for both MKIV and
> LMTX. Access by name with \tochar{n:a39} does not work in LMTX with log
> message: char ✓ (U+02713) in font 'ZapfDingbats-4' with id 8: missing.
> Also \ShowCompleteFont does not report any glyph names in LMTX.
should be a bit better in yesterdays upload (i also changed the file
name alias so that in pinciple unicode should work too)
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: ZapfDingbats Unicode differences MKIV vs LMTX
2020-09-19 10:04 ` Hans Hagen
@ 2020-09-21 12:55 ` Christoph Reller
2020-09-21 13:27 ` Hans Hagen
0 siblings, 1 reply; 9+ messages in thread
From: Christoph Reller @ 2020-09-21 12:55 UTC (permalink / raw)
To: Hans Hagen; +Cc: mailing list for ConTeXt users
[-- Attachment #1.1: Type: text/plain, Size: 2868 bytes --]
On Sat, Sep 19, 2020 at 12:04 PM Hans Hagen <j.hagen@xs4all.nl> wrote:
> On 9/19/2020 6:18 AM, Christoph Reller wrote:
> > On Fri, Sep 18, 2020 at 4:17 PM Hans Hagen <j.hagen@xs4all.nl
> > <mailto:j.hagen@xs4all.nl>> wrote:
> >
> > On 9/18/2020 11:23 AM, Christoph Reller wrote:
> >
> \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
> > > \usemodule [fnt-10]
> > > \starttext
> > > (1) \getglyphdirect{ZapfDingbats}{61491}\crlf % MKIV log: char
> > > (U+0F033) in font 'ZapfDingbats-4' with id 8: missing
> > > (2) \getglyphdirect{ZapfDingbats}{983059} % LMTX log: char
> > > (U+F0013) in font 'ZapfDingbats-4' with id 8: missing
> > > \ShowCompleteFont{name:ZapfDingbats}{14pt}{1}
> > > \stoptext
> > >
> > Dingbats are old school t1 without proper names so we can't use
> > unicodes. However, there is a goodie that should do that so that in
> > principle it should work with unicodes but there is some interference
> > going on (i'll look at that)
> >
> > For nwo access by 'name' or 'index' (these are kind of stable for
> such
> > an old font):
> >
> > n:a34 : \getglyph{ZapfDingbats}{\tochar{n:a34}} \par
> > n:a35 : \getglyph{ZapfDingbats}{\tochar{n:a35}} \par
> > i:48 : \getglyph{ZapfDingbats}{\tochar{i:48}} \par
> > i:49 : \getglyph{ZapfDingbats}{\tochar{i:49}} \par
> > n:a104 : \getglyph{ZapfDingbats}{\tochar{n:a104}} \par
> > n:a105 : \getglyph{ZapfDingbats}{\tochar{n:a105}} \par
> >
> > Thank you Hans!
> > Access by glyph index with \tochar{i:19} works well for both MKIV and
> > LMTX. Access by name with \tochar{n:a39} does not work in LMTX with log
> > message: char ✓ (U+02713) in font 'ZapfDingbats-4' with id 8: missing.
> > Also \ShowCompleteFont does not report any glyph names in LMTX.
> should be a bit better in yesterdays upload (i also changed the file
> name alias so that in pinciple unicode should work too)
Dear Hans,
Thank you for working on this. I have tried version 2020.09.20: Unicode
input works for the "Private Use Area" Unicodes reported in
\ShowCompleteFont. Such Unicodes are, however, not desirable. Moreover, in
MKIV, a Unicode U+2713 (Check Mark) in the input did produce the
ZapfDingbats check, e.g. as follows:
\definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
\definefont[zapfdingbats][ZapfDingbats]
\starttext
{\zapfdingbats ✓}
\definedfont[name:ZapfDingbats]✓
\stoptext
I still get no check mark in the output PDF and a log message "char ✓
(U+02713) in font 'ZapfDingbats-4' with id 8: missing". Am I using the font
wrongly?
(This has not a high priority for me, because I have the unified access by
glyph index.)
Christoph
[-- Attachment #1.2: Type: text/html, Size: 3777 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: ZapfDingbats Unicode differences MKIV vs LMTX
2020-09-21 12:55 ` Christoph Reller
@ 2020-09-21 13:27 ` Hans Hagen
2020-09-22 5:19 ` Christoph Reller
0 siblings, 1 reply; 9+ messages in thread
From: Hans Hagen @ 2020-09-21 13:27 UTC (permalink / raw)
To: Christoph Reller; +Cc: mailing list for ConTeXt users
On 9/21/2020 2:55 PM, Christoph Reller wrote:
> \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
I don't know what the previous line does ... but it works ok here when
you remove it.
> \definefont[zapfdingbats][ZapfDingbats]
> \starttext
> {\zapfdingbats ✓}
> \definedfont[name:ZapfDingbats]✓
> \stoptext
>
> I still get no check mark in the output PDF and a log message "char ✓
> (U+02713) in font 'ZapfDingbats-4' with id 8: missing". Am I using the
> font wrongly?
> (This has not a high priority for me, because I have the unified access
> by glyph index.)
>
> Christoph
>
--
-----------------------------------------------------------------
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: ZapfDingbats Unicode differences MKIV vs LMTX
2020-09-21 13:27 ` Hans Hagen
@ 2020-09-22 5:19 ` Christoph Reller
2020-09-22 11:51 ` Hans Hagen
0 siblings, 1 reply; 9+ messages in thread
From: Christoph Reller @ 2020-09-22 5:19 UTC (permalink / raw)
To: Hans Hagen; +Cc: mailing list for ConTeXt users
[-- Attachment #1.1: Type: text/plain, Size: 1133 bytes --]
On Mon, Sep 21, 2020 at 3:27 PM Hans Hagen <j.hagen@xs4all.nl> wrote:
> On 9/21/2020 2:55 PM, Christoph Reller wrote:
>
> > \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
>
> I don't know what the previous line does ... but it works ok here when
> you remove it.
This line loads the font from a file ZapfDingbats.ttf. Without this line I
get no check marks in the output and the following log messages:
fonts > defining > font with asked name 'uzdr' is not found using
lookup 'file'
fonts > defining > unknown font 'uzdr', loading aborted
Correct me if I am wrong, but there does not seem to be a font file named
uzdr* in the distribution tree.
> \definefont[zapfdingbats][ZapfDingbats]
> > \starttext
> > {\zapfdingbats ✓}
> > \definedfont[name:ZapfDingbats]✓
> > \stoptext
> >
> > I still get no check mark in the output PDF and a log message "char ✓
> > (U+02713) in font 'ZapfDingbats-4' with id 8: missing". Am I using the
> > font wrongly?
> > (This has not a high priority for me, because I have the unified access
> > by glyph index.)
>
[-- Attachment #1.2: Type: text/html, Size: 1739 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: ZapfDingbats Unicode differences MKIV vs LMTX
2020-09-22 5:19 ` Christoph Reller
@ 2020-09-22 11:51 ` Hans Hagen
2020-09-22 11:57 ` Taco Hoekwater
0 siblings, 1 reply; 9+ messages in thread
From: Hans Hagen @ 2020-09-22 11:51 UTC (permalink / raw)
To: Christoph Reller; +Cc: mailing list for ConTeXt users
On 9/22/2020 7:19 AM, Christoph Reller wrote:
> On Mon, Sep 21, 2020 at 3:27 PM Hans Hagen <j.hagen@xs4all.nl
> <mailto:j.hagen@xs4all.nl>> wrote:
>
> On 9/21/2020 2:55 PM, Christoph Reller wrote:
>
> >
> \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
>
> I don't know what the previous line does ... but it works ok here when
> you remove it.
>
> This line loads the font from a file ZapfDingbats.ttf. Without this line
> I get no check marks in the output and the following log messages:
i don't know that one
> fonts > defining > font with asked name 'uzdr' is not found
> using lookup 'file'
> fonts > defining > unknown font 'uzdr', loading aborted
i guess you can get it from ctan (or ask Mojca to add it)
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: ZapfDingbats Unicode differences MKIV vs LMTX
2020-09-22 11:51 ` Hans Hagen
@ 2020-09-22 11:57 ` Taco Hoekwater
0 siblings, 0 replies; 9+ messages in thread
From: Taco Hoekwater @ 2020-09-22 11:57 UTC (permalink / raw)
To: mailing list for ConTeXt users
> On 22 Sep 2020, at 13:51, Hans Hagen <j.hagen@xs4all.nl> wrote:
>
> On 9/22/2020 7:19 AM, Christoph Reller wrote:
>> On Mon, Sep 21, 2020 at 3:27 PM Hans Hagen <j.hagen@xs4all.nl <mailto:j.hagen@xs4all.nl>> wrote:
>> On 9/21/2020 2:55 PM, Christoph Reller wrote:
>> >
>> \definefontsynonym[ZapfDingbats][file:ZapfDingbats][features=dingbats]
>> I don't know what the previous line does ... but it works ok here when
>> you remove it.
>> This line loads the font from a file ZapfDingbats.ttf. Without this line I get no check marks in the output and the following log messages:
>
> i don't know that one
MacOS has it.
___________________________________________________________________________________
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
___________________________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2020-09-22 11:57 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-18 9:23 ZapfDingbats Unicode differences MKIV vs LMTX Christoph Reller
2020-09-18 14:17 ` Hans Hagen
2020-09-19 4:18 ` Christoph Reller
2020-09-19 10:04 ` Hans Hagen
2020-09-21 12:55 ` Christoph Reller
2020-09-21 13:27 ` Hans Hagen
2020-09-22 5:19 ` Christoph Reller
2020-09-22 11:51 ` Hans Hagen
2020-09-22 11:57 ` Taco Hoekwater
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).