spiegel-keyman/developer/docs/help/guides/distribute/tutorial/step-3.md
Marc Durdin b751336c13 refactor(developer): copy dev 17.0 help into repo
1. Copy help.keyman.com/developer/17.0/* into /developer/docs/help
2. Update references to 18.0 where appropriate
3. Copy all referenced images from /cdn/dev into
   /developer/docs/help/images and update links in documentation

Next commit: add deployment to help-keyman-com.sh. Note: simplest way to
test links at this point is to use the help.keyman.com auto deploy and
wait for the PR on help.keyman.com to be validated; we could look at an
internal link validation tool that verifies markdown links?

Relates-to: #12347
2024-09-16 08:46:24 +07:00

1.5 KiB


title: Step 3: Creating a package and adding files

We are finally ready to open up the Package Editor and create the new package.

  • In the Project Window in Keyman Developer, click the Packages tab, and click New Package.... Enter the path and filename of the package you are creating.

Tip

This tutorial makes a package named khmer_angkor.kps, but you could call yours qfrench.kps.

A package source file will have the extension .kps, and will be compiled in a file with extension .kmp.

After you click OK, the Package Editor will open with the Files tab visible.

  • In the Files tab, click Add... to add all the files we discussed in the previous step to the package. You can add multiple files at once, and from multiple folders. When the package is compiled, all the files will be placed in the same folder within the package.
  • If your package includes .js touch layout keyboards, you can associate fonts and languages in the Keyboards tab. A valid BCP 47 language tag must be set or the keyboard will not install on your mobile device.

You could stop here. This would be a completely valid package, but it would not be as good as it could be. So let's continue on to the next step, and fill in some descriptions of the package.

Step 4: Filling in package details