From: "Frans Goddijn" <frans@goddijn.com>
Subject: fonts are difficult outsite TeX too
Date: Mon, 16 Jul 2001 10:12:51 +0200 [thread overview]
Message-ID: <002101c10dcf$c01e7f20$6401a8c0@oemcomputerlap> (raw)
A friend, not a TeX user, has a problem with third party file viewing
software that his company embeds. The helpdesk of the third party software
manufacturer wrote these words:
--- knip ---
>
> We apologize for this problem. The system of fonts is so
> incredibly complex that its behavior is approaching
> randomness. It is also very hard for us to fix this when we
> cannot duplicate it here. Anything you can suggest to help
> reproduce the problem would be wonderful.
>
> Regards,
>
> Steve
> --
So next time I get into font knots I'll not blame TeX's complexity ;=}}
reply other threads:[~2001-07-16 8:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='002101c10dcf$c01e7f20$6401a8c0@oemcomputerlap' \
--to=frans@goddijn.com \
/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).