From: VnPenguin <vnpenguin@gmail.com>
Subject: Re: cont 2005.10.27 & t5-lmtt10 font problem
Date: Fri, 4 Nov 2005 11:21:22 +0100 [thread overview]
Message-ID: <e5d3f2650511040221n7a4e1401vc3d4a4a6bcf25956@mail.gmail.com> (raw)
In-Reply-To: <e06bd0fe0511040157k3c9bd44fh16f7781f6427e118@mail.gmail.com>
On 11/4/05, Tobias Wolf <towolf@gmail.com> wrote:
> Did you solve the problem for your installation? I have tetex 3.0 and
> lmodern from my distribution, but i copied the cont-lmt.zip into the
> main tree overwriting the files that came with the latin modern
> pakage, and still all I get are these mktexpk errors. Nothing works :(
No, I have not yet solution :(
--
http://vnoss.org
Vietnamese Open Source Software Community
next prev parent reply other threads:[~2005-11-04 10:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 21:45 VnPenguin
2005-11-01 22:17 ` Thomas A. Schmitz
2005-11-01 23:01 ` VnPenguin
2005-11-02 21:23 ` Tobias Wolf
2005-11-02 22:25 ` VnPenguin
2005-11-04 9:57 ` Tobias Wolf
2005-11-04 10:21 ` VnPenguin [this message]
2005-11-04 10:43 ` Taco Hoekwater
2005-11-04 12:44 ` Tobias Wolf
2005-11-04 13:38 ` Taco Hoekwater
2005-11-04 14:48 ` Tobias Wolf
2005-11-09 10:40 ` Hans Hagen
2005-11-04 15:17 ` Hans Hagen
2005-11-04 18:34 ` Tobias Wolf
2005-11-04 19:10 ` Taco Hoekwater
2005-11-04 21:30 ` Tobias Wolf
2005-11-09 8:30 ` Hans Hagen
2005-11-04 19:40 ` compiling pdftex docs (was: cont 2005.10.27 & t5-lmtt10 font problem) Taco Hoekwater
2005-11-04 21:15 ` Tobias Wolf
2005-11-04 22:15 ` compiling pdftex docs Taco Hoekwater
2005-11-05 10:59 ` compiling pdftex docs => BUG Taco Hoekwater
2005-11-09 8:34 ` compiling pdftex docs Hans Hagen
2005-11-09 8:28 ` cont 2005.10.27 & t5-lmtt10 font problem Hans Hagen
2005-11-07 10:16 ` Debian Installation (was: cont 2005.10.27 & t5-lmtt10 font problem) 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=e5d3f2650511040221n7a4e1401vc3d4a4a6bcf25956@mail.gmail.com \
--to=vnpenguin@gmail.com \
--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).