From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: trouble with typescripts
Date: Sun, 18 Dec 2005 09:06:59 +0100 [thread overview]
Message-ID: <244E13B7-E96F-4655-AB35-9E3472878F37@uni-bonn.de> (raw)
In-Reply-To: <EB7A0ED8-D88B-4DA7-9E79-64401A037D01@uni-bonn.de>
Replying to my own ooooooold question: this problem has disappeared
in newer versions of ConTeXt, as I just found out -- thanks for
taking care of it! Taco, one wish for the bug collector: could we
have a place for resolved bugs (or is it there and I just didn't find
it)? I knew there had been a bug report wrt this problem, and it
would've been reassuring to see a "resolved" tag attached to it.
Thanks, and best
Thomas
On Oct 30, 2005, at 8:59 AM, Thomas A. Schmitz wrote:
> Hi all,
>
> I have a specific problem with a typescriptfile that may be of
> general interest (the problem, not the typescript). I have
> collected a number of font definitions into one file and have
> observed that certain fonts cannot coexist. One small example:
>
> \starttypescript[greekcanonica]
> % font definitions
> \stoptypescript
>
> \starttypescript[GreekCanonica]
> \definetypeface[MyGreekCanonica]
> \stoptypescript
>
> and
> \starttypescript[greekcardo]
> % font definitions
> \stoptypescript
>
> \starttypescript
> \definetypeface[MyGreekCardo]
> \stoptypescript
>
> cannot be defined in the same typescriptfile. If I comment A out, B
> will work; it A is uncommented, ConTeXt will complain about missing
> font definitions for B. So I would suspect that in processing
> typescripts, names are somehow truncated to 9 or less characters.
> So these questions arise:
>
> 1. Can this be changed? (We had a similar behavior with names of
> modules, which was changed a while ago, I think.)
>
> 2. Is there a workaround? Is it possible to add other parameters to
> the \definetypeface[] line?
>
> Best
>
> Thomas
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2005-12-18 8:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 7:59 Thomas A. Schmitz
2005-12-18 8:06 ` Thomas A. Schmitz [this message]
2005-12-18 9:05 ` 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=244E13B7-E96F-4655-AB35-9E3472878F37@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).