[wpmu-trac] [WordPress MU Trac] #192: too long unicode character
[level-2] "post-slug"
WordPress MU Trac
wpmu-trac at lists.automattic.com
Fri Nov 3 19:02:29 GMT 2006
#192: too long unicode character [level-2] "post-slug"
----------------------------+-----------------------------------------------
Reporter: skcsknathan001 | Owner: somebody
Type: defect | Status: new
Priority: normal | Milestone: WPMU 2.0
Component: component1 | Version: 2.0
Severity: critical | Keywords: post-slug tamil multilingual
----------------------------+-----------------------------------------------
Too long unicode character [complex script] "post-slug" will not allow
users to re-save after editing once a post is posted. I experience this
for the language "Tamil", which is a level-2 Unicode = complex script.
Able to post, able to edit. But does not allow to re-save.
Also the permanent link leads to a Not Found post.
My guess is the URL exceeds the 255 characters limit, since complex
unicode scripts are more than one code for a particular character.
the URL comes up as
http://1soothanai.adadaa.com/2006/11/03/non-breaking-
tamil-%e0%ae%a4%e0%ae%ae%e0%ae%bf%e0%ae%b4%e0%af%8d-%e0%ae%89%e0%ae%9f%e0%af%88%e0%ae%af%e0%ae%be%e0%ae%ae%e0%ae%b2%e0%af%8d/
All these "...%e0%ae%a4%e0%ae%..." garbage is the result of URL encoding
for the unicode complex script Tamil. [note the above link actually
works]. But if I were to put more Tamil caracters, the post will appear
but the permanent link will fail, as well as re-save after editing.
So either a post should give error when tried to post, which *will* result
in more than 255 URL encoding.
or
the the auther should be allowed to re-save the post after editing. That
means the actual cut-off "post-slug" text maintained.
Don't know if I make sense, but let me know if you don't.
I have the nightly build wpmu-2006-10-24
--
Ticket URL: <http://trac.mu.wordpress.org/ticket/192>
WordPress MU Trac <http://mu.wordpress.org/>
WordPress Multiuser
More information about the wpmu-trac
mailing list