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

Arial fontfamily not kompletly available


Recommended Posts

I've got the trialversion of publisher. Now testing the program i dont get served the whole arial fontfamily. I am needing the komplete arial narrow group, normal, bold , bold italic and normal italic. Only Arial narrow normal is a chosable option.

Im using Windows 8 and in the windows fontmanager, the missed fonts are available. So, how can i integrate all these fonts in Affinity Publisher?

Link to comment
Share on other sites

Affinity uses fonts, that are installed in the OS.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

Welcome to the Serif Affinity forums, @AndreasDiehm.

As Pšenda mentioned, if the fonts are installed they should be available.

If you're seeing something like this:

image.png.f600ddeebb063c17546d731dfcc3e1ec.png

then you can choose additional variants by either clicking on the pulldown where it says Regular, or on the right-pointing triangle next to the font name.

 

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

Interesting, I see them all.

image.png.1c837a36e49f798ee83bb54fb758c2f4.png

image.png.1e645852dc2bf9f5fcde74083b3952d3.png

In other applications, are they all visible? What to try to reinstall the font?

P.S. Looks like all duplicate "Narrow" fonts have been hidden.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

33 minutes ago, Pšenda said:

I see them all.

But why do you have so many duplicate "Narrow"?

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

59 minutes ago, walt.farrell said:

But why do you have so many duplicate "Narrow"?

Because Affinity can't write the correct font name?
image.png.4ac219b7c599b707eaa2e05d5afdb1f3.png

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

1 hour ago, Pšenda said:

Because Affinity can't write the correct font name?

Because the font names are generally incorrect, especially if downloaded from the web. But even so, Arial Narrow is one of those fonts that can/do give print providers grief as the names are often messed up.

Capture_000466.png.31f8ae9073a0adac0e073f0147e2af47.png

And dang, I really wish I could resize the drop down and opt to hide the previews.

Link to comment
Share on other sites

1 hour ago, thomaso said:

On windows it isn't?

See the pictures in my and Andreas's post.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

13 minutes ago, AndreasDiehm said:

Thanks for your help. I just deletet the old font and installed a new version.

You're welcome, importantly that the problem has been solved.

 

44 minutes ago, MikeW said:

especially if downloaded from the web.

Arial is a standard part of Windows. I think, that Affinity has a problem with localized font names.

 

47 minutes ago, MikeW said:

I really wish I could resize the drop down and opt to hide the previews.

Yes, font list is too long and confusing.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

4 hours ago, walt.farrell said:

But why do you have so many duplicate "Narrow"?

Because the Affinity-Applications fail to display the Font-Name properly.

image.png.e0a7c9f8bf6823c2907b688989e5a600.png

"Schmal" means  condensed/narrow
"Halb" literally means "half", "not fully" ... -"Halb Schmal" = semi condensed
"Fett" = bold
"Kursiv" = italic

I found an interesting Article about fonts on wikipedia.
Sadly its available in german only: https://de.wikipedia.org/wiki/Schriftschnitt    (perhaps Google-Translate (or any other) may help..?)
contains Infos like this...

image.png.ee8023b48b793a7716d93e757b0080c1.png

--> Font-Handling of the Affinity Applications sadly is (still) pretty far from Business Class.

kind regards
Fritz

Link to comment
Share on other sites

On 2/5/2020 at 1:03 PM, AndreasDiehm said:

I've got the trialversion of publisher. Now testing the program i dont get served the whole arial fontfamily. I am needing the komplete arial narrow group, normal, bold , bold italic and normal italic. Only Arial narrow normal is a chosable option.

Check your Windows fonts folder to make sure you do not have old/different versions of the fonts in there.
You should only see:
ARIALN.TTF
ARIALNB.TTF
ARIALNBI.TTF
ARIALNI.TTF

If you see variations of those with a number on the end of the file name (i.e. _0) they are duplicates
You want to delete any duplicates because APub has problems with the duplicates.
The files may be locked if the duplicates are the ones which are installed.
Then un-install the fonts, delete all the remaining Arial Narrow files, re-install the correct ones.
Now you should see only the correct four files above.

 

On 2/6/2020 at 10:20 AM, Pšenda said:

Interesting, I see them all.

Notice that all four of your Arial Narrow previews look the same.
It appears you also have an issue.
My guess is you also have duplicate fonts in the Windows Fonts folder.

 

