epic: shared fonts in Keyman Developer packages 🐻 #12776
Draft
+11,974
−498
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The concept here is that the 'Name' property for a file can now be a remote reference, rather than a local file. There are two supported formats in this commit: * GitHub: This is a cutdown version of a plain github.com URL, and must match this exact format: ``` github:<owner>/<repo>/raw/<hash>/<filepath/filename> ``` This format is mandated in order to ensure that we always have a hashed version of a file from the origin. This gives us reproducible builds, which avoids churn issues when font files change. Example: `github:silnrsi/fonts/raw/b88c7af5d16681bd137156929ff8baec82526560/fonts/sil/alkalami/Alkalami-Regular.ttf` gets https://github.com/silnrsi/fonts/raw/b88c7af5d16681bd137156929ff8baec82526560/fonts/sil/alkalami/Alkalami-Regular.ttf An alternative could be to just have `https://github.com/silnrsi/fonts/raw/b88c7af5d16681bd137156929ff8baec82526560/fonts/sil/alkalami/Alkalami-Regular.ttf` which could be matched with a regex in the same way as the `github` prefix, and would avoid the need to munge the input URL. **Discuss!** * fonts.languagetechnology.org: references just a font identifier. This is somewhat broken, because if the source file changes, we don't know about it and won't publish an updated version of the package. So this needs some more discussion (we could e.g. embed the version number in the request, e.g. `flo:andika@6.200`). **Discuss!** ``` flo:<family> ``` e.g. `flo:andika` gets https://fonts.languagetechnology.org/fonts/sil/andika/Andika-Bold.ttf Future sources could be considered, e.g. noto. We don't want to allow arbitrary URLs, both for stability and for security reasons. This change is entirely compiler-side, so we don't need to make any changes to apps, and so packages will be backwardly compatible. A lot of work will need to be done with the Package Editor in TIKE to support this feature. Fixes: #11236
…at/developer/kmc-package-source-files-from-remotes-2
…es-from-remotes-2' of https://github.com/keymanapp/keyman into feat/developer/kmc-package-source-files-from-remotes-2
After the reorganization of the package compiler build, we now need to make sure all files referenced in the .kps exist in order for the unit tests to pass.
…matches As our data files often come from Windows, we need to test if paths are Windows-style absolute paths, with either path separator (e.g. `C:\...`, `\path\...`, `\\server\path\...`, `/path/...`). Technically, this means a posix path that starts with an escaped character would be regarded as absolute, but IMHO those kinds of shenanigans deserve to result in a failing build anyway. ;-)
…ge-source-files-from-remotes-2
Adds error for unsupported versions, hint for low versions when using remote references.
…es-from-remotes-2' into change/developer/12746-kmc-copy-full-gh-url
…ce-files-from-remotes-2
… into change/developer/12746-kmc-copy-full-gh-url
…ource-files-from-remotes-2 feat(developer): kmc-package support remote fonts and files 🐻
…opy-full-gh-url change(developer): use full github url in kmc copy parameters
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
…ed-fonts chore: merge master into shared-fonts 🐻
Test-bot: skip Build-bot: skip release:developer,windows
chore(windows): VS2022 patch for epic/shared-fonts 🐻
…o-shared-fonts auto: A19S15 merge master into shared-fonts 🐻
…o-shared-fonts auto: A19S16 merge master into shared-fonts 🐻
…o-shared-fonts auto: A19S17 merge master into shared-fonts 🐻
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brought to you by the Share Bear 🐻
See: #11236
Build-bot: build
Test-bot: skip