-
Posts
1,655 -
Joined
-
Last visited
About kenmcd
- Currently Viewing Forums Index
Recent Profile Visitors
4,734 profile views
-
Alfred reacted to a post in a topic: Variable fonts support
-
Apple font "SF Pro" doesn't render correct
kenmcd replied to PepGold's topic in V2 Bugs found on macOS
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. -
Alfred reacted to a post in a topic: Font has a macron character, but does not have the macron over any letters. Is there a way to combine them?
-
Alfred reacted to a post in a topic: Font has a macron character, but does not have the macron over any letters. Is there a way to combine them?
-
That is odd. U+0301 is acutecomb - the "correct" glyph to use these days (for combining) But Foundation Mono (that I have, v1.071, TTF) does not have that non-spacing combining character. It only has acute which is U+00B4 - which is spacing (it has a width) And E (U+0045) has no anchors for a non-spacing combining accent to attach to. The font has no combining accents to attach to any anchors. No anchors in the entire font (that I have). Maybe Affinity, or the PDF library is just confused by this. But... it does seem to work on Windows. Dunno what's goin' on. EDIT: maybe that is it - macOS changes the single character to components (for some unknown reason), then the font does not have the combining accent (acutecomb) so Affinity/PDFlib guesses that it should use what it does have (acute) - which being a spacing accent is going to have a width - and be placed after the E - which is what we see. Dunno. Current WAG.
-
No. In this case... In one font editor I enter either the Unicode code point or the glyph name. Then copy the character from the preview text. Which is what I did because I had Foundation Mono already open in that editor. Or in another editor just select the glyph and then copy the character by code. The Windows Character Map app can also copy by the correct character code. I assume there is a similar app on macOS.
-
kenmcd reacted to a post in a topic: Indicate Non-Breaking Hyphen as a Special Character
-
kenmcd reacted to a post in a topic: Printing with page information marks and accentuated characters
-
kenmcd reacted to a post in a topic: Indicate Non-Breaking Hyphen as a Special Character
-
kenmcd reacted to a post in a topic: Printing with page information marks and accentuated characters
-
kenmcd reacted to a post in a topic: Printing with page information marks and accentuated characters
-
Hangman reacted to a post in a topic: Printing with page information marks and accentuated characters
-
That is interesting - I checked and it is Foundation Mono (good call). That font is not installed on my Windows 10 system either. And it is not a default font on either macOS or Windows. Which means that the font is embedded in the Affinity applications. Or maybe in the PDF library. Very interesting.
-
Hangman reacted to a post in a topic: Printing with page information marks and accentuated characters
-
I think what is happening is your file name actually has two separate characters for É - the E and the acute. This is probably caused by how you type that character (and your keyboard layout). And since the file name does not go through the text shaping engine, those two characters are not combined into the single Unicode character (U+00C9). Normally the text shaping engine combines these two into a single character. But the file name is not processed by the text shaping engine. I tested by putting the actual single character É (U+00C9) in the file name. (copy this text: Étiquette) And it works fine like that. So change the file names to have the single character, not the base + an accent.
-
kenmcd reacted to a post in a topic: AutoCorrect - Capitalise first letter of sentences
-
PaoloT reacted to a post in a topic: Variable fonts support
-
PaulEC reacted to a post in a topic: Variable fonts support
-
Alfred reacted to a post in a topic: Variable fonts support
-
Variable fonts support
kenmcd replied to Athanasius Pernath's topic in Feedback for the Affinity V2 Suite of Products
Ahhh... another troll to join ranks with the CityRodent. -
Alfred reacted to a post in a topic: Help: Problem exporting PDF with "É" character
-
kenmcd started following Text not visible and Font without type (bold, italic...)
-
Sounds like you also installed the variable fonts. Cannot have the variable fonts installed at the same time (with Google Fonts fonts). There are name conflicts between the variable instances and the static fonts. So, no GF variable fonts at the same time as the statics. And Affinity apps cannot use the variable font anyway. Yeah. These are really nice fonts. Definitely one of the better GF text fonts for sure.
-
kenmcd reacted to a post in a topic: Help: Problem exporting PDF with "É" character
-
Font without type (bold, italic...)
kenmcd replied to Chris13123's topic in Affinity on Desktop Questions (macOS and Windows)
SVG files are text file - open it and look. It appears the font family is Open Sans, and it is probably the Regular (so select just that). The original Open Sans Regular font only has "Open Sans" in the PostScript Name. No Regular weight is listed. So perhaps that is where it came from. This happens quite a bit when Affinity opens other documents (no Font Style). So just select the text and apply the Regular weight (Font Style). Note the Regular weight in the original Open Sans does not match the Regular weight in the current Google Fonts version (they adjusted some of the weights when they made the variable font). So your original document may not look the same with the newer fonts. You may want to use the original fonts if you need to replicate something. -
kenmcd reacted to a post in a topic: Affinity Publisher placement results in missing Google Fonts and crazy formatting
-
Looks like this issue has been resolved... so, some additional info about Literata. Literata is a very nice font family. Well made. Lots of features. The Google Fonts download only includes static fonts in one optical size (12pt Text). The releases in the repository include static fonts in four optical sizes. Includes: 7pt Caption, 12pt Text, 36pt Subhead, and 72pt Display. So a lot more fonts for better typography. Latest official release is v3.103. Download here: https://github.com/googlefonts/literata/releases/tag/3.103 There is a v3.200 in-progress with some fixes, but it may be awhile before that ever sees official release. Google Fonts commissioned a commercial foundry for the fonts, and that foundry also created commercial quality documentation and specimens. So there are some useful PDF documents which you should have. Download here: https://github.com/googlefonts/literata/tree/main/Documentation
-
Text not visible
kenmcd replied to RachelPerez12's topic in Affinity on Desktop Questions (macOS and Windows)
That looks like a bitmap (image) format - so it is either SBIX or Color-SVG. Neither format is supported in Affinity right now. Probably Color-SVG if it works in Word. -
kenmcd reacted to a post in a topic: Variable fonts support
-
kenmcd reacted to a post in a topic: Variable fonts support
-
Font style names all the same
kenmcd replied to Paul Mc's topic in Affinity on Desktop Questions (macOS and Windows)
My main point is that these appear to be real original fonts. Not some hacked versions. Thus proving that the real static fonts do exist, and that it is highly likely that somebody at the company has them - and they should get them to you. Failing that - yes, exporting from the VF is the best option.