From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: issue with beta from 2019.11.29 21:47 in Windows
Date: Thu, 5 Dec 2019 09:23:47 +0100 [thread overview]
Message-ID: <777dbe67-70b2-d63b-dd21-4be5024194d4@xs4all.nl> (raw)
In-Reply-To: <65761236-5be0-5b50-cbcd-9d6db682eca0@gmx.es>
On 12/4/2019 10:19 PM, Pablo Rodriguez wrote:
> On 12/3/19 10:14 PM, Hans Hagen wrote:
>> On 12/3/2019 8:37 PM, Pablo Rodriguez wrote:
>>> [...]
>>> I’m afraid a new font is not an option for me at work.
>> But there are better (unicode) versions available on windows, why nmot
>> use those then (as wolfgang pointed out).
>
> Many thanks for your reply, Hans.
>
> I would use the Unicode versions at home (if I had a Windows license),
> but at work it is problematic even to ask for free fonts.
>
> My company may be to strict with these policies, but I don’t think it is
> a total exception in this matter.
>
> I hope we might switch to Windows 10 in the no so near future 😃.
- if you use tex, use fonts that are put in the tex tree, the only
guarantee you have for continuity
- i checked a few versions of that font on an old windows xp vm and it
works ok ... so does your company ever update the machines?
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:[~2019-12-05 8:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 15:18 Pablo Rodriguez
2019-12-02 17:01 ` Wolfgang Schuster
2019-12-02 17:46 ` Pablo Rodriguez
2019-12-02 20:45 ` Wolfgang Schuster
2019-12-03 19:37 ` Pablo Rodriguez
2019-12-03 21:14 ` Hans Hagen
2019-12-04 21:19 ` Pablo Rodriguez
2019-12-05 8:23 ` Hans Hagen [this message]
2019-12-05 19:31 ` Pablo Rodriguez
2019-12-06 9:01 ` Arthur Reutenauer
2019-12-07 13:40 ` Pablo Rodriguez
2019-12-07 15:32 ` Hans Hagen
2019-12-07 22:49 ` Pablo Rodriguez
2019-12-07 23:33 ` Hans Hagen
2019-12-04 21:27 ` Pablo Rodriguez
2019-12-02 17:05 ` Hans Hagen
2019-12-02 17:51 ` Pablo Rodriguez
2019-12-02 22:22 ` Hans Hagen
[not found] <7992CF71224042639D33FC342999C075@CJ3001517A>
2019-12-03 8:17 ` Hans Hagen
2019-12-03 19:45 ` Pablo Rodriguez
2019-12-03 21:11 ` Hans Hagen
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=777dbe67-70b2-d63b-dd21-4be5024194d4@xs4all.nl \
--to=j.hagen@xs4all.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).