ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: !pdfTeX error: pdftex (file lmmi12): Font lmmi12 at 600 not found
Date: Thu, 7 Feb 2008 16:27:00 +0100	[thread overview]
Message-ID: <6faad9f00802070727x561c03ebt5d41aad7191980f3@mail.gmail.com> (raw)
In-Reply-To: <47AB1D78.2060002@wxs.nl>

On Feb 7, 2008 4:02 PM, Hans Hagen wrote:
> Mojca Miklavec wrote:
> > Hello,
> >
> > I don't quite understand why, but my distribution became broken at
> > some random time point (I do not remember doing anything special in
> > the meantime). I have installed ConTeXt from scratch, but the same
> > problem persists:
>
> is your cont-sys.tex  or rme file gone? you need to set things like
>
> \autoloadmapfilestrue

Arghhhhhhh!!!

Please do not ask me how that was possible. I have created
cont-sys.tex and it automagically started to work. When comparing the
logs I have found out the following line:

system          : cont-sys.rme loaded
(./cont-sys.rme)
bodyfont        : 12pt rm is loaded

and then discovered that there was a file cont-sys.rme present in the
folder. But I have no idea how it came there nor where it came from as
it's considerably different from the one in distribution:

%D \module
%D   [       file=cont-sys,
%D        version=1995.10.10,
%D          title=\CONTEXT\ Miscellaneous Macros,
%D       subtitle=System Specific Setups,
%D         author=Hans Hagen,
%D           date=\currentdate,
%D      copyright={PRAGMA / Hans Hagen \& Ton Otten}]
%C
%C This module is part of the \CONTEXT\ macro||package and is
%C therefore copyrighted by \PRAGMA. See mreadme.pdf for
%C details.

\unprotect

% Here you can take care of overloading some (style)
% defaults. What goes here, depends on your local system.
%
% The following commands sets the default font encoding:
%
% \setupencoding [\s!default=ec]
%
% You can let \CONTEXT\ load the map files for \PDFTEX.
%
% \autoloadmapfilestrue
%
% If you use the more verbose naming scheme, uncomment this:
%
% \usetypescript [map] [default,\defaultencoding]
%
% or :
%
% \usetypescript [map] [all]
%
% In case you have set psfonts.map already, you can comment
% the following lines. Beware: pdftex uses the fontname
% (second entry on map file lines) for (not so) clever
% remapping, so in case of troubles, remove the names (is

Thanks a lot for the valuable remark,
    Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2008-02-07 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 14:14 Mojca Miklavec
2008-02-07 15:02 ` Hans Hagen
2008-02-07 15:27   ` Mojca Miklavec [this message]

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=6faad9f00802070727x561c03ebt5d41aad7191980f3@mail.gmail.com \
    --to=mojca.miklavec.lists@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).