To create a translated literal text, the key must be in snake case format and match its content value. The content value should be in lowercase and can include parameters using the "--param" syntax within curly brackets. For example, a key of "file--param_too_big" could have the value "File {{value}} is too big." This ensures the translated literal matches its intended meaning.
To create a translated literal text, the key must be in snake case format and match its content value. The content value should be in lowercase and can include parameters using the "--param" syntax within curly brackets. For example, a key of "file--param_too_big" could have the value "File {{value}} is too big." This ensures the translated literal matches its intended meaning.
To create a translated literal text, the key must be in snake case format and match its content value. The content value should be in lowercase and can include parameters using the "--param" syntax within curly brackets. For example, a key of "file--param_too_big" could have the value "File {{value}} is too big." This ensures the translated literal matches its intended meaning.
step 1: snake case format to key value for example: submission_references step 2: key matching with its content for example: exception_title: "exception to lack of novelty" → WRONG!! exception_lack_novelty : "exception to lack of novelty" → RIGHT!!! step 3: the value of the key is in lower case. step 4: if literal text has some parameter to add we should to use the reserved syntax"--param" for example: "file--param_too_big": "File {{value}} is too big."