« Previous | Main | Next »

Font Folio 10: Pay More For Less

According to the press release for Adobe's Font Folio "Open Type Edition", the new edition can be obtained as an upgrade for existing owners of Font Folio 8 or 9, for merely $2,499. What does this upgrade offer? Multi-platform and multi-lingual functionality, as well as wonderful tricks such as expanded glyph sets and optical weights. So far, so good. Problem No. 1 is the non-standardized feature set of OT fonts. Only a very small number of the included fonts offer expanded glyph sets and optical weights. The user expecting to find Bauer Bodoni or Garamond No. 3 with additional ligature support will be disappointed. Non standard charactersets constitute a recipe for customer confusion. Problem No. 2 is that the entire Berthold library has been removed since FF 9. Problem No. 3 is no multiple masters, which Adobe just stopped selling.

Problem No. 4 is that at the core of this "upgrade" transaction between Adobe and its existing Font Folio licensees lies another devaluing of the product already owned by customers. As an owner of Font Folio 8, Adobe offers to charge me $2,499 for a font license that is more restrictive than what I already have. Now only the Adobe "originals" ship with an editable embedding license, while all the Agfa, ITC, Linotype and Monotype fonts have new licensing which permits just read-only embedding. And this is now technologically enforceable. I can't help but wonder about the reaction of major advertising agencies and service bureaus when they find out that they have the privilege of paying for their font licensing to be more restrictive. I think they will keep on using Type 1.

Years ago I wrote on the OT list at length about the evils of digital signatures in fonts. It is simply a new copy protection ploy, and as everyone has known since the mid-1980s, copy protection = no sales. Supporters argue that the primary purpose of dig sigs is to help customers by allowing them to validate the "integrity" of fonts. Indeed?

Vive l'Open Type!

[The comments on this article are temporarily offline because one entry was gumming up our publishing system. They will be live again once the formating error is found and fixed. -- SJC]

Posted by | August 17, 2003 | LINK

Comments

The whole Font Folio concept is a bad deal to begin with. Practically speaking, most people use one or two fonts/weights per project. Why pay so much for something you'll never fully use? Reminds me of those unlimited cellular calling plans. It's a great scam for the phone company since they know that only 1 percent of the buyers will actually make enough calls to get their money's worth.

BTW, aren't you the one who claimed Jean-François Porchez copied Times New Roman for Le Monde Journal? Were those allegations ever substantiated? I'm just curious if his fame and notarity are justly deserved.

Albert Wu | Aug 18, 2003 07:57 PM

Well . . . service bureaus need complete libraries, though in this case, I imagine most would be better off with FF 8. I found FF 8 very handy when I was writing a lot about type. Believe me, when you're on deadline and need some obscure, God-forsaken type from the Adobe library to make a point, you don't have the time to make a separate request for that font or go through that insane Type On Call process; you just need the font. I expect, also, that large ad and design agencies do need to have instant access to these libraries.

That said, if I had a choice between FF8 and FF"10", I'd choose 8 anyday. And if I was a book designer with a lot of work to do, I'd gladly exchange the entire Adobe Library for Matthew Carter's Miller family.

Regarding Porchez, check out www.letimes.com (the cite that _celebrates_ type piracy) in a few weeks and the story on Porchez will be there in full -- along with some rather surprising new stuff. There's nothing on the site right now. I don't think I stated that Porchez "copied" Times for his Le Times font. What I think the screen shots I published a while back showed pretty conclusively, though, was that Porchez used the outlines in a unique cut of Times that Adobe distributed, for example, with Illustrator 6. In any case, there's no point talking about it til the screen shots are up again.

"Justly deserved"? Believe me, in the mid-90s, Porchez was telling everyone who would listen that he ripped off the Adobe outlines. This was even included in an interview in the ATypI daily from 1995, I think. The Dutch were all deeply shocked but I doubt if anyone else was.

But is it necessary to bring it up again? I'm sure Porchez is hot enough as it is.

Bill Troop | Aug 18, 2003 08:54 PM

Wait wait... lets back up here... digital signatures?? restrictive licensing??

kc! | Aug 18, 2003 09:38 PM

As has been explained dozens of times on the aforementioned OpenType list, digital signatures provide zero copy protection. They are simply a means of determining whether a font has been modified by someone other than the originator. You can copy a file as many times as you want, signature or no signature.

Microsoft has periodically hinted that a future OS revision will disallow unsigned fonts (and executables, scripts and other types of files in general) or at least provide the machine's administrator with the option of doing so. I was skeptical previously of how popular such an option would be, but after the MSBLAST festivities this weekend it seems that the MS crew might be on to something. I doubt dig-sigs will ever be compulsory in Windows. It would sell lots of Macs if they were.

John Butler | Aug 18, 2003 10:02 PM

Were those allegations ever substantiated?

Nope.

The Dutch were all deeply shocked but I doubt if anyone else was.

Typophile has a script that can perfectly simulate Bill Troop. I don't know if this is the real Bill posting this, or the script.

John Butler | Aug 18, 2003 10:07 PM

Bill, it's a shame anything you ever say about Adobe is tainted by a total lack of objectivity. Some valid points are mostly lost in the quicksand.

hhp

Hrant | Aug 18, 2003 10:26 PM

Here is some more info on digital signatures in fonts and in general.

John Butler | Aug 19, 2003 06:30 AM

Has anybody noticed that the "Ads by Google" on this page seems to be following the discussion? I guess that's how it's supposed to work. Just a little bit freaky, though.

Mark Simonson | Aug 19, 2003 08:05 AM

John, I hope you realize that the "official party line" is even more tainted than Bill's opinion of Adobe.

hhp

Hrant | Aug 19, 2003 08:25 AM

Are you talking about digital signatures, Hrant? If so, exactly what are MS &or Adobe saying about digital signatures that isn't true?

John Butler | Aug 19, 2003 08:51 AM

I'm talking about anything a corporation will say to deceive people into trusting them, in order to take their money away more easily. And often, the partial presentation of "facts" serves to deepen the deception. If we were to engage in a detailed technical discussion of what's "true", that would of course distract us from seeing the big sordid picture.

hhp

Hrant | Aug 19, 2003 09:38 AM

OK, so what are they not saying?

John Butler | Aug 19, 2003 10:27 AM

Why did Adobe change the licensing of the fonts? Won't that throw off existing customers?

Polly Madison | Aug 19, 2003 10:42 AM

Why did Adobe change the licensing of the fonts?

Because of this, I suspect.

John Butler | Aug 19, 2003 11:20 AM

> so what are they not saying?

That they will use things like digital signatures to milk you to their stockholders' satisfaction, of course.

BTW, I didn't mean to dismiss "factual" discussion in my previous post. If you could show that DigSigs simply cannot be used towards copy protection, that would be different.
But saying something like MS/Apple/Global-Tetrahedron doesn't intend to use DigSigs that way (because they said so in a press release!) holds no water.

hhp

Hrant | Aug 19, 2003 12:07 PM

Well, fantastic.
Fortunately, most of us live in free countries where we have the freedom to buy from other sources. Garamond 3? This is 2003, so let's move forward.

The Typophile foundry links list should get things started.

Sorry, I'm in a mood today.

Eric Olson | Aug 19, 2003 12:16 PM

> Garamond 3?

Indeed. Fart Folio 10. Masterworks like Kinesis-MM notwithstanding.

hhp

Hrant | Aug 19, 2003 12:21 PM

On the one hand, a few scholars and print professionals can really use the breadth of OpenType for multiple languages, or optional characters (built-in old style figures, ligatures, small caps, more fractions, etc.). I do not in any way deny these benefits.

However, for the vast majority of font users, Open Type is merely an undisguised step in cooperating corporations' self-serving attempt to ...

(1) make all the compact face files you've paid for seem old fashioned, obsolete, ... and probably unusable, one or two O.S. revisions from now.

(2) make us all covet bloatware fonts which more than a few amateur founders won't have the skills, or free or cheap software, to create, thereby competing with the big boys for the hearts and minds and coinage of the fonting public ... and

(3) Force us all to buy new versions of what we've already got in T1 or TT -- at monopoly pricing.

This being a type-loving forum; to the extent my analysis is all or partly true, some readers are probably aghast, while others are licking their lips and savoring this darling idea.

For all but a few users (and the self-serving promotors), Open Type is mainly a solution in search of a problem. Driven by marketing, not design. For the most, there will be no problem with current formats unless the conspiracy succeeds in eliminating support for them in favored applications.

If you haven't read it elsewhere, you read it here in August 2003

Tubby | Aug 19, 2003 01:29 PM

You're right, but you're not the first to say it! :-)

> Driven by marketing, not design.

Yes, the foundation of contemporary society.

hhp

Hrant | Aug 19, 2003 02:00 PM

On the other hand:
Now that OT is in place, we might as well as use it to the max.

