Use a language directory's manual.xml when present#322
Open
lacatoire wants to merge 1 commit into
Open
Conversation
Let a language directory ship its own manual.xml to build a self-contained manual that references only its own books, instead of the main manual skeleton in doc-base. Falls back to the doc-base manual.xml when absent, so existing builds are unaffected.
lacatoire
force-pushed
the
feat/per-language-manual
branch
from
19df0db to
fe2ce5c
Compare
alfsb
approved these changes
Jul 16, 2026
alfsb
left a comment
alfsb
left a comment
Member
There was a problem hiding this comment.
This is ok for me, and aligns with what I'm developing in doc-en 5682. But it may conflict with doc-base 321, so a bit of manual merge would be necessary.
In the meantime, apply these changes locally, so you are not blocked while all configure.php PRs are not merged.
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
2 participants
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.
When a language directory contains its own
manual.xml,configure.phpnow builds from it instead of the main manual skeleton in doc-base. When absent, the doc-basemanual.xmlis used as before, so all existing builds (en and translations) are byte-for-byte unaffected.This lets a manual be fully self-contained in its own repository: it can declare its own entity wiring and reference only its own books. Motivation is the third-party extension manual split (lacatoire/doc-contrib), where reusing the main skeleton fails because it references ~160 core books the contrib repo does not provide. Supersedes the file-entities scanning approach discussed in #320.