On 2/6/2020 at 12:38 PM, thomaso said:

In macOS the Arial appears separated in family parts. – On windows it isn't?

APub displays the fonts using the Typographic Family Name and Typographic Style Name.
The Windows version of Arial Narrow has Arial as the Typographic Family Name.
So all the fonts are listed together with the other Arial fonts.
The Mac version of Arial Narrow has Arial Narrow as the Typographic Family Name.
So it is listed separately.

 

On 2/6/2020 at 2:20 PM, Fritz_H said:

Because the Affinity-Applications fail to display the Font-Name properly.

This is an interface translation issue not really a fonts issue.
You should probably post this as a separate issue if you think it should be changed/improved.

 

Keep in mind that you may have to clear the Windows font cache after fixing the font issues.

 

Link to comment
Share on other sites

8 minutes ago, LibreTraining said:

This is an interface translation issue not really a fonts issue.
You should probably post this as a separate issue if you think it should be changed/improved.

translation issue?
nope. Check the posting regarding "Bahnschrift" - variable Fonts. Chinese Fonts...

also: 
- Why are the Styles not translated? ("Bold" ?  should be "Fett" etc..)
-  4x Narrow? 
image.png.2f6cf8a189b1500fa8d56d12b4a25fad.png

should be at least:
- semi condensed  (2 words)
- semi condensed bold  (3 words)
- semi condensed italic  (3 words)
- semi condensed bold italic  (4 words).

why counting words?
Because with other fonts, Affinity-Applications seem to work fine:

image.png.7d3d4538eac86399ff91273388f74590.png

image.png.8f32ca6773ba223f574bf19c908ca57e.png
 

If the Arial-Issue was just a translation issue, there should be 2, 3 or even 4 wrongly translated words... not just "narrow".

Fritz

Link to comment
Share on other sites

13 minutes ago, Fritz_H said:

translation issue?
nope. Check the posting regarding "Bahnschrift" - variable Fonts. Chinese Fonts...

Bahnschrift is a different issue. APub cannot properly read/display the instances in the variable font.

Listing Chinese fonts is a different issue. Inside those fonts the font name fields are actually in Chinese.
The user wants those to show up in the interface.

In Arial the name fields are all in English. I assume APub is not translating those as you desire.

 

13 minutes ago, Fritz_H said:

also: 
- Why are the Styles not translated? ("Bold" ?  should be "Fett" etc..)
-  4x Narrow? 
image.png.2f6cf8a189b1500fa8d56d12b4a25fad.png

This looks like you have the same issue as Psenda above.
The preview is the same and the name is the same for all four.
This is probably because you have duplicate fonts in the Windows fonts folder.

Once the font issues are solved, again the lack of translation is an interface translation issue.

Link to comment
Share on other sites

18 minutes ago, LibreTraining said:

In Arial the name fields are all in English. I assume APub is translating those.

This looks like you have the same issue as Psenda above.
The preview is the same and the name is the same for all four.
This is probably because you have duplicate fonts in the Windows fonts folder.

The Operating-System* does know the correct Font-Style-Names ("Schriftschnitt"):
image.png.413d4cb41edbcc74a762cc35680ee6f2.png
(* in my case: Windows 8.1 Pro)

Even the open-source Software Scribus (terrible UI, btw.) knows that
there is something fishy about the Arial-Font Microsoft shipped with the Operating System:
image.png.812539cdda56fbb1b569490d32200221.png

in Fact:
Publisher is capable to display the correct style when one of those 4 "Narrow" - Styles is selected.. just the Name is wrong

In the end: one more good reason not to use Arial.  :-)


@Serif: don´t forget to translate the Font-Style-Names...

kind regards
Fritz

Link to comment
Share on other sites

40 minutes ago, Fritz_H said:

Publisher is capable to display the correct style when one of those 4 "Narrow" - Styles is selected.. just the Name is wrong

The font list display issue indicates there is some issue with the fonts.
It indicates at a minimum that the APub font cache is corrupted/confused.
You may or may not get the correct font on print output.
You may or may not get the correct font on PDF output.

The Windows font list is useless for solving duplicate font issues.
It only displays the last fonts installed.
It does nothing about the duplicates which exist in the fonts folder.
Just because it can properly translate the installed font names means nothing.
APub has problems when there are duplicate fonts in the Windows fonts folder.
Other applications may, and do, also have problems.

