Consider blessing an official system location for tldr.zip? #19775
Description
Imagine a Linux distribution that wanted to package a system that worked entirely offline, or a build engineer that wants to consume tldr.zip but has build servers without Internet access or needs to be able to verify hashes of all inputs to the build. Both use cases would benefit from an officially blessed directory (maybe something like /usr/share/tldr) that could be preloaded with a copy of tldr.zip and have tldr clients read from that location as a fallback if caching fails or is disabled. This is also UNIX-friendly as the shared zip file can be reused by multiple user accounts on the same system.
The alternative is to load up the tldr client's cache dir ahead of time. The location is both tldr client specific and scoped to the individual user account. Having a system-wide fallback and asking tldr clients to respect that default is a more general solution and has its own benefits.