Closed (outdated)
Project:
Pathauto
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
16 Aug 2008 at 14:03 UTC
Updated:
7 Feb 2026 at 09:30 UTC
Jump to comment: Most recent
Comments
Comment #1
gregglesI think they should all be "remove" except for the setting for whatever character they use as the separator which should be set to "do nothing."
Comment #2
Freso commentedBut we won't know, when deciding the standards, what they choose to use as separator. I use "_" as I prefer the human readability over the (alleged) SEO of "-" - and both are safe to use, so I'd vote for a "do nothing" for both of those anyway. I think we need to figure out which ones are "safe" and which ones aren't. This means URL entities (:/.#?&), XML/HTML entities ("><'), and... ? "\" should probably be removed as well, as Windows use that. So... anything left on the list, besides "-" and "_"?
Comment #3
Freso commentedOnce #212208: allow other modules to affect strings (to help with custom accent/string replacement) goes in, other modules can plug into the process and customise the handling of "punctuation" characters. So I think we should just removed them from 6.x-2.x - site variables and all - and let people customise through modules if they really need to do things differently from our (sane'n'sensible ;)) defaults.
Comment #4
gregglesThis does get us into a tricky spot - what if they change the default separator. The default separator should always be set to do nothing, so we'll need to do that automatically for them if we remove this control.
Comment #5
Freso commentedOr... we could remove "punctuation" before replacing spaces with the replacement? (E.g. "awesome_function() is awe-some" would first become "awesomefunction is awesome" and then "awesomefunction-is-awesome".)
Comment #6
mably commented