There is nothing wrong with how the Arial fonts are constructed.
Arial and Arial Black come with the Windows operating system.
Arial Narrow comes with MS Office 2010, 2013, 2016, etc.
If someone mixed and matched some downloaded Mac and PC versions, that would be a problem.
If Scribus is having a problem the original PC version fonts, the problem is Scribus.
But is could just be Scribus too is having an issue with duplicate fonts in the Windows Fonts folder.

The fact that all your Arial Narrow previews look the same indicates a problem.
You can fix it or ignore it.
Obviously that is up to you.
But the problem is not APub or the fonts.

First fix the font problems.
Then make some suggestions regarding translating the names, widths, weights, and styles, etc.

 

Link to comment
Share on other sites

1 hour ago, LibreTraining said:

Check your Windows fonts folder to make sure you do not have old/different versions of the fonts in there.
You should only see:
ARIALN.TTF
ARIALNB.TTF
ARIALNBI.TTF
ARIALNI.TTF

If you see variations of those with a number on the end of the file name (i.e. _0) they are duplicates

I have no duplicates !!!

image.png.04c8b8e2ced4046cd4048eb34c6db856.png

There are nine ttf arial font files in the font folder, that normally appear in Windows (10), see my previous post.
Only Affinity has a problem with correct name interpretation for Narrow files ("N" in file name).

image.png.c824b37152a566427a27b5c6c1d5a413.png

The truth is that these files are already quite old (14.7.2006 vs 19.3.2019), and compared to others it is an old version.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

@LibreTraining 

I will stop that here - too many misunderstandings...

There is no problem with Scribus, the opposite is true:
It shows 4x "Narrow" but extends the name with additional info (in brackets) which indicates: it recognizes that there is something strange/wrong about these Arial-Fonts.

No need to discuss this any further.. esp. since there is no Arial needed on my side..

kind regards
Fritz

Link to comment
Share on other sites

19 hours ago, Pšenda said:

The truth is that these files are already quite old (14.7.2006 vs 19.3.2019), and compared to others it is an old version.

Arial Narrow does not come with Windows.
Users typically get Arial Narrow from MS Office.
The v2.37 you have was included with MS Office 2007 and 2010.

In APub my Arial Narrow font previews look correct - just like MikeW's image above.
It appears you have some corruption of the APub font cache and/or the Windows font cache.
This could be caused by duplicate fonts, OR some other issue.
First, make sure you do not have duplicate fonts in the Windows Fonts folder.
Then, clear your Windows font cache.

Link to comment
Share on other sites

19 hours ago, Fritz_H said:

There is no problem with Scribus, the opposite is true:
It shows 4x "Narrow" but extends the name with additional info (in brackets) which indicates: it recognizes that there is something strange/wrong about these Arial-Fonts.

Just checked using Scribus v1.56-svn - all Arial fonts are listed correctly, including Arial Narrow.
I see nothing "strange/wrong" at all.
My guess is you also have a fonts cache issue.

 

Link to comment
Share on other sites

2 hours ago, LibreTraining said:

Just checked using Scribus v1.56-svn - all Arial fonts are listed correctly, including Arial Narrow.
(...)
My guess is you also have a fonts cache issue.

I used Scribus 1.48 portable (= release branch) for testing.

No Font-Cache-Issue since I deleted Font-Cache-Files.
Perhaps it´s related to the OS (Windows 8.1); don´t know what Psenda ist using, the OP also uses Windows 8.x...

again: Who cares?  Arial is boring and the Affinity-Applications still have so many bugs.. one bug more or less does not count...
esp. since you can use the fonts, just the name is not displayed correctly. ( @AndreasDiehm  )
 



kind regards
Fritz
Link to comment
Share on other sites

4 hours ago, LibreTraining said:

First, make sure you do not have duplicate fonts in the Windows Fonts folder.

What do you not understand about my previous post?

 

4 hours ago, LibreTraining said:

Then, clear your Windows font cache.

I've tried it before, but of course no effect.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

4 hours ago, LibreTraining said:

In APub my Arial Narrow font previews look correct - just like MikeW's image above.

Are you and Mike using a foreign language version of OS?

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.