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

Support string-search for advanced subtitle mode #484

Closed
Kokujou opened this issue Apr 5, 2022 · 3 comments
Closed

Support string-search for advanced subtitle mode #484

Kokujou opened this issue Apr 5, 2022 · 3 comments

Comments

@Kokujou
Copy link

Kokujou commented Apr 5, 2022

Hello. I want to realize the following scenario:
When having german audio (ger), i want to have only forced subtitles.
the syntax for this would be ger:*|f

now, the problem for this is, not all subtitle creators are as nice as normal people to set the forced flag for their sub
instead, they will just name it "German Forced [ger] (ass) [default]"

so i want to request a pattern, that allows me to select the subtitle by name. my proposal would be something like this:
ger:forced meaning, for the german language select subtitles containing the word "forced", similar would be
ger:forced if you want to make the "contains"-functionality explicit or
ger:"forced" if you want to make it clear that we're talking about string-search

i already tried some things to work around, but i can't think of any way to do it with negations.
ger:|!n wouldn't work because you would still select default subtitles - i don't want that
ger:
|!n!d would'nt work in case the forced subtitle is a default subtitle - like in my current case

@Nevcairiel
Copy link
Owner

You can already match against the name

"ger@forced" would look for a german track that contains the string "forced" in its title.

The @ should always be the last part, so you can also do eg. "ger|d@forced" if you want to include a flag.

The only limitation is that the string cannot contain spaces (or commas or semicolons), so you can only match a single word, but for checking for Forced that should be plenty.

@Kokujou
Copy link
Author

Kokujou commented Apr 5, 2022

awesome :o then my only suggestion is to put that as an example in the git documentation^^ thank you!

@Kokujou
Copy link
Author

Kokujou commented Apr 5, 2022

ah ... and another request: please make it case insensitive ^^

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