My original document only used Arial ttf format, after a period of time, open the document again, it shows that the lack of fonts, and is the lack of [otf], it is amazing, I have not used Arial otf ah.
I have not used Arial otf ah.
Found one, but it's hard to reproduce the example, so I won't post the file.
Could it still be that the font pointing was confused?
2 Correct answers
Most of the time, Font families (fonts with the same family name) are differentiated by type.
A few InDesign versions ago the types were even shown as icons in the Find Fonts dialog, now you have to use "More Info".
Lesser known, there are multiple "OpenType" types, showing the same [otf] suffix and the same icon, but they have a different type for matching. In scripting you can see them:
For this reason (types are relevant) you can come across multiple font families with the same family name, w
...
I guess your translation is wrong: Changes were applied to styles and/or named grids.
Named grids are a concept of Japanese typography, they can also specify a font.
The "Font Usage Dialog" (original name), later "Find Fonts" or "Find/Change Fonts" reports fonts as they are used with text in the document. If you replace fonts, you'd change with local overrides. This is where it works best.
As an afterthought, in western versions the checkbox below enables that you also apply the changes to charac
...
11
Replies
Most of the time, Font families (fonts with the same family name) are differentiated by type.
A few InDesign versions ago the types were even shown as icons in the Find Fonts dialog, now you have to use "More Info".
Lesser known, there are multiple "OpenType" types, showing the same [otf] suffix and the same icon, but they have a different type for matching. In scripting you can see them:
For this reason (types are relevant) you can come across multiple font families with the same family name, which is already known as bad and confusing the font subsystem thus better avoided, and even multiple [otf] of them. There are some more reasons for mismatches in font family - such as native names (discussed below).
This is the easy part. Under certain circumstances a font is identified by postscript name rather than by combination of font family, type and font style. Could be the placed PDFs where name+style are lost, or a copy-paste from Illustrator, where only the postscript name is known. When you import Word texts, they can also specify fonts never known to your system, I haven't looked what exactly happens then.
Anyway in these cases InDesign tries to substitute (one of the multiple font status values). Most of the time with Latin fonts it ends up at the default font (Myriad) but there is also a mechanism to list font families with "same name", and the found font might spill over. For inconsistency sake, dependent on the program one approach is taken or the other. For example a glyph might be found by the more forgiving composer and rendered accordingly a decade later from composer output, but the missing font highlighter might disagree.
The font lookup mechanism also differentiates between font managers - a font is less likely to get found with the document fonts folder even when it should along the mechanisms mentioned above, so sometimes it is suggested here in the forum to avoid document fonts.
Other criteria come with the font style, e.g. when you have the correct Arial around but the particular semi-bold is only in the other Arial … A font style might also spill over, within the family or across types, e.g. you specify Italic and get Kursiv, Regular for Roman. There is another mechanism that matches beyond the style name, and so forth.
All of these could explain why a Arial TTF specified in a legacy document could end up showing one Arial OTF that might happen to exist on your machine, even if you never used the OTF and the [Regular] font style is or isn't supported by the OTF font family.
Back to your screenshot - could be the paragraph style editor - which is also adding to the confusion. For example when you choose a named font style for a variable font, the font style name will display different from the font menu.
Font families and styles can also have multiple native names, displayed according to the system script if it is not Latin. Not sure why you show a pstyle with that GBK font while the question is about Arial, is that the chinese native name for Arial? If so, could be there is a mismatch in native name between the original Arial and your current one?
Otherwise, was Arial substituted in that pstyle and we're seeing the result? Both font family and font style are surrounded by [], which to me indicates something is missing for both. As we don't see the language from the following dialog page, and GBK is about a specific character set, maybe you have a mismatch there, and the language setting forced the GBK font?
I don't know enough about CJK typography, also for lack of example documents, so forgive any speculation errors.
This 40S in Chapter, where did it come from?
This font doesn't have this property.
40S is a property of the “mypar” paragraph style, but they shouldn't inherit such a property because they are two different fonts.
An instance that cannot be reproduced.
After a long time he was well again.
Hi Dirk Becker.
May I ask what this means:
“Preferences have been applied to one or more styles and named grids.”
Preferences have been applied to one or more styles and named grids
Here a more complicated, constructed example. The paragraph style has drop caps, nested style on word 1 and line style on line 1. The character styles used with these nested styles are named accordingly. They all specify font styles only so the font family still comes from the pstyle.
Let's look at the effective style using a plug-in. I hope it is not too confusing, but you don't have that level of detail with pure InDesign.
The plug-in works on the current selection (here the dropcap "P") producing the effective style as the composer sees it (InDesign calls this "composition style"), but otherwise visualizes the same attributes that also show in the style summary text field from the first screen shot.
At the top you see pstyle2 indented below pstyle1, showing the based-on inheritance.
pstyle2 is selected because it is applied in paragraph 2.
pstyle2 also has dropcaps, nested style "Word" and line style "Line", further indented and indicated as "D", "N" and "L" icons. D and L are also applied thus hilighted, while N (first word) does not apply to the first dropcaps character. There is no character style directly applied.
The equivalent in InDesign's UI the character styles panel, where you see the (Mixed) at the bottom because there are multiple nested styles.
Below the styles hierarchies you see the attributes - font family from the paragraph style, font style from the "D" style indicated by the far right icon. All other basic attributes are inherited from text defaults (the smallish A).
Here another example: The bullet of pstyle3 uses an own font (Big Caslon) via separate attributes, while the "bullet" character style specifies none. You don't usually see those bullet specific attributes, but they are there.
The Find/Replace Fonts dialog also sees the attributes and it will change the font if matching, even if the bullet unicode (or glyph ID!) is not supported in the replacement. Thus the warning, something was changed in a style. Better go look for yourself.
This is only a reminder warning, because when you're using the Find/Replace Fonts dialog, you should first walk thru all the actual usages using the "Find" and "Find Next" buttons.
If you only specify one of the bullet font attributes, Find/Replace again fails. Difficult to achieve and reproduce, it involves based-on inheritance tricks or scripting …
I don't know Chinese typography, but Japanese has several more font specifying attributes in the styles, including for Ruby and Kenten.
AdChoices