The error message built into `fluent.syntax` could use some rewording for sure. But I think that since they're produced directly by the parser, it might be impossible to ensure they are phrased given every possible audience. So perhaps the best way forward is to keep them succint and "dry". For this use-case, I think the alternative would be to check the `error.code` and use the array of `error.args` to build custom error messages. This would allow tailoring the wording to the expect audience (translators), as well as localizing them in the future, too.
Bug 1630407 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The error messages built into `fluent.syntax` could use some rewording for sure. But I think that since they're produced directly by the parser, it might be impossible to ensure they are phrased in a way which caters to every possible audience. So perhaps the best way forward is to keep them succint and "dry". For this use-case, I think the alternative would be to check the `error.code` and use the array of `error.args` to build custom error messages. This would allow tailoring the wording to the expect audience (translators), as well as localizing them in the future, too.