hhp

Hrant | Aug 19, 2003 03:04 PM

The embedding issue is interesting. From my recollection Adobe originally limited embedding to read-only/print and preview when they were still making Type 1 fonts. So by offering their own library with editable embedding they're making things less restrictive, no?

This old font licensing FAQ (coughed up by Google) seems to back this up - http://www.adobe.com/type/topics/licenseqa.html, as does the fact that the TrueType fonts they shipped a while back had embedding bits set to P&P, not editable.

Cheers, Si

Si | Aug 19, 2003 03:28 PM

Whether you want to buy the new Font Folio is up to you.

If you have a previous version, the licence you obtained then will still be valid. I have Berthold face that I obtained from Adobe years ago. Berthold no longer has an agreement with them, but my fonts are still valid and legal.

So, for upgrades, you lose nothing. If the latest version isn't of interest, just don't buy it!

Adobe WANTS the other foundries to allow full use with PDFs - all Adobe fonts allow embedding in editable docs. Remember, they make Acrobat! Why would they want it crippled?

Nobody's forced to use OpenType, all major apps support Type one, of course. But, if you want to change languages without changing fonts, or compose arbitrary fractions, or have a series of contextual alternates in a script face, or set smallcaps easily, or...

Well, I don't think it's a nefarious plot.

John Nolan | Aug 19, 2003 04:03 PM

From section 2.6.5 of the Font Folio 8 End User Licensing Agreement: You may embed the font software, or outlines of the font software, in your electronic documents to the extent that the font vendor copyright owner allows for such embedding. The fonts contained in this package may contain both Adobe and non-Adobe owned fonts. You may fully embed any font owned by Adobe. Refer to the font sample or font information file to determine font ownership.

I can't find anything in any font samples or font information files mentioning embedding restrictions. This is the first time I have seen or heard about a Font Folio Embedding Permissions List anywhere. Nothing of the kind is on the Font Folio 8 media.

Over the past few months we have been wondering if we should switch to InDesign and Open Type, but now I'm too afraid to consider it. Embedding is too important for our workflow to make such a move.

Polly Madison | Aug 19, 2003 04:07 PM

I agree with Mr Nolan: I don't believe that Adobe is up to anything nefarious. What we're seeing is the result of several things, most of them technical, some of them legal.

When early license agreements were assembled by lawyers for Adobe and other foundries, the Portable Document Format was just a gleam in (some other division of) Adobe's eye. As Acrobat advanced and grew capable of more stuff, some foundries realised (a little late) that their code was being embedded in files in such a way that they could be pulled out by those interested in doing so. And they added new stipulations to their license agreements to protect their code / design / intellectual property.

OpenType, of course, has nothing whatsoever to do with the changes to the license agreements. Coincidence is what it is.

Adobe and Microsoft have done typography and typographers an immense service in developing the OpenType format; it is so much more capable than TrueType or Type 1 formats, and the fact that these two companies are behemoths means that the format will stick. (Unlike TrueType GX and Multiple Master.)

Will it take a while for other foundries to jump on board? Of course. There is a learning curve involved in developing new fonts in OT format - not to mention the extra time required to make several sets of figures and accented characters. It also takes time and effort to update old fonts to work as OT format.

But is it worth it? Not if you insist upon using QuarkXPress, which is still OpenType-negligent. But if you are using InDesign or PhotoShop (and future versions of these software programmes will doubtless be even more OT-aware) then you can avail yourself of many great and smart features of well-made OT fonts.

Wading through muddy waters,
c

chester | Aug 19, 2003 04:40 PM

I will be releasing my first opentype font in a few days and I found it really easy to do using the newest version of fontlab. My plan is to offer it free when you purchase the tt & ps versions. I think opentype is going to make fonts so much cooler and I'm really excited by it.

Jess Latham | Aug 19, 2003 08:43 PM

Please Eric Olson (and Hrant), try to keep your tastes in type out of this kind of discussion. Garamond 3 has nothing to do with the observations over Adobe's FontFolio, ethics and policies.
You have all the freedom you want to be disgusted by it, but I'd never say this seriously of your work.
I have no problem in "hate lists". I find funny doing them, but they are not meant to be "serious" (and even less critical).

Probably the italics of Jannon are absolutely my favorites (even more than the original Garamond ones). I'm not sure of the digitization quality of "Garamond 3" (which is a Jannon-based type).
I really was attracted into reading light-years before developing an interest on type by the Jannon faces. His italics are just great. You may be surprised but Peter Bilak loves them as well, and was inspired by them (conceptually, not graphically) for the italics of Fedra Serif. But I have no intention to suggest you should like them. Just try to leave out the "taste" element in a discussion which has nothing to do with your own tastes.

You may not like it, but here we are not talking of Comic Sans, c'mon. I may even end up trying to write a short piece on why Revue is good (Revue makes me vomit but I realize its value, even if mostly in historical perspective).

Claudio Piccinini | Aug 20, 2003 01:33 AM

Jess,
you go girl/guy! Using FontLab's OT Panel to encode your OT features is pretty easy. One word of advice: all of the sexy glyphs that you are adding outside of the 256 basics...

Using the Properties panel: Give each glyph a name, preferably the correct Unicode name*, get the Unicode number, set what kind of glyph it is ("Simple", "Ligature", etc.) Then "Apply". Very important to "Apply", or nothing sticks.

Good luck. Look after the trees and the forest will look after itself,
c


*Use this: http://partners.adobe.com/asn/tech/type/aglfn13.txt

chester | Aug 20, 2003 07:06 AM

> they are not meant to be "serious"

I'm always serious.

BTW:
1) It's not that Garamond 3 is as bad as CS, but it's just too affected and too old for most contemporary jobs.
2) The italic looks less affected because it's an italic.

Over the past few months I've been working with metal ATF Garamond (the predecessor to the #3), and although I might appreciate how nicely it conveyed the spirit of its time, its true value to me is the technical mastery in its optical scaling (due to Benton, not Jannon, or even the IN). But of course the #3 has none of that.

hhp

Hrant | Aug 20, 2003 08:17 AM

I designed a typeface for Headliners, which sold typesetting by the word at their chain of (40+, international) franchises, and I was paid my royalty on a per word basis. That was in the early 1980s.

No-one knows precisely where this technology is all headed, but many of us have positive general belief in things like Unicode, Open Type, and possibly Digital Signatures.

The future possibilities for automated payment systems based on Dig Sig documents are mind-boggling.

For instance, every time a graphic file is opened, the content creators could receive a royalty. Surely this kind of automation is being worked on. Isn't the iDisk concept heading that way?

It's a small step from incremental payments based on "click-throughs", to incremental payment based on "double clicks".

In principle, it's no different than when all those who have "points" in a movie get payment based on number of showings of the movie.

The trick is to make sure that if your work is involved in a project, you get paid percentage points. So it's a power play to decide what warrants that. Fonts may not be very obvious candidates, but they are always on the first wave of new technologies.

nick shinn | Aug 20, 2003 10:08 AM

I still don't get why foundries are so against font embedding in PDFs. As far as I'm concerned, a PDF is a final-output format...just like paper. The whole point of PDF is to have an electronic copy of what the paper version should be.

Yea, I know Adobe claims PDF to be much, much more, and maybe that's what some of the foundries are against, but still, what's the point of having a typeface if you can't use it in PDFs you create?

Darrel | Aug 20, 2003 11:50 AM

Because:
1) Fonts can be extracted from PDFs.
2) They can sue Adobe and get a settlement.

hhp

Hrant | Aug 20, 2003 12:34 PM

I'm pretty sick of Bill Troop trotting out this tale of piracy by JFP based on, at best, hearsay.

Bill's happy to say "in the ATypI daily it says blah..."

To the best of my knowledge Bill has never claimed to have been at the presentation JFP gave in Barcelona, or even at the ATypI conference in Barcelona at all.

I was at both, and here's exactly what happened.

I didn't know Jean-Francois at the time, I was hanging out in the TypeLab and JFP was about to give a lecture about Le Monde in the small lecture theatre there, it only seated about 50 and i don't remember there being much room to spare.

JFP tells the story of how he developed the font, at one stage he show Times on a separate layer to Le Monde to compare the two.

What you have to remember here is that you have a Frenchman who's English is pretty good, but he's going to use not quite the right term now and then. Giving a lecture in English to a mixed audience of native English speakers and those that, like JFP, speak it as a second language.

Got to be some confusion going on.

JFP certainly implied that he had copied the Times outlines from what he was saying, and "whoops" says I in the back of the room.

