Jinx wrote:
@Ken, Newart, Compass, Alledia,
Hehe, I kinda had a feeling this reaction would be coming. I wonder if you guys actually took the time to read my latests replies in this thread and/or had a look at the SVN. 
I already hinted in my blog post that the truth is in the SVN and I quote myself :
Quote:
I have implemented a very basic segment encoder/decoder that is capable of rewriting the slugs. A default implementation is in place that uses a '_' to seperate the id from the name. In the future we could expose this into the configuration if the need exists to give the administrator more control over the formatting of the URL segments. ... The segment encoder/decoder could be used to remove the text information from a segment and only keep the integer, for the moment this behavior is not yet implement. If somebody want's to have a go at it be my guest.
Now if you would have taken the time to look at the actual code or had tried to understand my post you would probably have noticed that the whole segment encoding/decoding mechanism is fully extendable and that I just implemented a very basic solution that using a str_replace call due to a lack of time (had a flight to cacht to Asia 
). If you want to change this you can easily implement a more intelligent regular expression to replace the '_' with a '-' or even make it a configurable setting of JRouter. It's only two lines of code that needs to be changed.
These reactions exactly demonstrate the kind of behavior I don't want on this forum. If you not willing or capable to offer solutions don't bother posting here. We (the development working group) don't need the SEO lectures, we have had those, the forum is full of them. We need solutions. I took the URL routing to 99% of a complete solution, maybe you guys should consider throwing in the last 1% yourself. Submitting a patch maybe ? 
Geez.
This was not some big attack on
the code.
I
have read the entire thread and all the Dev site posts.
The only reason I posted in this thread is I assumed there was finally some movement on embracing and implementing some real SEO concepts in Joomla core URLs and thought I may actually have something to contribute.
My strategy thus far has been to simply point-out some issues (like using a reserved character).
Some SEO experts are here trying to gingerly inject some
common SEO knowledge into the J 1.5 implementation.
If you are going to do it, you may actually want to try to do it right.
Embracing some other peoples' knowledge may actually be beneficial.
Really.
I tested the SVN code a few days ago - it is broken.
The pathway links are broken.
Tried Apache mod_rewrite on and off.
I assumed that this is a work-in-progress and hoped that various short-comings will be addressed as the work progresses.
Reasonable assumption?
No need to post the problems here as this is a work-in-progress.
In an earlier post it was alluded to that the "slug" may become a configuration item.
That would definitely be a plus as the majority of SEO-knowledgeable users would immediately change from the : or _ to a -.
99% of Joomla users are not going to read or edit the code to fix this issue.
That option is not reasonable.
Yes, SEO knowledgeable users will invariably create a hopefully well known hack to fix the
new URL SEO issues.
This could be avoided by not being defensive and actually listening to what many SEO knowledgeable Joomla users have been saying for months (years?) and actually implementing it right the first time.
Obviously trying to be tactful is not working.
How about this . . .
The : is a bad idea.
The _ is a bad idea.
The - is the best option for a default separator.
Is that clear enough?
SOS.
Login
Register
Rules
FAQ
The team
)
) and I liked very much the interview in the link posted, very informative. So if I've well understood we have to wait for Johan and his reply to that 
