Localisation of schematron strings #38
Open
Conversation
This file contains 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
10 tasks
CMath04
approved these changes
Feb 18, 2025
joachimnielandt
force-pushed
the
feature/schematron-loc
branch
from
231c18e to
01405bf
Compare
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.
Depends on core change proposed in geonetwork/core-geonetwork#8665.
Schematron localisations that make use of a generic function that replaces placeholders by their respective values. Localisation strings can be sourced from the rule-specific file or a schematron-shared file. Testing this approach on
enganddut, with a fallback toengwhen localisations are missing.To do: