-
Posts
908 -
Joined
Everything posted by Pyanepsion
-
It's sent. I managed to reduce the document that reproduced the bug. The images are full-color SVG vector images that are included in an Affinity Designer frame. With the public version 1. 8. 641, the spread on pages 12-13 is correctly grayscaled. With beta version 1. 8. 651, it is displayed in color. See the two PDF versions obtained.
-
I don't know. On this page there are frames containing text and frames containing Affinity Designer external vector images. These frames with image have an outline effect of 1 px black, and a 3d effect of 5 px. The phenomenon had previously occurred on other pages with only one vector image, but has disappeared.
-
Yes and no. I did indeed think of the first solution first, but this is a printed book project. So I looked at the second option. This is expensive (480 € for Helvetica for example). I then looked towards Monserrat (free). It appears that this second solution uses in all cases fonts that do not correspond to the theme of the guide. I am currently studying a third solution: creating specific fonts for each of the 10 standard weight required using specialized software, using a font that allows modification. I'm thinking of the Gill Sans Nova melt. No. This technique was once used for printing, but did not always give a good result with all fonts. Variable fonts (a technology created in 2016) revolutionize the way we work on font weights using the process described on the aforementioned link.
-
I couldn't figure out how to get an accurate manual selection of font weights in Publisher to do: Thin= 100 Extra-Light (Ultra-light) = 200 Light = 300 Roman (Normal, Regular, Current) = 400 Medium = 500 Semi-Bold (Demi-Bold) = 600 Bold= 700 Extra-Bold (Ultra-Bold) = 800 Black (Heavy) = 900 Extra-black (Ultra-Black) = 950 (I noticed a few days ago that Publishers does not support variable fonts. This is a serious shortcoming, and I imagine Serif will correct this quickly, as many other software packages now manage them, especially since variable fonts are often not very expensive compared to the full sets of other fonts. I think this will be a strong signal for large companies who are still hesitant about the Affinity suite.).
-
I'm talking about light, regular, bold, black, etc. and these are indeed variants of fonts. By algorithm, we can weigh down or lighten a grease on the fonts. In practice, this basically works on variable fonts. https://developer.mozilla.org/fr/docs/Web/CSS/font-weight#Polices_variables (French version)
-
Yes! As you said, the author of the suggestion is indeed often involved in the consequences of a quick resolution, which disturbs his or her judgment. He's not the only one. The manufacturer may also sometimes see only one aspect of things, if only because the person making the suggestion has even argued it, or even completely out of touch with reality.
-
The difficulty comes here from the organization of the forum by Affinity. Support & Questions: Present functionalities working correctly, but not understood, or Missing functionalities. Bugs: Present functionalities not working correctly. Other manufacturers use a decision tree that seems much better to me: Present functionalities working correctly, but not understood: Support & Questions. Present functionalities not working correctly: Bugs. Important missing features: To be developed quickly. Secondary absent functions: Wishes to be included in the To-do list. The difficulty is then to differentiate between the points 3 and 4. Some features will be classified very easily: adding a wallpaper will be in 4, and recognizing the color fonts for a font editor tool will be in 3. Other features are less so. A software manufacturer once told me that a good part of the job of moderators was to migrate messages between 3 and 4. Example: Integrating translation management may seem inappropriate in 4 to the manufacturer since he paid a translator without suspecting that this professional is an incapable (this is the case for French translation of Publisher, where translation is often literally a horror and an incomprehensible gibberish) and that managing translations would make it easier to obtain a more understandable software. It would suffice that there is a mode allowing to translate live on the interface, then to import or export the file obtained.
-
Footnotes/Endnotes
Pyanepsion replied to garrettm30's topic in Feedback for Affinity Publisher V1 on Desktop
For my part, I find that the shortcut mentioned by Peter Falkenberg Brown a little earlier in the discussion is a good idea while waiting for the creation of the "Footnote" functionality. -
Footnotes/Endnotes
Pyanepsion replied to garrettm30's topic in Feedback for Affinity Publisher V1 on Desktop
Yes. This is a welcome shortcut suggestion from Affinity. The setting is made in the “Edit/Preferences/Keybord Shortcuts” menu in the “Publisher/text” section.
