cannot install Noto Sans CJK multilingual OTF after Noto Sans CJK OTC is installed, or vice versa

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install Noto Sans CJK OTC
2. Install Noto Sans CJK multilingual OTF

What is the expected output? What do you see instead?
got duplicate font error message. expect to install both successfully. 
Swap step 1 and 2, I will get the same error message.

What version of the product are you using? On what operating system?
In installed latest gold mater version on Mac OSX 10.9.3

Please provide any additional information below.
As mentioned above, I cannot install multilingual OTF after OTC is installed, 
or vice versa. Is it intended or error? They have different font family names:
- multilingual OTC: Noto Sans CJK Simplified Chinese, Noto Sans CJK Traditional 
Chinese, Noto Sans CJK Japanese, Noto Sans CJK Korean
- multilingual OTF: Noto Sans CJK. 
- (monolingual OTFs: Noto Sans S Chinese; Noto Sans T Chinese, Noto Sans 
Japanese, Noto Sans Korean)

So, I am confused on why I still got the duplicate font error. Can this because 
of the same file name? OTC's file name is NotoSansCJK-regular.otc. Multilingual 
OTF's file name is NotoSansCJK-regular.otf.

Original issue reported on code.google.com by xian...@google.com on 29 Jul 2014 at 10:53

[GoogleCodeExporter]

This is intentional, and the reason is because both share the same PostScript 
name as specified in the 'CFF' table. It has nothing to do with the file names.

There is no reason to install both the multilingual OTFs and the OTCs. The 
Japanese font instance of the OTCs is identical to the corresponding 
multilingual OTF except for the menu names and the presence of the 'hngl' GSUB 
feature in the multilingual OTFs.

If you're in an environment that consumes OTCs, install the OTCs. Otherwise, 
install the multilingual OTFs.

Original comment by ken.lu...@gmail.com on 30 Jul 2014 at 2:41

[GoogleCodeExporter]

End users will not want to do this and making it so that it doesn't happen is a 
"good thing". It might be something somebody in a test environment wants to do. 
If so, you can put the OTC extracted fonts into a set inside of FontBook and 
then disable them. After that you can install the others. If you put them into 
a different set also then you can disable them to allow you to re-enable the 
fonts from the OTC.

Original comment by stua...@google.com on 30 Jul 2014 at 4:49

• Changed state: Invalid