Sushain Cherivirala
Sushain Cherivirala
A bunch of elements need labels for screen readers, e.g. the language selectors, locale selectors, copy/clear buttons. Also, we should probably be localizing the close modal sr-only buttons.
Progress has been made in #73 and https://github.com/goavki/apertium-apy/pull/31 Make language detection work properly and do "did you mean" style if people choose an unlikely source language.
I really want it to retain my heights. Resetting them to whatever the app wants is silly and I'm not sure when this bad behavior creeped in. @share-with-me perhaps this...
but it isn't visible to the user in that view. - if APy actually uses it, then it should be made visible to the user. - if APy does not...
From someone: - Add a mode that colours the resulting translation depending on how reliable it is. - One possibility would be for language pairs to have different colours depending...
It would be cool if we could specify a pair within the metadata JSON for a `*.json` strings file and use `localization-tools.py` to automatically fill in missing localizations. We would...
It would be cool to have chained translation display the path taken to get from say eng => kaz. @jonorthwash
> IMO, it's pretty silly having these docstrings just repeat the type of the argument. Rather, they should describe the argument and then whatever document generation tool we use will...
- [ ] check what APy supports - [ ] check https://github.com/apertium/apertium-init/blob/master/hfst-language-module/modes.xml - [ ] check https://github.com/apertium/apertium-init/blob/master/lttoolbox-language-module/modes.xml