He finishes, and being the rabid anti-pirate that I am, and not really caring if I upset him (because I didn't know him at the time anyway), I asked him directly if he copied and manipulated the Times outlines. His explanation was that no, he had not, he had studied Times on prints to learn the craft of making a newspaper type. It seemed to me that the pasting the fonts into the background was something he'd done for the presentation - because he was talking about how a face for a French newspaper should differ from that of an English one.

He may have used the digital outlines for reference in his own development, I don't know for certain either way, but he certainly denied manipulating the Times outlines to create Le Monde.

You can imagine then that someone hasn't quite understood what has been said, and writes an article in English (not their native language) which implies something that didn't actually happen.

And years later you still have Bill repeating this hearsay.

So, can we please put this myth to bed?

clive bruton | Aug 20, 2003 02:30 PM

Le Clive, the internet's hearsay bobby, writes: "I'm pretty sick of Bill Troop trotting out this tale of piracy by JFP based on, at best, hearsay." -- missing the point as always. (1) I did not bring the matter up, someone else did. (2) I did not merely repeat some vague allegations. I rigorously compared LeTimes to every significant digitization of Times and came to the inescapable conclusion that LeTimes had been point-pirated from a specific Adobe cut of Times. I published these findings with enough screen shots to make the point. Where were you, Clive, typonaut, accountanaut, when all of this was going on? In any case, as soon as possible, I will put the content back up on LeTimes.com, the site intended to _celebrate_ type piracy. Let us please have no rancorous posturing when discussing these high matters! What is it I said? "The only un-pirate is the pirate you love..." ? And may I say this is frightfully off-topic?

Bill Troop | Aug 20, 2003 03:07 PM

Oh no, the two berserkers are here simultaneously.

> I don't know for certain either way

> can we please put this myth to bed?

First, make up your mind.

hhp

Hrant | Aug 20, 2003 03:33 PM

oh for godssake

j. lurie-terrell | Aug 20, 2003 03:50 PM

Hrant it's pretty clear, Bill's stated on more than one occasion that JFP manipulated the outlines from Times. His reference is something that appeared in a newssheet at the Barcelona conference, reviewing JFPs presentation - Bill was not even there. I was, and asked JFP specifically if that's what he did, and he said "no".

So there's the myth. Bill's claim that JFP said this in Barcelona is a lie. And, like Tony Blair's 45 minutes, it doesn't get any truer just because it gets repeated.

Whether JFP pasted Times in another FOG layer for comparing characters as he was designing, I don't know. But even if he did that's still not manipulating the Times data.

And either way no one knows, especially not Bill Troop.

Bill, you want to claim "off topic" but still repeat the same old lies.

I think you repeating things I've said as if they're something insighful is truly hilarious - keep it up.

Back on topic.

The Adobe Font Folio is a funny old beast, 35 of 500 or so packages actually having features or extended character sets, only three of those supporting greek and only two cyrillic.

So there's your multi-lingual effort.

JLT, put an apostrophe in it.

Clive Bruton | Aug 20, 2003 04:48 PM

Hey, look at that, I've even got a copy of the "Gaczeta" with the article in question.

Martin Majoor writes about a presentation that JFP gave, seems to be the same one I went to because a quick glance through the programme doesnt show two.

Martin writes it as if really JFP had copied the outlines from Times. Like I already wrote this was the impression JFP had given. But as I wrote I put this down to his use of English, rather than really what he meant.

Martin seems to not recall in his article that JFP was asked for clarification on this issue - and said "no" he did not copy/manipulate the outlines from Times.

In the "bag-o-stuff" I have from Barcelona there is an info sheet about Le Monde. It again makes comparisons to Times and shows the two fonts overlayed (they appear quite different to me). Martin's article also makes the point that Times was the face of Le Monde before JFP's new work - so I think it's logical to show that comparison.

As far as outline comparison goes, that is comparing points on specific faces, you're really on a losing track if you can't literally overlay the fonts and show that at least 50% of the points are identical. When you have two faces that have similar constructions and purposes the logical and "correct" placement of control points is going to lead to a good deal of similarity - real derivation is actually pretty difficult to distinguish.

I've done a few adaptions from faces myself (paying the appropriate licence fees), and even where it is known that one started off from a certain point, it is all but impossible to see the derivation - even though to lay person the fonts look the "same".

So, when Bill gets his PhD in forensic type digitisation, we can all sit up and take note. Until then it's hearsay at best, and outright lies at worst.

Clive Bruton | Aug 20, 2003 05:29 PM

a backroom whoops alerts jfp to the booboo he made during the presentation then a freak incident sneaking past many multilevel linguistic fauxpas end up in a daring article published at the atypi daily. the intrigue! the suspense! the thrill! what a friggin epic! i want movie rights with none other than pacino starring and no less than michael mann directing!

blive cruton | Aug 20, 2003 05:32 PM

Well, ask Bill nicely and he'll write the screenplay for you.

Clive Bruton | Aug 20, 2003 05:42 PM

Clive, not that I agree with Bill's stance, but you obviously have only a fraction of the information if you think JFP's "admission" is the whole basis for this. Although I wouldn't expect (or want) you to change your stance, you should really wait for Bill's site (or dig through the Type Design list archives, assuming the links still work).

> I've done a few adaptions from faces myself (paying the appropriate licence fees)

That's funny, I would think a stalwart (to use a tactful qualifier) protectionist like you would side with those who feel that a groveling request for written permission is more important than the money. Not to mention full public credit.

hhp

Hrant | Aug 20, 2003 08:14 PM

So in essence you are saying that Martin Majoor wrote falsehoods about Jean-Francois Porchez in the ATypI Gaczeta publication. Incredible! The Gaczeta editors let the story run and published it with the full knowledge that Porchez had denied his initial self-misrepresentation? Did Porchez request and obtain an apology or a correction of stance from Majoor or ATypI? I see Porchez now holds a high position on the ATypI board, so is it safe to presume that a proper public rectification of the error was made by Majoor or ATypI?

Nick Mitoulas | Aug 20, 2003 09:11 PM

I remember when fonts were a key thing in selling drawing programs. I would argue this in one thing Corel has been able to use in whacking Freehand and Illustrator over the head mercilessly (along with a much much faster screen refresh --I don't care how much of an AI or FH snob anyone might be, both are pathetically slow in their current versions).

Anyway, Adobe Illustrator 4.0 sucked big time. The only reason I bought it back in the early 1990's was for the wealth of Berthold fonts that came included with it. In later versions they slapped AI users in the face with Image Club knockoffs. Macromedia has stuck with the same, tired 500 URW fonts for several years now without any sign of update.

As far as font value with drawing programs go, Corel is king with their mix of 1000 fonts from Bitstream, ITC and others.

Font Folio 10? I don't care if it is OpenType or not. Withtout the Berthold stuff and their disavowment of Multiple Master format has me saying "no sale" big time.

I'm going to keep a couple old computers alive and well so I can keep using the MM fonts I paid too much money for! Screw that "we're not supporting them anymore" garbage. I won't give up on Penumbra.

Bobby Henderson | Aug 20, 2003 11:47 PM

Hrant, I don't know what other "evidence" Bill has, I've just seen him repeat this thing about Barcelona several times, and again here. Here's the first hand witness account - it's a lie.

As to adaptions of fonts, yes, of course, I've always gone to the foundry and asked permission. Sometimes that's been a bit difficult - but not because they want to protect their fonts, but because they want to do the work themselves (ie they want the client directly). But we get there in the end.

And yes of course, always give credit to the original.

Nick, you place far too much formality on the nature of the gaczeta, or any of the newssheets produced at ATypI conferences. The "editors" just take the material they are given at face value, happy to have something to fill up a blank page. Much of it is somewhat less than serious.

I suppose I am saying that Martin's report was false, or at least he too misunderstood what JFP had said. But I also understand that Martin and JFP are good friends and have a running joke about "stealing from the old blokes", or standing on the shoulders of giants if you like. While it's a bit difficult for me to read a joke into Martin's article, perhaps that is what e meant?

Either way, as I've stated a couple of times now, I asked JFP for clarification at the end of the presentation - from the back of the room, so everyone there should have understood the point – and he said "no".

I need to stress that the whole thrust of the presentation was somewhat forensic in nature, comparing the detais of Times to Le Monde, why and how those differnces came about.

I'm not saying that Times wasn't a big influence on JFP, it was undoubtably his main reference point for Le Monde (for all the reasons stated already). But that it's a definitive "no" on stealing the point data.

Clive Bruton | Aug 21, 2003 02:32 AM

> I don't know what other "evidence" Bill has

Yes, that was my point.

> perhaps that is what e meant?

Don't you realize how lopsided your "benefit of the doubt" is?

> he said "no".

But maybe that's when the language barrier kicked in? Why would something he told you off the cuff in semi-private be more reliable than something he said during a prepared public presentation, perhaps as a subsequent "correction" of sorts?

Again, just to be clear, this isn't a partisanship with Bill on this (his hamartia is too strong to make him reliable), just an attempt at uncovering bias.

hhp

Hrant | Aug 21, 2003 07:42 AM

> From: Hrant
> Because:
> 1) Fonts can be extracted from PDFs.

To do what, set a headline?
Plus most of those pdf-embedding restrictions are for large amounts of pdfs for big corps. which use the same fonts anyway for 90% of the time. So I don't think this can be a reason.

> From: Darrel
> As far as I'm concerned, a PDF is a final-output format...just like paper

True and therefor distributors shouldn't have such stupid licenses. It doens't make sense. When you print a book - do you pay for every copy that rolls of the presses? It's the same thing in these days.

As far as OT goes; it's great and it sure makes Type1 fonts look "old". No more buying two copies for PC/Mac (or creating your own version for the other platform)..
With FontFolio you get all the standard fonts most agencies want anyway and you'll probably get new Adobe OTs with the new release of FOntFolio as well - which is great.
At least academies should have it so student have enough choice.

rolf | Aug 21, 2003 09:17 AM

> To do what, set a headline?

No, dude. You can save out a font from FontLab.

hhp

Hrant | Aug 21, 2003 09:46 AM

> Yes, that was my point.

Well, I think I know he has no other evidence from Barcelona, and that's the only thing I'm commenting on.

>Don't you realize how lopsided your "benefit of the doubt" is?

I'm not sure who you think I'm giving that benefit too? Not to JFP, because I know what he said. I was leaving it open Martin was making a joke.

Thing to do here is ask Martin what his recollection of Barcelona eight years ago was - I know what mine is - and that's as clear as if it were yesterday.

>But maybe that's when the language barrier kicked in?
>Why would something he told you off the cuff in
>semi-private be more reliable than something he
>said during a prepared public presentation, perhaps
>as a subsequent "correction" of sorts?

You see the problem here is that you're reading more into this than actually exists, or has been stated.

First, this was more of an informal presentation. Yes JFP came prepared to show some work on Le Monde, but it was part of TypeLab, not the main conference, people were just turning up and talking - it wasn't a formal lecture.

JFP's style during the presentation was informal. As someone on site listening to it I say that what he said implied that he'd open the outlines to work on them, because of what he was also showing - ie here's Le Monde, then in the background you see Times.

When I asked him it wasn't "semi-private", it was in the course of answering questions about the presentation. There's no way you can construct that one part of this has more weight than the other.

Now you're going to think, "but that's exactly what you're doing". Right, but I'm applying more weight to the answer to a direct question than to something that was merely implied in the presentation.

If I had been sure of what he'd meant in the presentation there would have been no need to ask the question.

>Again, just to be clear, this isn't a partisanship with
>Bill on this (his hamartia is too strong to make him
>reliable), just an attempt at uncovering bias.

There's no bias on my part, as I stated previously I did not know JFP at the time, I'm just giving a true account of what happened during that presentation. I don't really have anything against Bill, I just think it's ridiculous that he keeps repeating something that he only heard/read second hand, especially when I know that's not the way things actually happened.

In fact, if you think about it, my bias would be more likely to run against JFP, if he had not reassured me back then that he had not "pirated the points" from Times. No?

clive bruton | Aug 21, 2003 09:50 AM

Rolf:
>No more buying two copies for PC/Mac

But the FontFolio always came with fonts for both platforms anyway!? So no advantage here.

clive bruton | Aug 21, 2003 09:54 AM

> that's the only thing I'm commenting on.

No you're not.

> I know what he said.

Which one?

> There's no way you can construct that one part of this has more weight than the other.

Then neither can you.

> No?

Who knows? We know now how you feel about people (like Bill, and me) who tolerate piracy when it's mild. It's just not a full moon at the moment.

hhp

Hrant | Aug 21, 2003 09:57 AM

Hrant, usual problem, you read what you want to read and ignore the rest.

Assemble a grand jury and I'll happily appear before it and tell exactly what I saw and heard. But I don't see the point in arguing it with you because you weren't there and neither was anyone else contributing to this thread (except, obviously, me).

Awooooooooo.

clive bruton | Aug 21, 2003 10:59 AM

They may have Whirling Dervishes, we have a Spinning Lycanthrope.

hhp

Hrant | Aug 21, 2003 11:02 AM

Hrant;
I meant what's the use of extracting a font from a pdf - aside from looking/admiring it. I mean w/ the kerning setting a heading is probably the only useful thing.
and running some quick auto kerning is not the way either if you really plan to use an extract font for much text.

all i'm saying is that having restrictive licenses for pdf embedding is kind of weird to me.. :)

rolf | Aug 21, 2003 11:21 AM

Clive:
But the FontFolio always came with fonts for both platforms anyway!? So no advantage here.

---

Sure, but just in the OT spirit that I'm all up for. Even without the extra features that OT has the fact that it is cross platform is a blessing, and already worth it :)

As far as FontFolio I would never get it, too expensive of course and not made for a one-man business. I do however think it's a useful library when you have a bigger agency and the money for it (or for academies).
OT is the future, not using it is like keep on using Photoshop 4 and Illustrator 6 (especially in about 2 years I think).. And the OT Pro versions of Adobe type faces are a well worth addition to Font Folio. I don't know how many *new* additions there are to the new FontFolio.....

rolf | Aug 21, 2003 11:30 AM

> >No more buying two copies for PC/Mac
>But the FontFolio always came with fonts
>for both platforms anyway!? So no advantage here.

Au contraire, mon ami Clive...

Amongst the loveliest things about OpenType is the fact that a (correctly-made) OTF works perfectly on both platforms. The very same file, not two different sets of files à la PostScript Type 1, or two different files à la TrueType.

So, one Unicode-stuffed OTF file will be equally happy and perform correctly on either Mac or Wintel machine.

As for the (side) discussion of Le Monde versus Times... I was not at that ATypI presentation either, so will take your word for what JFP said. I will throw my two centimes into the thread and state that Jean François Porchez is one of the most talented, intellectually rigorous, and original type designers alive. I cannot believe that he would plagiarise anyone or anything. It only makes sense that he might have compared his work on Le Monde against Times as he developed the face, to better understand the things that he was seeing in his tests.

And if he made presentation visuals which compared the forms of Le Monde and Times? So what! It's often illuminating to create such comparitive illustrations. Gerard Unger made a very convincing argument for his Gulliver typeface by comparing its text-fitting abilities with those of Times. Jonathan Hoefler and Tobias Frere-Jones show a comparison of the old WSJ stock list font, Helvetica Condensed, with the new font they developed, Retina Agate. We do the same thing at Thirstype; we compare and contrast, giving examples. It helps us demonstrate how our designs differ from already-published work, and it allows us to beat our chests with a marketing spin. ("Our new sans serif has 10% more calcium than the leading nation brand!")

With best regards,
c

chester | Aug 21, 2003 11:33 AM

>Au contraire, mon ami Clive...

Nothing contrary there, I know how OpenType works, but what I'm saying is you got (separate) fonts for both platforms anyway. It's not like suddenly you're buying the Mac version of FontFolio and getting Windows compatibility thrown in.

On the other matter, I think you have about the correct measure of it.

clive bruton | Aug 21, 2003 12:37 PM

As Si points out, I think our licensing is less restrictive with Font Folio OpenType Edition. What the new EULA says is that some fonts, such as all of the Adobe Originals fonts, are set for the less restrictive "Editable" embedding. We just wanted to make it clearer for customers.

I can also think of a number of advantages of OpenType. Yes, you used to get both platforms in FF9, but did you ever try to move documents across platforms even with the same fonts installed. Not always successful. Also, if you are on a PC do you know what PBO____.PFB is? (Palatino Bold). Finally, there is the whole issue of Unicode. To me this is the most important long-term benefit of OT.

Cheers,
Harold
Adobe Systems

Harold Grey, Adobe | Aug 21, 2003 12:55 PM

Hang on a minute, Harold. Less restrictive?
As I understand it, if I open a new document in Illustrator 11 beta, and type in a few words in your new, improved, opentype Dante STD, then try to save as a PDF, Illustrator won't let me embed the font. Is my understanding correct?

Bill Troop | Aug 21, 2003 03:58 PM

Regarding Clive and this off-topic discussion of Porchez and Le Times Roman: Clive, the Barcelona story was never important to me, and I don't recall commenting on it except in the most cursory manner. My comments, and the associated web pages, which you evidently missed, were based on a rigorous comparison of Le Times and Times, showing in total over 100 glyphs that were absolutely identical, point for point. Given that, there can be no argument that Porchez point-pirated the 1993 Adobe Times. (You know, sometimes, I wonder if I'm the only person in the online type community who actually examines type in Fog.)

