ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: libertine otf file not recognised
Date: Sun, 04 Jul 2010 23:07:58 +0200	[thread overview]
Message-ID: <4C30F82E.2090102@wxs.nl> (raw)
In-Reply-To: <4C30CCF8.2010203@googlemail.com>

On 4-7-2010 8:03, Wolfgang Schuster wrote:
> Am 04.07.10 19:56, schrieb Vnpenguin:
>> On Sun, Jul 4, 2010 at 19:51, Wolfgang Schuster
>> <schuster.wolfgang@googlemail.com> wrote:
>>> Am 04.07.10 19:44, schrieb Vnpenguin:
>>>> But in PDF there is no Libertine font at all. I see only
>>>> "LMMono10-Regular" font.
>>> Please update the font database: mtxrun --script fonts --reload
>> The same. Nothing of Libertine font in PDF file.
>
> \setupbodyfont[libertine,rm]
>
> Don't know why but Hans made typewriter the default style for the libertine
> fonts and this is why you get LM Mono.

probably because i had no proper typewriter l at that time (or maybe it 
looked like crap), i also remember the biolinum being far from ok

so, these typescript can be adapted to the situation (we probably need 
to use the filenames used on tex live)

feel free to adapt them ..

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________


      parent reply	other threads:[~2010-07-04 21:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 13:00 minimal example of some problems Michael Saunders
2010-04-08 16:45 ` libertine otf file not recognised Salil Sayed
2010-04-08 18:23   ` Taco Hoekwater
2010-04-08 20:58     ` Wolfgang Schuster
2010-04-09  7:18       ` Salil Sayed
2010-04-09  7:45       ` streams! atleast the left||right synchronization mechanism Salil Sayed
2010-04-09  7:53         ` Wolfgang Schuster
2010-04-09  8:18           ` Salil Sayed
2010-07-04  9:54       ` libertine otf file not recognised Vnpenguin
2010-07-04 11:10         ` Wolfgang Schuster
2010-07-04 11:27           ` luigi scarso
2010-07-04 16:57           ` Vnpenguin
2010-07-04 17:00             ` Wolfgang Schuster
2010-07-04 17:44               ` Vnpenguin
2010-07-04 17:51                 ` Wolfgang Schuster
2010-07-04 17:56                   ` Vnpenguin
2010-07-04 18:03                     ` Wolfgang Schuster
2010-07-04 18:07                       ` Vnpenguin
2010-07-04 21:07                       ` Hans Hagen [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=4C30F82E.2090102@wxs.nl \
    --to=pragma@wxs.nl \
    --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).