I have the same problem with Greek. I dont think its possible to fix it. Most websites are using codes to display the name

I have no problem of getting a 200 response with the mentioned URLs

curl -i -X HEAD http://institutoparamitas.org.br/wp-content/uploads/2013/03/Aplicativo-auxilia-a-alfabetização-de-crianças-_corpo-150x150.jpg

Since RFC 3986 2.3 only allow a-z, A-Z, 0-9, -, ., _ & ~, http://tools.ietf.org/html/rfc3986#section-2.3

It is to better to encode the URL before using it as the image src.

Using any character other than the defined reserved & unreserved character is not reliable, up to the user agent to handle.

Hello,

Thanks Tony Tsang and Meletis Flevarakis by return.

The problem was solved, it was a problem with uploading files.

The solution was to delete and upload the files again.

=)

Hi!
I have the same problem, but I´m unable to fix it uploading again the files with a utf8 ftp.

For example:
http://95.85.13.136/fotos/2014/04/Almenas-en-el-techo-Visita-a-la-torre-Bellesguard-o-Casa-Figueres-Gaudí-en-Barcelona-Cataluña-España-by-machbel.jpg

give error 404, but file exists exactly in server.
access.log say:

[14/Apr/2014:13:04:40 +0200] "GET /fotos/2014/04/Almenas-en-el-techo-Visita-a-la-torre-Bellesguard-o-Casa-Figueres-Gaud%c3%ad-en-Barcelona-Catalu%c3%b1a-Espa%c3%b1a-by-machbel.jpg HTTP/1.1" 404 342 "http://95.85.13.136/fotos/2014/04/" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0"

So, there is any way to fix this?
Server is Debian7 with apache.