LibreTraining

Works fine for me.

File size is zero. Check to see if your file has a filesize on your drive. If it does you need to upload the file again.

It means you have no Paragraph Style or Character Style applied. You did all your text formatting manually rather than applying styles.

Nothing wrong with the fonts. But in your document none of the text has a Font Style selected. The field is just blank for me. So the font is defaulting to the Regular. For example, at the top I highlighted the text and selected Bold from the Font Style drop-down. Same with the other text. Exported to PDF and it looks good. You just need to go through the document and apply the fonts and styles again. FYI - there is a much improved v2.000 of Signika available here: https://fonts.google.com/specimen/Signika

Which version of the Roboto Slab family do you have installed? And where did you get it from? Some of the older versions (e.g. like the ones from FontSquirrel) have broken style groups. In your PDF the font embedded is RobotoSlab-Regular, not the Bold. This could happen with broken font names/style groups in the fonts. Can you attach your APub doc for testing? And the fonts? So I can check them for you.

Go here and follow the instructions to get out of "S Mode". https://support.microsoft.com/en-us/windows/windows-10-in-s-mode-faq-851057d6-1ee9-b9e5-c30b-93baebeebc85 Read this one: How do I switch out of S mode? That should fix it for good. It does have a warning in that answer: "Note: Don't select the link under Upgrade your edition of Windows. That's a different process that will keep you in S mode." That may be the issue you are having.

They are here every day. Many QA, Support, Developers, and Moderators. Major difference from Adopey forum. See Staff Directory: https://forum.affinity.serif.com/index.php?/staff/

QuarkXPress has a similar feature. Makes it real easy to just drop a copy of the fonts in the same folder as the document. Even LibreOffice has a fonts folder (undocumented) which makes un-installed fonts available to use in documents. I test there first to avoid any font cache or other font install issues. Makes it very easy to test without any font problems.

I went looking for this recently to insert some Unicode characters directly. ... found it here: https://affinity.help/publisher/en-US.lproj/index.html?page=pages/Text/specialCharacters.html?title=Special characters and glyphs To insert glyphs/Unicode characters directly using Hex code: Click for an insertion point in the text. Do one of the following: For a glyph: Type 'G+' then enter the Hex code, e.g. '02F5' or '2F5'. For a Unicode character: Type 'U+' then the Hex code, e.g. '0040', '040' or '40'. Toggle from code to displayed character by using Text>Toggle Unicode. Toggle back to Hex code using the same command; keep insertion point at end of character.

This depends on what the font designer does. Both smcp and c2sc may (and do) include letters, punctuation, currency signs, numbers, etc., etc. There is no set standard. Since there is no actual OpenType feature of All Small Caps what you are usually seeing is smcp plus c2sc. And again exactly which characters that affects should only be those characters actually substituted in those two OpenType features. Any other characters would be faked small caps. I have recently for the first time seen where the font designer actually made c2sc act like All Small Caps. The designer included substitutions for both uppercase and lowercase in Capitals to Small Cap (c2sc). Rare. First time I have ever seen this. I am not seeing that. Tested with Times New Roman and it all works as expected. Caps to Small Caps only affects the capital letters. All Small Caps affects both uppercase and lowercase. That could appear differently if the font designer did something like I described above. What font were you testing with? It may act differently in a font which actually does not have any small caps.

Yes, it is an adventure for some. 😁 But glad to hear it is working now, and that my guess at the issue appears to be wrong.

@janeH Arial does have some stylistic sets to test with. I looked at them yesterday when testing this. Since they are simple replacements they work correctly. One stylistic set replicates the unicase OpenType feature. Some of the others do standard stuff like alternate forms of a, g, y, etc.

APub may be having an issue with the fonts' non-standard sub-family names. Can you post your document for testing? I think I have all of that font family so I can take a look. Also, what operating system, and version of APub? And what version of the fonts?

I have been looking at it some more by selecting various characters and in almost every case the options presented are wrong. @Gabe That tutorial should be replaced. Not good to demonstrate a feature in a way that is not working properly. Every new user who views that video is going be frustrated and confused.

Gabriola is not a good choice to demonstrate stylistic sets. Too much going on. And I am not sure exactly what APub is displaying (some appears to be wrong and/or misleading). For example: ss04, ss05, ss06, and-ss07 all have a lot of contextual substitutions. APub is displaying the stylistic sets as available on characters which are not in the correct context. So applying the displayed stylistic set does nothing. That is confusing to users. There are much better font choices to use to demonstrate stylistic sets.with simple replacements which: Will not be displayed wrong by APub Will not confuse users.