Is your feature request related to a problem? Please describe.
The title might be a bit confusing, i'll explain. While the current variables for the external search websites support many sites some sites do not match the format given.
Some sites i've run into do not use %20 for spaces in the surname, but use a + instead.
Other cases i've run into is sites asking for date ranges in dd-mm-yyyy format, or yyyy-mm-dd, and i'm sure American sites would use mm-dd-yyyy.
And a regional image archive saving images as "John Doe" or "J. Doe"
It's an impossible task to add variables for all possible cases.
Describe the solution you'd like
I'm thinking of a subset of a templating language to possibly achieve some customization.
In e.g. Home Assistant they use Jinja2 (python) where the filters look like a possible solution to this.
I reckon Javascript may have some library like this as well where we can safely expose filters to use on the data without allowing xss
Is your feature request related to a problem? Please describe.
The title might be a bit confusing, i'll explain. While the current variables for the external search websites support many sites some sites do not match the format given.
Some sites i've run into do not use
%20for spaces in the surname, but use a+instead.Other cases i've run into is sites asking for date ranges in dd-mm-yyyy format, or yyyy-mm-dd, and i'm sure American sites would use mm-dd-yyyy.
And a regional image archive saving images as "John Doe" or "J. Doe"
It's an impossible task to add variables for all possible cases.
Describe the solution you'd like
I'm thinking of a subset of a templating language to possibly achieve some customization.
In e.g. Home Assistant they use Jinja2 (python) where the filters look like a possible solution to this.
I reckon Javascript may have some library like this as well where we can safely expose filters to use on the data without allowing xss