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
[add] translations filter: Filter by translations #3019
base: develop
Are you sure you want to change the base?
Conversation
Been using this for some time as a user plugin and works as expected! Is this relevant to flexget? Or can it be closed? |
This PR is stale because it has been open 150 days with no activity. Remove stale label or comment or this will be closed in 60 days. |
any updates? |
This PR is stale because it has been open 150 days with no activity. Remove stale label or comment or this will be closed in 60 days. |
This looks awesome! Sorry for delays. |
def clean_symbols(self, text: str) -> str: | ||
"""Replaces common symbols with spaces. Also normalize unicode strings in decomposed form. | ||
|
||
Args: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reStructured would be preferable, although not as critical anymore with type hinting
if mycode: | ||
lang = mycode.name | ||
except babelfish.LanguageReverseError: | ||
pass |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will hide errors, is this always desirable? Log exception / debug instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now I return a debug message
|
||
translations: | ||
languages: | ||
- "imdb_languages" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't quite follow, in some examples the "languages" key contains list of languages like "japanese" but here we have entry field names. If it has some intelligence/magic that allows both, I would much prefer to be explicit and have "language_fields" configuration key instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've split the fields, now we have languages and language_fields
Hello @paranoidi I've been out for some time, but now I'm back, I'll look into it and make the adjustments. The change on the language field (and yes it's "magic" to see if it's a language or a field), I don't like that change, but I understand the reason, I'll make the adjustment. Tks |
This PR is stale because it has been open 150 days with no activity. Remove stale label or comment or this will be closed in 60 days. |
Sorry for the delay on this, had a lot over my hands lately! Going to get back on this ASAP. |
I did the reviews sorry for the delay on this @paranoidi I've been very busy. |
This PR is stale because it has been open 150 days with no activity. Remove stale label or comment or this will be closed in 60 days. |
Not yet forgotten! I'll look at this as soon as possible |
This PR is stale because it has been open 150 days with no activity. Remove stale label or comment or this will be closed in 60 days. |
Not forgotten... Just low on time |
Motivation for changes:
Filter entry based on translations (subbed or dubbed) and original language
Detailed changes:
Config:
Log and/or tests output (preferably both):
Test cases in test_translations_filter.py
To Do: