7/29/2023 0 Comments Fontlab going forward in historyThis is what is being used with the CC cloud fonts too. Restricted here is simply due to the font's location. MonotypeImagingInc.MonotypeChristmasFontPack_1.0.0.0_neutral_776bkhgfrgb7pĪfter one takes ownership of that folder (it's not enough to view hidden files/folders), and look at one of the font's properties: These MS Store fonts are installed in a hidden folder structure: The font below is part of Monotypes "Christmas font pack," available on the Windows store. That a font is Installable (no embedding restrictions, the most permissive fsType bit set) has no bearing as to it being marked as Restricted in Apub's packaging process. Serif is (at least in part) determining that a font is to be listed as Restricted based upon a non-standard, hidden font folder. But sharing a package's assets isn't really one of them-with exceptions, like sending to a print service, to aid a software vendor in troubleshooting, etc. Which, aside from sharing a package, the main point of packaging has been to collect all required assets (images, fonts, etc.) in a central folder structure for archival purposes. However, what has historically been permitted are backups. You can learn more about Monotype here: Perhaps the pertinent part is now bolded above. If you have any questions concerning your rights you should review the license agreement you received with the software. You may not copy or distribute this software. Unless you have entered into a specific license agreement granting you additional rights, your use of this software is limited by the terms of the actual license agreement you have entered into with Monotype. This software is a valuable asset of Monotype. You have obtained this font software either directly from Monotype or together with software distributed by one of the licensees of Monotype. This font software is the property of Monotype Imaging Inc., or one of its affiliated entities (collectively, Monotype) and its use by you is covered under the terms of a license agreement. Inside the font itself, the brief license statement is: While they point to their website to read the full EULA, I couldn't find it. The Monotype EULA (for any of their fonts) is fairly difficult to actually find. However, the Adobe Cloud fonts as per the original point of this thread are explicitly forbidden to be handed over to even a print service, which is why Adobe/QXP will not package them. As for non-cloud fonts from Adobe, it has been permitted-but never to another, regular application user. Still, that technically has never been permitted from many font foundries but has historically not been something font foundries has sued over. The only exception that one wouldn't get into trouble sharing the font/package file if sending to a print service. No, it would not be permissible to share the font to another user, either as a font file nor as an APub packaged file. As long as I am the only user bof that font in that package. Yes, it would be permissible to be packaged. That font should not be marked as Restricted.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |