ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Problem following "OpenType installation basics for	ConTeXt" article
Date: Sun, 11 Sep 2005 19:52:49 +0200	[thread overview]
Message-ID: <43246EF1.8080209@wxs.nl> (raw)
In-Reply-To: <6faad9f005090913443325ef79@mail.gmail.com>

Mojca Miklavec wrote:

>Gavin Sinclair wrote:
>  
>
>>Greetings (first post),
>>
>>Adam Lindsay's recent article "OpenType installation basics for
>>ConTeXt" in The PracTeX Journal
>>(http://www.tug.org/pracjourn/2005-2/lindsay) is very well written.
>>Unfortunately, I was unable to perform the first step.
>>
>>As the article specified, I ran the command:
>>
>>$ texfont --ma --in --ve=public --co=torunska --lcdf --pre --va=liga,kern
>>
>>It started off OK, but failed to properly create the map file.
>>    
>>
>
>After playing a bit with TeXfont I figured out that it is pretty
>hopeless to try to use TeXfont under windows (esp. under MikTeX) until
>some code portions get fixed. You can replace single quotes by double
>quotes in line 900 of TeXfont, but that won't lead you much further.
>There are problems with slashes/backslashes as well (the developers
>use linux & mac and probably nobody ever checked the functionality
>under windows besides the fact that I had problems with otftotfm
>alone).
>
>  
>
the problem is limited to the otf part ... the rest works ok for me on 
windows

>In the mean time, it's perhaps possible to use linux to make font
>metrics/map files and copy them to windows partition again or to
>manually call the otftotfm program and make a map file by yourself.
>  
>
we can set up a font repository ... 

Hans 

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

      parent reply	other threads:[~2005-09-11 17:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-03  5:42 Gavin Sinclair
2005-09-07  6:27 ` Adam Lindsay
2005-09-07  8:17   ` Gavin Sinclair
2005-09-07  8:37     ` Taco Hoekwater
2005-09-07 15:54     ` Mojca Miklavec
2005-09-08  6:51       ` Gavin Sinclair
2005-09-08  7:58         ` Hans Hagen
2005-09-08 15:13           ` Gavin Sinclair
2005-09-08 15:31             ` Hans Hagen
2005-09-09 15:29             ` Linux and Context on 64 bit luigi.scarso
2005-09-09 15:44               ` Taco Hoekwater
2005-09-09 16:41                 ` luigi.scarso
2005-09-09 17:48                   ` Taco Hoekwater
2005-09-12 21:03                   ` Stuart Jansen
2005-09-14 12:43                 ` luigi.scarso
2005-09-14 13:11                   ` Taco Hoekwater
2005-09-09 22:09               ` VnPenguin
2005-09-12  7:24                 ` luigi.scarso
2005-09-09 20:44 ` Problem following "OpenType installation basics for ConTeXt" article Mojca Miklavec
2005-09-10 10:50   ` Gavin Sinclair
2005-09-11 17:52   ` 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=43246EF1.8080209@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).