Skip to content

Commit c81a916

Browse files
authored
Merge pull request #2455 from keymanapp/docs/displaymap-font-info
docs: add more detail on `&displayMap` font choices
2 parents c271166 + f323fdc commit c81a916

1 file changed

Lines changed: 12 additions & 2 deletions

File tree

developer/language/reference/displaymap.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,8 +72,18 @@ Using `&displayMap` means that the design-time model for the On Screen Keyboard
7272
and Touch Layout can continue to use the correct Unicode values on the keycaps,
7373
making the transformation to PUA characters only in the compilation process.
7474

75-
The Kbd font associated with the `&displayMap` should be added to the keyboard's
76-
package and selected in the package 'Keyboard Font' field.
75+
## Font selection
76+
77+
* The Kbd font associated with the `&displayMap` should be added to the
78+
keyboard's package and selected in the package 'Keyboard Font' field
79+
(`OSKFont` property in the .kps XML source).
80+
* There is no need to add the font also to the list in the `Keyboard Font` /
81+
`Web Fonts` dialog box (`WebOSKFonts` property in the .kps XML source).
82+
* The .kvks file and .keyman-touch-layout file can also reference fonts. These
83+
fonts are used only at design time, so they should be any font that supports
84+
the script, and should not be the `&displayMap` Kbd font, because the
85+
transform to use the `&displayMap` Kbd font is done during the compilation
86+
of the keyboard and package.
7787

7888
## Standard conventions for use of displayMaps
7989

0 commit comments

Comments
 (0)