Khmer slug maker
A Khmer headline turned into a link somebody would actually paste.
What most systems do with a Khmer title
One of two things, and both are bad. A CMS that slugs by removing everything non-ASCII gives you an empty string, so you end up with /post-1478/. One that percent-encodes gives you forty characters of hex that nobody can read, type, or recognise in a search result.
Neither is a link a person will paste into a message, and the second is the one that looks fine in the address bar and terrible everywhere the address is written down.
This is transliteration, not translation
The output is the Khmer written in Latin letters — it does not tell an English reader what the page is about. If that matters for a particular page, write an English slug by hand instead; this is for the hundreds of pages where it does not.
There is also no single correct romanisation of Khmer. The UN system, the Cambodian government’s and the mapping services’ all differ, and none of them was designed for URLs. The table here aims at short, stable and recognisable rather than at linguistic accuracy.
Hyphens, not underscores
Google treats a hyphen as a word break and an underscore as a joiner. So web_design is one word to a search engine and web-design is two, which is why every guide has said hyphens for fifteen years and why the setting is here rather than assumed.
Keep them lower case as well. Some servers treat /About/ and /about/ as different pages, and the day that becomes a problem is the day somebody links to the wrong one.
Set it once
A slug is part of the address, so changing it later breaks every link anyone has already shared — and the redirect that would fix it is the thing everybody forgets. Decide the slug when the page is created and leave it alone, even when the title changes.
Keep them short, too. The length control here defaults to sixty characters, which is enough to be descriptive and short enough to survive being pasted into a chat message without wrapping.