Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read Monolingual modes.xml #129

Open
mr-martian opened this issue Mar 13, 2023 · 1 comment
Open

Read Monolingual modes.xml #129

mr-martian opened this issue Mar 13, 2023 · 1 comment

Comments

@mr-martian
Copy link
Contributor

Every bilingual option except which transfer system to use can be derived from the monolingual modes.xml, so why not have a --with-lang1 and --with-lang2 that figures it out? This could also then support creating translators for languages with variants or multiple orthographies.

Some specific notes:

  • if there's a mode matching *-lexc or *-lexd, we need HFST trimming
  • are all preference files present in monolingual modes, or should we add an option for that?
@unhammer
Copy link
Member

unhammer commented Mar 14, 2023

apertium-nno/modes.xml has nno-gener-prefs at least

https://github.com/apertium/apertium-nno/blob/master/modes.xml#L19-L29

For bilingual preferences, it's kind of independent of the existence of monolingual preferences. That is, people might potentially want preferences when translating into some language that doesn't have monolingual preferences; they might also not want to bother with bilingual preferences even if the monolingual has preferences (though I'm guessing this situation is less likely). Maybe a good default is to include bilingual prefs if there are monolingual, otherwise there's a switch --biprefs=on|off

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants