ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: issue with beta from 2019.11.29 21:47 in Windows
Date: Thu, 5 Dec 2019 20:31:45 +0100	[thread overview]
Message-ID: <3228ed52-c39a-1aa0-e79e-c69a0cd48b2f@gmx.es> (raw)
In-Reply-To: <777dbe67-70b2-d63b-dd21-4be5024194d4@xs4all.nl>

On 12/5/19 9:23 AM, Hans Hagen wrote:
> On 12/4/2019 10:19 PM, Pablo Rodriguez wrote:
>> [...]
>> 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?

Hi Hans,

I wonder whether my issue with the fonts might be caused by my ConTeXt
distribution (such as the one with expansion, reported some ).

Windows is updated with security patches (or whichever the name might be).

If I try to explain to the IT people that a font is misbehaving and an
application (I don’t even try to explain what ConTeXt actually is [they
won’t understand]) cannot recognize it, they will reply that the
application is wrong. Because of that, I’m not even trying to explain
what is wrong with the font at all.

In my previous company, I remember a guy (which had as slightly idea of
what TeX was [he used LaTeX for his PhD decades ago]) with a strong
background in computer science. He was impressed that I “developed” a
system with no coding knowledge, but he objected that ConTeXt wasn’t
standard software (the standard for him was OpenOffice.org). I replied
that the standard was in the output PDF documents (which were PDF/A-3a).
(I didn’t mention that working with OOo was a real pain and that trying
to write conditionals with document merging was extremely annoying for me.)

Many thanks for your help and your new betas,

Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2019-12-05 19:31 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
2019-12-05 19:31               ` Pablo Rodriguez [this message]
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=3228ed52-c39a-1aa0-e79e-c69a0cd48b2f@gmx.es \
    --to=oinos@gmx.es \
    --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).