Categories WordPress IÃ±tÃ«rnÃ¢tiÃ´nÃ lizÃ¦tiÃ¸n Post author By Matt Post date September 7, 2004 50 Comments on IÃ±tÃ«rnÃ¢tiÃ´nÃ lizÃ¦tiÃ¸n Can you link to this? How does it look in your aggregator? What’s it look like in your address bar? If you can’t get to this entry leave a comment on the previous one. Hat tip: Anne. Share this:Click to email this to a friend (Opens in new window)Click to share on Facebook (Opens in new window)Click to share on Twitter (Opens in new window) Related ← International URIs → Firefox Worm 50 replies on “IÃ±tÃ«rnÃ¢tiÃ´nÃ lizÃ¦tiÃ¸n” http://photomatt.net/2004/09/07/i%c3%b1t%c3%abrn%c3%a2ti%c3%b4n%c3%a0liz%c3%a6ti%c3%b8n/ Works, just looks crap :p Confirmed to work in Firefox, Opera, and IE on this Windows XP laptop. It looks good in Firefox and Opera, kinda yucky in IE. Dale, I think you just outed yourself as an IE user. 😉 Also note that if you have a unicode-savvy publishing system you should be able to paste the pretty version into your post, not the yucky version. IE! Yuck, no no. Firefox here 0.9.3. Might be to do with what fonts I have installed or something. I’ve got the same thing as Dale though.. although in that status bar at the bottom… it looks nice. I take that back, you see the percent-encoded in the address bar of Firefox too. Sorry for that awful slander Dale. 🙂 It seems like Opera handles this best. I’m pretty glad that my title image generator was able to handle this too. That one is dumb luck though, both in how I encode things and that the font I’m using has all the right characters. Works fine in Safari: http://photomatt.net/2004/09/07/iÃ±tÃ«rnÃ¢tiÃ´nÃ lizÃ¦tiÃ¸n/ appears in both the address bar and the status bar. Works in bloglines… Looks interesting, but it works. Looks great with Safari, looks mangled in the adress-bar in Camino-nightly from a week ago. Looks just fine after being fetched by MagpieRSS and displayed in a home-built reader/archiver in Mozilla 1.8b3. Thanks for the test 😉 Works fine. My home-grown aggregator rocks, Linux rocks, Firefox rocks. 😉 http://photomatt.net/2004/09/07/i%c3%b1t%c3%abrn%c3%a2ti%c3%b4n%c3%a0liz%c3%a6ti%c3%b8n/ Firefox on XP. Looks great in Bloglines works for me! Magled in the addressbar of course, using FireFox. But it works. 😀 Safari looks great. Also, my heavy beta 0.1 of Newsfire (latest Mac aggregator) displays it fine. Link works fine in Firefox 0.9 on Windows XP. Link text comes out borked though, doesn’t look right at al. Neat! How cool that this stuff actually works cross browser and thanks for testing it out. Bloglines has no problem with it of course. Opera is perfect, Konqueror displays it fine in the address bar but messes up the window title, Firefox excapes the whole string in the address bar but at least does it right in the title. BTW, how do we get WP’s comment notification emails to do it right? Works fine in Firefox 0.9.3 on Linux with Sage 1.2.1 It works in IE, just the URI is as stated in the first comment. Does it display the actual non-ASCII characters in Firefox? I’ll check when I get home, I guess. Kinja doesn’t seem to have any problem displaying it either. I’m not sure that displaying the hex encoding of the URI in a browser is really something to complain about. I wouldn’t expect it to display it otherwise — after all, that’s what a URI is supposed to look like according to the specs. The url comes thru as the percent encoded (yucky version) in the entry using Opera’s RSS reader. The subject for the entry comes out fine, and the link works… Firefox 0.9.3 and Sage are cool with it. Looks great in BottomFeeder. I confirm, it works fine on Opera. Mozilla/Firefox/Opera/IE on Win2000 (French) botch it with percent encoding, but load the page well and show the title correctly (image, title tag, the works). Heck, even Netscape 4 handles it! (Sort of…) OmniWeb 5.0.1 / Mac OS X 10.3.5: Title bar – fine; address bar – %nonsense; page – gorgeous. NetNewsWire seems happy enough with it, and the hand-off from NNW to OW worked fine too. Headline is :I t rn ti n liz ti n Link is identical to comment 12 Abilon Aggregator Very nice in Safari, Matt! It looks fine in both IE6 and Feedster… On a second thought. When I view source I see the name is URI encoded already. When you enter the unescaped form into the browser you won’t get the same result. (It has to be encoded by the way to be URI compliant.) I believe this was discussed some time ago by Mark Pilgrim and Sam Ruby as well and it seems that there are multiple ways to encode non us-ascii characters in an URI. it works in IE Works in Camino and Safari (so I’m guessing Firefox on OS X as well)… Very cool. Works in NetNewsWire (2.0alpha). Ohh! what a lot of “%” signs in the address bar. Title is alright though. Works great in Safari, even the URL looks fine. Gotta love OS X. Interesting Matt. However you can use the Sanitizer Plugin, specially for non-english blogs, in which for example letters as Ã¡, Ã©, Ã, Ã³, Ãº, and Ã±; become a, e, i, o, u, and n. Check it here: http://www.100px.com/100wordpress/categoria/plugins/ Cheers Looks good in Feedreader 2.7 build 646. I’m running FeedOnFeeds and the title showed up fine in the RSS display of it, however in the description field the word “What’s” of “What’s it look like in your address bar?” was incorrectly displayed – the ‘ in what’s was a ? I’ve seen that happen a few times on you rss feed from FoF too. (I’m using FF0.9.2 to browse with FoF) Also, looks great in Sage with FF too. No problems at all. Perhaps FoF needs some UTF-8 encoding headers sent? Mrhmm… Works for me in Feed On Feeds (0.1.7) / Firefox 0.8 / Win2K, without the apostrophe issue that Jeff mentioned. I think he’s right about the encoding headers, through. Leaving them out is causing some problems. In my address bar I see percent signs. http://photomatt.net/2004/09/07/i%c3%b1t%c3%abrn%c3%a2ti%c3%b4n%c3%a0liz%c3%a6ti%c3%b8n/ In IE6(SP1) on Win2k(SP4). a problem I think. Damn, why can’t it be like it is in Safari?? Damn!! This stuff is funky! Amit, what IE 6.0 does is perfectly fine. As has been said, percent-encoded in Firefox (on Linux). Though few people care these days, it’s totally mangled in Lynx (in XTerm w/ Bitstream Vera Sans Mono font). ELinks, however, substitutes those characters for strings of ASCII characters which look similar. It looks pretty in Konqueror, looks ugly in Firefox (both on linux). My RSS Reader seems to be doing fine though. looks fine on my aggregator Linking to this post proved tricky under Movable Type. No amount of copying and pasting was going to let me use the actual characters as a link description, sadly. The only way I managed to finally make the link itself work was by copying the escape codes from comment #1 and using that. Safari wouldn’t let me do it any other way. Mea culpa, looks like the MT problem was a result of my upgrade (as opposed to a fresh install.) It is, in fact, entirely possible to copy and paste the characters into MT3, provided you’ve actually turned on UTF-8. (And with that, I’m done with the MT talk on here) Yes, it works, but it’s not great for Accessability. One of the WAI tips from the W3C is to make readable URIs. That certainly isn’t readable for anyone with a Gecko based browser. I think that’s why internationalisation gets abbreviated to i18n — it’s just so much easier to read and type. Copying the web address from Opera’s address bar into Firefox fails to find the post. Opening the link from the archives works in Firefox though. The numbers you’re using for each comment overlap the text in Opera BTW… I get the yuk version when I click on the links for your article in IE6 on Win2000Prof http://photomatt.net/2004/09/07/i%c3%b1t%c3%abrn%c3%a2ti%c3%b4n%c3%a0liz%c3%a6ti%c3%b8n/ But If I click on link Ryan Meade posted in comment No 8 I get the nice version Comments are closed.