Forum Moderators: phranque
Another example is on my Swedish page where these browsers change a Swedish girls name from
http://www.domain.com/directory/directory/Anaïs.html#girl
to
http://www.domain.com/directory/directory/Anaïs.html#girl
I have temporarily fixed the models name by adding a mirrored page by that name, and am working on something simular for the flash transolation. But as forgen submitions are getting more prevelent this problem is only going to get worse. Would apreciat any input on how to tame these browsers.
for your second problem you have to find out the correct entity for every letter which is not part of the group of 'normal letters'. for example, if i want to write the german word märz, i have to type in märz in html. this is the same for attribute values in html. all you have to do is to find out, which entity is used for the special letter you're using. your 'special i' for example is ï.
the first problem is not solveable that easy i think. it seems to be the browsers decision to urlencode the # letter instead of leaving it untouched. this might be a bug of the plugin-interface of ie and opera. or it's a bug of the flash plugin these two browsers are using, but i think, opera will use the netscape plugin.
For example, if you use quotes on a page to display something like this:
"My Quoted Text"
... you can then look at the actual HTML code and you'll see this:
"My Quoted Text"
For some reason your HTML editor is looking at the bogus link as "displayed text" rather than "link code". What HTML editor you use will determine how to fix it and see that it doesn't happen again. You can go into the HTML code and fix it by hand, but the next time you load the page and save it again, the editor just might burn you again. Keep an eye on it.
Hope this helps.
G.
so if you want every browser to get your link the right way use only standard characters. some browsers for example interpreted the special characters and some not. and: it also depends on the server, too, how it handles these non-ascii chars in a request. that's all you've to deal with then, so i removed any special character.
Personally, I doubt that it's a browser problem. I use #'s in my URL's all the time, and have never experienced a problem like the one you're talking about. .. especially not if it's a newer browser.
The fact that it shows as # binary doesn't necessarily mean anything. I bet that a lot of non-word characters would be converted too.
I think it's a Flash issue.
Checked on their web site/help files?