Reverting i18n.csv file back to UTF-8 no BOM as encourtered increased risk of corruption when handled by multiple tools. Need to find a way to make this much easier for people to contribute and edit translations as it is problematic to deal with the encoding issues between Excel and other programs. Seems many are using Google Docs as a workaround.
Merge pull request #1846 from pjackson28/v3.0

Reverting i18n.csv file back to UTF-8 no BOM