From: "Bruce D\\\\\\'Arcus" <bdarcus.lists@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: typescript repository
Date: Wed, 25 Mar 2009 13:52:34 +0000 (UTC) [thread overview]
Message-ID: <loom.20090325T134827-268@post.gmane.org> (raw)
In-Reply-To: <20090325072442.GY14844@atos.labs.wmid.amu.edu.pl>
Marcin Borkowski <mbork <at> atos.wmid.amu.edu.pl> writes:
>
> Dnia Tue, Mar 24, 2009 at 05:14:49PM -0600, Idris Samawi Hamid ادريس سماوي
حامد napisał(a):
> > On Tue, 24 Mar 2009 09:27:09 -0600, Bruce D'Arcus
> > <bdarcus.lists <at> gmail.com> wrote:
> >
> > >c) that there's no reason at all to make a distinction between free
> > >and professional fonts in such a repository
> >
> > I absolutely agree with Bruce on this point
>
> And I strongly disagree. A repository of that kind would be a great
> idea, but at least one column in the table (price, or just "free: Y/N")
> would be very useful - especially for people like me, who cannot afford
> expensive commercial fonts.
OK, let me rephrase: I mean there's no reason to exclude commercial font
tyepscripts from the repository.
Also, I think it would be useful to include availability information in the file
(if possible) regardless of the whether it's free or commercial.
> And note that the distinction is *not* between "free" and
> "professional", but rather "free" and "commercial". Aren't LM or TeX
> Gyre professional;)?
You're right that my word choice was wrong. OTOH, I think LM looks like crap ;-)
But your wording is also a little loose; "free" is rather vague, and licensing
details matter quite a lot with fonts.
Bruce
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-03-25 13:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 20:30 Wolfgang Schuster
2009-03-23 20:32 ` luigi scarso
2009-03-23 21:20 ` Curiouslearn
2009-03-23 21:44 ` Peter Münster
2009-03-23 21:46 ` Aditya Mahajan
2009-03-23 21:51 ` Mohamed Bana
2009-03-23 22:11 ` Wolfgang Schuster
2009-03-24 15:27 ` Bruce D'Arcus
2009-03-24 17:39 ` Wolfgang Schuster
2009-03-25 3:08 ` Bruce D\'Arcus
2009-03-25 3:31 ` Mohamed Bana
2009-03-25 11:51 ` Wolfgang Schuster
2009-03-25 13:37 ` Mohamed Bana
2009-03-25 14:33 ` Wolfgang Schuster
2009-03-25 14:42 ` Mohamed Bana
2009-03-26 9:35 ` Henning Hraban Ramm
2009-03-26 10:00 ` Wolfgang Schuster
2009-03-24 23:14 ` Idris Samawi Hamid ادريس سماوي حامد
2009-03-25 7:24 ` Marcin Borkowski
2009-03-25 13:52 ` Bruce D\\\'Arcus [this message]
2009-03-25 14:30 ` Marcin Borkowski
2009-03-26 9:04 ` Hans Hagen
2009-03-26 9:13 ` Arthur Reutenauer
2009-03-26 9:23 ` luigi scarso
2009-03-26 9:29 ` Wolfgang Schuster
2009-03-26 9:50 ` Hans Hagen
2009-03-25 14:40 ` Wolfgang Schuster
2009-03-23 22:00 ` Diego Depaoli
2009-03-23 22:00 ` luigi scarso
2009-03-24 10:17 ` Alan Stone
2009-03-25 20:43 ` Wolfgang Schuster
2009-03-26 18:38 ` Mohamed Bana
2009-03-26 18:44 ` Aditya Mahajan
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=loom.20090325T134827-268@post.gmane.org \
--to=bdarcus.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).