Re: Scripter setFontFeatures usage
Victor / tokiop <[email protected]>
| Newsgroups | gmane.comp.graphics.scribus |
|---|---|
| Message-ID | <[email protected]> |
Hi JL, Le 23/02/2020 à 21:13, JLuc a écrit : > This is the way scribus manages bold, italic and other font features : > it's not managed and coded as attribute for the base font > and these variants are only available when the exact altered font exists. > It's said to be the only way to provide a pro DTP quality font management. Thanks for the context, it makes sense to avoid faux-bold and keep typographic quality. I thought otherwise by looking at the possible values for createCharStyle()'s "features" attributes listed on this page : https://wiki.scribus.net/canvas/Automatic_Scripter_Commands_list Testing it with createCharStyle(name="bold-char-style", features="inherit,bold,italic,underline,smallcaps") , the bold and italic features are ignored, but underline and smallcaps are taken in account. It can be a little counter-intuitive that when changing a paragraph style's font, bold sections will keep the old font. > OTOH when i need a bold variant of a font that doesnt have one, > i use a finetuned "outline" attribute. nice trick, will keep it in mind for fallback ! ___ Scribus Mailing List: [email protected] Edit your options or unsubscribe: http://lists.scribus.net/mailman/listinfo/scribus See also: http://wiki.scribus.net http://forums.scribus.net