Steven R. Loomis

blocked by #11236

https://build.palaso.org/buildConfiguration/Keyman_Common_KPAPI_TestPullRequests_macOS/431756?expandBuildDeploymentsSection=false&hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildProblemsSection=true&expandBuildChangesSection=true had: ``` Downloading icu-for-uset source from https://github.com/unicode-org/icu/releases/download/release-73-1/icu4c-73_1-src.tgz [10:24:22 ] A fallback URL could be specified using source_fallback_url key in the wrap file [10:24:22 ] [10:24:22 ](https://build.palaso.org/buildConfiguration/Keyman_Common_KPAPI_TestPullRequests_macOS/4317 src/meson.build:59:0: ERROR: could...

`MESON_PACKAGE_CACHE_DIR=${HOME}/Downloads/packagecache` works well globally with meson 1.3.0, allows sharing between keyman builds locally so I just set this in my local environment globally

can we simply set MESON_PACKAGE_CACHE_DIR to something persistent on the build servers?

see https://github.com/keyman-keyboards/ldml_test/pull/1 for a manually generated README

Sorry, I was in file mode and didn't see this: per #10614 quoth @mcdurdin > Our messages (errors, hints, and warnings) don't have line numbers at present, which is going...

Perhaps we could use JavaScript symbols for the Line information, similar to what I'm already doing for import information

`CompilerEvent` already has: ```js export interface CompilerEvent { filename?: string; line?: number; code: number; message: string; /** * an internal error occurred that should be captured with a stack trace...

- Browsers usually evergreen, so unicode version ala #10183 not as much of an issue. - majority of browsers visiting the site are recent

- could use icu4x's UnicodeSet support