Jump to content

Search the Community

Showing results for tags 'type design'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests, Suggestions & Discussions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Hello, I'm working on glyphs drawn first using Robofont, which is a type design app. Each letters and characters are displayed as Bezier curves, which are in the app text files. I could copy paste shapes from Robofont directly into Illustrator and it keeps the shapes as vectors, but once I copy and paste the vectors from Robofont into Affinity Designer, it seems to turn the curves into text informations that I can't do anything with... Is there a way to make this work? Thank you for your help
  2. Hi all! I am writing you not as the usually nitpicky and potential Affinity-fanboy-who-lives-off-of-Publisher (I do currently live off of InDesign, so it would be only a matter of time, but things just may take a bit of a turn in my career path soon-ish), but as a prospective full-blown professional type designer and current type design teacher with some serious grievances to air; as you may guess, I recommend Affinity apps for most graphic design related tasks, and even though I vehemently tell all my students to familiarize themselves with type design packages (namely Glyphs.app, FontLab, RoboFont, etc.) and start drawing inside them right away, they are all more familiarised with all-purpose vector drawing packages when they begin studying type design, so, for those who may wish to go that route, I also make a point of explaining to them how to properly size their curves/paths in points, in order to correctly import them into Glyphs.app further on. Now, this usually works fine when using Adobe Illustrator, but when doing so with curves/paths drawn in Affinity Designer, some less-than-optimal results occur, as you can see from the enclosed screenshots. The result will always be the same (on both apps, mind you), either if I paste the curves/paths directly or if I export them into .EPS and import them into Glyphs (actually, Glyphs won't even let me try the latter – and gives me the enclosed error message, whereas .EPS content generated from Illustrator, whether pasted directly from the clipboard or dragged into Glyphs, will work just fine). If I export it from Affinity Designer into .SVG I will be able to import it into Glyphs.app without any missing nodes, but the scale will be way off, thus making the whole process needlessly complicated. I happen to be acquainted with Mr. Rainer Erich Scheichelbauer, from the Austrian type design studio Schriftlabor and the Glyphs.app development team, and I can put you guys in contact with him in order to work on fixing this issue. As for the recently released FontLab VI, I don't own it so I can't get into the compatibility with it for the moment in any authoritative fashion whatsoever. I did give their very feature-complete and stable public beta a go, however, and it seemed the interoperability was even more broken, so maybe you should chime in with Mr. Adam Twardoch from FontLab Inc. on that issue as well (though I'm guessing that FontLab's even more advanced curve/path drawing tools and its focus on über-pros – their app is expensive as hell, after all –, combined with their still less-than-elegant usage of – ugh – Qt, may mean that they don't care much about those interoperability niceties and would rather force their users to always draw inside of FontLab from the get-go). As it stands, Affinity Designer in standalone form (I have yet to test InkScape as a bridging app, but… I'd rather not, as it's even more cumbersome than AI) is completely unfit for type design purposes with Glyphs.app and, as such, I can't recommend it to my students at all, which is a pity because the price bracket and the target audience of both packages seem to be very similar. Do you have any insight as to what may be going wrong here (a non-standard/reverse-engineered or even standard and well-documented .EPS and .SVG implementation, just a bit gone wrong, perhaps?) and could you provide us with a tentative ETA for its resolution? Now, for some explanation on what each of these screenshots mean… Here we have the original outlines, all nice and dandy, without duplicate nodes or anything: And here we have the result of copying said outlines and pasting them directly to Glyphs.app and, as you can see, the scale is indeed correct but we're missing one node: Now, if we try to export a file into .EPS using Affinity and import it into Glyphs.app, we get this error message: Surely we'll get better results if we try using Adobe Illustrator, right? By opening the .EPS file in AI and saving it back, also in .EPS format but with a different name, and importing it into Glyphs, here's what we get, and indeed the results are better, as we get the correct scaling and all the nodes (plus some extraneous ones on the same place where Affinity Designer defined the first/main/closing nodes to be): For the sake of it, let's try saving both .EPS files, in their respective apps, into .SVG format instead and import them back into Glyphs.app… The result on the right was from the file generated in Affinity Designer, and the one on the left from the file generated in AI and, as you can see, AD got the scale way off but finally all the right nodes, whereas AI gave us the same result: Interestingly, if we copy the paths from the .SVG file generated in AI from the .EPS file exported in Affinity Designer and paste them directly from AI into Glyphs.app, we get the best results yet: So, all things considered, it seems the best course of action is to export the artwork in Affinity Designer into .EPS format (and not directly into .SVG, because, as I've just found out and pointed out in the thread title, Affinity Designer seems to mess up with the scaling factor when exporting into .SVG), then opening it on Adobe Illustrator, then saving it into .SVG format and, only then, directly copying it and pasting it into Glyphs.app. It's an effective but extremely convoluted process, which forces you to use AI anyway and kind of defeats the whole purpose of switching to Affinity Designer… :\ For your reference and… forensics, I guess, I am also enclosing the files used in the course of this test: p (generated with Illustrator from the EPS generated with Affinity).svg p (generated with Illustrator from the EPS generated with Affinity).eps p (generated with Affinity).svg p (generated with Affinity).eps test.glyphs
×