From f17b9be0e1576acc7fa68f4d870fe615b830b642 Mon Sep 17 00:00:00 2001
From: David Ducatel <david.ducatel@3ds.com>
Date: Thu, 6 Jun 2019 10:37:43 +0200
Subject: [PATCH] (doc) Add documentation of new token in readme

Also and me in contributors list
---
 CONTRIBUTORS | 1 +
 README.md    | 4 ++++
 2 files changed, 5 insertions(+)

diff --git a/CONTRIBUTORS b/CONTRIBUTORS
index de1b252..e407423 100644
--- a/CONTRIBUTORS
+++ b/CONTRIBUTORS
@@ -11,6 +11,7 @@
 # Please keep the list sorted.
 
 Andrew Arnott <andrewarnott@gmail.com>
+David Ducatel <david@ducatel.eu>
 Geert van Horrik <geert@catenalogic.com>
 Wesley Eledui <wefilmer@gmail.com>
 Marek Fišera <mara@neptuo.com>
diff --git a/README.md b/README.md
index 6147ad1..ad3cba1 100644
--- a/README.md
+++ b/README.md
@@ -70,6 +70,10 @@ When working with a repository using uncommon URL you can use placeholders to sp
 
     GitLink.exe <pdbfile> -u "https://host/projects/catel/repos/catel/browse/{filename}?at={revision}&raw"
 
+Or if you require URL encoded filename you can use `urlencoded_filename` token
+
+    GitLink.exe <pdbfile> -u "http://host/api/v4/projects/42/repository/files/{urlencoded_filename}/raw?ref={revision}"
+
 The custom url will be used to fill the placeholders with the relative file path and the revision hash.
 
 ### Git repository location