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
ResultFieldMatchFinder / Support |+lang= filter in PrintRequests #2037
Conversation
@kghbln FYI
|
Does this also make sense, though in a reduced degree to "Has property description"? like e.g. here on sandbox Going further I think it will be nice to use this feature it in conjunction with a variable which is providing the language code from the users preference setting. I will have a look if there is an extension for this around. |
Great, found it: MyVariables |
I have the feeling that this does not just work by chance. ;)
Now also available on sandbox. |
Hmm, I did a field test with "Has property description" While it works for "fr" i.e. showing nothing is only works for the first property "Foaf:homepage" and not for "Foaf:knows" or "Foaf:name" when using "en" and "de". The latter two show both languages. |
This happens when you only test half a meal and declare it as delicious. Should be fixed with #2048 containing a similar test case. |
It works! Perfect! 👍 |
Now documented. |
This PR is made in reference to: #1344, #594
This PR addresses or contains:
|+lang=
is to support filtering of results that match a specific language and is applied during query post-processing after the condition has retrieved matchable entities. (ThePrintRequest
and hereby the DV may match text in different languages and unless the query condition was designed in a way that would made them reducible, it would display them all)lang
value|+lang=
filtering is only applied to instances of typeMonolingual text
This PR includes: