Fallback to DeepL autodetection if source language is unsupported #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kauz56
force-pushed
the
autodetect-fallback
branch
3 times, most recently
from
cfcb4e0 to
4fe6aa4
Compare
kauz56
force-pushed
the
autodetect-fallback
branch
from
4fe6aa4 to
e189b59
Compare
|
Also just added compatibility with glossaries. Sorry for the mess with the force pushes... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ran across this with a project, where we're using a mixed language source (locale
xx-XX), for a "show in original language" feature on the translated pages. This is likely a rare edge case, so I'd understand if you don't want to support this. Would be appreciated though! 😃