ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: Khaled Hosny <khaledhosny@eglug.org>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \nocap does not work
Date: Tue, 13 Apr 2010 14:00:39 +0200	[thread overview]
Message-ID: <4BC45CE7.1010701@wxs.nl> (raw)
In-Reply-To: <20100413110323.GB6300@khaled-laptop>

On 13-4-2010 1:03, Khaled Hosny wrote:

> Fontforge in script mode does not require X, mingw is enough, and AFAIK
> latest FF CVS can be compiled under mingw without patching. One can
> always run FF under some virtual machine etc. But to run Windows I need
> a Windows license which I cannot afford.

there are some issues when using it as library

also, you don't need a windows licence to run a program under wine (but 
i can be wrong)

> They have the very right to pick the tools they won't, but this is
> alienating many potential contributors, an that what I was complaining
> about.

well, it's their project and given their full agenda i can imagine that 
dealing with many contributers (managing) is not that high on their 
agenda; the couple of discussions there were when the fonts were 
developed (should this accent be a few nanometers more this or that way) 
already took quite some time and energy

as said: patches or suggestions with respect to ordening of the glyphs 
cq features are less problematic (and welcome) than endless discussions 
about shapes (and coming up with arguments why to reject them)

> They already shipped glyphs with such poor artistic value, being in the
> Ghostscript fonts is not an excuse, they could have resorted to the
> original URW fonts, which were released under GPL, from the start if
> quality is so high priority to them. So, I don't see how welcoming
> potential contributers can be any worse, it might actually improve the
> miserable state of some areas of the fonts.

the miserable shaped would have been improved if there had been any 
interest in it but a fact is that neither greek nor cyrillic users ever 
gave any feedback (about right shapes to start with) and as such they 
became a burden. Of course greek has to be brought in (maybe from px/tx) 
again when math is done.

of course, if someone would provide the perfect cyrillic / greek shapes 
that would be great but even then adding them officially should go 
through the team and be part of the normal assembling process

so, feel free to come up with or improve shapes (i suppose that the team 
wants them in metatype 1 format) ... the gust foundry people are quite 
open and show up at tex meetings on a regular basis (also to give 
detailed progress reports)

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
-----------------------------------------------------------------
___________________________________________________________________________________
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-04-13 12:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 13:47 Marco
2010-04-12 17:26 ` Wolfgang Schuster
2010-04-12 19:00   ` Hans Hagen
2010-04-12 19:23   ` Marco
2010-04-12 19:43     ` Khaled Hosny
2010-04-12 21:41       ` Hans Hagen
2010-04-12 22:58         ` Khaled Hosny
2010-04-13 10:13           ` Hans Hagen
2010-04-13 10:48             ` Arthur Reutenauer
2010-04-13 11:18               ` Khaled Hosny
2010-04-13 11:49               ` Hans Hagen
2010-04-13 11:54                 ` Arthur Reutenauer
2010-04-13 12:04                   ` Hans Hagen
2010-04-13 11:03             ` Khaled Hosny
2010-04-13 11:06               ` Arthur Reutenauer
2010-04-13 17:19                 ` Khaled Hosny
2010-04-13 17:37                   ` Taco Hoekwater
2010-04-13 18:03                     ` Khaled Hosny
2010-04-13 17:51                   ` Arthur Reutenauer
2010-04-13 18:07                     ` Khaled Hosny
2010-04-13 19:17                       ` Arthur Reutenauer
2010-04-14 11:19                         ` Khaled Hosny
2010-04-14 14:21                       ` Hans Hagen
2010-04-14 15:16                         ` Khaled Hosny
2010-04-14 15:38                           ` Arthur Reutenauer
2010-04-13 12:00               ` Hans Hagen [this message]
2010-04-13 17:16                 ` Khaled Hosny
2010-04-13 17:33                   ` Thomas A. Schmitz
2010-04-13 18:00                     ` Khaled Hosny
2010-04-12 23:21         ` Marco
2010-04-13 11:19     ` Wolfgang Schuster

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=4BC45CE7.1010701@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=khaledhosny@eglug.org \
    --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).