lucy24
msg:4520444 | 5:55 pm on Nov 19, 2012 (gmt 0) |
Uhm... er... are we talking about non-ASCII characters in URLs? I wouldn't risk it unless the whole thing is in a non-Roman script.
|
maike
msg:4520455 | 6:13 pm on Nov 19, 2012 (gmt 0) |
But I needed for my script is one page pt-BR and associety on my database but I need create pastes is possible utilization?
|
lucy24
msg:4520590 | 1:52 am on Nov 20, 2012 (gmt 0) |
The page can be any language you like. I thought you were asking about the URL. Or are you asking about the URL?
Do the directory names have to have accents? For example are they based on people's personal names?
If you simply need to convert your õ's and ñ's into something else, your php script should be able to do that in a few lines. The tricky part is making something that converts in both directions. ñ > nh > ñ is no problem, but you can't simply change ã to am or an and then change "back" again.
Technically there is no rule against using non-ASCII characters in an URL or in any kind of link. It's just not always safe. I once had to change a bunch of fragment links that used yogh. They were safe on my HD and safe in my personal www space-- but all it takes is one server that doesn't use UTF-8 and it would have been a horrible mess.
|
phranque
msg:4520638 | 5:51 am on Nov 20, 2012 (gmt 0) |
| Technically there is no rule against using non-ASCII characters in an URL or in any kind of link |
|
while there is a proposal out for "internationalized resource identifiers", non-Latin-alphabet characters in a URL should be percent-encoded.
please see section 1.2.1:
http://www.ietf.org/rfc/rfc3986 [ietf.org]
| A URI is a sequence of characters from a very limited set: the letters of the basic Latin alphabet, digits, and a few special characters. |
|
|
swa66
msg:4520679 | 10:30 am on Nov 20, 2012 (gmt 0) |
URLs need to be UTF-8 encoded.
Take care: UTF-8 is not ISO-Latin-1 or any of its siblings or derivatives (like windows code pages). This is an encoding that has the potential for multibyte characters and requires proper care in handling.
Anything that falls outside the normal US ascii range should be %encoded (note: if you have UTF-8 sequences you have to %encode them). Alpha (a-zA-Z), digits (0-9) hyphen (-), period (.), underscore (_), or tilde (~) should never be encoded (normalization rules).
If you do output it in html or xml: you need to additionally encode " ' < > and & with the html entities (" ' < > and & as well.
That said: make your life easy and don't go for URLs with accented characters as they get mutilated beyond recognition anyway.
|
maike
msg:4520700 | 11:43 am on Nov 20, 2012 (gmt 0) |
Good was giving a lot of work I choose to modify my script with php, when I made a function that will record the data in the database is the geito that the user typed the folder but it removes the accents and whenever I need to use it in their own use more attention I thank you all.
|
phranque
msg:4520754 | 2:24 pm on Nov 20, 2012 (gmt 0) |
welcome to WebmasterWorld, maike!
|
maike
msg:4520769 | 3:05 pm on Nov 20, 2012 (gmt 0) |
Tank you.
|
|
