Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for 'variable fonts'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

  1. Serif announced yesterday that variable fonts support is coming. Please see this message from Serif: https://affinity.serif.com/en-us/press/newsroom/affinity-and-canva-pledge/
  2. Windows 10 64-bit NVIDIA RTX 3070 Any V2 Affinity software ------- The problem: Affinity Designer and Photo would no longer open any file or create a new project without becoming unresponsive or not loading. Half the time it would open and become unresponsive immediately. Half the time it would not load at all, but be found in the Task Manager in order to close. Coincidence: this happened conspicuously at nearly exactly the moment Serif announced their acquisition by Canva. ------- Identified cause of the problem: After hours of trying just about everything I read about online (reinstall, install older versions, reset all settings, delete AppData files, install desktop exe files instead of Windows Store msix file, reboot Windows, new graphics drivers, turn off hardware acceleration, and probably some more or combination of above), I discovered that what caused this problem was a font, namely this one found on Google Fonts: Aref Ruqaa Ink - Google Fonts . If Aref Ruqaa Ink is installed in the system, then Affinity is broken. Does anyone know why a font (one available on Google Fonts no less) would break Affinity? It's not because a font is a variable font, because I've installed a variable font before and Affinity didn't break. The variable font just didn't work properly.
  3. If you want to use that font in Designer you'll need to uninstall the Variable version and install the Static version that Google Fonts also provides in the download file.
  4. Variable Fonts spec announced - 2016 This forum thread started - 2018 This forum thread still relevant - 2024 I've taken to rendering out instantiated cuts of variable fonts using the Python `fonttools` package, but really I shouldn't have to. For everyone else looking, https://fonttools.readthedocs.io/en/latest/varLib/instancer.html has everything needed to work with variable fonts and subset, instantiate, modify them etc.
  5. I'll just add my voice here, asking for Variable Fonts support Rather Soon Please. I only realized two days ago that Designer did not support Variable Fonts, after searching for the missing axis configuration for ... a while. And it's not even just that I cannot edit the different display axes, but e.g. installing the Roboto Flex Variable Font straight from the Google Fonts website doesn't even show up right in Affinity Designer 2.4.1 with the predefined weights - I just get Roboto Flex "Regular" x7. Meanwhile, everything just works(tm) in Figma. Honestly, I was quite surprised that in mid-2024, illustration and design software would not let me use Variable Fonts, let alone not properly recognize them?
  6. I don't think Canva is in the Adobe market at all. Affinity is. So I think Canva wants a slice of that pro market using the goodwill Affinity has/had to get a slice of it. The only reason Adobe would have for buying Canva or Affinity is to close i it down. That the Affinity PR mentioned variable fonts and a few other things going into Affinity in V2 suggests that Canva does want to move into the pro areas. I hope so. The BIG point about Affinity is that it is perpetual licences and not subscription.
  7. I am really nervous about this, as I expressed in my answers to your (ugh, Google) form. What I did not mention there, but should have, is the one thing that I really need from Affinity Publisher, and that it the ability to make either (or both!) ACCESSIBLE PDF files or E-BOOKS. I don’t care about variable fonts, I now have footnotes (thank you), but not yet accessibility. I don’t see how Canva will help with that.
  8. These two days have felt a little like an emotional roller coaster. It’s a little embarrassing to admit that the choices a software company has made could have that effect on some of us, but I guess it goes to show how we felt about it before, and how many of us have invested a lot of time not only in using it but also in participating with the users on this forum. Today’s email from Serif/Canva has helped change my mood. Yesterday I was contemplating a wait-and-see approach with a very pessimistic feeling of keeping an eye on the emergency exits. Today I am still in a wait-and-see approach, but it has shifted to a more cautiously optimistic outlook. It seems the general mindset among the posters who have contributed to this discussion since the latest email is still rather discouraged. I admit that now we are on edge and fearing the worst, but supposing that they truly do intend to maintain Affinity as a stand-alone product always with a perpetual license option, and the future proves that to be true, I do not know how they could say anything different than what they have not said, so I am willing to give it a chance. Truly, I want it to work out since I like Affinity so well. Consider that yesterday’s statement was worded so carefully to make no promises other than that we can continue to use what we already bought with unspecific promises about updates in the version 2 cycle. There was no promise beyond that. It practically read like a promise that all would change after that. However, today, we have a promise that it will go beyond 2.0. The copy of the email says this: “We are committed to continue to offer perpetual licenses in the future.” Note that “in the future,” is there unqualified, so we could read it just as more PR to make us think they hear us all while intending “in the future” to mean for a set period of time. But in the infographic, we instead see these words: “Perpetual licenses will always be offered and we will always price Affinity fairly and affordably.” Notice the double use of “always.” That’s a big word, and remember that statements such as these are crafted very carefully. I know that we may be inclined to be skeptical even here, but at the very least, making a promise such as that means they are betting the goodwill and continued loyalty on their customers on their ability to keep that statement, because now if they ever take away perpetual license, they will have broken their word. And if they really mean it, what could they have said any different to make us feel better? I don’t know, so I think for now I will take them at their word, which is fair. And of course, we will hold them to their word, which also is fair. That being the case, I am eager to wait and see what this might mean for the promised additional development resources. For example, variable fonts were mentioned in the examples of features that they want to bring in, and unless I have forgotten, that is the first time they have ever indicated they do hope to add it to the feature list. I am excited for that. Quick question: formerly we were used to the name Serif as the company and Affinity as the product, but the current communication seems to keep referring to Affinity as the team behind the product. Does the name “Serif” as such still have any meaning or continue to exist?
  9. They know, but Variable Fonts are a complex issue to handle, and much more complex than many users realize.
  10. Desperately hoping that Canva's involvement means that variable fonts will be prioritised.
  11. I now used Junicode in InDesign, and might have a little (but only little) better understanding on the way glyphs are listed in Stylistic Sets and Character Variables (both in InDesign and Affinity apps). They do get listed also in InDesign as a category (rather than just contextually as alternatives for selected glyphs), but this is not so obvious for anyone not well aware of internals of OpenType technology unless using sorts of super fonts as Junicode. It seems that InDesign lists alternatives for a selected glyph based on encoding (glyph names), as e.g. for Latin capital letter Eng it also lists Runic letters Ing and Ingwaz, so stylistically and otherwise totally unrelated glyphs. CorelDRAW does the same thing when using its OpenType contextual selector, as does VectorStyler. Perhaps this is what you mean by "construction" of aalt glyphs for glyph selection, whether they exist in OT for a selected glyph or not? Anyway, when having Junicode active, InDesign does list up to 20 Stylistic Sets for the font, and, it seems, without showing the table names, all available Character Variable tables, as well (in order): cvetc.mp4 The screen recorder I use on Windows unfortunately appears to disable tool tips so the glyph names (and cv codes) shown by InDesign are not displayed in recording, but it seems all tables from cv01 to cv98 get listed. There are also some other unnamed tables like rtlm which lists Runic letters. On the other hand, Photoshop 2024 (latest version) only shows three alternative glyphs for capital letter Eng (in Junicode), not the Runic ones, but then fails to show any if Alternates for Selection is selected. And it only shows three named Stylistic Sets for the whole font. So I cannot say that my confusion has remarkably diminished.
  12. You will never be able to move flawlessly from AI to the Affinity applications. Even if variable fonts were supportted, the format of the .ai files is undocumented (largely, if not completely), and Serif is not interested in trying to reverse engineer that format and then maintain compatibility with future changes. If you have documents that were saved by AI in compatibility mode, so they contain a PDF version of the AI data, then Affinity can partly show the contents, but not fully.
  13. The Affinity programs cannot read certain proprietary data in the Adopay file formats; Serif would have to license an API from Adobe for this. And that three times (APhoto, ADesigner, APublisher). This means three license fees per suite sold. Try to open your files in https://www.photopea.com And as far as your variable font problem is concerned, check whether the fonts are also available in the static version.
  14. Hi guys, unfortunately I have some previous AI files with variable fonts with I CAN'T TOUCH (doesn't worth to change) and I was surprise that is still missing. I can't move forward to the Affinity adoption and I must stick to Ilustrator for now although I spend money for affinity suite. I prefer PARK the Affinity designer adoption for now. I am disappointed. Despite the variable fonts, other parts of the same AI file (exported in CC-legacy) is not read consistently by affinity designer.
  15. Google Fonts are typically supplied in a set comprising variable font TTF files, a copy of the Open Font Licence, a Read Me file, and a subfolder containing static fonts. For Source Sans 3, the files are as follows: SourceSans3-VariableFont_wght.ttf SourceSans3-Italic-VariableFont_wght.ttf OFL.txt README.txt static [folder] The ‘static’ folder in this case contains 16 TTF files.
  16. How many fonts do you have? Is it hundreds or thousands? Be aware that Affinity cannot use Variable or Colour fonts. To the best of my knowledge fonts stored on the internet (or perhaps even any network) may not work with Affinity. Finally old PostScript type one fonts are a problem as well.
  17. Support for variable fonts is completely different from CJK text handling.
  18. None of the fonts in that repo will work properly in Affinity or any application which looks at style groups - the Bold and Italic buttons depend on this. They have not been fixed. The other repo I was thinking about called them "for Windows 10," and added TTF versions, but I just checked and he also did not fix the fonts. There are ton of name conflicts. So if you install them all - there will be issues. Such as the wrong font embedded in a PDF, etc. Which font? - do not know any version which has 25 named instances. SF Pro variable from the developer site currently has 36 instances. It has three axes - opsz, wght, wdth The older SF Pro variable with two axes (opsz, wght) had only had 9 instances. SFNS - the macOS system font - currently has 369 named instances. Have not seen any static versions by width. If you need/want various widths - you will have to make those yourself. Text, Display, Compact, etc. are basically optical sizes they made static fonts for. It really does not matter what they did with the named instances (in any VF font). You can make what ever you want, or actually need.
  19. In my example above it was a font from Adobe Fonts (not a variable one). The bug also occurs if I replace it with Montserrat. I attached a test file. test.afdesign
  20. The variable bundle includes the static fonts, from what I have read on that site:
  21. That’s great advice…assuming I want to buy and license a single family from the typeface with predetermined weights and intensity. Then, you’re ignoring the strength and the whole point of variable fonts. The variable bundle that includes everything is 199€ in total, whereas the 3 families cost 119€ each and totaling to 357€. I don’t know about you, but I don’t wanna pay 375€-(the valuable variable font benefits) instead of 199€+(the valuable variable font benefits)
  22. Paul was responding to another user's comment that seemed to say that Google Fonts provides only Variable fonts. That statement is false, and thus Paul's statement has value, even if it doesn't apply to you. In any case, Nikolas Type also provides the static versions of Solare, if that's really the font you want to use. So you wouldn't need to use Google Fonts for that one.
  23. While we continue to wait for any sign of variable fonts in the Affinity apps from Serif, tools such as https://slice-gui.netlify.app/docs/ can be used to work around the problem (yes, another work-around) by creating static versions of variable fonts that can then be used in the Affinity apps. Annoying, time-consuming, and far from ideal, but if needs must, it’s an option.
  24. QuarkXPress comes in at a significantly higher price point than the entire Affinity suite, and they do not seem to fully support variable fonts yet either (though they have said it is on the roadmap for several years now).
  25. There are plenty of free fonts (not variable) from Google Fonts, and elsewhere, you don’t need to spend lots of money!
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.