gmane.comp.freedesktop.fonts

Re: [GFD] Re: [ft-devel] new CFF engine

Vernon Adams — 2013-05-03T14:07:31

Thomas (or others),
Could you recommned a few opentype fonts, with known good industry standard ps hints, that i could use for control tests of this new engine versus truetype on Freetype?

thanks

-v



On 1 May 2013, at 18:03, Thomas Phinney <tphinney-aP5ABqoqSTtUAgJt6FLh2g< at >public.gmane.org> wrote:

Re: [GFD] Re: [ft-devel] new CFF engine

Liam R E Quin — 2013-05-03T05:33:10


"better" is in many ways subjective. Distance from the viewer's eye to
the screen and the viewer's eyesight make a big difference.

People who wear glasses often prefer fonts that are not anti-aliased,
for example, especially at distances of under 18 inches/0.5 metres.

Ambient lighting can also make a difference.

Having said that, hinting for Type 1 / CFF fonts is very important, e.g.
to get the three vertical strokes of "m" to be the same thickness (if
that's desired by the design) at low resolutions.

Liam

Re: Fwd: [ft-devel] new CFF engine

Dave Crossland — 2013-05-03T04:33:56

I have unsubscribed you :-)

Re: [GFD] Re: [ft-devel] new CFF engine

Vernon Adams — 2013-05-03T01:29:18

I might well do a little of that, not that i have any free time :) …but… 
I'm very curious to see how desktop UI fonts render under this new freetype CFF autohinter. 

One thing i have noticed when testing UI fonts on android and Chrome (both use a tweaked freetype) is that unhinted truetype fonts render better than ttfautohinted or manual hinted fonts. The freetype bytecode interpreter on those OS's (especially on a hi res screen) seems to result in too harsh rendering with hinted truetype fonts. I'm curious if the new CFF interpreter will bring opentype fonts to the first choice as a UI font.

-v


On 1 May 2013, at 18:05, Thomas Phinney <tphinney-aP5ABqoqSTtUAgJt6FLh2g< at >public.gmane.org> wrote:

Re: [GFD] Re: [ft-devel] new CFF engine

Barry Schwartz — 2013-05-02T19:41:11

vernon adams <vern-nztp2eEOrCR84o+VKJ9KNPXRex20P6io< at >public.gmane.org> skribis:

I would assume they did it to advance the state of the art and support
human progress. For years I’ve been wanting them to do this for
exactly that reason. Also Google asked Adobe nicely (I assume),
because Google wanted to advance the state of the art, support human
progress, and make money doing so.

It is not good to withhold knowledge of how to render fonts well, when
that’s not even a source of income due to the withholding, and when
obviously most of the rest of the industry hasn’t the vaguest clue how
to render a font, and causes extensive damage by trying
(unsuccessfully) to foist that job onto font designers.

Unsurprisingly this also makes good business sense. Perhaps full
openness a lot sooner could have prevented the existence of TrueType
in the first place.

Re: Fwd: [ft-devel] new CFF engine

Liam R E Quin — 2013-05-02T02:11:55

Much awesomeness and kudos to Adobe!

Liam

Re: [GFD] Re: [ft-devel] new CFF engine

vernon adams — 2013-05-01T23:46:47

So (their) fonts would look better rendered on screens? 

On 1 May 2013, at 16:44, Claus Eggers Sørensen <clauses-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: [GFD] Re: [ft-devel] new CFF engine

Dave Crossland — 2013-05-01T23:45:16

What patent?

Re: Fwd: [ft-devel] new CFF engine

Elliot Polinsky — 2013-05-01T18:35:56

Hi, could I unsubscribe from this list?  Thanks.


On Wed, May 1, 2013 at 2:15 PM, Dave Crossland <dave-yX7OcqChgmE< at >public.gmane.org> wrote:

Fwd: [ft-devel] new CFF engine

Dave Crossland — 2013-05-01T18:15:06

:D

---------- Forwarded message ----------
From: Werner LEMBERG <wl-mXXj517/zsQ< at >public.gmane.org>
Date: 1 May 2013 20:11
Subject: [ft-devel] new CFF engine
To: freetype-devel-qX2TKyscuCcdnm+yROfE0A< at >public.gmane.org

Folks,

Adobe, in collaboration with Google, has contributed a new CFF parsing
and hinting engine.  The last few months it was my job to fully
integrate the code into FreeType, and I'm very pleased with the
results.  Here are links to the relevant blogs:

  http://adobe.ly/12mJWGv
  http://google-opensource.blogspot.com/2013/05/got-cff.html

Look at the comparison images :-)

Below are the relevant parts of the CHANGES file (which also give
details how to enable it); as you can see, there are also a bunch of
improvements for ftview and ftdiff.

I plan to release 2.4.12 in about a week.

  Please test and enjoy!

    Werner

======================================================================

    - We have another CFF parsing and hinting engine!  Written by Dave
      Arnold <darnold-dv/

Re: LGM 2013 and libre typography

Vernon Adams — 2013-04-16T22:08:42

yep. I simply removed the parenthese from around the url links, so the links worked.
Will add some proper comments later :)

On 16 Apr 2013, at 02:38, Raphaël Bastide <raphael.bastide-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: LGM 2013 and libre typography

Dave Crossland — 2013-04-16T21:52:04

Thanks! I took a quick pass over it. Will dive in to more detail later

