ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: libertine otf file not recognised
Date: Thu, 08 Apr 2010 20:23:23 +0200	[thread overview]
Message-ID: <4BBE1F1B.3080108@elvenkind.com> (raw)
In-Reply-To: <749521.6327.qm@web57506.mail.re1.yahoo.com>

Salil Sayed wrote:
> I have the following problem with mkVI. (updated today)
> 
> __________________________________________________________________ 
> systems         : begin file env_manuscript at line 4 
> (../env_manuscript.tex (/media/documents/test/type-libertine.tex) 
> !define font    : forced type otf of
> /home/me/.fonts/LinLibertine_Re-4.4.1 not found !define font    :
> font with name /home/me/.fonts/LinLibertine_Re-4.4.1 is not found 
> !define font    : unknown font /home/me/.fonts/LinLibertine_Re-4.4.1,
> loading aborted !define font    : unable to define linuxlibertineo as
> \*Libertine11ptrmtf* ) systems         : end file env_manuscript at
> line 4 ) 
> __________________________________________________________________
> 
> the relevant line in my typescript is thus:
> 
> \definefontsynonym [LibertineRegular]   [name:linuxlibertineo]
> [features=default]
> 
> All other otf fonts in the same directory work. The libertine fonts
> (from the same files) work with other applications such as gedit,
> inkscape etc. (obviously not with openoffice)
> 
> What can be the problem?

Perhaps the version number in the file name (which contains dots).
IIRC, this or a similar issue popped up a few months ago. Perhaps
I even replied then.

Best wishes,
Taco
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2010-04-08 18:23 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 [this message]
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

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=4BBE1F1B.3080108@elvenkind.com \
    --to=taco@elvenkind.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).