Home | Blog | Software | Reviews and Features | Forum | Help | Donate | About us

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • November 21, 2017, 04:19 AM
  • Proudly celebrating 10 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Wish: UTF-8 and URL encoding  (Read 1331 times)

Jesper Hertel

  • Charter Member
  • Joined in 2006
  • ***
  • Posts: 102
    • View Profile
    • Donate to Member
Wish: UTF-8 and URL encoding
« on: September 01, 2011, 12:11 PM »
You can use $$u1 and $$uc in place of $$1 and $$c to have FARR perform urlencoding on the arguments, making them suitable for web searches. (Direct quote from the help file ;)).

As a Dane using special non-ascii letters very often, this is very cool and I use it a lot! :Thmbsup:

But now I wanted to create an alias to search my Gmail. This takes a URL of the form
where my+search+terms+in+utf-8 is in URL encoded UTF-8 format. And it is the UTF-8 that is the problem.

If I just use ordinary $$u1 like this in my alias:
and use the alias to search for "s√¶rlige √łnsker", I get
but then Gmail gets stuck loading and I get an almost blank screen. The functioning URL is
which brings the correct search result.

So I miss being able to tell FARR to URL encode the UTF-8 encoded equivalent of the search string.

Would it be possible to add something like $$uu1, $$uu2, ..., $$uuc to perform URL encoding of the UTF-8 encoded string?