Plugins, Facebook translations (I'm not sure about Google+ but they probably have something, too), resx files, a giant list of custom XML schemas, you name it.This madness has to stop.ProblematicFirst of all, when one talks about localization, the NBA Live Coins common subject is text files. But anyone who has been involved in that process knows that it actually implies a whole umbrella of elements. Text with Unicode support is a given (even though there is a plethora of issues there),
you have images with text on them, videos, audio files, local legal requirements, and Cheap FIFA 17 Coins maybe content tailored for a local market -- one culture may think one symbol is cool while others may think it resembles death incarnate.Sure, you could say, don't complicate things and just stamp an Excel file or a document there, put an incremental number scheme on the file name, and you are set. Whilst that could work for text, when you have images or audio involved, it just doesn't cut
. Every format has its quirks and ways of testing it, and it's not like your QA team speaks five major languages and can corroborate whether the content is correct or not.So you have all these digital assets, you send it to translators and localizators, whether it's a big company or contractors. You get them back, you approve them for updating, editing takes place. Voila, somebody forgot about a word here or proof-reading there. You have to send it back to the translators,
now the deadline has to be pushed a little forth. Rinse, repeat.Of course, there are already several localization initiatives (for instance, i18n, l10n, etc). However, it's important to have something shoehorned to our industry.But let's be a bit more precise and summarize the problematic:Inconsistency: Most tools don't talk well to each other. They could reside on different platforms which you don't have access to. Conversion must be MMOGO made at several levels -- lost in translation