Answers.Body: <p>This post helped me with my issue with a different approach (except of using the kebab filter the slug of the tag is used for the route)</p>
  
  <p><a href="https://craftcms.stackexchange.com/questions/17026/use-of-tag-slug-instead-of-tag-title-in-a-custom-route">Use of tag.slug instead of tag.title in a custom route</a></p>
  
  <p>as I think that makes lot more sense then using the title, maybe it would be a good idea to update the article in the support section of the craftcms website.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-01T14:53:58.520Z
Answers.Text: +100 on updating the article in the support section. I think that article predates the existance of `tag.slug`
Answers.UserDisplayName: Marion Newlevant
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-08-01T06:51:16.547Z
Answers.LastActivityDate: 2017-08-01T06:51:16.547Z
Answers.UserDisplayName: Jan
Body: <p>I use the code "Link to the Tag URLs" from the following article:
  <a href="https://craftcms.com/support/tag-urls" rel="nofollow noreferrer">https://craftcms.com/support/tag-urls</a></p>
  
  <pre><code>{% if entry.tags | length %}
  &lt;h3&gt;This entry is tagged with:&lt;/h3&gt;
  
  &lt;ul&gt;
      {% for tag in entry.tags %}
          &lt;li&gt;&lt;a href="{{ siteUrl }}tags/{{ tag.title | url_encode }}"&gt;{{ tag.title }}&lt;/a&gt;&lt;/li&gt;
      {% endfor %}
  &lt;/ul&gt;{% endif %}
  </code></pre>
  
  <p>One thing is that the "url_encode" doesnt really apply as if I expected. The URL looks like this:
  <a href="http://domain.dev/tags/My%20Tag%20Name" rel="nofollow noreferrer">http://domain.dev/tags/My%20Tag%20Name</a></p>
  
  <p>But when I click on it, there are still spaces in the address line. </p>
  
  <p>So my question is: is that ok like this?</p>
  
  <p>I was also thinking about using the kebab filter. There I receive this url:
  <a href="http://domain.dev/tags/my-tag-name" rel="nofollow noreferrer">http://domain.dev/tags/my-tag-name</a></p>
  
  <p>which looks prettier. But I now I get an error with the routing when I want fetch the tag:</p>
  
  <pre><code>{% set tag = craft.tags.title(tag).first() %}
  </code></pre>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-07-24T18:01:07.717Z
Comments.Text: Possible dupes? https://craftcms.stackexchange.com/questions/10344/how-can-i-use-tag-slugs-in-urls and https://craftcms.stackexchange.com/questions/18277/best-method-to-handle-20-in-tag-urls-with-multiple-words and https://craftcms.stackexchange.com/questions/6581/problem-with-accents-in-tags-url ?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-07-26T15:34:40.117Z
Comments.Text: Yes, definitly. But another post helped me: https://craftcms.stackexchange.com/questions/17026/use-of-tag-slug-instead-of-tag-title-in-a-custom-route Thanks anyway Brad!
Comments.UserDisplayName: Jan
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-07-26T18:11:02.770Z
Comments.Text: Awesome... would you mind adding what worked for you as an official answer?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-07-31T00:45:02.113Z
Comments.Text: If you look towards the bottom of this page, you should see a "Your Answer" section followed by a big WYSIWIG editor where you can add an answer.
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-07-31T10:09:19.677Z
Comments.Text: yes, I know that but stackexchange always marks my entry as "trivial answer" and moves it here in the comment section.
Comments.UserDisplayName: Jan
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-07-31T23:16:22.610Z
Comments.Text: Oh... I think maybe they're looking for a certain answer length? i.e. over X characters long or something?
Comments.UserDisplayName: Brad Bell
Tags: <routes><tags>
Title: How to get a proper tag Url
ThreadText: # How to get a proper tag Url
  
  (Asked by: username_0 on 2017-07-24)
  
  I use the code "Link to the Tag URLs" from the following article:
  <https://craftcms.com/support/tag-urls>
  
  ```
  {% if entry.tags | length %}
  <h3>This entry is tagged with:</h3>
  
  <ul>
      {% for tag in entry.tags %}
          <li><a href="{{ siteUrl }}tags/{{ tag.title | url_encode }}">{{ tag.title }}</a></li>
      {% endfor %}
  </ul>{% endif %}
  
  ```
  
  One thing is that the "url\_encode" doesnt really apply as if I expected. The URL looks like this:
  <http://domain.dev/tags/My%20Tag%20Name>
  
  But when I click on it, there are still spaces in the address line.
  
  So my question is: is that ok like this?
  
  I was also thinking about using the kebab filter. There I receive this url:
  <http://domain.dev/tags/my-tag-name>
  
  which looks prettier. But I now I get an error with the routing when I want fetch the tag:
  
  ```
  {% set tag = craft.tags.title(tag).first() %}
  
  ```
  
  **Tags:** routes, tags
  
  > **Comments:**
  > **username_1**: Possible dupes? https://craftcms.stackexchange.com/questions/10344/how-can-i-use-tag-slugs-in-urls and https://craftcms.stackexchange.com/questions/18277/best-method-to-handle-20-in-tag-urls-with-multiple-words and https://craftcms.stackexchange.com/questions/6581/problem-with-accents-in-tags-url ?  
  > **username_0**: Yes, definitly. But another post helped me: https://craftcms.stackexchange.com/questions/17026/use-of-tag-slug-instead-of-tag-title-in-a-custom-route Thanks anyway username_1!  
  > **username_1**: Awesome... would you mind adding what worked for you as an official answer?  
  > **username_1**: If you look towards the bottom of this page, you should see a "Your Answer" section followed by a big WYSIWIG editor where you can add an answer.  
  > **username_0**: yes, I know that but stackexchange always marks my entry as "trivial answer" and moves it here in the comment section.  
  > **username_1**: Oh... I think maybe they're looking for a certain answer length? i.e. over X characters long or something?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2017-08-01. Score: 1
  
  This post helped me with my issue with a different approach (except of using the kebab filter the slug of the tag is used for the route)
  
  [Use of tag.slug instead of tag.title in a custom route](https://craftcms.stackexchange.com/questions/17026/use-of-tag-slug-instead-of-tag-title-in-a-custom-route)
  
  as I think that makes lot more sense then using the title, maybe it would be a good idea to update the article in the support section of the craftcms website.
  
  > **Comments:**
  > **username_2**: +100 on updating the article in the support section. I think that article predates the existance of `tag.slug`  
  
  ---
  
  