On Mon, Jun 14, 2010 at 5:23 PM, Nicolas Mailhot
wrote:
>
> Dejavu and Andrey Panov's Heuristica are two examples that get it right
> (good releases, in source format, with clear licensing and makefiles
> that just work, simple versions, changes tracked in a public vcs one can
> easily consult to
Le mardi 15 juin 2010 à 00:52 +0400, Alexandre Prokoudine a écrit :
> In other words, would it be considered polite to just distribute
> FontForge source and expect someone contribute a script that exports
> it to UFO or whatever, in case that someone really-really needs it?
At this point it wou
fontfree...@aol.com skribis:
> >We've got to start making these fontforge changes ourselves, but I'm
> >not happy working on a program that is written in glorified PDP-11
> >assembly language. Doing that is how I ended up disabled. :)
>
> Let me guess, you wish the whole thing was written in P
Khaled Hosny skribis:
> On Tue, Jun 15, 2010 at 05:12:30PM +0200, Ben Laenen wrote:
> > Khaled Hosny wrote:
> > > On Tue, Jun 15, 2010 at 09:32:48AM +0200, Ben Laenen wrote:
> > > > On Tue, Jun 15, 2010 at 3:53 AM, Peter Baker wrote:
> > > > > Couple of quick points. First, the FontForge format h
On Tue, Jun 15, 2010 at 05:12:30PM +0200, Ben Laenen wrote:
> Khaled Hosny wrote:
> > On Tue, Jun 15, 2010 at 09:32:48AM +0200, Ben Laenen wrote:
> > > On Tue, Jun 15, 2010 at 3:53 AM, Peter Baker wrote:
> > > > Couple of quick points. First, the FontForge format has always been
> > > > plain text
Khaled Hosny wrote:
> On Tue, Jun 15, 2010 at 09:32:48AM +0200, Ben Laenen wrote:
> > On Tue, Jun 15, 2010 at 3:53 AM, Peter Baker wrote:
> > > Couple of quick points. First, the FontForge format has always been
> > > plain text. It works well with CVS, SVN, etc.
> >
> > Only if you cut out the u
On Tue, Jun 15, 2010 at 09:32:48AM +0200, Ben Laenen wrote:
> On Tue, Jun 15, 2010 at 3:53 AM, Peter Baker wrote:
> > Couple of quick points. First, the FontForge format has always been
> > plain text. It works well with CVS, SVN, etc.
>
> Only if you cut out the unneeded bits like we do with Dej
On Tue, Jun 15, 2010 at 9:40 AM, Ben Laenen wrote:
> Dave Crossland wrote:
>> Like the XGF format?
>
> Don't know. But we need to have some distinction here between
>
> * how you edit the instructions in a program
> * how it's saved in the file
>
> Is the xgridfit format good to write down instruc
Dave Crossland wrote:
> Like the XGF format?
Don't know. But we need to have some distinction here between
* how you edit the instructions in a program
* how it's saved in the file
Is the xgridfit format good to write down instructions: I'm not a fan of it.
If you have to write down instruction
On 15 jun 2010, at 14:48, Ben Laenen wrote:
Erik van Blokland wrote:
Perhaps I can explain a bit about the state of support of hinting
data
in UFO. It is largely due to the different ways in which TrueType
hinting can be represented and the different expectations/formats
various editors have
Like the XGF format?
On 15 Jun 2010, 1:49 PM, "Ben Laenen" wrote:
Erik van Blokland wrote: > Perhaps I can explain a bit about the state of
support of hinting data > ...
Well, it's not exactly ambiguous how to store truetype hinting: you only
need
to define an xml syntax for each hinting instruc
Erik van Blokland wrote:
> Perhaps I can explain a bit about the state of support of hinting data
> in UFO. It is largely due to the different ways in which TrueType
> hinting can be represented and the different expectations/formats
> various editors have. We're trying to avoid having to dictate w
Op 15 jun 2010, om 12:15 heeft Barry Schwartz het volgende geschreven:
Hi,
> There is no way it would
> work for me; I've got my stuff in a combination of sfd, feature files,
> and python, with fontforge features hijacked to perform tasks for
> which they never were intended.
Yeah but that would
Alexandre Prokoudine skribis:
> I'm finally looking inside
> http://oflb.open-fonts.org/foo-open-font-sources-2.0.tar.gz that
> Nicolas mentioned during his talk at LGM. Is there some kind of
> description of the recommended workflow? Like doing everything in
> separate UFO files and then combinin
On Tue, 15 Jun 2010 09:39:32 +0100, Dave Crossland wrote:
> Where? :)
+1 :)
It was late and then I start to sound absolute :); so let me nuance: I
don’t think UFO is what you *should* use; it’s what I would probably
use for a project, and I am biased towards it because I have used it before
and
On 15 jun 2010, at 09:12, Ben Laenen wrote:
And the main reason why you shouldn't work with UFO *at this moment*
is that it doesn't support basic stuff like truetype hinting yet.
Perhaps I can explain a bit about the state of support of hinting data
in UFO. It is largely due to the differen
Where? :)
On 15 Jun 2010, 9:25 AM, "Barry Schwartz"
wrote:
Ben Laenen skribis:
> Anyway, FontForge's normalized SFD format is by far the best we've got >
for collaborative font de...
Actually, George Williams has recommended OpenType. As if to prove so,
he has those extra tables in which you c
Ben Laenen skribis:
> Anyway, FontForge's normalized SFD format is by far the best we've got
> for collaborative font development.
Actually, George Williams has recommended OpenType. As if to prove so,
he has those extra tables in which you can stash the same information
as would go into the sfd.
On Tue, Jun 15, 2010 at 9:32 AM, Ben Laenen wrote:
>> Strangely, the binary font formats remain very good for exchange. Both
>> the major editors read them!
>
> You'd still lose a lot of metadata though, like OpenType rule names
> for which there's no room in the ttf file. And it's absolutely not
On Tue, Jun 15, 2010 at 3:53 AM, Peter Baker wrote:
> Couple of quick points. First, the FontForge format has always been
> plain text. It works well with CVS, SVN, etc.
Only if you cut out the unneeded bits like we do with DejaVu. If we
would forget to run that script and commit a change to SVN
On Tue, Jun 15, 2010 at 12:03 AM, Schrijver wrote:
> The main reason why you would want to use UFO is that it is agnostic to the
> editor being used.
And the main reason why you shouldn't work with UFO *at this moment*
is that it doesn't support basic stuff like truetype hinting yet.
I know it'
On Monday, June 14, 2010, Schrijver
> You could actually come up with collaboration strategies around Fontforge’s
> own format too; I think they made a plain-text version of it for this
> purpose. (And I think this is in Nicolas’ templates as well). The main reason
> why you would want to use UF
>
>
> In other words, would it be considered polite to just distribute
> FontForge source and expect someone contribute a script that exports
> it to UFO or whatever, in case that someone really-really needs it?
>
> Alexandre Prokoudine
> http://libregraphicsworld.org
Well that depends. If you
On 6/15/10, Schrijver wrote:
> Generally, you won’t want to work on the UFO files directly, but you
> interface through an editor which can read and write UFO, like fontforge or
> the proprietary alternative.
I sort of suspected that :-P
> I guess internally fontforge then creates a fontforge pr
Hi Alexandre,
IIRC Nicolas doesn’t recommend a specific workflow,
rather, this template seeks to accommodate the various workflows people might
have.
Generally, you won’t want to work on the UFO files directly, but you interface
through an editor which can read and write UFO, like fontforge or
Hi,
I'm finally looking inside
http://oflb.open-fonts.org/foo-open-font-sources-2.0.tar.gz that
Nicolas mentioned during his talk at LGM. Is there some kind of
description of the recommended workflow? Like doing everything in
separate UFO files and then combining them in FF, or working on a
FontFo
26 matches
Mail list logo
