Last post by Lobsteroid - December 02, 2023, 10:03:46 PM
Relevant to Windows 10, Scribus 1.5.8 (installed as stand-aloe) and 1.4.8 (installed with PortableApps).
I have an Adobe subscription that give me access to the "Adobe Fonts" service. It works well in that when a font is enabled through Adobe it become available to the OS and installed programs like MS Office, Libre Office, PDF-XChange and other but not Scribus.
The other apps on the system detect the new fonts automatically but Scribus does not see them. Using the "additional fonts" feature of Scribus I have:
1) Directed Scribus to look in the super-secret location where Adobe Fonts stores the fonts (\[username]\AppData\Roaming\Adobe\CoreSync\plugins\livetype\r\ in case you wondered). Scribus does not detect the fonts.
2) The font files described in point (1) have numerical file names and no file name extension. The files can be renamed with an extension (.ttf or .otf) and installed into the OS as normal. The rest of the OS and installed programs detect the new font but not Scribus.
3) The moved and renamed font from point (2) can be put in a custom directory elsewhere and use the "additional fonts" feature to direct Scribus to look in the directory and still, Scribus does not detect them.
I have tested that I am doing this right by directing Scribus to another directory created by myself containing fonts from elsewhere. It works as it should.
Note I am not trying to circumvent or abuse the license terms with Adobe Fonts. I just want them to work with Scribus.
starting with a # and having four or seven chars...
the more i write about it, the more i start believing that it could be a nice simplification.
the problem is that currently, one has not really an overview of what is possible. you pick a function that somehow fits your need and then look for a website that converts the values you have into what you think scribus is requesting. having a good documentation in one place might be longer to read, but at the end one should know about all the available options.
Last post by a.l.e - December 02, 2023, 09:54:14 AM
sorry, i did not check what the ...Float variants do.
now that i've read your explanation, i think that the name is terrible. i (wrongly) understood that you wanted to get rid of them (i naively assumed that the "normal" function passes the values as int and the float ones as... float, numbers with decimals).
well, in my extreme proposal, we would then need a second function or a second named argument in the unique function (with a better name than "Float").
defineColor(name, r_or_c, g_or_m, b_or_y[, k = None]) will cover most usages (since we don't have RGBA) and the named argument offer access to all previous features in a "self-documenting" way. it would even be possible to add support for HLC colors in the scripter, without adding a new function : - )
but, as said, it's an extreme proposal and i will not fight to get it through.
Last post by AdmFubar - December 01, 2023, 06:46:32 PM
While on the subject of colors...can the color and fill window be made dock-able? Would like to see a one window to a selected set of colors and another that is for colors being used in a document, with drag and drop to add colors to you current document.
Last post by Darkoni - December 01, 2023, 04:32:46 PM
What about a float?
defineColorCMYK("name", c, m, y, k) Defines a new color "name". The color Value is defined via four components: c = Cyan, m = Magenta, y = Yellow and k = Black. Color components should be in the range from 0 to 255.
defineColorCMYKFloat("name", c, m, y, k) Defines a new color "name". The color Value is defined via four components: c = Cyan, m = Magenta, y = Yellow and k = Black. Color components are floating point values between 0 and 100.