Whether Le Times is a valid design statement, I am not competent to judge, as I have not looked at the type from the standpoint of usage. In any event, I think that question has been adequately answered by Le Monde's use of it.

It is also unquestionable that Porchez has later modified his design considerably, and has had it completely redigitized by a competent technician who was aware of the problems. We are only speaking of ancient history here. I suspect -- I don't know for a fact because I have not examined the latest data for Le Times -- that the latest version is non-infringing.

Two or three years later, in Canada, Porchez was still boasting about point-pirating Le Times, confirming what he told Majoor. But I am not interested in these stories. My opinion is based on my published examination of the data.

C'est un tangled web ou quoi?

Bill Troop | Aug 21, 2003 04:30 PM

Bill, I can't really see that the "Barcelona incident" is a minor point to you, since it's the only issue I've seen you raise and the only evidence you gave here.

I don't think JFP said anything different to Martin than he did to anyone else present at the presentation - that's what Martin's article is about.

JFP's statement, as the result of a direct question, was that he did not work into the Times outlines, he only studied the face for reference.

At what event was JFP "boasting" of this alleged point piracy?

I don't know what source you have for stating that JFP had someone else fix the outlines, AFAIK he's always digitised his own work.

I also find it very unlikely that, even if he had used the data, you could find 100 identical characters in a font given that the widths, cap and x-height are quite different.

