Open jonorthwash opened 11 months ago
yeah some kind of naming convention would do it; apy just looks in the modes folder for pairs names xyz-xyz
(where xyz can include underscores)
(Though ideally we'd have metadata associated with modes files to make the detection more robust.)
Agreed about metadata.
The big-picture question is whether it makes sense to treat orthographic conversion modes separately from translation modes. Conceptually they're pretty similar.
For example, orthographic conversion modes between
zab_Simp
andzab_Phon
are detected as translation pair modes:However, conversion between them doesn't work via APy:
This does work in the command-line version of the mode:
Some modes between different locales may legitimately be more than just orthography; i.e., they should be thought of as full translation pairs (e.g., between American and British English). So I'm wondering whether, instead of fixing this, it would make sense to name the orthography-only modes
-ortho
or something and have a separate detection process for them, and serve them separately (and eventually have a different interface for them in html-tools).