Skip to content

Conversation

@TWF1212
Copy link
Contributor

@TWF1212 TWF1212 commented Sep 5, 2025

This will allow an optional keyword to be supplied. This keyword needs to be present in either the title or displayTitle in order to be considered for matching.

I made this change so I can easily make subtitles with "Forced" in the title be the only subtitles applied. This can be improved if there is a way to determine the forced flag instead of it needing to be in the name, but for my library this was sufficient and helpful.
image

image image

This will allow an optional keyword to be supplied. This keyword needs to be present in either the title or displayTitle in order to be considered for matching.

I made this change so I can easily make subtitles with "Forced" in the title be the only subtitles applied. This can be improved if there is a way to determine the forced flag instead of it needing to be in the name, but for my library this was sufficient and helpful.
@TWF1212
Copy link
Contributor Author

TWF1212 commented Sep 5, 2025

I implemented this based off the idea in an Issue 53 comment:
#53 (comment)

@TWF1212
Copy link
Contributor Author

TWF1212 commented Sep 7, 2025

I also added a search for show since I was working on this code and saw this comment:
#90 (comment)

@TWF1212 TWF1212 changed the title Add subtitle keyword input for filtering subtitle tracks. Add subtitle keyword input for filtering subtitle tracks and Series Search. Sep 7, 2025
Copy link
Owner

@cglatot cglatot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty good work!

2 comments to note for the subtitle keyword matching, though:

  1. The search box pushing down the subtitles table makes it look lopsided when side-by-side with the audio tracks table in in desktop. But I'm not sure how you would make this look nicer. Maybe a similar keyword search for audio as well? Less relevant, but might be some usecase for it, and would match styling.
  2. It's not very obvious that after you type in the keyword, you still need to select the track. I mean, I know it's not obvious even beforehand, but I find it counterintuitive. Might be worth updating the wording under the search box to say something.

Since these are enhancements, I've still approved and merged this, and opened #91

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

Successfully merging this pull request may close these issues.

2 participants