Static font assets are prepared in the editor where their content in terms of characters, glyphs, font features and texture atlas are static. This includes fallback font assets and those assigned for specific font weights. This is a longer conversation so here we go.įont Assets can be static or dynamic. This retains the settings of the font asset but clears the Glyph, Character and Font Feature data tables as well as Atlas texture(s). So while working on the project in the editor, these font assets will get populated.Īt any time, these font assets can be reset to their default state by using the Context menu reset on the font asset. In the Editor, these additions are persistent but not at Runtime. In the Editor and at Runtime, when the first character and glyph is requested, the atlas texture will be resized to the defined size in the creation settings and the glyph, character and potential kerning data will be added to the appropriate table in the font asset. These are all possible workflows used by different users.ĭynamic Font Assets typically start out empty with their atlas texture set at a size of zero (to minimize memory footprint until needed). These assets should be tracked by source control unless you plan on resetting these assets before shipping or something or to convert these dynamic font asset to static as some point.
Ultimately, I opted to publish the first document that I created using Affinity Publisher while foregoing the use of image captions, but a quick and convenient way to inset image captions is an option that I think that many would find to be useful.Īffordability and pricing scheme were also other factors that weighed heavily in my purchasing decision.Again, assuming the font asset(s) is / are dynamic, new glyphs and characters would be added as needed based on the text and characters present in the text. One feature that I would like to see, assuming that I did not just outright overlook it, is an option to add a caption to images and photos that I insert into a document when using Affinity Publisher. The videos that I watched were helpful and instrumental in my purchase decision, as was this forum and the advice provided by various forum users here. I went ahead, a few days ago, and started over from scratch on a new document, and have been able (thus far, at least) to avoid the problem, by following the advice listed in this thread.Īdditionally, I went ahead and purchased Affinity Publisher, even though there's still a lot about the program that I have not yet mastered, nor even attempted to utilize, as of yet. I do, however, need to be able to consistently control the font size in documents created with Affinity Publisher. I appreciate being able to draw on the forum as a resource, also. The program certainly has a lot of very nice features. Of course, with any new product, there will be things that need to be smoothed out. If it does this, it's usefulness plummets dramatically. The core problem, for me, is that it is a deal breaker, on the purchasing end of things. If, as you say, the program doesn't tell you that there's a problem, and if there's no way to reset an object which got scaled wrong, that strikes me as a rather poor design of that particular "feature."" I will try again, this evening, but it certainly isn't very user-friendly, whereas much of the program is. Yesterday, I actually ended up starting completely over on the entire document. To determine whats going on in your document or app it might be informative to see a screencast of you creating a text frame, pasting text and getting confusing font size. Unfortunately there is no way to reset an object which got scaled with the outer handle to its initial size there also is no UI to see whether an object got scaled that way at all. In case you only entered new text in a frame scaled with outer handles that would not work. This means you may have already created this problem "already set", but this became apparent later. In my example above, I set the frame sizes with the outer handle before inserting text.
0 kommentar(er)
