From: Rob Ermers <r.ermers@hccnet.nl>
Subject: Re: chancery font
Date: Sun, 03 Apr 2005 16:03:24 +0200 [thread overview]
Message-ID: <424FF7AC.4050507@hccnet.nl> (raw)
In-Reply-To: <297ee2eb0504021533408e74d0@mail.gmail.com>
Hi Ciro,
I completely agree. Context works fine but, like you, I have not
succeeded in installing any new font thusfar.
A few months ago I tried again with a very simple font, which I got
working under Latex, but not under Context, despite all my attempts and
suggestions from other subscribers: alas!
Two years ago I recoded a cyrillic font under Latex, that contains
special characters not available in other fonts, therefore I guess I
know how the TeX font mechanism works. I achieved that by carefully
reading all kinds of manuals available on the net.
For the time being I manage with Context with the standard fonts &
Palatino, waiting for a breakthrough of some kind: the golden tip!
Kind regards,
Robert
Ciro Soto wrote:
>>(untested, but hopefully you get the idea...)
>>
>>adam
>
>
> unfortunately, I have a mental mess with the font business in tex.
> How can one keep track with so many directories, encodings, file types,
> maps, etc... I am tired of trying to undestand. Manuals are useless
> because they are outdated, trees are changed and need texhash, plus,
> on top, one needs to learn the syntax for Context to use fonts.
> I've been spending days trying to install a verdana font, and no
> matter what I do,
> it doesnt' work, and I think the same is happening with the garamond.
> I have no lesss than 3000 font files in my computer, but so far, only a handful
> are available in context. At this point,
> I really wish I had a graphical tool to install and use a font,
> without going through
> all the --always changing-- steps...
> I guess, some day, someone will clear this up for once...
>
> ciro
> Ciro
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
>
next prev parent reply other threads:[~2005-04-03 14:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 8:37 btex-etex Jiri Polcar
2005-04-01 9:24 ` btex-etex Patrick Gundlach
2005-04-01 9:49 ` btex-etex Jiri Polcar
2005-04-02 6:37 ` Taco Hoekwater
2005-04-03 7:59 ` Jiri Polcar
2005-04-03 18:20 ` Taco Hoekwater
2005-04-03 19:28 ` h h extern
2005-04-04 7:28 ` Jiri Polcar
2005-04-04 8:22 ` Hans Hagen
2005-04-05 8:10 ` Jiri Polcar
2005-04-04 10:53 ` btex-etex Patrick Gundlach
2005-04-02 16:52 ` chancery font Ciro Soto
2005-04-02 17:27 ` Idris Samawi Hamid
2005-04-02 17:52 ` Willi Egger
2005-04-02 18:29 ` Ciro Soto
2005-04-02 19:21 ` Idris Samawi Hamid
2005-04-02 20:00 ` Ciro Soto
2005-04-02 21:22 ` Adam Lindsay
2005-04-02 23:33 ` Ciro Soto
2005-04-03 14:03 ` Rob Ermers [this message]
2005-04-03 14:57 ` Adam Lindsay
2005-04-03 16:22 ` Ciro Soto
2005-04-03 19:41 ` h h extern
2005-04-02 21:21 Idris Samawi Hamid
2005-04-02 22:33 Idris Samawi Hamid
2005-04-03 16:15 Idris Samawi Hamid
2005-04-03 16:42 ` Rob Ermers
2005-04-03 16:57 ` Paul Tremblay
2005-04-03 17:10 ` Thomas A.Schmitz
2005-04-03 18:45 Idris Samawi Hamid
2005-04-03 20:25 ` Ciro Soto
2005-04-03 21:06 ` h h extern
2005-04-03 18:46 Idris Samawi Hamid
2005-04-03 19:40 Idris Samawi Hamid
2005-04-03 19:54 ` Paul Tremblay
2005-04-03 20:22 ` Thomas A.Schmitz
2005-04-03 20:39 Idris Samawi Hamid
2005-04-16 14:13 Enrique Laya
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=424FF7AC.4050507@hccnet.nl \
--to=r.ermers@hccnet.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).