I wanted to know if there is an option to force lowercase slugs instead of the same capitilization it is written. I prefer lowercase URLs than mixed ones.

c# is a compiled language, it is 10x to 100x faster than Ruby. Please write back when you have tested in Ruby. I strongly recommend switching to another discussion software if this is a hard requirement.

Where is the app.yml located, I need the full path in Ubuntu. I can’t find it under /var/

If you followed the default installation steps, it’s /var/discourse/containers/app.yml.

[image] fefrei: DISCOURSE_DEFAULT_LOCALE That’s what I have there: env: LANG: en_US.UTF-8 DISCOURSE_DEFAULT_LOCALE: en

Anyone can help me with this, can’t continue using the platform without being soves.

I’ve found out that the slug is lowercase in ‘ascii’ mode, but when I change to ‘encoded’ it stays with the same letter case that I’ve written the topic with.

Because I want the keywords to be in the URL, even if they are written in Japanes, Chinese or any other non-English keywords. If I use ascii, this topic title: “どういたしましてどういたしまして” becomes /t/topic/17 I used it in all my websites, it’s great for usability and make the URL meaningful in search engines after indexing, and it’s useful for SEO as well. You already have a percentage encoding option, so you just need to apply lowercasing, so it will work as ASCII for English letters with small case and will be compatible with non-ASCII characters. Wordpress and all the other popular blog and forum software have this. Google also shows the URL with the decoded characters, not the encoded ones.

What happens when you lowercase unicode? This is complex and indeterminate. Not sure if Ruby can even do it.

You lowercase before encoding, Every platform that I use (and I have 15 years of developing experoence, not in Ruby though), does that. It’s a missed opportunity, I will look into rubi and see what I find. If you aim your platform for multilanguage, you have to do that.

Force Lowercase slug URLs when set to "encoded"

Product Support

codinghorror (Jeff Atwood) June 20, 2016, 8:59pm 11

Why do you need it in “encoded”? ASCII is correct for western languages.

Topic		Replies	Views
Removing the concept of "slugs" for some languages Feature	24	10655	December 13, 2017
Mods/admins to change topic URL slug (just like in WordPress) Feature	2	1402	December 2, 2014
Automatic encoding of parsed URL params Development	43	8908	May 15, 2025
Disabling English slugfier for topic's URL in Korean language setting Product Support	13	4801	September 3, 2018
Discourse slugs aren't transliterated Feature	3	822	December 29, 2019

Force Lowercase slug URLs when set to "encoded"

Related topics