Your best chance is asking the authors themselves: http://www.omnibus-type.com/

Maybe buy Univers Narrow eh?

hhp

How much do you spend on your cellphone bill? (Monthly...)

hhp

Hopefully they'll fix it quickly (and hopefully other problems won't pop up). In the meantime: individual weights of Univers are as low as $26. Since it's much less likely to cause technical headaches than a freebie it wouldn't be a waste. Unlike the lion's share of your cellphone bill, or your next dinner out.

Let's not confuse frugality (which I'm a huge fan of) with opportunistic penny-pinching.

hhp

Could you post a screenshot or even a screencast video to youtube?

Using CS4

I have just moved to CS6 and so I do not know how representative it will be. The fonts show up in the font menu but separated, the bold, bold italic and regular weights/styles appearing under "Archivo Narrow" and the italic appearing separately as "ArchivoNarrow-Italic".

Looking at the font files this appears to be the result of the naming conventions for the OT Family Name (TTX: nameID="16") field, which varies as follows for the four weights/styles:

Regular = Archivo Narrow
Italic = Archivo Narrow Italic
Bold = Archivo Narrow
Bold Italic = (none)

It should be a simple matter of updating the naming metadata to fix the above and have them all appear together in the font menu but if you are experiencing an issue with missing characters I can replicate the problem or see what might be causing it.

I get the same display but typing is fine, the expected characters come out. Perhaps something in the handling that differs between CS4 and CS6?

I could not identify any encoding issues within FontLab and DTL OTMaster only turned up issues relating to the metrics, which should not cause the problem you are encountering. Could you give an example of cause and effect, as in a character you type and the character that is displayed?

Glyph window comparison

An this seems to be the version info(?): Archivo Narrow Bold: 2012 Archivo Narrow Bold 1.002; ttfautohint (v0.8); ttfautohint (v0.8)

The left screenshot shows Archivo Narrow with its glyphs sorted by Glyph Index, not by Unicode (which ought to have been the only setting for Illustrator).

I find something strange in v1.002, quite possible related, or the immediate cause. The cmap table, determining the mapping between Unicode and font glyphs, seems correct for Platform 0 (Unicode) and Platform 3 (Windows). A snippet:

U+003E = greater   U+003F = question   U+0040 = at   U+0041 = A
U+0042 = B   U+0043 = C   U+0044 = D   U+0045 = E
U+0046 = F   U+0047 = G   U+0048 = H   U+0049 = I

However, for Platform 1 (Macintosh encoding), I see this:

U+0005 = B   U+0006 = C   U+0007 = D   U+0008 = E
U+0009 = F   U+000A = G   U+000B = H   U+000C = I
U+000D = J   U+000E = K   U+000F = L   U+0010 = M

As you can see, totally the wrong Unicodes. Most surprising of this is that Illustrator CS4 prefers a Macintosh encoding, even on a Windows system :^)

This problem cannot be fixed by a font user, it's up to the designer to repair it.

Thanks for pointing, Jens. So what?

1) I'm generally not paying anything out of my own pocket that a client should pay.

2) Asking for some quick advice online (my initial post) can be very valuable and time saving – sometimes, so hence I tried.

3) I don't mind to contribute a little to some community efforts (all my other posts in this thread)

Meanwhile I've done my visuals with Univers which I have on my computer, and will let the client know that the online version will look 'similar'. As you see from the face that I've replied, I'm not pressed for time...

Theunis: Thanks for your input.
Spirelli: We are working to fix the problem. Once we have the solution, I will notify you.
Thank you all for your time.

Pablo Cosgaya
Omnibus-Type Team

It takes three months to fix a cmap? Or did they just forget to come back and post here?

AFAIK the font fax fixed a few days after the problem was reported.