L20n/Features/Resource file syntax
Jump to navigation
Jump to search
goal
Consider potential improvements in the resource file syntax in order to improve working with the source files.
The format is supposed to follow L20n/File_format_principles.
content
Currently we have LOL syntax, and feedback on it from Mozilla French Team [12].
The counter proposal is revolving around changes to the LOL syntax that would make it less XML'y, and more YAML'y, so to say. The list of proposed changes is the following:
- remove entity delimiters (<>) and replace them with indentation-based entity structure recognition.
- separate entity attributes into separate entities
- C-like comments vs. YAML-like comments
- string delimiters in YAML vs LOL
Example: LOL:
<brandName[plural(downloadCount)] "Value" accesskey: "c">
Proposal:
brandName[plural(downloadCount)]: Value brandName.accesskey: c
Alternative proposal:
brandName[plural(downloadCount)]: Value accesskey: c
See demo file
status
We need to investigate how such syntax may work for the localizers, will it indeed make working with files easier, how will it accommodate the grammar that we have for LOL together with the proposed extensions listed on the L20n/Features list.