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

Improve the way finders are defined #71

Open
ali1234 opened this issue May 1, 2022 · 0 comments
Open

Improve the way finders are defined #71

ali1234 opened this issue May 1, 2022 · 0 comments

Comments

@ali1234
Copy link
Owner

ali1234 commented May 1, 2022

Finder("100\x02ARD/ZDF\x07Mo 26.12.88\x0222:00:00",

Currently finders use two strings. One contains a literal example of a header and the other contains special characters that define how the header can vary. It works well for UK Teletext/Oracle/Ceefax but has problems with other broadcasts from countries:

  • No way to define numeric month/year dates.
  • Text patterns expect the English spellings.
  • The system is quite confusing to use.

One possible way to improve the finders would be to use regular expressions. This would allow any arbitrary type of header to be matched. However the finder needs to do fuzzy matching with ranking based on the type of match. Also, regular expressions would probably be even harder to understand - although they are at least a standard rather than something I have made up.

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

No branches or pull requests

1 participant