I also don't really understand your comments about it being "unquestionable" that Le Monde has been modified over time. The implication being that this has been to disguise it as being "son of Times". I've samples from '95, and the distinction is clear enough there.

My recollection is that the face only went into production use earlier that year.

All I see here are "grassy knoll" conspiracy theories.

Clive Bruton | Aug 21, 2003 05:05 PM

I now invite the both of you to take the Le Monde discussion to private email where it will enjoy a small audience, similiar to its current count of 2 or 3.

Stephen Coles | Aug 21, 2003 05:13 PM

I would like to hear more from people about
Open Type and embedding.

Bill Troop | Aug 21, 2003 06:00 PM


>As I understand it, if I open a new document in Illustrator 11 beta, and type in a few words in your new, improved, opentype Dante STD, then try to save as a PDF, Illustrator won't let me embed the font. Is my understanding correct?

Hmmm, this doesn't make much sense. The AMT fonts are set to 'print and preview', the Adobe fonts are 'editable' - both are embeddable. The difference should only come into play when you try to 'edit' the document in which the font is embedded.

What you're describing is what I'd expect from a 'no embedding' font.

Si

Si | Aug 21, 2003 06:09 PM

...However if the app is not able to stop a user for editing text set in a P&P font it should not let you embed it. But that's an implementation issue related to the app - not the font license's fault.

Convert to curves?

Si | Aug 21, 2003 06:15 PM

> it's the only issue I've seen you raise

The pivotal word there being "I".

hhp

Hrant | Aug 21, 2003 06:33 PM

>I would like to hear more from people about Open Type and embedding.

Embedding...

PostScript Type 1 - a section in a hard to understand written license which probably doesn't relate to today's reality of PDF, Flash etc.,

TrueType & OpenType - a section in a hard to understand written license, also embedding permissions encoded within the font that should match the written license.

The license may also be included within the font file iteself along with a URL that links to online information about the font's license.

Si | Aug 21, 2003 06:44 PM

Hrant dispays his awesome omniscience yet again.

Si: From my recollection Adobe originally limited embedding to read-only/print and preview when they were still making Type 1 fonts

You mean in the OpenType fonts they offered?

I'm sure you know there are no embedding bits in Type 1. There is a control you can put in a PS font for Acrobat Distiller which prevents it being embedded in PDF though.

Clive Bruton | Aug 22, 2003 01:36 AM

Oh, and as stated, there's no copy protection in a DSIG.

If you want some clues as to where big software vendors are going with copy protection take a look at the new install procedures for XPress 6.0 and the methods Adobe is testing in Australia.

Clive Bruton | Aug 22, 2003 01:41 AM

>I now invite the both of you to take the Le Monde discussion to private email where it will enjoy a small audience, similiar to its current count of 2 or 3.

Greeeaaat! Stephen!!!
We really need more your (or someone else's) moderation. There was a point where there were at least two simultaneous discussion (not thread-related) going on. This is absurd.

My small viewpoint(s) on embedding:

1) I think a typeface stripped of its metrics has little or no value. Automatic kerning or whatever will never be able to replicate a visual approach;

2) Assumed you've extracted a weight (with no metrics), applied an "autokerning" or whatever, you'll still need to adjust it manually each time for headlines;

3) If you don't feel the need to do as per point 2) you are not really a professional, and neither a "collector" (the grey figure standing between the pirate, the junkie and the type historian);

4) If you are not a professional or a "collector", it's very unlikely you are able to use FontLab to output a really satisfying version of an extracted set of outlines. It could be good just to have the outlines as a reference, but I can't see real piracy as long as the typeface is not duplicated, hacked or actually used without a license.

5) There is a 1% of people which would still be willing (in their ignorance) to buy a hacked collection of typefaces. They are used by amateurs and in the end they vanish.

6) Real pirates and "collectors" are disgusted by hacked faces. They crave for the originals.

What do you think? (especially Adobe)

Claudio Piccinini | Aug 22, 2003 03:33 AM

P.S.
Stephen, could you remove all that [crap] about Porchez, LeMonde, Times, whatever?
It has nothing to do with this discussion and it makes the whole thread hard to read.

Claudio Piccinini | Aug 22, 2003 03:38 AM

> Automatic kerning or whatever will never be able to replicate a visual approach

In theory, a human will indeed do a better job than InDesign's optical spacing. But that assumes some key ingredients: talent, skill, motivation, time, etc... It's not surprising that in practice Indy does a better job than like 90% of type designers.

> you'll still need to adjust it manually each time for headlines

Not at all.

And what makes you think metric information is lost? Or do you mean just kerning. Anyway, do you realize how little kerning some very highly valuable (correction: valued) fonts have?

> it's very unlikely you are able to use FontLab to output a really satisfying version

Satisfying to whom? Most people would in fact be happy to get a free copy of a highly prized font no matter if it's a bit degraded. In fact, I would say that having inferior versions of a font floating around is more aggravating to a designer!

--

> could you remove all that [crap] about .... it makes the whole thread hard to read.

Is that the real reason you want it removed?

hhp

Hrant | Aug 22, 2003 07:56 AM

I agree with Harold Grey's comment that one of the great benefits of OpenType is Unicode support.

While only Adobe originals are the only "Pro" fonts is also understandable as Adobe owns the IP rights. The amount of work involved is not justified for other foundries fonts. And if Adobe permits the editing of their fonts while other foundries do not what is wrong in that?

If Adobe's motive with OpenType is to induce customers into purchasing InDesign, Photoshop and Illustrator then that is their right. Quark does not even support Unicode?

From the foundries included in Font Folio 8 neither Agfa, Berthold, ITC, Linotype (they market the Adobe otf fonts) or Monotype have released a commercial OpenType font. Why?

Currently with a Type 1 font the customer has to purchase a license for the Mac and Windows platforms as well as foreign language versions. One single OpenType font does not compare in revenue.

Nigel Hamilton | Aug 22, 2003 08:11 AM

Clive ...

>You mean in the OpenType fonts they offered?

No I was talking about the written license for their Type 1 fonts.

Si

Si | Aug 22, 2003 08:14 AM

OpenType crushes Type 1 single master, easily and decisively. My only problem with it is not with OpenType itself but with the combination of other factors that serve to confuse a type buyer.

Adobe sells OpenType versions of Joanna and Officina, but they don't contain the SC+OsF present in the Monotype and ITC versions, because those glyphs weren't included when Adobe did the original cross-licensing agreements. For Officina they might not even have been drawn yet. Both are called "Std." How is the type buyer supposed to know this, and how is Adobe supposed to explain it concisely and coherently?

But some fonts with names ending in "Std" can and do have features. In fact, the main criterion differentiating "Std" and "Pro" is whether or not it supports the whole Adobe Western character set. The only thing that the "Pro" suffix tells you for sure is that it supports CE and a few other codepages. Some "Pro" fonts contain Greek, others Cyrillic, and still others both. They don't have a uniform set of features because they can't (e.g. what's the point in a Trajan swash, etc.)

John Butler | Aug 22, 2003 08:30 AM

> My only problem with it is ....

While some of us have a problem with the actual raison-d'être of OT (even if we think it's technically wonderful). The less you look at the source of things the more you'll be manipulated.

hhp

Hrant | Aug 22, 2003 08:42 AM

John, your're right about that one. Clearly Adobe (in this case, but distributors/foundries in general) should provide *clear* info on what is exactly in the package when you buy it. Especially with smaller foundries you can easily write a mail if it's not listed and you'll get answers pretty quick. Don't know how long you have to wait till Adobe, ITC, URW++ or Linotype would take to answer the mail (and therefor should mention it online clearly).
I think Adobe made a good attempt in that direction already though, with the icons that state "all the fonts in this package include"...

