![]() I also understand that with the cloud Adobe enables protection of the fonts as well as their own software from non legal use. It brings some problems.Īnd there would be no problem if everyone simply uses the cloud. So some may not be aware of the possible complications later. But I think that is quite rare whereas using the cloud-fonts may be or may become very common. It is not new that some fonts may be protected and for that reason cannot be included in the package. I might add that in order to view the document correctly the CS6(and below)-user would have to have the fonts installed already - or go find/buy them. But not everybody is, on the contrary many designers/users prefer to stay out of the cloud and the dependency and prizing that comes with it. Of course if everybody is connected to the cloud there is no problem. Thank you, I read your answer - and image - as a confirmation to my question that you can never include the subscripted fonts in a CC-InDesign package. But this will get you a job package folder that's useful in both the current version of InDesign CC and CS6. And of course you will have to manually address version control issues, since you will be working with two separate files. Understand that features introduced in later versions of the software won't make the trip, like use of Typekit/Adobe Fonts for example. This will overwrite your current-version InDesign document file and can cause you unnecessary complication. This will include a legacy file which can be opened as far back as InDesign CS4. When you package the file, make sure that the Include IDML check box is selected. It's cumbersome, but you can reach back to InDesign CS6, with various degrees of success, by first packaging your InDesign CC 2019 version of the file. Adobe Systems made a conscious decision to break with CS6, which was introduced more than 7 years ago.Īll is not lost, however. ![]() indd files that are backward-compatible with CS6, the issue is more than just font packaging. It will not store cloud-based Adobe Fonts, as you've surmised correctly, because the fonts are protected by the subscription.Īs for the latest versions of InDesign CC not creating. I'd like to be able to just distribute the font with the scripts folder rather than installing the font through the OS on the target systems.Your inference is correct InDesign packages only fonts that are actually stored on your system. ![]() ![]() I'm wondering if I'm just having a problem with the path to the font but any of my experiments have not revealed the issue. Now, I've read about needing fontconfig in order to load fonts in Unix/X11 so I tried installing that with brew. If I run the same code on Linux, it works MySillyFont loads and is available in a Qt Font Dialog Box. I find that a) test is = to -1 (meaning it didn't load the font)ī) Qt just uses Lucida Grande c) A Qt font dialog box doesn't (obviously) find the MySillyFont. Test = fontbase.addApplicationFont("MySillyFont") If I have a ttf font in the same folder as my Python script and I do something like this: fontbase = QtGui.QFontDatabase() I've done quite a bit of googling and found some interesting info but haven't been able to solve this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |