From: Idris Samawi Hamid <ishamid@lamar.colostate.edu>
Subject: RE: chancery font
Date: Sun, 3 Apr 2005 12:45:24 -0600 [thread overview]
Message-ID: <42AE2AED@webmail.colostate.edu> (raw)
>===== Original Message From ciro@kavyata.com, mailing list for ConTeXt users
<ntg-context@ntg.nl> =====
>My problem goes beyond fonts. What I think I need is a simple explanation
>of the TeX-like package system. For instance:
>
>I see tetex,pdftex,contex, latex,web2c,...and so on, but I don't understand
>their interrelation/dependency.
teTeX, fpTeX, gwTeX, and MiKTeX are os-dependent distrbutions.
LaTeX and ConTeXt are os-independent macropackages.
Web2C is the Pascal-to-C translator that allows compilation of TeX on Unix,
Windows, etc. /web2c is the directory that contains configuration files and
os-dependent format files. But I don't know why it's called "/web2c"
>Why the livetex tree is like it is? What is needed for a context user?
ConTeXt has become so detailed and powerful, and changes so fast, that the
os-dependent distrbutions can't keep up. I predict that one day ConTeXt will
be completely independent of TeXLive. Some of the problems many of us have
been facing ultimately boil down to the growing, but not yet complete,
independence of ConTeXt from TeXLive. Personally, I think this a good thing,
because ConTeXt is really a stand-alone system in the final analysis.
mswincontext.zip is _almost_ there; maybe Hans could use volunteers to build
and maintain independent Mac and Unix packages a la mswincontext.zip. Then we
could contribute to a test/torture suite to make sure that everything runs
identically on all os's. Each of us may have pet issues that concern us (I
have my aleph work for example, there are fonts, xml, etc).
>What are the steps to upgrade context with a cont-tmf.zip and a texlive2004?
>Would it be possible to create an shell script that automize all this?
I would get the tetex package from pragma, install it in its own tree, define
your path so that your ConTeXt bin is searched BEFORE TeXLive's, and have your
shell script initialize your tree (maybe there are instructions in the teTeX
package). I modified my setuptex.bat so that my ConTeXt tree would search my
TeXLive tree as well; I suppose you could do the same with setuptex.csh.
>
>Where are fonts registered/stored/mapped/encoded?
There is a document somewhere on the TeX Directory Structure (tds), I think.
Look in /texmf/doc/tds
>
>Most books on TeX,latex, etc, only explain how to use them, but not
>the 'system administration' part, which must of us have to learn as well.
There is an old book, Making TeX Work, that aimed to do just this. But it's 11
years old and woefully out of date.
>
>BTW, I used Idris instructions (without step4 because my texfont works)
>and I have installed three different fonts so far. Actually, I
>converted TTF fonts
>to pfb/afm, then used the Idris steps, and I am happy.
How did you convert ttf>pfb? I did this once using FontLab and I lost all my
macron accents:-(
But texfont and pdfetex work with ttf files so there is no need to convert:-)
Now I hace to learn how
>to build typescript files, and learn where to put them,
What I did was just get one complete working typescript and model my other
typescripts on that one. If type-ugm is working for you, just study that one.
Five steps:
% raw fonts
%Names
%Synonyms
%maps
%typefaces
Note that you can mix and match fonts to create your own complete typefaces. I
am enclosing a typescript I did for Times New Roman and Arial (type-tnr.tex)
that I posted a few weeks ago.
About placing type-* files: You can put them anywhere in your TeX path; I put
mine, along with some other private configuration files, in
/texmf-local/tex/generic/private, but you can put them anywhere you like under
your TeX path.
>and the mapping/encoding
>business.
I think you don't have to worry about this too much, except that texfont
defaults to texnansi, while the fonts that come with TeXLive are mostly ec. So
you should avoid use of \char as much as possible in your macros, and stick to
character control sequences like \circumflex.
Best
Idris
============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-04-03 18:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 18:45 Idris Samawi Hamid [this message]
2005-04-03 20:25 ` Ciro Soto
2005-04-03 21:06 ` h h extern
-- strict thread matches above, loose matches on Subject: below --
2005-04-16 14:13 Enrique Laya
2005-04-03 20:39 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 18:46 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-02 22:33 Idris Samawi Hamid
2005-04-02 21:21 Idris Samawi Hamid
2005-04-01 8:37 btex-etex Jiri Polcar
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
2005-04-03 14:57 ` Adam Lindsay
2005-04-03 16:22 ` Ciro Soto
2005-04-03 19:41 ` h h extern
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=42AE2AED@webmail.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--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).