Claudio, I agree with you totally on the embedding issue. Plus I can't even think about people that are selling extracted fonts with auto. kerning as the real thing? Haha, hilarious, plus the buyers are in that case pretty stupid.. I mean if you're going to buy type you know what you must look for not? And sure you will pick out fakes or don't trust cheesy looking home-burned cd's at discount stores at the corner of your street which has "ADOBE Fonts" on its cover ;)).

Hrant, I've never see of heard about anyone using extracted unkerned fonts for real jobs. Perhaps - like I earlier mentioned - some headlines on a flyer or poster..

But I don't think the issue (as far as the embedding restrictions) is extracting, I mean how many are there really that are being used or even been sold [haha] as real versions to dumb people? No, it's about font publishers/foundries that don't allow embedding in a pdf which you're going to mail out to 2000 people. And I really don't see a problem with that or understand why you need to pay more for font in that occassion. If the big corp. would print 4000 annuals you don't hear the foundry/publisher/distributor.. but when it's a PDF they want money. What if I print it and also want to put it online for other people? I don't understand it...


rolf | Aug 22, 2003 08:59 AM

> I've never see of heard about anyone using extracted unkerned fonts for real jobs.

What's real? Is fake smallcaps real? They're used by the biggest players in the field!

If you mean that certain types of piracy don't in fact affect font house profits, then I agree.

On the other hand, many fonts people pay a lot of money for have lousy or non-existent kerning.

BTW, I don't think many extracted fonts are sold, just distributed.

hhp

Hrant | Aug 22, 2003 09:31 AM

To me, the OpenType font collection by Adobe is a seriously higher standard in many cases. The "Pro" fonts are awesome. They have been reworked, cleaned up, many new glyphs have been added, and some completely new designs have been created. The power of automatic contextual ligature substitution in fonts such as Caflisch Script Pro actually make the font usable in productive work.

Imagine using a font with over 500 ligatures when it were split into several expert sets, and having to type "fake" keystrokes to get some particular ligature. Without OpenType, to get the word "offices" set with Caflisch Script using the glyphs o_f_f_i + c + e_s, I'd probably have to type something like "McG" and switch the font twice.

I should mention that the Pro fonts actually make it possible to get good typography in Polish, Czech, Hungarian and other languages that had been trated "stepmotherly" so far. Adobe helpd users in Central and Eastern Europe to fill the decades-long gap between their own typographic quality and that of the Western world.

But note that many of the "Std" fonts also are much more that pure conversions. The kerning sets have been expanded to really support all accented glyphs even in large fonts (thank you class kerning). And, in some cases, long-awaited revisions have been made (for example, in addition to the long-tailed "R" in Bembo -- that many hate --, there is also an alternate short-tailed "R").

Adobe's OpenTypes rock. Although I will still miss the Bertholds, I completely agree that Adobe has done the right thing to remove these fonts from sale. One thing I'll greatly miss greatly are the Multiple Master fonts. But none of them ever contained aogonek anyway, so what... ;)

Adam

Adam Twardoch | Aug 22, 2003 10:11 AM

The Adobe versions of the Berthold typefaces ae still available, just not from Adobe.

And what about Rotis series, where is the OpenType version?

Nigel Hamilton | Aug 22, 2003 10:21 AM

While some of us have a problem with the actual raison-d’être of OT (even if we think it’s technically wonderful). The less you look at the source of things the more you’ll be manipulated.

I'm sorry, Hrant, but could you possibly be more vague?

John Butler | Aug 22, 2003 12:02 PM

Yes, but work with that one first.

hhp

Hrant | Aug 22, 2003 12:17 PM

What's the problem, Hrant? Put up or shut up already.

John Butler | Aug 22, 2003 12:22 PM

Embedding.

I had a conversation with friend of mine a few days ago. He gave me the best reason, why we should look sceptical at embedding:

People tend to look at things the way they are at the moment. You should not forget about the possibillities the PDF format will offer in the future.
Imagine a re-editable PDF document which is used by your customers. He or she will send it to someone else, who will work with it. And so on.
This means, that the typeface, which has been imbedded, will be used over and over again by people, who never paid for it or even know they have to.

One could think of much more possible future PDF functionallity, but it should be enough to get the point.

---Jacques

PS: Paul v. d. L., thanks

fonthausen | Aug 22, 2003 01:06 PM

Jacques,

This is exactly why Adobe and Microsoft (primarily application vendors) prefer 'editable' fonts, these make our apps more useful.

And it's exactly why Agfa Monotype and others who primarily sell fonts prefer 'print & preview' embedding.

If I were a font vendor I'd make 'no embedding' fonts, and sell upgrades on request.

If I were buying fonts for my own use I'd only license editable fonts.

Cheers, Si

Si | Aug 22, 2003 01:19 PM

> Put up or shut up already.

John, you don't have to agree, but I know you're not dense. Plus now I'm confused if I should be more abstract or less. ;-)

hhp

Hrant | Aug 22, 2003 02:36 PM

While only Adobe originals are the only "Pro" fonts is also understandable as Adobe owns the IP rights.

This isn't even remotely true.

And Unicode is a red herring with most of Adobe's current OT fonts - they don't have the character sets to take advantage of it.

But, I suppose they'll get there one day.

Walter Racey | Aug 22, 2003 03:56 PM

And Unicode is a red herring with most of Adobe’s current OT fonts - they don’t have the character sets to take advantage of it.

Do you actually believe that's what Unicode is for? Making 65000-character fonts?

John Butler | Aug 22, 2003 08:14 PM

I'm curious, what proportion of Adobe's fonts have non-Latin (or extended-Latin) characters? If the MMs didn't support Polish for example (like Adam said), I wonder how much the typical Adobe font user benefits from Unicode.

hhp

Hrant | Aug 22, 2003 08:20 PM

