Tino Didriksen <m...@tinodidriksen.com> čálii: > The monolingual packages install many more modes, because they are used for > further development. So you can get morph from those. But biltrans is not > normal to want if you aren't a developer, and thus building from source.
The reasoning is that - people who want to use Apertium for translation only care about installing pairs - `apertium -l` lists all available modes of installed apertium packages - we shouldn't clutter that list for people who want to use Apertium for translation So kaz-rus shouldn't be installing biltrans, because an end-user would find it confusing/annoying and have more trouble finding what's useful to them in that list. However – there are people who want to use debug modes but would rather not want to compile a pair and manually `git pull && make && make test || revert-to-last-working-revision`. Would it make sense to install debug-modes to a debug-modes folder? Put stuff like -biltrans etc. in /usr/share/apertium/debug-modes, and then `apertium -l` only shows translation /modes while `apertium -L` shows both /modes and /debug-modes? (And `apertium kaz-rus-biltrans` works without any special switches because why not, while `apertium nonexistent` runs `apertium -l` and gives a hint to use `-L` to show the rest.)
signature.asc
Description: PGP signature
_______________________________________________ Apertium-stuff mailing list Apertium-stuff@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/apertium-stuff
