L20n/Issues
< L20n
- bug tracking
- We should be able to file and track bugs. We'll start with bugs in the Mozilla Localizations product, Component Other. Make sure to CC l10n@moz on those. We'll create a structure for those bugs once we know what needs to get tracked.
- Editors
- If you know someone who should be participating in this work as an editor, please convince her or him to apply.
- Tools used
- One part of the specification should be a grammar specification for the fileformat, in a somewhat understandable syntax. Currently, I'm using antlr to create parsers from a EBNF-like grammar. It promised to create code for more than just java, but currently, I'm hitting a few blockers. It might be that I'm hitting bugs in the 3.0b5, or just limitations of the approach in antlr. Anyway, there's currently no descent output other than java, and creating ASTs doesn't work that well without putting AST-related constructs into the grammar. Which is merely noise. Suggestions welcome, in particular for tools that could even generate js.
- Platform dependent strings
- Can l20n help with doing platform-specific strings (think Options vs Preferences) for Mozilla apps?
- yes/no dialogs
- Can we provide context specific button values for stuff like yes and no? See proposal for that on gnome-i18n.
- Noun classes
- We should use noun classes to describe the strengths of l20n.
- Genitive case (possessives)
- See genitive case for more.
Back to L20n...