Opened 7 years ago

Last modified 3 months ago

#54098 new defect

ghostscript-fonts-hiragino @9.21: Font file "/opt/local/share/fonts/otf/Hiragino/ヒラギノ角ゴ Pro W3.otf" is not found.

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: cooljeanius (Eric Gallager)
Port: ghostscript-fonts-hiragino

Description

ghostscript-fonts-hiragino @9.21 fails to build on macOS Sierra. See https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/25622. The error is:

Error: Failed to destroot ghostscript-fonts-hiragino: Font file "/opt/local/share/fonts/otf/Hiragino/ヒラギノ角ゴ Pro W3.otf" is not found. 
If you have former versions of OS X such as Yosemite, copy the font file from it.

Change History (3)

comment:1 in reply to:  description ; Changed 7 years ago by kobayos

Replying to ryandesign:

ghostscript-fonts-hiragino @9.21 fails to build on macOS Sierra. See https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/25622. The error is:

Error: Failed to destroot ghostscript-fonts-hiragino: Font file "/opt/local/share/fonts/otf/Hiragino/ヒラギノ角ゴ Pro W3.otf" is not found. 
If you have former versions of OS X such as Yosemite, copy the font file from it.

This is not an error. As you may know, Fonts in OTC format is not available in Ghostscript. Since format of Hiragino fonts was changed from OTF to OTC when El Capitan was released, the fonts involved in OS are not available in Ghostscript at present.

Thus, users have to copy Hiragino fonts in OTF format from Operating systems which are up to Yosemite to the specified location.

According to Apple support, there are no problems about legality on the use of the fonts in the old operating systems on the newer operating systems if the users legally own the old operating systems.

This situation would be improved if Ghostscript support fonts in OTC format.

comment:2 Changed 4 years ago by cooljeanius (Eric Gallager)

Cc: cooljeanius added

comment:3 in reply to:  1 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)

Replying to kobayos:

This is not an error.

A port failing to destroot is an error, and it is still happening today.

Note: See TracTickets for help on using tickets.