[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Google Summer of Code - Ideas List, please discuss
From: |
Carl Sorensen |
Subject: |
Re: Google Summer of Code - Ideas List, please discuss |
Date: |
Wed, 22 Feb 2012 17:29:16 +0000 |
User-agent: |
Microsoft-MacOutlook/14.14.0.111121 |
On 2/22/12 10:17 AM, "Han-Wen Nienhuys" <address@hidden> wrote:
>On Wed, Feb 22, 2012 at 3:12 PM, David Kastrup <address@hidden> wrote:
>> Han-Wen Nienhuys <address@hidden> writes:
>>
>>> On Wed, Feb 22, 2012 at 4:42 AM, David Kastrup <address@hidden> wrote:
>>>>>> Somewhat independently, there is a mf2pt1.pl Perl script that
>>>>>> (shudder) generates .pe script to transform a metapost output to a
>>>>>> Type 1 font. I guess that could be done more concisely directly as
>>>>>> a python script.
>>>>>
>>>>> This sounds like a very nice addition. Maybe generating Python
>>>>>should
>>>>> be the default, retaining the old .pe approach with as an option.
>>>>>The
>>>>> FontForge list is quite helpful in case questions arise.
>>>>>
>>>>> Scott Pakin, author of mf2pt1, will certainly add any improvements.
>>>>
>>>> There is also a program/utility Metatype in the TeX world, and it has
>>>> been used for generating various Type1 fonts from Metafont sources.
>>>
>>> This looks very outdated, and it seems to use autotrace. We abandoned
>>> traced outlines for exact conversions a few years ago.
>>
>> I should be surprised, actually. The Wikipedia page is at
>> <URL:http://en.wikipedia.org/wiki/METATYPE1>, and it explicitly states
>> that it can only work with filled outlines rather than pens, and the
>> toolchain processes the Bezier outlines from METAPOST. For an
>> autotraced outline, that would make no sense, and there is no mention of
>> any tracing tool in the process. I think that the Type1 versions of the
>> ec fonts were created with some kind of autotracing of large bitmaps,
>> but the Latin Modern fonts, as far as I know, were created using special
>> font sources adapted for Metatype1. The whole Metatype1 project came
>> into being because the Polish programmers did not consider the
>> autotraced bitmap fonts to be of sufficient quality.
>
>I was looking at http://metatype.sourceforge.net/ . Your wikipedia
>page doesn't host a live link, so I suppose the project died.
Metatype1 is hosted on a polish server:
http://www.gust.org.pl/projects/e-foundry/metatype1
and was updated in 2009 on the CTAN:
http://ctan.org/tex-archive/fonts/utilities/metatype1
Since it's now 2012, I guess one could say the project died.
The project is placed in the public domain, so we could include it in
LilyPond if we wanted to.
Thanks,
Carl
- Re: Google Summer of Code - Ideas List, please discuss, (continued)
- Re: Google Summer of Code - Ideas List, please discuss, Han-Wen Nienhuys, 2012/02/13
- Re: Google Summer of Code - Ideas List, please discuss, Reinhold Kainhofer, 2012/02/15
- Re: Google Summer of Code - Ideas List, please discuss, Janek Warchoł, 2012/02/21
- Re: Google Summer of Code - Ideas List, please discuss, Han-Wen Nienhuys, 2012/02/21
- Re: Google Summer of Code - Ideas List, please discuss, Werner LEMBERG, 2012/02/22
- Re: Google Summer of Code - Ideas List, please discuss, David Kastrup, 2012/02/22
- Re: Google Summer of Code - Ideas List, please discuss, Han-Wen Nienhuys, 2012/02/22
- Re: Google Summer of Code - Ideas List, please discuss, David Kastrup, 2012/02/22
- Re: Google Summer of Code - Ideas List, please discuss, Han-Wen Nienhuys, 2012/02/22
- Re: Google Summer of Code - Ideas List, please discuss,
Carl Sorensen <=
- Re: Google Summer of Code - Ideas List, please discuss, Werner LEMBERG, 2012/02/22
- Re: Google Summer of Code - Ideas List, please discuss, David Kastrup, 2012/02/22
- Re: Google Summer of Code - Ideas List, please discuss, Xavier Scheuer, 2012/02/22
Google Summer of Code - legal matters, FSF, Thorsten, 2012/02/27