French-English Blazon Term Cross-Mapper
Exact caller verified edition-specific FrenchEnglishBlazoncrosswalk; no unrestricted translation or historical abbreviation ambiguity resolution.
Description
Heraldic term translation depends on the vocabulary and context of the reference being used.
Heraldic term translation depends on the vocabulary and context of the reference being used.1
Exact lexical pairs provide a controlled glossary rather than free-text translation.
When to use French-English Blazon Term Cross-Mapper
Use this tool to calculate or review the supplied observations under the stated rules. Establish the source tradition, viewing frame, coordinate units and independently annotated features.
How to use French-English Blazon Term Cross-Mapper and understand its results
- Establish the source tradition, viewing frame, coordinate units and independently annotated features.
- Enter queryTerms, callerVerifiedSourceTerms, callerVerifiedTargetTerms, using the field meanings and rules below, then run the tool.
- Read result.mappedTerms, using the output meanings and calculation rules below.
- Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| queryTerms | Query terms; use the exact reference token or coordinate domain stated below | list of string | Required |
| callerVerifiedSourceTerms | Caller verified source terms; supplied assertion retained unchanged, not independently verified | list of string | Required |
| callerVerifiedTargetTerms | Caller verified target terms | list of string | Required |
Supply nonempty aligned source and target term lists with unique nonblank exact source strings. For each query term find its exact source match and return the corresponding target in query order. Queries may be empty or repeated. Any unknown query fails the entire invocation; target strings are returned unchanged.
translations_i=targetTerms[indexOf(sourceTerms,query_i)] Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Calculated observation or reference | object |
| result.mappedTerms | mapped Terms | list |
{
"input": {
"queryTerms": [
"a",
"b"
],
"callerVerifiedSourceTerms": [
"a",
"b"
],
"callerVerifiedTargetTerms": [
"x",
"y"
]
},
"output": {
"result": {
"mappedTerms": [
"x",
"y"
]
}
}
}Limitations and assumptions
There is no translation engine, normalization or contextual disambiguation. The glossary must be independently suitable for the terms and source edition.
Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above. Extremely large composite outputs are rejected.
Alternative or Complementary methods
For a related step, use Cross Type Variant Identifier (fitchy/patty etc.): Cross variants are named through their shape and the adopted heraldic vocabulary. For a complementary comparison, use Diminutives Size Hierarchy Lookup: Ordinary diminutive names and size relationships depend on heraldic convention.
References
-
French-English Blazon Term Cross-Mapper — tool.io
Similar or alternative tools
- Cross Type Variant Identifier (fitchy/patty etc.)
Cross variants are named through their shape and the adopted heraldic vocabulary.
- Diminutives Size Hierarchy Lookup
Ordinary diminutive names and size relationships depend on heraldic convention.