LWN: Comments on "Adobe's open source font experience"
http://lwn.net/Articles/564803/
This is a special feed containing comments posted
to the individual LWN article titled "Adobe's open source font experience".
hourly2Adobe's open source font experience
http://lwn.net/Articles/565654/rss
2013-09-04T10:50:34+00:00vimja
<div class="FormattedComment">
Just as a side note: Source Code Pro was the font used for the 29c3 logo and official texts:<br>
<p>
<a href="http://events.ccc.de/congress/2012/wiki/Propaganda#Basic_Rules_to_use_the_29C3_design">http://events.ccc.de/congress/2012/wiki/Propaganda#Basic_...</a><br>
</div>
Adobe's open source font experience
http://lwn.net/Articles/565472/rss
2013-09-02T17:25:49+00:00n8willis
<div class="FormattedComment">
Have you tried? I haven't, but some of its content includes things that are available for Linux (such as ttx), plus Python and Perl scripts that are likely usable either standalone or with FontForge. The compiled things for which there is no source available is what needs work on the company's side to turn into a real FOSS release, but I'm not sure if any of those would be usable with WINE; it's certainly possible, since they are pretty small and self-contained. I have not delved into it, but it may be quite usable. Getting a better picture of how usable it is would be a good first step toward eventually shaping a real Linux release further down the road.<br>
<p>
Nate<br>
</div>
Adobe's open source font experience
http://lwn.net/Articles/565399/rss
2013-08-30T21:50:16+00:00lsl
<div class="FormattedComment">
<font class="QuotedText">> AFDKO is free to download and use, and hoped that people would not let the EULA be an excuse to not get involved.</font><br>
<p>
If not the EULA then certainly the fact that the AFDKO is just plain unavailable for Linux (or any other free operating system).<br>
</div>
Adobe's open source font experience
http://lwn.net/Articles/565392/rss
2013-08-30T19:01:38+00:00jbailey
<div class="FormattedComment">
Please consider linking "most-viewed post" to the actual post. I think you mean <a href="http://blogs.adobe.com/typblography/2012/09/source-code-pro.html">http://blogs.adobe.com/typblography/2012/09/source-code-p...</a> but that's a guess.<br>
</div>
Cutups
http://lwn.net/Articles/565389/rss
2013-08-30T18:07:23+00:00k8to
<div class="FormattedComment">
Here are the fonts being compared:<br>
<p>
<a href="http://www.google.com/fonts#ReviewPlace:refine/Collection:Source+Code+Pro|Inconsolata">http://www.google.com/fonts#ReviewPlace:refine/Collection...</a><br>
<p>
to compare the Source Sans with the fixed width font would be silly.<br>
<p>
I must admit this particular rendering makes them look quite different, with inconsolata being much thicker. I have no idea if they are being handled differently in some way.<br>
</div>
Cutups
http://lwn.net/Articles/565388/rss
2013-08-30T17:56:44+00:00k8to
<div class="FormattedComment">
From the article, there are two fonts from Adobe, one is Sans Source Pro, which is monospaced.<br>
<p>
I'm too lazy to investigate the similarity under discussion.<br>
</div>
Adobe's open source font experience
http://lwn.net/Articles/565356/rss
2013-08-30T13:51:55+00:00n8willis
<div class="FormattedComment">
Nothing stops you from using either of the fonts for any purpose you choose.<br>
<p>
Nate<br>
</div>
Adobe's open source font experience
http://lwn.net/Articles/565340/rss
2013-08-30T06:24:28+00:00thedevil
<div class="FormattedComment">
"Brackets is a web application"<br>
<p>
IMO, that does not fundamentally change the situation.<br>
<p>
"it's a straightforward usability feature"<br>
<p>
why not work on a font that is genrally usable as replacement for<br>
Courier then? Or maybe I'm unfair and that's actually what they are<br>
doing, but that is not what your article suggests.<br>
<p>
</div>
Cutups
http://lwn.net/Articles/565311/rss
2013-08-29T20:08:33+00:00ncm
<div class="FormattedComment">
Yes, monospace fonts are converging on the Ur-monospace, the one true monospace of the gods. No, this is not plagiarism. It's Evolution in Action. Departures from the ur-norm exploit niches that enable them to compete in protected spaces.<br>
<p>
Falcons and hawks have similarly converged on the ur-raptor design from opposite branches of the avian tree. Owls exploit the nocturnal niche.<br>
</div>
Cutups
http://lwn.net/Articles/565310/rss
2013-08-29T19:14:16+00:00bvanheu
<div class="FormattedComment">
For the lazy:<br>
<p>
<a href="http://www.google.com/fonts#ReviewPlace:refine/Collection:Source+Sans+Pro|Inconsolata">http://www.google.com/fonts#ReviewPlace:refine/Collection...</a><br>
<p>
Click on the 'compare' tab.<br>
</div>
Cutups
http://lwn.net/Articles/565257/rss
2013-08-29T13:46:24+00:00n8willis
<div class="FormattedComment">
It's far simpler to just open up both fonts in the Google Fonts collection browser; in the "Compare" tab, the app will show the characters from both faces overlayed, so you can clearly see the differences.<br>
<p>
Nate<br>
</div>
Cutups
http://lwn.net/Articles/565245/rss
2013-08-29T13:42:37+00:00fb
<div class="FormattedComment">
(I am not an expert but I care about monospace fonts.)<br>
<p>
Aren't all newer monospace fonts sort of look a likes? I used Inconsolata for a number of years before settling at Ubuntu Monospace for all my coding needs. <br>
<p>
I just tried comparing Ubuntu Monospace with Source Code Pro and found (to my untrained eye) the usual problematic characters to be even closer to Ubuntu Monospace than to Inconsolata.<br>
<p>
Can you provide us with some (superimposed) image showing Inconsolata and Ubuntu Monospace with Source Code Pro? Honestly, IMHO if you super-impose any of these modern monospace fonts (Inconsolata, UbuntuMono, LiberationMono etc) and try hard to see plagiarism, you will be able to "see" it.<br>
<p>
BTW, does anyone knows of a tool that would allow me to achieve that easily? <br>
</div>
Adobe's open source font experience
http://lwn.net/Articles/565246/rss
2013-08-29T13:37:15+00:00n8willis
<div class="FormattedComment">
Brackets is a web application; they can deliver a better font via @font-face, so the user experience is better. I'm not seeing what's wrong with that. While they could just omit it and fall back on the browser's default monospaced font, then you'd get things like Courier's indistinguishable 0/O and 1/l. That has nothing to do with having the font "be recognizable;" it's a straightforward usability feature.<br>
<p>
Nate<br>
</div>
Adobe's open source font experience
http://lwn.net/Articles/565242/rss
2013-08-29T13:22:21+00:00corbet
This account says that too, toward the end...
Cutups
http://lwn.net/Articles/565224/rss
2013-08-29T11:39:51+00:00rsidd
<div class="FormattedComment">
Sorry my bad -- was confusing inconsolata with something else, and inconsolata is indeed open source -- but it is monospace and Source Sans isn't (the original blog post says the monospace ones are WIP) -- so I don't see your point. Nor do I see such a striking similarity in general.<br>
</div>
Cutups
http://lwn.net/Articles/565222/rss
2013-08-29T11:33:41+00:00rsidd
<div class="FormattedComment">
Can you point us uninitiated folks to the open-source Inconsolata project? <br>
</div>
Cutups
http://lwn.net/Articles/565214/rss
2013-08-29T11:09:24+00:00ncm
<div class="FormattedComment">
They are not bitmap fonts, but they are rendered on screens using pixels. On a typical 96 dpi laptop screen, the pixels end up in the same place.<br>
<p>
It's easy to examine precisely how the faces differ, or don't. In MATE or Gnome2, set one face as the default monospace font, and set the terminal emulator to use the the other face. In the terminal preferences page, rapidly flip the toggle that chooses between using the two, and watch which pixels stay the same, or bounce up and down predictably.<br>
<p>
Plagiarism is not possible with typefaces. Any typeface may be based on any other, although it's courteous to acknowledge one's sources, and to name yours in a way that prevents confusion. (Otherwise we might call SCP "Inconsolata Squat".) It's possible that both are derived from a common source. Raph acknowledges debts to Consolas and Bitstream Vera, among others.<br>
<p>
</div>
Adobe's open source font experience
http://lwn.net/Articles/565212/rss
2013-08-29T10:20:46+00:00pabs
<div class="FormattedComment">
In another account of this talk I read that Adobe are working on releasing AFDKO as free software:<br>
<p>
<a href="http://understandingfonts.com/blog/2013/08/typecon-portland/">http://understandingfonts.com/blog/2013/08/typecon-portland/</a><br>
</div>
Cutups
http://lwn.net/Articles/565182/rss
2013-08-29T05:12:12+00:00jubal
<div class="FormattedComment">
These are not bitmap fonts. (Also: do prove the plagiarism, please. Or GTFO.)<br>
</div>
Adobe's open source font experience
http://lwn.net/Articles/565180/rss
2013-08-29T04:50:49+00:00thedevil
<div class="FormattedComment">
Also, this<br>
<p>
"Adobe created the Source Sans Pro font because the company has been<br>
developing more open source software in recent years, and it needed<br>
fonts that it could incorporate into its releases"<br>
<p>
is dangerous nonsense. As if each application needed its own special<br>
font to be recognized by! Why not do the right thing and let the user<br>
choose one (or at most a very few) font for the entire "desktop"?<br>
Consistency, what a concept!!<br>
<p>
</div>
Cutups
http://lwn.net/Articles/565172/rss
2013-08-29T04:02:07+00:00ncm
Those guys at Adobe are almost as brilliantly subtle as The Onion. If you haven't paid <i>very</i> close attention, you might never guess it was all a jape.
<p>
But if you study Source Code Pro carefully, it turns out to be a pixel-by-pixel match to (the brilliant!) Inconsolata, except squashed a bit to make more leading, and replacing a few glyphs with wacky mutants. To make the switcheroo a little harder to spot, they shifted the point-size labels so that (e.g.) Source Code Pro 9 is a squashed Inconsolata 11, and similarly up and down the scale.
<p>
Good one.