Hiya.

Thanks for the feedback and the reference! Please see also my separate 
answer to Character's findings.

When you say "yours open for me", do you mean the woff versions, or the 
OTFs I produced from them? Because the OTFs are effectively 
'conversions', although I have tried to *not* convert the glyph 
information from PS to TTF or vice versa.

I didn't mention how I got to the woff versions in the first place, but 
that's simple: Using the Chrome browser, open the Developer Tools 
window. When the page with teh woffs is loaded, the fonts show up in the 
Resources pane (with a neat little preview for each when selected!). 
Double clicking the woff name will download them, but in most cases one 
has to add the .woff extension by hand.

I also found that this works for the TypeKit site as well, but the woffs 
are encoded there as data stream. Double clicking these download an 
untitled file. I just added the .woff extension and I was good to go.

So again, thanks for thinking along!

Arthur

Op 25-08-12 19:45, Elaine schreef:
> LeFly wrote:
>
>> Should you want to try this for yourself, I have included the unaltered
>> woff-files as well.
>
> Thanks.
>
>> The fonts seem complete and fault-free, although I can not be sure they
>> are technically exactly identical to the 'real' ones.
>
> Not identical, no. And Character has pointed out the name problems
> already. The number of characters seems about right. The originals are
> kerned, though. Other than those two things, yours look okay.
>
> At least yours do open for me. My hd is full of web font extracts that
> I can't get to work *at all* without converting to another format
> (something I like to avoid!).
>
> Original Effra family is attached for your reference.