I made a thought exercise of imaging what it would be like to design the L20n syntax from scratch, today.
I was guided by the following goals: - Make the most commonly used syntax easy on the eyes and easy to understand. - Improve error recovery and make it easier to use HTML in translations. - Make it easy to parse complex expressions. They are important for the advanced features of L20n, but cost a lot in terms of parsing and resolving. - Allow to use dashes in entity names. - Make it possible to reference entities by dynamic names unknown at parse time. - Make it clearer that translation variants are different permutations of the same translation data and as such, they are different than attributes and are not part of the social contract. I created a sample file with a new proposed syntax. Nothing is set in stone yet and I'm looking forward to hearing your thoughts about the goals and the proposal. https://gist.github.com/stasm/c99010a8ab6d467562ba Thanks, -stas _______________________________________________ tools-l10n mailing list [email protected] https://lists.mozilla.org/listinfo/tools-l10n
