From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Trying to move from LaTeX to MKIV in MikTeX (Mojca Miklavec)
Date: Wed, 24 Nov 2010 09:57:44 +0100 [thread overview]
Message-ID: <AANLkTimDJ=tPYOeM0nmubWgMyi2zLXRyCxQmKA3O0nYo@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimd=-GkG3SjJssdhOxWgeeOt0pYEyjWQyZm6T23@mail.gmail.com>
On Wed, Nov 24, 2010 at 08:10, barney schwartz wrote:
>
> Thanks for trying to help, Here's what I do know so far. . .
>
> 1. Yes I bought TUG Lucida and have installed the fonts in c:\localtexmf and
> done fndb update via MikTeX 2.9 wizard.
> 2. Yes I also used 3rd party patch and installed those tfm files also in the
> localtexmf directory
What 3rd party patch exactly? After the fix in ConTeXt core one should
not need any 3rd part patch.
This package is obsolete:
http://modules.contextgarden.net/lucidabright
I need to reboot into windows in order to be able to test.
> Missing character: There is no ∘ (U+2218) in font c:/windows/fonts/LBRITE!
> Missing character: There is no ∘ (U+2218) in font c:/windows/fonts/LBRITE!
What exactly is this LBRITE font in c:/windows? That one is not
supposed to be used.
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2010-11-24 8:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 7:10 barney schwartz
2010-11-24 8:57 ` 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='AANLkTimDJ=tPYOeM0nmubWgMyi2zLXRyCxQmKA3O0nYo@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).