Custom web search encoding for non-Latin URLs broke in Alfred 5

[ivm]

Hello! I had some custom searches, one of them for Reverso.net which uses Cyrillic symbols in its URLs:

https://context.reverso.net/перевод/английский-испанский/{query}

 

After updating to Alfred 5, these searches no longer work because Alfred started encoding non-basic-Latin symbols, for example searching está results in:

https://context.reverso.net/перевод/английский-испанский/est%C3%A1 (instead of https://context.reverso.net/перевод/английский-испанский/está)

 

At the same time, searching está in SpanishDIct works well, probably because it uses only basic Latin in the URL:

https://www.spanishdict.com/translate/{query} results in https://www.spanishdict.com/translate/está

 

I'm running Alfred 5.0.6 [2110] on macOS 12.6, and tested these searches with Safari 16 and Chrome 112 set as default browsers.

 

Can you please take a look? Thanks!

 

Edited April 16, 2023 by ivm

[Andrew]

@ivm There is mixed encoding which is what is causing the issue. For this specific case, if you switch from using a Custom Search to using a Workflow, then you get more control over the encoding.

 

Create a workflow with a Keyword wired into an Open URL:

 

 

Configure the Open URL with your specified URL, then uncheck the option to Encode {query} placeholder:

I've just tested this and it works as expected  

[ivm]

Perfect, thank you!