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

kenmcd

Members
  • Posts

    1,666
  • Joined

  • Last visited

Everything posted by kenmcd

  1. Everything after the last / is not needed. That is their own internal reference tracking and is not needed to get to that page. PDF readers typically have a feature to automatically convert text which looks like a link to an actual link. Most likely your reader is doing this wrong and breaking the link. Check the reader's settings to turn this feature Off.
  2. Why would a bunch of curves need the features of a font? Kind of a silly question. Trying to edit text with a defective font is a completely different issue.
  3. Extracted fonts from a PDF are usually of very limited use. No kerning. No OpenType features (so text may look different). Vertical metrics may be off (and usually are). Character set is usually just a subset. Rarely useful unless you just need a couple characters.
  4. Ghostscript can do this. (free, Windows and Linux) But it appears you are on a Mac. It is possible to install on a Mac https://ghostscript.readthedocs.io/en/latest/Install.html#installing-ghostscript-on-macos I have a Windows batch file called: TextToCurves.bat With this in it: "C:\Program Files\gs\gs10.02.1\bin\gswin64c.exe" -o text-to-outlines.pdf -dNoOutputFonts -sDEVICE=pdfwrite text-original.pdf The original text input file is: text-original.pdf The curves-only output file is: text-to-outlines.pdf Then just run the batch file in the same folder as the original PDF. Obviously your batch file would be different on a Mac, but the commands are the same.
  5. Yeah, I just went to check if it was a "Document-support font" and found it is still a standard font installed with the OS (checked Ventura and Sonoma). So now I am wondering if he has O365 installed and that is creating a conflict. If that is not it, I am out of ideas.
  6. Since you are on a Mac I assume you got Times New Roman from Office 365 for Mac. And we have seen some reports here in the forum that Microsoft has started restricting Office 365 fonts to use only in Office 365 applications. Do you have Office 365 for Mac installed, or just have the fonts installed? I think if you just have the fonts installed on your Mac they should work, because there is no O365 controlling the fonts. Can you use Times New Roman in an Apple Pages doc and export it to PDF? EDIT: I forgot TNR is also installed with macOS. So I wonder if you have a conflict. Do you have Office 365 for Mac installed?
  7. Does not matter. The PDF does not know it is a variable font. @BarbaraSki What font is that? The kerning/spacing on your heading is really bad. You could manually kern it to look better, or use a better font.
  8. This font has come up before: https://forum.affinity.serif.com/index.php?/search/&q=cooper hewitt&search_and_or=and
  9. As I said that is still not 100% fixed - the bold and italic buttons will not work as expected for the Regular weight. Bold and Bold Italic are in a separate style group. Just keep that in mind - you can work around it. Common issue from font designers who only work on one platform, and only work in certain applications - and do not care if the fonts work correctly for all situations. No commercial fonts would do this because they want their fonts to always work correctly. Not an edge case, just a lazy and/or uncaring font developer.
  10. The original fonts are broken. The style groups are not correct so they will not work correctly in most Windows applications, and also in many other applications such as Affinity. "Fixed" versions have been made available by others. But, the version mentioned in that thread still does not have a correct RIBBI style group (so the bold and italic buttons will not work properly). I made a fixed version for LibreOffice quite awhile ago - would you like that version? (it will work correctly in Affinity)
  11. You may have created the document with an earlier version of Open Sans. The v1 originals and the v3 from Google Fonts have different names internally. The Full Font Name and the PostScript Name are different - and these are often used to identify a font. The font name you see in the Affinity font menu is the Font Family Name (for these fonts), and it is the same in both versions. So it could be confused by the different internal names. (note: the Affinity font matching is rather dim and should be able figure-out these things). You could try the v1 original fonts and see how that works. Download here: http://www.opensans.com/download/open-sans.zip p.s. What is "Open Sans Bold Number Lines" and may I please have a copy of it?
  12. Looks like an issue with the names inside the font files (not multi-mapping). The names inside the fonts are kind of a mess which can confuse the APub font cache and/or the PDF library. One font alone may work - so shut-down APub and un-install the Catchwords font. The Regular font alone may work correctly. (and I assume you know you cannot install both the OTF and TTF versions at the same time) So test that font alone and if it works then my theory is probably correct. Would take about five minutes to fix the fonts so both will work at the same time, so let me know.
  13. Affinity defaults to having these "Positional Alternate" features On for Latin scripts, while other text shapers default to Off for Latin scripts. So all the Latin-script fonts which use these features work wrong in Affinity. For the appropriate Unicode scripts (e.g. Arabic) these same shapers default to On, because for those scripts/languages those features are required to be On. In 2016 the OpenType docs were modified to say that these features (which Affinity groups under the "Positional Alternate" label) are intended primarily for Arabic and that they should be On by default. Prior to this 2016 text change... many, many, many Latin-only fonts were created using these features - and more are still being created today. Back when you could still search MyFonts by OpenType feature tags, I searched for these features - and found hundreds of Latin-only fonts using these features. And there are many in Google Fonts also. So hundreds of these fonts are being purchased/downloaded every day. And users already own thousands of these fonts. Affinity does not handle these fonts correctly. What is really silly is Affinity does not support Arabic, but defaults these features to On. Other shapers in InDesign, Illustrator, QuarkXPress, Word, LibreOffice, etc. all default to Off for these features for Unicode Latin script. So this is why a user coming from Illustrator is confused when their fonts suddenly start looking wrong - like in this situation. These OpenType features should be Off by default for Latin script: - Initial Forms (init) - Isolated Forms (isol) - Medial Forms (medi) - Terminal Forms (fina) - Terminal Forms 2 (fin2) - Terminal Forms 3 (fin3) - Final Glyph on Line Alternates (falt) I was reviewing a bunch of script/handwriting fonts from Google Fonts yesterday and found the first four (init, medi, isol, fina) over and over again - in Latin-only fonts. The last two (fin2, fin3) are less common, but I do find them in other advanced script-style fonts (as we did in the post @lacerto linked above). Minion 3 (and Pro) uses fina - for Latin. Gabriola uses falt - for Latin and Cyrillic. Both fonts are designed expecting these to be Off by default. These features should probably default Off for Cyrillic also. Affinity needs to fix this.
  14. Appears to affect fonts which do not have a figurespace character (U+2007). If the font has the figurespace character - just the space appears. If the font does not have the figurespace character - the zero appears.
  15. @debraspicher Exactly what are you trying to measure? I am guessing AA means anti-alias? And I assume this is related to your other post in the thread about poor image output. The rendering clarity of the fonts on Windows is going to be affected by hinting in the font. Brusher has no hinting at all. Arial has both standard TrueType hinting and MS ClearType hinting. Those will affect the gridfitting, grayscale, and smoothing. Palatino Linotype (which comes with Windows) includes standard TrueType hinting for gridfitting and grayscale. Georgia (which comes with Windows) includes standard TrueType hinting for gridfitting and grayscale, and ClearType gridfitting and smoothing. If the rasterizer is using the hints, those fonts with hinting will look better. The design of the fonts can affect the gridfitting. The Inter font you are reading here was designed with a 2816 UPM so it will fit better in various interface grids. The icons you see here are from the FontAwesome font which has a 1792 UPM. These were decisions they made for drawing and gridfitting. All fonts will fit the grid better at some sizes rather than other sizes. So you should test a mini-waterfall of sizes - 8pt, 10pt, 12pt, 14pt, 18pt, 24pt, etc., etc. Some lines/pt sizes will look better than others (if the hinting is working). Fira Code is designed with a 1950 UPM and has the hinting to optimize it for best display at 13pt. That is for a display, but the same thing applies for output images. Hinting can be optimized for specific sizes, and often is. Gabriola (which comes with Windows) is designed with a UPM of 4096 to accommodate the fine lines and details in the font. When printed/exported at 300dpi, some of those lines can be only one or two dots. If those are then anti-aliased, or resampled, it can become a mess. So what exactly are you trying to measure? If you are trying to compare the effects of various output settings from different applications, you may want to have a more controlled font selection. Noto Sans and Noto Serif both have multiple versions available. OTF unhinted, TTF unhinted, and TTF auto-hinted. I would expect each of those to look different when output to images from different applications, with different settings. The fonts could be renamed so all of them could be installed and tested at once. We could also remove the hinting from any font that looks good, to see if that has any effect. Would take about a minute to remove the hinting from a font. Open Sans (the current version from Google Fonts) has extensive manual hinting done by an expert (who did some of the Microsoft fonts). This font, Open Sans, should look good in many different output situations. Segoe UI is designed to look good at small sizes and is well hinted. Any of the Microsoft ClearType Collection have extensive manual hinting. Calibri, Cambria, Candara, Consolas, Constantia, Corbel. Gabriola has curves galore, and standard TrueType and ClearType hinting. Always going to be more difficult to render fonts at smaller sizes. And curvy fonts are even more difficult. Have to take font hinting into consideration on Windows. All of this assumes the rasterizer is actually using the hinting. If it is not, then none of this matters (and the rasterizer is kinda dumb).
  16. Looks like it (and that makes more sense). The shape of the uppercase S in your image appears to be confirmation. And the E, and the e, etc.
  17. We had this discussion before about the Windows interface font. I thought it would be Segoe UI like most Windows applications. But using screenshots someone showed that it was actually Arial. I cannot find that post or I would provide a link.
  18. This appears to be a Windows issue. https://duckduckgo.com/?q="0x800700b7" I looked at many of the search results and did not find a definitive answer. Most of the results are regarding Windows update, not installing applications. Some of the results are regarding the Windows Store. What version did you install, the store version or the EXE/MSI files? If you installed the store version, try installing from the files instead.
  19. Seravek is now one of Apple's "Document-support fonts" so it is blocked by Apple. https://support.apple.com/en-us/103197#document Affinity does not support Apple's font controls. If you search this forum for "Seravek" or "Athelas" etc. - you will find other similar discussions. The work-around is to rename the fonts (properly). Apple apparently keys on the PostScript Name.
  20. From within the font... Versions String: Version 1.024;Fontself Maker 3.5.0 The good thing about Fontself Maker is anybody can make a font. The bad thing about Fontself Maker is anybody can make a font. Multi-mapping is a bad practice that experienced font developers avoid. There is a reason Adobe is against it and Google Fonts does not allow it. You will not find any multi-mapped glyphs in Monotype's Helvetica Now. Because support is spotty in OSs, text shapers, PDF libraries, and applications. Given that the developer used Fontself Maker means they are on a Mac. And that particular combination of OS and text shaper (Coretext) happened to work. Doubtful they tested anywhere else. I did not examine this closely enough to determine exactly what is causing Affinity problems - but my guess is the ridiculous level of multi-mapping, and including ranges, is confusing Affinity. Regardless this font is junk. I have a pet peeve against purposely broken "free" fonts. Think it is a very sleazy practice. All the characters with diacritics which were there are now mapped to just the base. Be honest. Just make a limited version and let users know it is limited. Don't mislead and confuse them by mapping all the characters they actually need for anything other than English to just the plain base character. And the curly left/right single and double quotes are mapped to the plain versions. I assume there were actual left/right versions. Sleazy. If you just gotta have this font, you can edit it and remove all the multi-mapping, and also remove the unneeded old control characters - and then it may work properly in Affinity. So if you only need Basic Latin uppercase, and some of the normal punctuation, that may be a good option. Could also take a shot and buy the commercial version. May work.
  21. @Konrad1 The problem is the Aquire font. Wadda mess. Multi-mapping is when a glyph is mapped to more than one Unicode code point. This can quite often cause problems for applications with those fonts. Adobe strongly recommends against multi-mapping. Google Fonts does not allow multi-mapping at all in their fonts. It is a dumb idea to do it. It appears this free version of the font was created by deleting the extended glyphs, and then multi-mapping the deleted glyphs code points to the base glyph. For example the capital A glyph has 14 code points mapped to it. That is beyond stupid. And it uses ranges of code points in addition to single code points. Many applications will choke on that. This "free" font is basically unusable. It may work in some situations, but not cross-platform, and not in many applications. Could not find the commercial version to take a look at it and see if it too is a mess, but, regardless, I would not trust anything made by this "font designer."
  22. The Typography panel shows you have Swashes enabled. Which I assume you have Enabled because it looks less swashy with it On. This font has some additional Final Forms features (which are On by default in Affinity), ... which do not appear in the Typography panel - so you cannot turn them Off. In the Positional Alternates section of the Typography panel you can only see Initial Forms (init) and Final Forms (fina) - (these) are the OpenType feature codes. And since you can see them, you can turn them Off. This font has two more "final forms" features - fin2 and fin3 - which you cannot see. So there is no way to turn them Off. OpenType specs say these features should be On by default. But, other text shaping engines default to Off for the Latin script. Because many Latin-only fonts use these features (not just Arabic & Indic, etc.). Harfbuzz (LibreOffice, Inkscape), DirectWrite (Windows, Word), Coretext (Apple, Typeface), InDesign shaper, and more - all default to Off for the Unicode Latin script for these OpenType features. Affinity needs to fix this. @DWright Affinity is the only one enabling these by default for the Latin script. They should be Off by default - or this is just going to keep happening. Affinity looks broken to users when they come from InDesign or another applications and suddenly all these odd glyphs start appearing. These should default to Off for Unicode Latin script: fina, fin2, fin3, init, medi This is at a minimum, there may be a couple others. And there needs to be a switch for fin2 and fin3 in the Typography Panel like for fina. @MsMeowy Your only work-around at this point is to use the version from Dafonts or other download sites (which have no OpenType features). Or hack the font you have.
  23. "was typed" LOL - by whom? The Invisible Man? This appears to be exactly opposite from my initial understanding/assumptions. I assumed you, or The Invisible Man, had entered the characters correctly, and the shaper had broken it. But it appears that The Invisible Man (TIM) had entered the wrong characters, and the shapers actually hacked the display to show the intended character. The yi-cyrl (ї) U+0457 character is in Ukrainian, and not in Russian. My guess is that TIM is using an old Russian flavored keyboard layout, and has to use some old trick to enter the character. And the shapers in Word and LibreOffice are aware of this old hack, and they display the correct glyph - but the underlying characters are still wrong. Unfortunately this has the effect of standardizing the hack. When the correct fix is to correct the character input. Windows has three different Russian keyboard layouts available, and also has two Ukrainian keyboard layouts available. And there are apparently some popular 3rd-party Russian keyboard layouts. I assume there are similar keyboard layout choices available for Linux. The best fix is for TIM to use a keyboard layout or tool which enables him to enter the correct character codes, not some hack which the shaper has to hack visually. @Hangman demonstrated one working solution above. Or you could use find-and-replace to correct the characters. I hope Affinity never adds this hack to their shaper as it just perpetuates this. Affinity is just correctly showing what is actually there. What is there should be corrected by the author.
×
×
  • 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.