title: Special characters encoding in image filenames after server migration
body: <p>I've migrated a WordPress website from a Hostgator shared host to a Ubuntu Digital Ocean LAMP stack. </p>
  
  <p>The trouble started when I exported the image files which had special characters, for example the file
  <code>operários_tarsila-1024x640.jpg</code>.</p>
  
  <p>When WordPress tries to reach the file, it displays an error. I've found the cause: </p>
  
  <p>I can see via Inspect Element that Wordpress tries to call: <a href="http://mywebsite.com/wp-content/uploads/2013/02/oper%C3%A1rios_tarsila-1024x640.jpg" rel="noreferrer">http://mywebsite.com/wp-content/uploads/2013/02/oper%C3%A1rios_tarsila-1024x640.jpg</a> and the server returns a 404 error.</p>
  
  <p>However if I type this URL in the browser: <a href="http://mywebsite.com/wp-content/uploads/2013/02/opera%CC%81rios_tarsila-1024x640.jpg" rel="noreferrer">http://mywebsite.com/wp-content/uploads/2013/02/opera%CC%81rios_tarsila-1024x640.jpg</a> it works and the image is displayed.</p>
  
  <p>So, it seems like this difference between the <code>á</code> encoding from <code>%C3%A1</code> (<code>á</code> character) to <code>a</code>+<code>%CC%81</code> (combining accute accent) is what is causing WordPress to not display my images. </p>
  
  <p>So now I have in my server thousands of accented image filenames with the structure <code>character</code>+ <code>combining accent</code> and WordPress calling the image filenames with the structure <code>accented character</code>. </p>
  
  <p>Is there a way bash rename all of them with a comparisson table? Or a way to make Apache aware of those differences and point to the right file when this kind of confusion happen?</p>