Shaping differences

[vv-monsalve]

When installing and testing the models (ARG, COL) in InDesing, Word, and Pages, some shaping differences are observed.

In Word and InDesign the Contextual Alternates features were activated. Should something else be enabled in InDesign for the shaping to work well?

ARG

InDesign

Pages

MS Word

[vv-monsalve]

COL

InDesign

Word

Pages

[josescaglione]

yes, indesign requires, for the time being, the wolrd paragrph composer.

[vv-monsalve]

In that case, please include the following:

• [x] A list of the applications you foresee the target users would use (ordered by priority)
• [x] Tests for the fonts in all of those applications, both in Windows and Mac
• [x] A document with usage instructions for each of those applications. Specifying which features should be activated for optimal performance of the font (e.g. Contextual alternates in Word)

[josescaglione]

Please find the list and test results below. Would you like this included in the Readme file or as a separate document?

Text editors:

Microsoft Word Mac/Win Must activate Contextual alternates in the Advanced tap of the Fonts screen. Also recommend to activate kerning for all text sizes.

Libre Office Mac/Win No action necessary. CALT is active automatically.

TextEdit Mac No action necessary. CALT is active automatically.

Pages Mac No action necessary. CALT is active automatically.

Microsoft Notepad Win No support

Design applications:

Adobe Indesign Mac/Win CALT is active automatically. Must select Adobe World Ready Paragraph Composer in the Paragraph panel.

Adobe Illustrator Mac/Win CALT is active automatically. Must select Middle Eastern Composer in the Paragraph panel.

Adobe Photoshop Mac/Win CALT is active automatically. Must select World-Ready Layout in the Paragraph panel.

Affinity Publisher Mac No support

Slide presentations:

Keynote Mac No action necessary. CALT is active automatically.

[vv-monsalve]

Would you like this included in the Readme file or as a separate document?

We discussed this with @josescaglione. This information would be included in a separate document for each model addressed to the teachers (as the targeted audience) and not expert users, at the end of it. Ideally, including print screens of the places where these features should be enabled on each application.

[vv-monsalve]

After multiple tests with different build systems, we found that some of the issues shown above were caused when there is no PostScript names declared for all the instances included in the variable font. So, we must ensure they are always included in the fonts.

Closing this issue here.