[mpeg-OTspec] RE: name ID proposed changes

[Ken Lunde]

Sairus,

One thing to add would be that name.ID=20 is associated with legacy uses of CID-keyed fonts, meaning non-Unicode. For our CID-keyed OpenType/CFF fonts that are based on the Adobe-Identity-0 ROS, such as Kazuraki, we don't even bother including a name.ID=20 string. For CJK fonts that do include this string, the CMap resource that is specified is always a non-Unicode, such as 83pv-RJSJ-H (Shift-JIS), B5pc-H (Big Five), GBpc-EUC-H (EUC-CN), or KSCpc-EUC-H (EUC-KR).

In other words, it seems as though name.ID=20 use can be deprecated, or at least its importance deemphasized.

-- Ken

On Jun 13, 2014, at 3:00 PM, Sairus Patel sppatel at adobe.com [mpeg-OTspec] <mpeg-OTspec at yahoogroups.com> wrote:

> 
> The specs for name IDs 6 and 20 (which were proposed at the same time) certainly look out of place when compared with the specs for the other name IDs: they are lengthy and full of various implementation details and directives. Thanks, Josh, for taking the initiative to clean this up (that mythical redo of the ’name’ table may never happen, but we can chip away at it bit by bit).
> 
> I’ve chatted with a couple of folks here at Adobe, and we’re OK with what Josh proposes for name ID 6, so long as we do the same for name ID 20 (the specs for name IDs 6 and 20 refer to each other). So the normative part of name ID 20 would be:
> 
> <<<
> Name ID 20: PostScript CID findfont name; Its presence in a font means that the nameID 6 holds a PostScript font name that is meant to be used with the “composefont” invocation in order to invoke the font in a PostScript interpreter. See the definition of name ID 6.
> 
> The value held in the name ID 20 string is interpreted as a PostScript font name that is meant to be used with the “findfont” invocation, in order to invoke the font in a PostScript interpreter.
> 
> When translated to ASCII, this name string must be restricted to the printable ASCII subset, codes 33 through 126, except for the 10 characters: '[', ']', '(', ')', '{', '}', '<', '>', '/', '%’. See 'name' table section of clause 7 "Recommendations for OFF fonts" for additional information.
> >>>
> 
> The Recommendations section would include a "name ID 20” subsection that would contain the entire text of the currently published name ID 20 definition.
> 
> Vlad, I hope this helps and that you can move this forward.
> 
> Thanks,
> Sairus
> 
> From: <'Levantovsky>, "mpeg-OTspec at yahoogroups.com" <mpeg-OTspec at yahoogroups.com>
> Reply-To: Vladimir Levantovsky <Vladimir.Levantovsky at monotype.com>
> Date: Friday, June 13, 2014 at 12:37 PM
> To: Sairus Patel <sppatel at adobe.com>, "mpeg-OTspec at yahoogroups.com" <mpeg-OTspec at yahoogroups.com>
> Subject: [mpeg-OTspec] RE: name ID proposed changes [1 Attachment]
> 
>  
> 
> Bring the discussion back on the AHG list …
> 
>  
> 
> Hi Sairus,
> 
>  
> 
> The main purpose of the proposal from Josh (as I understand it) wasn’t to change the description of the Name ID 6 but to rather make it a non-normative, so that the font that doesn’t have both Name ID 6 strings defined for two platforms would still be considered a compliant font. Nothing else changes, and it following your response and other comments I simply moved the rest of the Name ID 6 description to the Recommendations section (see attached the latest version of the comments).
> 
>  
> 
> If you disagree with the proposed change as a whole, we can postpone it until the next time and I can still remove Name ID 6 related changes. Please let me know if you are okay with the way how proposed changes are defined now, or if you do want to remove them from the ballot comments.
> 
>  
> 
> Thank you,
> 
> Vlad
> 
> 
> 
>