From: Radhelorn <radhelorn@mail.ru>
Subject: Re: Problems with the pscyr font package
Date: Tue, 14 Jun 2005 16:18:30 +0400 [thread overview]
Message-ID: <42AECB16.4090300@mail.ru> (raw)
In-Reply-To: <42AE7941.8020704@elvenkind.com>
Taco Hoekwater wrote:
>>
>> Thanks, this explains the situation. Is there a command to trace font
>> loading? Which files are loaded, etc.
>
>
> Nothing that would help you understand it better, I'm afraid. There is
> a way to trace file opne/file close in the search library, but you
> have to be an expert to understand the output of that I'm afraid.
>
> Taco
>
Thank you for the explanation. Now I make typescript file for the
package and have some problems with math, but I will try to get through
this myself.
--
Radhelorn <radhelorn@mail.ru>
next prev parent reply other threads:[~2005-06-14 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 10:37 Radhelorn
2005-06-13 11:01 ` Taco Hoekwater
2005-06-13 12:44 ` Radhelorn
2005-06-13 12:47 ` Taco Hoekwater
2005-06-13 15:13 ` Radhelorn
2005-06-13 17:38 ` Taco Hoekwater
2005-06-14 3:16 ` Radhelorn
2005-06-14 6:29 ` Taco Hoekwater
2005-06-14 12:18 ` Radhelorn [this message]
2005-06-13 17:40 ` Taco Hoekwater
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=42AECB16.4090300@mail.ru \
--to=radhelorn@mail.ru \
--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).