|Subject:||Re: [ft-devel] Major bug with varfonts named instances when avar table present|
|Date:||Tue, 1 Aug 2017 15:00:33 +0100|
> What you mean is, it's not valid in this context.
Exactly. We are *only* talking about the valid `psid' values for
*named instances*! It's fully OK to restrict the possible indices
*for this specific case* to 6, 256-32767, and 0xFFFF.
> I'll ask Peter to remove it. Just because the spec says so, doesn't
> mean fonts wouldn't do otherwise.
I don't understand why you want that.
> My point is: nameid 0 is a valid nameid. By using 0 to mean "not
> set" in this context, you are requiring all clients of this
> particular API (fvar) to check for nameid==0 and call that invalid.
> In reality, most will forget and just pass it to the name table and
> get the copyright notice back. Just use 0xFFFF which is used for
> this purpose all across the spec.
I've just pushed a change to do that, as announced in a previous
|[Prev in Thread]||Current Thread||[Next in Thread]|