Hrant:
Okay, if metrics information is not lost you have a quite usable font (it's right: well spaced faces need often very little kerning).
I've not said having hacked versions around is not a damage, I've just said it's more likely they'll vanish, in time, if they don't work so good. This puts the "display" faces more in danger than "textsetting" faces. But embedding is mostly done with text faces, to make pdf documents lighter.

In the end I keep thinking hacked faces are used mostly by non-professionals. This represents a big damage anyway, especially in countries with high piracy-rates (I think Italy ranks pretty higher, if not in pole-position). But I think it' quite unlikely amateurs and non-professionals have the knowledge and skills to extract a PDF and generate a usable face.
Most non-professionals does not even have a type design program.

But, in the end, what I wished to know (and you keep answering bits and pieces, Hrant) was your (of everyone) opinion on pdf embedding. Is that OK to you?
To me it is, and although I can see the problems, well, we'll always have them. Jeremy Tankard used to put a protection on some of his faces but real pirates or "collectors" managed to crack them anyway.
But I've hardly seen any Tankard face pirated or used by the mass of non-designers and non-professionals.
And even the Enschedè typefaces, so craved and copied by "collectors", I've never seen them actually used or hacked as Emigre faces (still being "trendy") have been. Tarzana and Mrs. Eaves are everywhere, and this is not because pirates hate Emigre: ordinary people look for Emigre fonts, and here in Italy you have a minority of designers buying a license.

Anyway, if we should vote I'd agree on allowing PDF embedding, and I'd like just to know your opinion.

>> could you remove all that [crap] about .… it makes >>the whole thread hard to read.

>Is that the real reason you want it removed?

No, it's to avoid you making stupid/useless comments (like this) as well.

Claudio Piccinini | Aug 23, 2003 03:01 AM

John wrote:
"Adobe sells OpenType versions of Joanna and Officina, but they don’t contain the SC+OsF present in the Monotype and ITC versions, because those glyphs weren’t included when Adobe did the original cross-licensing agreements. For Officina they might not even have been drawn yet. Both are called “Std.” How is the type buyer supposed to know this, and how is Adobe supposed to explain it concisely and coherently?

But some fonts with names ending in “Std” can and do have features. In fact, the main criterion differentiating “Std” and “Pro” is whether or not it supports the whole Adobe Western character set. The only thing that the “Pro” suffix tells you for sure is that it supports CE and a few other codepages. Some “Pro” fonts contain Greek, others Cyrillic, and still others both. They don’t have a uniform set of features because they can’t (e.g. what’s the point in a Trajan swash, etc.)"

This is a *very* good point, as usual coming from John.
And I keep saying I want good old exhaustive specimen sheets/booklets for each f***ing face I buy a license for, not some dumb collection like the FontFolio, handy for service bureaus but not for designers.

Claudio Piccinini | Aug 23, 2003 03:08 AM

I should add that Adobe has made the best possible effort to show the entire glyph set in every font on their website. (This should satisfy your demands, Claudio, although they don't all have text specimens.) It's just that the designations "Std" and "Pro" in the family names by their nature simply cannot convey in detail what the font contains, and so might not be worth including to begin with.

Oh, and let's not forget this is the first Font Folio with Euros in every single non-Pi font.

John Butler | Aug 23, 2003 08:28 AM

Claudio, I think embedding is worth the risk.

BTW, one man's stupid/useless is another man's chocolate. Do censor, but... v e r y _ c a r e f u l l y.

hhp

Hrant | Aug 23, 2003 09:53 AM

Jacques said: Imagine a re-editable PDF document which is used by your customers. He or she will send it to someone else, who will work with it. And so on.

That's the whole point, and it's an extremely useful feature. I often create PDF ads for clients, and those ads may have to be used for several months in different magazines. It's very handy if they can edit certain details like phone numbers and sales specials without me having to generate new files and bill them again. It's not like they're ever going to figure out how to extract fonts, or use them in a valuable way on their own.

Paul

Paul D | Aug 23, 2003 02:16 PM

But if you can modify an existing PDF document enough to end up with something that saves you from having to buy the font yourself...

Picture in fact a product line which is a series of document templates where you might be able to choose the font from "inside".

hhp

Hrant | Aug 23, 2003 07:36 PM

John: Do you actually believe that's what Unicode is for? Making 65000-character fonts?

Ha, that would be fun wouldn't it!

No, of course not. But there seems little point invoking Unicode when the character sets of the fonts in question support little more than the 8-bit PS versions already in circulation. The vast majority of Adobe's OpenType fonts only have the superset of Windows+MacOS Latin 1. This hardly seems something to be shouting about.

They don't even have Central European support.

In fact, more than anything, highlighting Unicode just shows off the shortcomings of these fonts.

Walter Racey | Aug 24, 2003 06:28 PM

I would not say these fonts have "shortcomings" compared to their Type 1 predecessors. Being able to get small caps, old style figures and swashes in Fairfield Std or Centaur through OpenType features sure beats doing it manually via Type 1.

But you raise an interesting point: perhaps Adobe should package the subsets of Font Folio fonts that contain CE, Cyrillic and Greek support. Some of the "Std" fonts contain Cyrillic (like ITC Baskerville and Helvetica.)

John Butler | Aug 25, 2003 04:02 AM

John

At least with a Type 1 small caps font you can access them in programs other than InDesign and Photoshop. What is the difference between switching fonts or turning the small caps feature on or off.

Nigel Hamilton | Aug 25, 2003 07:05 AM

Nigel, the focus on Small Caps may not help the argument for OpenType; since Small Caps often reside in the lowercase position in SC Type 1 fonts, all it takes is a font change and voila!

The cool thing about OT is that it doesn't change your text. In other words, you grab that text that your client has sent you in an email, set it nicely, turning on auto ligatures, so that all of your fi, fl, ff, fb, fk, ft, st, Th, ffz, Qu - whatever ligs you may have in your font - in place. You don't have to replace certain combinations with single glyphs from an expert font. AND when the client calls and asks you to send her the text as she deleted it by mistake, you can just copy the copy and paste it in your email file, and all of the letters are still ther; everything thta had been ligated is still there in the text.

One of the things I like best about OpenType is that you can tell fonts to set up much better in all-caps settings. You can set it up so that when the user selects All Caps from the OT menu, the letters are spaced wider, and parenthetics and punctuation center on the cap.

But again, the content is not altered: an 'a' is an 'a' is an 'a', but you can program OT to treat those 'a's differently depending upon their context.

And to get back to Small Caps... How often do you see heinous QXP-generated Small Caps? Good typographers will switch to proper Small Caps when setting type in QXP, but the 90%+ of designers who aren't "power users" of type will just click that little k button. Unfortunately, Quark does not understand OT, despite their having many many years to get with the program. (Guess they were too busy working out things like multiple undo and layers.)

I need coffee,
c

chester | Aug 25, 2003 07:28 AM

> How often do you see heinous QXP-generated Small Caps?

Pretty much 99% of the time. It might be painful to admit it, but virtually nobody uses smallcaps. And your 90% wouldn't even press "that little k button"...

hhp

Hrant | Aug 25, 2003 07:53 AM

Bright side: People who buy typefaces, such as the Adobe Font Folio, instead of relying upon system fonts and clipart fonts: those are the people who would use Small Caps properly.

This is all pretty far off-topic, isn't it?

Yep,
c

chester | Aug 25, 2003 09:12 AM

I work for one of the larger US statistics organizations. One of the methods we use for plausible surveying involves Acrobat forms. A lesser method involves Word forms. My employer's creative department will not license any font that cannot be embedded in forms. This is why I take issue with the move to restrict PDF embedding and enforce it in a new font format.

We are adamant about trying to hold high design standards, but there is only so much we can comply with before our workflow gets affected. The new format may be great, but if it paves the way for more PDF embedding restrictions, I don't think it can realistically be popular with my employer, or the numerous companies that compete with us.

I don't understand the embedding issue from the font vendor's perspective. If it is true that a vendor is afraid of font extraction from within the PDF, can the same argument not be made about Flash files, or even simple web bitmaps? On this very site I have seen a product announcement billing Scanfont's ability to construct fonts from any type of image. If a person wants a font badly enough, is she not able to use its many web showings to easily reproduce it with such products?

There must be a more valid reason for trying to restrict the embedding of fonts, or at least an understandable justification for selling a new technology that paradoxically improves workflow and restricts it at once.

Polly Madison | Aug 25, 2003 11:31 AM

All the Adobe Originals fonts in the Font Folio allow editable embedding. The stronger embedding restrictions on other fonts in Adobe's library, e.g. ITC and Monotype fonts, are the results of ITC and Monotype objecting. [Since they don't have their own portable document technology, this makes sense. Adobe and MS anticipated that not all foundries would want the same set of permissions in their fonts.] If you are designing forms in PDF, Adobe Originals fonts are probably the first fonts you should consider in your design precisely because of their liberal embedding policy.

The full list of originals can be found here.

The embedding flags in OpenType fonts are the same embedding flags found in TrueType fonts in general. Acrobat and Word check the same settings in every font. I don't know if Word allows CFF (.otf format) embedding in documents just yet.

John Butler | Aug 25, 2003 11:51 AM

Polly, be as adamant as you like, if you want that feature then some foundries are going to want to charge you an extra licensing fee.

The simple reason for this, and the reason you are "adamant" (Adam Ant!?), is that you get an added benefit from embedding software that was meant for rasterizing for print.

The reason font vendors see this embedding as a threat to their incomes is very well illustrated in this thread. Someone says he distributes ads for his clients to change, with the fonts embedded, you say you want your clients to fill in forms to your design standards - that's a lot of people using but not buying fonts.

If you don't like it, really, just send out pieces of paper - or use another font (hey, no compromise there in those design standards). Then you can clearly see that an embedding licence is something worth paying that bit extra for.

Walter Racey | Aug 25, 2003 11:52 AM

Polly,
when you buy a font, YOU pay the foundry an amount of money to get the official rights to use it.

If you'll send someone an editable PDF in the future*, which has all the thinkable features, the chance this person will pay the rights of usage are very, very small. But he or she will want to work with the given document. This is the problem.

You should not forget, people (clients) like to take things for granted, especially when it comes to topics like type. Even if you tell your customer to be aware, he or all the people following, will certainly not be.

---Jacques

* for example a presentation for a big corporate, for which a lot of external experts need to write a piece of text. The document will be sent to a dozen of people, who, logically won't see the need to pay for the typeface used by the corporate for its communication.

fonthausen | Aug 25, 2003 12:42 PM

> some foundries are going to want to charge you an extra licensing fee.

And those foundries will lose out...

> an embedding licence is something worth paying that bit extra for.

Are you kidding? People have trouble justifying just buying fonts at all!

hhp

Hrant | Aug 25, 2003 01:55 PM

There is an unfortunate misunderstanding being perpetuated throughout this thread, despite Simon's and John's efforts to clarify. Perhaps it can be made more clear.

Font embedding is not an all-or-nothing parameter. There are 3 (THREE) levels of embedding. to understand the differences visit Agfa's glossary.

It might help this thread and future discussions of font embedding.

CC

Carl Crossgrove | Aug 25, 2003 04:30 PM

Carl,
I doubt if there is a big difference in selling embeddable fonts, for which only a small percentage of the users will pay, or non-embeddable fonts, which won't sell if PDF might become the standard.

---Jacques

fonthausen | Aug 26, 2003 02:50 AM

>And those foundries will lose out...

IMO, the only winner here is Adobe, which really doesn't care about type - it's just a tool to sell more copies of Acrobat (or product X).

Just to note, when discussing licenses for embedding I was referring to extensions for editable embedding, not for sub-set view and print.

>Are you kidding? People have trouble justifying
>just buying fonts at all!

I don't think this is true. Individuals may have trouble justifying this to themselves (especially if they have access to pirated copies or don't care too much about quality), but commercial users understand the purpose of licensing, and will pay to have an additional feature (ie editable embedding) that they never had available previously.

