LibreTraining

@Passorolle It sounds like what you are looking for is Old Style figures. These figures match the x-height of the text and do not break the visual flow like the Lining figures. In most general purpose fonts the Lining figures are the usual default. Some fonts include the Old Style figures as an OpenType feature. When that is available APub will display Figure Style in the Typography dialog which will enable you to easily change your figures. Apparently the font you are using does not have Old Style figures available. Some fonts designed specifically for text will have the Old Style figures as the default. For example Vollkorn (FOSS) does this. It includes both Lining vs. Old Style, and Proportional vs. Tabular. It's free, give it a try.

How many fonts do you have installed?

I am using Windows 7 x64.

Regarding use cases ... This is very helpful for many different uses: Business users compiling a monthly report from many different depts/locations Newsletters collecting articles from many different authors Books with different chapters being written and/or edited by different people Etc., etc., etc ... Word has the ability to restrict which styles may be used in a document. So when you have multiple contributors you set them up with a document template. That along with a little instruction can make it easy to import multiple Word docs with little fixing required. Because styles allowed in the Word doc correspond directly with the target publication (in InDesign) the text is imported with no need for any mapping of styles. Have not tried this yet with APub.

I can see that "italic" character in the All list. It is Glyph 213.

This is because LibreOffice on Windows is using the old Styling Groups like it is done in Word. This is the typical Regular/Italics/Bold/BoldItalics (R/I/B/BI) groups used in older applications. More modern applications like APub, InDesign, QuarkXPress, etc. use the Typographical Family and Sub-Family. More modern font families have entered the name metadata in the fonts to properly handle both ways. Alegreya Sans is constructed to work properly in both older and newer modern applications. In LibreOffice on Windows there is a styling group for the Regular font. So you select the regular font from the font list, and then apply the Italic and Bold buttons to get the other fonts. So the Regular Italic, Bold, and BoldItalic fonts do not appear in the main font list. They do appear in the Character font list which is similar to Typographical Family. Note that this works differently in LibreOffice on Linux or Mac. They have their own issues. Below is a printed image of my Alegreya Sans tests on LibreOffice on Windows. It looks good. Some other font families do not.

Update on problems with the above mentioned Interstate fonts ... The fonts were as suspected quite a mess in the naming metadata. Missing name fields, wrong name field settings, wrong weight settings, wrong width settings. Fixed fonts work properly in APub in my tests. So the issues do not appear to be an APub issue.

It looks like there may be some hidden characters in the text. How was this text placed? What is the source? Does this still happen if you first paste the text into a text editor to remove any formatting, and then paste into the APub document?

What font are you using? Does it still happen with a different font?

Some of the Interstate font collections floating around out there are a real mess inside the files. Some are older TTF fonts. Some are OTF-TT fonts. Some are converted Type1 fonts. All of them I have looked at have severe naming issues. Even the newer Font Bureau versions I have looked at are just a mess. Be happy to look at yours and tell you why they are not working. Send me a PM with a link. Can probably fix them for you. Like I said I have versions that are TTF, OTF, T1, names Interstate, InterstatePlus, GLInterstate, etc. All pretty much a mess by modern standards. FOSS alternatives: Overpass, Route 159 - have tested both families in LibreOffice (LO). Both have minor name issues which affect LO on Windows, but should work properly in APub. Commercial alternative: Expressway (some weird issues, but not the newest fonts)

InDesign has quite a few different non-standard characters that it uses for formatting. The U+0007 is the "Indent To Here" character per some old docs. There are a few others which will probably surface as users transfer content to APub from InDesign.

One of the problems I have seen in many font families is they are only designed to work properly on the original platform they were created on - the particular OS. Many font families are originally created on a Mac and quite often are simply broken on Windows and Linux because the designer either doesn't know any better, or simply doesn't care. I have edited (fixed) many FOSS font families to work properly on LibreOffice on Windows. Actually it is easier to get fully working font families in LibreOffice on Windows than it is in LibreOffice on Mac or Linux due to problems in the underlying libraries used on those platforms. For example an updated Open Sans family does not work properly in LibreOffice (or Word) on Windows. The required naming conventions to work properly cross-platform are simply missing. So I created the Opens Sans LO font family which works perfectly in LibreOffice on Windows. And it still works properly in modern applications like APublisher, InDesign, Quark, etc. This is not difficult, it simply requires some best-practices. FontLab makes this very easy. So does TransType. It is nearly automatic. FontCreator is a little more manual, but all the tools are there. FontForge may have all the tools. Dunno. The interface is so bad I stopped trying to use it. I do not use Glyphs, but the documentation appears to show the tools are there. They all use different terminology for the same fields (I used the FontCreator terminology above). You mentioned "style-linked" which is what Glyphs uses (and I assume FontForge). The goal is the same - cross-platform support in both older and modern applications. My point ... Tweaking one or two name fields with a three-font family may enable it to work on one OS or in one application, but to work properly cross-platform and in older and modern Windows requires properly filling-in all the correct naming fields not simply tweaking a few to get it to work today on this application on this OS. Glad to see you fixed the Medium font, but the other two should also be fixed for consistent cross-platform support. That is what I meant about being fixed "properly." So please accept my apologies if that seemed a bit harsh. Glad you got it working.

Well that is a partial fix that works in APublisher probably because you filled-in the Typographic Family and Typographic Subfamily on the Medium font. Changing the Font Family for medium to Akzidenz-Grotesk BQ Medium will help older Windows apps. Even though leaving Font Subfamily set to Medium is simply wrong, it will likely work because it is the only font in that new medium family and many applications will assume it is the regular font. To do it correctly for both modern applications and older applications: - Typographic Family and Typographic Subfamily should be filled-in properly to support modern applications which support multiple weights and widths under one family - Font Family and Font Subfamily should be filled-in properly to support older applications which only support the limited R/I/B/BI fonts. This partial fix is a band-aid that may or may not work in other applications.

FontLab has a feature to quickly export all the defined weight/width combos of a variable font. It worked great ... except that the font names were completely wacko. Fixed the font names in TransType. Three widths: Condensed, SemiCondensed, and Normal. Five weights: Light, SemiLight, Regular, SemiBold, and Bold. Total of 15 font files (in file below). I installed and tested in LibreOffice. All seem to be working OK. Please test in APub and report back here. Bahnschrift LO.7z

I examined the font files - and it was as I suspected. The Medium font has Medium in the Font Subfamily, and the Font Family is Akzidenz-Grotesk BQ. To work properly in older Windows apps like Word the medium font should be a separate Font Family . - Font Family: Akzidenz-Grotesk BQ Medium - Font Subfamily: Regular This is why the fonts do not work properly in Word. And they also do not work properly in APub because of this and the missing Typographic Family and Subfamily. I will PM you a link to some properly structured fonts for testing.