Repository navigation
chore(release): v1.23.1 — add qya (Quenya/Tengwar) to the default locale list - #341
Merged
Merged
Conversation
…ale list Adds `qya` to tiger.i18n.locales in core.ini, alongside the existing `tlh` stunt locale, so /qya/ resolves fleet-wide the same codified way Klingon does. No code change: LocalePrefix and Tiger_Theme::contentFile already accept a 3-letter code, and installs with no qya content fall back to the English base page (exactly as tlh does). The Quenya home + Alcarin Tengwar font ship in the TigerMarketing theme (v1.1.0); this just makes the locale selectable. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ASauLLscjqdsNqBNsx2Typ
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Adds
qyatotiger.i18n.localesinconfigs/core.ini, next to the existingtlhstunt locale, and bumpsTiger_Versionto 1.23.1.Why
/qya/(the Quenya/Tengwar marketing home) only resolves whenqyais a supported locale.tlhlives in the core default list, so the codified, drift-free, fleet-consistent way to enableqyais the same: incore.ini. Prod (and the fleet) picks it up through the normal one-click update — no per-box config poking.Blast radius
Tiger_Controller_Plugin_LocalePrefixandTiger_Theme::contentFile()already accept a 3-letter code (that's howtlhworks), and thecontentFilevariant regex^[a-z]{2,3}$already matchesqya.tlhbehaves on a bare install. No corelanguages/qya/*files are required (liketlh, it's a partial/stunt locale; the Quenya content + Alcarin Tengwar OFL font ship in the private TigerMarketing theme, v1.1.0).['en','es','tlh'],['en','es']), so none asserts the full default and none breaks.Proven
The qya page already renders end-to-end on tiger-dev through the real dispatch pipeline (
/qya/→ 200,LANG=qya,<html lang="qya">, 782 Tengwar glyphs) withqyaenabled; this PR makes that enablement the codified default instead of a dev-onlyapplication.inioverride.🤖 Generated with Claude Code
https://claude.ai/code/session_01ASauLLscjqdsNqBNsx2Typ