Repository navigation
docs: where translations.xml lives, and translations of included projects - #468
Merged
Merged
Conversation
…ects - translations.mdx: translations are read only from translations.xml at the project root, one file per project; an included project can have its own, whose tags and languages the including project gets. - project.mdx: the three root XML files are the exception to "LVGL Pro doesn't enforce a folder structure"; included projects also share their translations. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
All reported issues were addressed across 2 files
Reply with feedback, questions, or to request a fix.
View guided diff | Turn on auto-fix | Re-trigger cubic
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An included project cannot have a translations.xml; the product has one set of translations, in the root project. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
All reported issues were addressed across 2 files (changes from recent commits).
Reply with feedback, questions, or to request a fix.
View guided diff | Turn on auto-fix | Re-trigger cubic
lv_xml_load_all_from_path() registers every <translations> file it finds at runtime, so the page says that too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
The docs never said where the translations file lives, or that a product has only one. In the Editor and the CLI, translations come only from
translations.xmlat the root of the main project.Changes
docs/syntax/translations.mdx: new "The translations file" section.translations.xmlat the project root.translations.xmlin a sub-folder is an error, and a translations file under any other name is not loaded.translations.xml, and all strings go into the root project's file.docs/syntax/project.mdx:project.xmlandglobals.xmlare required,translations.xmlis optional, and each must sit at the root under exactly that name.translations.xml.Where this comes from in the Editor
translations.xmlis recognized by name, only at the project root (lved-xml-schemaworkspace-index-builder.ts).lved-project-layoutvalidation.ts).<project>/translations.xml.translations.xmlin an included project, and for a root file with a<translations>root under another name.🤖 Generated with Claude Code