ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: frantisek holop <minusf@obiit.org>
Subject: Re: updating ConTeXt to latest on openbsd-current Q #3
Date: Mon, 6 Mar 2006 23:50:18 +0100	[thread overview]
Message-ID: <20060306225018.GR21773@obiit.org> (raw)
In-Reply-To: <440CB1E9.8060702@elvenkind.com>

hmm, on Mon, Mar 06, 2006 at 11:04:25PM +0100, Taco Hoekwater said that
> This is one of the latin modern fonts. ConTeXt depends on the latin
> modern package, and will not run without errors if latin modern is
> not installed.


thanks for the all the answers...

this all could be in the wiki thought, would save you/me mining the
archives :)  so i'll shamefully steal and put this info into the
openbsd upgrade page i just started :)


ok, seems like my last problem is about the fonts.  i must say the
wiki gets a bit controversial here:

http://wiki.contextgarden.net/TeTeX_3.0_installation says:

Install a Latin Modern font update

The Latin Modern fonts are still in development, so teTeX has a hard
time catching up. To get a stable system, you have to manually download
the [Latin Modern distribution] from ctan and install the package
according to the[instructions in the FAQ].

The ConTeXt-specific support files are included in Cont-tmf.zip, so it
is just a matter of installing the actual font files. 



http://wiki.contextgarden.net/Cont-lmt.zip says:

This was the Latin Modern release from CTAN, repackaged for an easier
download.

It has disappeared since Context 2006.02.01 



http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uselmfonts says:

<snip>
Note that teTeX distributions, from version 3.0, already have the lm
fonts: all you need do is use them. 



according to the wiki, i don't need cont-lmt.zip anymore.

according to the tex faq i already have them.


what now?   i downloaded the lm.tgz package, compared files, and
clearly, teTeX 3.0 files are old-old-old.

so i copied over the old files, run texhash, and lo and behold,
fonts are all right.



ok, the only problem i see at first glance is \"{o}
(long hungarian umlaut) is with a wave and not the proper umlaut.

could this be a problem with context's encodings?
i presume the lm fonts contain the right character...
it is certainly not that special :)

-f
-- 
part-time musicians are semiconductors.

  reply	other threads:[~2006-03-06 22:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 21:47 frantisek holop
2006-03-06 22:04 ` Taco Hoekwater
2006-03-06 22:50   ` frantisek holop [this message]
2006-03-07  8:28     ` Taco Hoekwater
2006-03-07 10:12     ` Mojca Miklavec
2006-03-07 10:16       ` frantisek holop
2006-03-07 16:38         ` Mojca Miklavec

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=20060306225018.GR21773@obiit.org \
    --to=minusf@obiit.org \
    --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).