Though perhaps you have better experience in font licensing?

Walter Racey | Aug 26, 2003 05:55 AM

> Though perhaps you have better experience in font licensing?

I have enough (read my site), but I have much more experience working in mid-size companies -and one really large university- where if you suggested that the fonts being used should actually be payed for, you'd get laughed at. Since I started my "working life", I've only managed to get one PTF font and a couple of Adobe fonts bought by my employers (who in total used hundreds of them), and only through a lot of pestering. And remember that few employees are type-freaks like me! Get real.

----

BTW, who are you, that you have to hide your identity for such mildly critical comments? And how do we know you have any experience in any of this? You could be Apostrophe.

hhp

Hrant | Aug 26, 2003 07:39 AM

What you're putting forward is piracy by your employers. If they are not happy to buy fonts at all, having an embedding license extension isn't going to make any difference to them at anyway.

What we should be concerned about is the people who want to be honest. The thieves will stay thieves, and one day they may get caught.

You could be a Comma(!?)

Walter Racey | Aug 26, 2003 11:00 AM

Nigel, the focus on Small Caps may not help the argument for OpenType; since Small Caps often reside in the lowercase position in SC Type 1 fonts, all it takes is a font change and voila!

This results in a document that used to refer to NASA and UNESCO referring to nasa and unesco. Yes, you get the smallcap appearance, but to do so you have to massacre your text. Using OpenType with the feature you maintain the text level distinction between upper- and lowercase characters. This is particularly important these days, when people are publishing to multiple media from a single document, including web and other electronic media in which control of display is often out of the publisher's hands. The Unicode character/glyph distinction as implemented by OpenType allows you to produce different qualities of typographic refinement without ever having to touch the text string.

John Hudson | Aug 26, 2003 11:06 AM

Oh, you must be Our President then...
People are not Evil or Good, everybody is a shade of gray - it's a matter of degrees, otherwise none of my employers would have bought any fonts. Any excuse you give them will make it harder for people like me to get them to pay up, sometimes.

What you need to be concerned about is reality. My employers have generally been pretty much average in terms of ethics.

----

Use your real name, jelly boy.

hhp

Hrant | Aug 26, 2003 11:14 AM

John: NASA and UNESCO referring to nasa and unesco

This kind of misses the point that some people think it's alright to write "Nasa" and "Unesco".

I'm not really sure there's any "correct" way to form small caps - should they be formed from lowercase, or uppercase. Whichever way you choose there are an equal number of arguments against.

Walter Racey | Aug 26, 2003 11:39 AM

sometimes

Sometimes it will, and sometime it won't. That's as it is right now, so no advantage/disadvantage perceived.

Oh, you must be Our President then…

No idea who your president is, you could be anywhere.

Use your real name, jelly boy.

One might even say the same of you, no one could possibly be called "H Rant"!

Walter Racey | Aug 26, 2003 11:46 AM

Walter and Hrant: please continue this discussion about Adobe, Font Folio, and OpenType without mentioning each other. Let's see how that goes.

Stephen Coles | Aug 26, 2003 11:58 AM

> so no advantage/disadvantage perceived.

What are you talking about? If the fonts my employers did buy had unfavorable embedding restrictions, the chances would be less they'd have consented to buying them. Duh.

If you're out to make people into saints, then sure, there's no point factoring in human nature. But if you're out to make more money in the retail font market, then pragmatism is your best tool.

And if you must cower behind a pseudonym (my name is ~3000 years old, btw) then it's in poor taste to use one derived from somebody who was such a gift to type design. Use "ratspine" or something.

hhp

Hrant | Aug 26, 2003 02:18 PM

How about those 3 levels of embedding. Is it somewhere clearly stated which level we are talking about in case of Font Folio? Is viewing/printing allowed in the ITCs or others with these restrictive licenses?

Walter, I don't think only Adobe benefits from this, just to sell more Acrobats. In fact, I welcome any other corporation beating Adobe creating something similar; pdf is a wonderful format regardless. ;)

I'd like to see some sort of license policy that would restrict big corps. like Sony or companies > 100 employees that gotta pay for embedding (editable docs?) and freelance designers get 'full granted licences' - haha

rolf | Aug 26, 2003 02:22 PM

Rolf,

What we're talking about is a setting in the font file itself, documented here... http://www.microsoft.com/typography/otspec/os2.htm#fst

A foundry or independent designer can make and licnese 'no embedding' fonts, but it's been my experience that most make 'print and preview' fonts, including ITC and AMT.

Note that these settings relate only embedding a font in a 'document file'. These settings give you no rights to embed the font within other types of file.

Si

Si | Aug 26, 2003 02:44 PM

How about those 3 levels of embedding. Is it somewhere clearly stated which level we are talking about in case of Font Folio? Is viewing/printing allowed in the ITCs or others with these restrictive licenses?

Yes, Adobe's OpenType fonts are "editable" embedding.

Walter, I don't think only Adobe benefits from this, just to sell more Acrobats. In fact, I welcome any other corporation beating Adobe creating something similar; pdf is a wonderful format regardless. ;)

I think Adobe's in a sensitive position, but isn't reacting very sensively to the concerns of some of its partners. It is offering fonts for sale in competition to some of those partners, and it is using its position to leverage the entire market to its own ends.

Yes, PDF is a great format, but Adobe can't be the only company that commercial gains from it - just because it has the muscle to do so.

I'd like to see some sort of license policy that would restrict big corps. like Sony or companies > 100 employees that gotta pay for embedding (editable docs?) and freelance designers get 'full granted licences' - haha

I suppose we'd all like everything for free. :-)

I think there is something to be said for "scalable" licensing, or more adaptive licensing, but the way things are right now we are kind of stuck with a blunt instrument - that was put together by Apple, without the benefit of an oracle, back in the late 80s.

In a perfect world I'd like to see cheaper fonts and less piracy - but there seems to be no will to do this (the software companies are only concerned about protecting their monolithic apps).

--

An aside: there are at least 19 other Racey’s listed in the NY telephone directory

Walter Racey | Aug 26, 2003 02:48 PM

Voice from the oracle: it may take another ten years but Adobe's default document structure is going to be PDF - Illustrator, Photoshop, InDesign... all will be opening and editing structured PDF and the "native" file formats will disappear.

Walter Racey | Aug 26, 2003 03:01 PM

> there are at least 19 other Racey’s
> listed in the NY telephone directory

And Nefertiti was a real Egyptian princess.

hhp

Nefertiti | Aug 26, 2003 03:08 PM


http://www.creativepro.com/story/feature/20045.html

Coincidence? Perhaps it's not just the Google ad's that are watching us!

Si | Aug 26, 2003 03:40 PM

>This kind of misses the point that some people think it's alright to write "Nasa" and "Unesco".

Not just some people; most English newspapers, including the Telegraph.

Bill Troop | Aug 26, 2003 06:14 PM

>I think Adobe’s in a sensitive position, but isn’t reacting very sensively to the concerns of some of its partners. It is offering fonts for sale in competition to some of those partners, and it is using its position to leverage the entire market to its own ends.

My personal view is much simpler. Adobe would have clearly preferred -- for simple marketing reasons -- to have all fonts in FF embeddable. Knowing this, the other foundries, who are perpetually whining about how little they got from Adobe, went to Adobe and said, give us x dollars or you can't embed. Adobe called their bluff and said -- have it your own way. It is difficult not to sympathize with Adobe in this particular situation, but I of course have not been privy to all the inside details.

Bill Troop | Aug 26, 2003 06:19 PM

With regard to the subject of extracted fonts which lack kerning, I have this to say:

Extracted fonts have the correct spacing, and that could be fine for text applications. Isn't it a little rash to suppose that a font has been well-kerned? Very few really are. There are many objectionable kerns typical of Bitstream and Adobe fonts. Have a look at the hardcover edition of Gitta Sereny's Speer. It's impeccably set in Minion, using all f-ligatures and oldstyle figures -- what a lot of work, given the font changes involved! And there isn't a single typographical error in the entire book. But if I recall correctly, this diligent, tasteful designer turned kerning off. Why? Because there is a lot to object to in Minion's kerning, as there is in much of the Adobe Originals.

My point is that it is silly to presuppose that kerning is desirable merely because someone put it there.

My feeling is that kerning can often be as obtrusive as lack of kerning can.

I have also reluctantly become convinced that nobody really understands the kerning of text faces besides Matthew Carter!

But if you look at his faces, they are carefully fitted so as to require a bare minimum of kerning. Most of his actual kerning is concerned with refinements that are somewhat out of the ordinary.

Bill Troop | Aug 26, 2003 06:30 PM

This kind of misses the point that some peo