LGM 2013 and libre typography

Raphaël Bastide — 2013-04-16T09:38:19

Hello,

Here is a draft for a summary concerning the emerging projects around Libre
typography. As this is an open text, feel free to correct and complete it.
This text could be used as LGM report as well.

http://titanpad.com/lgm13-typography

Cheers,

Raphaël Bastide
raphaelbastide.com

Re: more font categories for OFL

Dave Crossland — 2013-04-11T23:56:21

Here is the contents of the pad from the LGM at http://piratepad.net/9yWPMBaJWE


Open Font Library Catalog-a-thon < at > LGM 2013
==========================================
People Present
------------------------------------
This pad text is synchronized as you type, so that everyone viewing
this page sees the same text.  This allows you to collaborate
seamlessly on documents!

 Right now, the OFLB catalog contains 222 fonts at
http://openfontlibrary.org/en/catalogue
Step One
------------------------------------
Collecting our knowledge of where libre/open fonts are that we don't
currently have in the collection.
**Please add to these lists!**
Existing List
------------------------------------
The list on this OFLB page:
http://openfontlibrary.org/en/guidebook/existing_libre_open_fonts
Other large collections
------------------------------------
* Google Web Fonts
* FontSquirrel
* League of Movable Type
* SIL
http://www.alanwood.net/unicode/fonts.html
...these are big enough that they need to be treated separate

more font categories for OFL

Manuel Schmalstieg — 2013-04-11T23:32:02

Hey list,

After discussion this afternoon at LGM Madrid with Nathan and Dave, I have
the following proposal for the OpenFontLibrary website: let's add more
categories! More precisely, the common categories used by AtypI (VOX-ATypI
classification) as well as the British Standards Classification of
Typefaces (BS 2961:1967). More details here:
http://en.wikipedia.org/wiki/Vox-ATypI_classification

What's currently on the website:

Blackletter · 4
Dingbat · 12
Display · 38
Handwriting · 39
Monospaced · 12
Sans-serif · 63
Serif · 54

What should be therefore added:

Humanist Serif (or Humanist Classical)
Garalde (examples: EB Garamond, Crimson, Sorts Mill Goudy)
Transitional (example: Open Baskerville)
Didone (example: ADF Berenis)
Mechanistic or Slab Serif (example: Le Patin Helvete)
Grotesque (example: Lil Grotesk)
Neo-grotesque (examples: Chivo, Karla, News Cycle)
Geometric (examples: Futura Renner, Didact Gothic, Tex Gyre Adventor)
Humanist Sans-serif (or Humanist Lineal) (examples: DejaVu, Lato)

Fro

Catalogathon link

Nathan Willis — 2013-04-11T12:55:12

We're just getting started, but feel free to join:
http://piratepad.net/9yWPMBaJWE

Re: Library-a-thon at LGM?

Robert Martinez — 2013-03-03T20:11:29

I'm in, too. Lets see if I can be of some help :)

Re: Library-a-thon at LGM?

Nathan Willis — 2013-03-01T18:09:50

Got the notification from the LGM Planning Cabal that this session has been
*approved*.  The schedule itself is still in the depths of the drafting
process, so the exact date & time will come later.

But in the meantime, practice your restocking skills!

Nate

Announcing Libre Graphics magazine issue 2.1

Ricardo Lafuente — 2013-02-28T16:25:58

⤹⟷...⟺...⇄...sorry for cross-posting...⇄...⟺...⟷⤸


-----> Announcing Libre Graphics magazine issue 2.1 <-----

This February, Libre Graphics magazine (http://libregraphicsmag.com/) 
has reached a major milestone. We have published and shipped issue 2.1, 
the first number in our second volume. Titled 
"Localization/Internationalisation," this issue explores the unique 
problems of non-latin type, the hyper-localisation of custom clothing 
patterns and international visual languages, among other topics.

Launched at FOSDEM, this issue marks the beginning of our second volume 
of publication, and heralds our move towards an increasingly critical 
slant. Exploring not just how Free/Libre Open Source Software can be 
used to create high quality art and design, in volume 2, we see a 
growing emphasis on the cultural and social issues around F/LOSS and 
Free Culture. With 2.1, we discuss issues of regionality. We are 
currently seeking submissions 
(http://libregraphicsmag.com/2013/02/gendering-flo

Re: Library-a-thon at LGM?

Dave Crossland — 2013-02-15T20:30:58

Sounds great! I'll be there :)

Library-a-thon at LGM?

Nathan Willis — 2013-02-15T19:48:38

I proposed a workshop/hack-a-thon session for Libre Graphics Meeting (April
10-13 2013 in Madrid) dedicated to cataloging (and, with luck, importing)
as many open fonts as we can find into the OFLB db -- over the course of 2
hours, anyway.

Obviously we've had a lot of discussions over the past year or so about
what OFLB does, what it can or can't do, and how we might get it to do
those things.  This is orthogonal to that; my interest is just in making a
concerted full-court push to capture as much info out there as we can.  If
OFLB gets a reboot on a new platform, that's great; I'd just like it to
pick up a lot of additional records in the meantime, since we know they're
out there.

The hard part is undoubtedly finding and organizing the list of fonts --
especially individuals not listed in GWF or a foundry project.  That
includes verifying an acceptable license, which is not a given.  From
there, it will be deciding on the correct categorization (and other
metadata, like "description").  It is possible the