I'm working with someone who is interested in building an Omeka site with Korean audio files with transcripts in Korean, some of which might be translated into English. Am I correct in thinking that enabling this would just require a setting the collation and character sets in the MySQL database? It wouldn't require a localized version of the Omeka software in Korean, right?
Yes, you don't need a translated version of the software to store non-Latin text, only to change what text shows up on the interface and things like the formats of the dates we automatically generate.
Omeka already sets the character set and collation for all the tables it creates to UTF-8, so it should be able to store and work with Korean, or a mixture of Korean and English, out of the box.