Myslnik Posted August 4, 2022 Share Posted August 4, 2022 I have a ton of custom web searches for Swedish (and Polish) websites. For some reason, after the recent Alfred update, when I type in any country specific characters (such as å, ä, ö) as my search term, it returns the UTF-8 equivalents instead (obviously ruining my searches). For example, if i search for the word "häst" ("horse"), on my custom Swedish Wikipedia search, it used to return häst, whereas after the update it returns h%C3%A4st. Is there any way I can stop this from happening? Please help. Link to comment
vitor Posted August 4, 2022 Share Posted August 4, 2022 Welcome @Myslnik, Those aren’t UTF-8 representations, they are URL encoded. Indeed %C3%A4 is the correct URL encoding for ä. I can’t reproduce an issue, setting up a Swedish Wikipedia search and searching for characters with diacritics is working fine. Can you share your Custom Search (edit it and click Copy URL for sharing on the bottom left)? Also, what exact versions of Alfred and macOS are you on? Link to comment
Myslnik Posted August 4, 2022 Author Share Posted August 4, 2022 Thanks for this @vitor. i stand corrected, those are not UTF-8 versions (I guess I was looking at the letter ä and its hex. value in this chart?) You're also right about a custom Swedish Wikipedia search working (I gave it as a random example but tested it just now and Swedish letters did work). But my custom Swedish Google page search does not. Here is the Custom Search url i use for this (it includes a double quotes/exact match) : alfred://customsearch/Google%20Sverige/s/utf8/+/https://www.google.se/search?q=%22%7Bquery%7D%22&hl=sv&le=sv&btnG=Google+Search&num=20&start=0 This url used to work before the update to 5.0. What am I doing wrong? Link to comment
vitor Posted August 5, 2022 Share Posted August 5, 2022 The quotes themselves are special characters which have to be URL encoded. Instead of ", use %22: alfred://customsearch/Google%20Sverige/s/utf8/+/https://www.google.se/search?q=%2522%7Bquery%7D%2522&hl=sv&le=sv&btnG=Google+Search&num=20&start=0 Link to comment
Myslnik Posted August 5, 2022 Author Share Posted August 5, 2022 (edited) Thanks for the tip @vitor! I ended up with this simplified custom search and now it works: alfred://customsearch/Google%20Sverige/s/utf8/+/https://www.google.se/search?q=%2522%7Bquery%7D%2522 It's odd though that when validating this search via the Alfred UI (by pressing the "Test" button) it returns the wrong result in Google ("%22häst%22" instead of "häst"). Whereas the opposite happened with the old custom search url (i.e. the validation worked with the Test button but not when using the Alfred search window). Edited August 5, 2022 by Myslnik Link to comment
vitor Posted August 8, 2022 Share Posted August 8, 2022 (edited) I can reproduce. Opening an issue internally. Thank you for the notice. Edited August 8, 2022 by vitor Myslnik 1 Link to comment
vitor Posted August 23, 2022 Share Posted August 23, 2022 This has been fixed in Alfred 5.0.2 Pre-release (2071). Link to comment
Kassi Posted September 28, 2022 Share Posted September 28, 2022 @vitor I don't agree that this issue is fixed. I'm using version 5.0.2 (just checked) and my custom web searches don't work anymore (since upgrade to version 5). Looks like double url-encoding to me (%C3%BC => %25C3%25BC) It worked perfecly in v4. Link to comment
vitor Posted September 28, 2022 Share Posted September 28, 2022 @Kassi The original URL isn’t properly encoded. It should be https://de.pons.com/%C3%BCbersetzung?q={query}&l=deen&in=&lf=de (encoding the ü). The fix mentioned above was specifically about the validation. Link to comment
Kassi Posted September 28, 2022 Share Posted September 28, 2022 @vitor oh well, you're right. Haven't recognized that since it was always working. Works now. Thanks Link to comment
DDAlex24 Posted October 3, 2023 Share Posted October 3, 2023 On 9/28/2022 at 7:40 PM, vitor said: @Kassi The original URL isn’t properly encoded. It should be https://de.pons.com/übersetzung?q={query}&l=deen&in=&lf=de (encoding the ü). The fix mentioned above was specifically about the validation. Hey, does Alfred support site:searches like that in my Screenshot? Cause it does not work and I don´t know why.I suspect that Alfred or Google translated the ü one time too many Link to comment
vitor Posted October 3, 2023 Share Posted October 3, 2023 36 minutes ago, DDAlex24 said: does Alfred support site:searches Yes. There’s nothing special about those, they’re just text: the search engine is what interprets what to do with them. I can’t reproduce your issue at all, it works fine for me. What version of Alfred are you on? Link to comment
DDAlex24 Posted October 3, 2023 Share Posted October 3, 2023 39 minutes ago, vitor said: Yes. There’s nothing special about those, they’re just text: the search engine is what interprets what to do with them. I can’t reproduce your issue at all, it works fine for me. What version of Alfred are you on? Thanks for the quick reply. I have 5.1.3. (2715). I'm also confused because when I recreate a "simple" Google search myself, it works with "Müller" without any problems. Only if I place "site:tag24" in front of it. I am very perplexed. Link to comment
DDAlex24 Posted October 3, 2023 Share Posted October 3, 2023 (edited) 54 minutes ago, vitor said: I can’t reproduce your issue at all, it works fine for me. What version of Alfred are you on? I know why finally... I use Velja as my default browser, which isn't really a browser, it just selects which URL is used in which browser. If I activate Safari as default Browser, it works! So Velja is the problem... Edited October 3, 2023 by DDAlex24 Link to comment
DDAlex24 Posted October 31, 2023 Share Posted October 31, 2023 Unfortunately, I have the problem again even though I deactivated Velja as the default browser. All of my custom searches work with Müller, but it doesn't work with IMAGO. Does anyone see the problem here? Kind regards and thanks for any help Link to comment
vitor Posted October 31, 2023 Share Posted October 31, 2023 4 hours ago, DDAlex24 said: All of my custom searches work with Müller, but it doesn't work with IMAGO. If it works with every website but one, then the problem is that website. Indeed, searching for müller returns m%FCller in the URL, which is not the correct URL encoding (that would be m%C3%BCller). You can verify this yourself in a URL encoder/decoder. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now