Jump to content

CLC

Members
  • Content count

    58
  • Joined

  • Last visited

About CLC

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I never mentioned anything about resemblence to the old Type 1 PostScript fonts. Just convert an OpenType font with TrueType outlines to curves in any vector editor. Do the same with the same font that's distributed with PostScript outlines. Compare the output (amount of points, differences in curves). That was my point - you can see the difference when you want to plot or CNC the TrueType outlines. Do the same with PostScript outlines of any chosen font. First one will take 3 times more time to finish than the 1st one, yet they are the same fonts from the same distributor. I had no other points. That's the reason why I say that the true OpenType font is the one with PostScript outlines. Just my 2 cents.
  2. Here you go, as a sample, this font might be enough to test the features https://pinspiry.com/10-latest-modern-script-fonts-free-for-personal-use/#download (Harland or Hypathia font ie)
  3. Congrats to you too. It was your post that started this further debate
  4. Alfred. Read OP's question. Again, I must insist that Dwright's answer: was completely correct and the point about PostScript is irrelevant. You argued that DWright's answer was misleading: That is imo wrong. See the highlighted part of your own quote. The rest of the debate is irrelevant to OP's post and can be considered Thread Hijacking. Anyway, here is some interesting stuff from FontLab manual, no further discussion is imo necessary:
  5. DWright's point was that TTF font's don't allow stylistic features (or other OpenType features), while OpenType fonts do. Mentioning PostScript was completely irrelevant.
  6. DWright's answer was correct. He states (and I quote) He doesn't argue that OTF is ONLY PostScript font at all. Edit: Anyway, DWright was correct, TTF fonts don't support any OpenType features anyway. His point was correct. Never mind. [drops the mic]
  7. Yes. TTF outlines are supported, but not recommended. Just see FontLab user manual or Adobe Font Guidelines. People do silly things, indeed - like using a software without reading its manuals first. Then they generate wrong results and come back to forums or post questions, that are answered in user manuals, to reddit. True OTF font is a font with PostScript outlines. OTF font containing TrueType outlines is just a fallback. Works but only creates issues.
  8. You are wrong. OTF = Fonts with PostScript outlines. TTF = TrueType fonts ...some people rename .ttf fonts to .otf and it mostly works, but the base square size in units is different and the type of curves also. Edit: There is, of course, plenty of other differences, like Open Type features, compression etc., but if font contains True Type curves, it should not be generated as .otf, but a .ttf - just for sanity purposes.
  9. CLC

    Studio Link

    Indeed. But a professional software should be professionally tested before official releases are pushed to the public. And open forums are for open discussion, even one that you (or forum owner) might not like... So many bugs isn't a good sign. And ignoring long standing issues while constantly pushing new features (with more bugs) isn't a good thing either. Fixing bugs should be major priority, before adding new features. Same goes with long requested features and roadmap features. It really feels that agile releasing scheme isn't a good way for a professional graphic design suite. Just my humble opinion. BTW I'm quite happy with Studio Link and don't have any issues with lack of some features that I can do easily via the "old" workflow (opening files in the other editor and replacing the links in Publisher later). For me, the basic set of features is currently enough. All the apps are quite good for their price, I have to admit. But they still lack some polishing, sadly. Lack of basic features (Envelope Disort, Select by..., buggy Expand Stroke feature, missing Offset Path feature...) in Designer is what really grinds my gears though.
  10. If you got obtrusive notifications set up in your e-mail client, just disable them while recording. Easier than you'd think Or just close the mail client completely while you're recording. Maybe setup your phone so it can catch new mails during recording? Possibilities are limitless, you just have to try
  11. But it records anything within specified frame. But I understand. Another go is ShareX (if you're on Windows) at https://getsharex.com - it allows you to record a specific window.
  12. For me LiceCAP from https://www.cockos.com/licecap/ works well for both Mac and Windows. It records to its own .lcf loseless format, but also to .gif directly (I know, color depth of .gif files isn't awesome, but it might be good enough, just try).
  13. To me it seems (without attempting to reverse-engineer the software) that Designer internally converts the vector outlines to a bitmap and attempts to trace it, since the results seems to be exactly the same as vector tracing small-resolution bitmap images in Inkscape... I still don't get why Designer doesn't (internally) enlarge such smaller objects 10 or 100 times, do the conversion, and then resize them back. I guess it'd be better than directing users to do this routine by themselves... At least as a temporary pseudo-fix until Affinity devs find out how to do the expansion properly... since even in high-resolutions, the outline expansion is nearly never exactly the same as the original outline.
  14. They're still not looking for an ux expert. That kinda explains a lot
  15. CLC

    Why is the fill error?

    Notice the red node at the bottom? I'd bet the curve isn't closed there... Try to move it, just to see if it's causing the issue.
×