This is a good article. Click here for more information.

Localization of Square Enix video games

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

The Japanese video game developer and publisher Square Enix (formally two companies called Square and Enix prior to 2003) has been translating its games for North America and the PAL region since the late 1980s. It has not always released all of its games in all major regions, and continues to selectively release games even today depending on multiple factors such as the viability of platforms or the condition of the game itself. The process of localization has changed during that time from having a one-person team with a short time and tight memory capacities to having a team of translators preparing simultaneous launches in multiple languages.

The companies' first major projects were Dragon Quest and Final Fantasy, which each proved successful enough to launch video game franchises. Since then, the majority of the games produced by the companies have been localized for western audiences, although the process was not given a high priority at Square until the international success of Final Fantasy VII. Richard Honeywood was recruited to start a dedicated localization department at the company. Enix remained without a translation department until its merger with Square. In some cases, such as Alexander O. Smith, teams or individuals became attached to particular subseries. In recent years, the process of localization has undergone changes, mainly due to difficult experiences with various titles, and Square Enix has sometimes developed the titles in localized form first in order to appeal to the western market.

Staff

The localization staff at Square Enix works mainly from Japanese to English and the other way around, and from American English to British English, French, Italian, German, and Spanish.[1] Prior to the merger of Square and Enix in 2003, Enix did not initially have a localization department and outsourced its Western releases to translators who had no close contact with the original development teams. Square also did not initially have a localization department, though Kaoru Moriyama and Ted Woolsey worked with them regularly on a contractual basis. Following the massive international success of Final Fantasy VII, the company looked into improving the quality of its translated products—the game was widely criticized for its rushed translation, which had been handled entirely by Michael Baskett, the company's only in-house translator at the time.[2] To that end, Square tasked Richard Honeywood, originally a programmer, with creating a dedicated localization team.[3] His first major project was Xenogears.[2] While there were only two members at first, including Honeywood, the staff grew to include more than 40 employees by 2007, four years after the merger between Square and Enix.[1] By the late 2000s, for self-contained series or games linked by story events or similar elements, Square Enix can use the same localization team, as in the case of titles set in the fictional world of Ivalice.[4] The translator most associated with the Ivalice games is Alexander O. Smith.[5][6] Another noted translator is Tom Slattery, who has worked the localizations of the Nintendo DS remake of Final Fantasy IV, the Game Boy Advance port of Final Fantasy VI, and Final Fantasy XIII and its sequels.[7]

Approach

Before a translation is greenlit and translators are allocated, the localization, quality assurance (QA) and marketing staff play through a build of the game and sometimes do a focus group study. The localization team's playthrough can sometimes take over 100 hours of gameplay. Once the company greenlights a localization project, a period of brainstorming starts in which glossary, style, naming schemes and fonts are chosen. During the translation phase, voiced sections are translated first. Text files are cross-checked by multiple translators and editors. The text is then integrated along with any graphic and sound changes, and the game goes to quality assurance. During a period of several weeks to up to three months, Japanese QA teams look for bugs while Western QA teams check linguistic issues. The localization team often re-plays the game during this phase, translates the manuals and help out on the guidebooks if these are made. Finally, the game is sent to the hardware manufacturers to be approved.[3]

Challenges for the localization teams include space limitation (due to data storage and/or on-screen space), achieving a natural dialogue flow despite multiple plot branches and script lines being stored out of order, and, when voiced footage is not re-recorded for lip movement, dealing with file length and lip-synch limitations.[3][8] When the same team works on different games in a series such as Final Fantasy, they often need to adopt different writing styles depending on the setting of their games.[2] Another point to consider is humorous elements that do not translate properly into English, and different cultural expectations about character interactions.[9] The localization process depends on factors such as the development teams' wishes, as well as budget and schedule. Translation usually starts late in development, although some titles, like Final Fantasy XI, are translated from Japanese to English during initial development, making the translators appear more like additional planners than actual translators. A few titles, like The Bouncer, have actually been developed in English first and only then translated to Japanese.[3] The Last Remnant also adopted this approach, featuring motion-capture and dialogue synched to English rather than Japanese actors.[10] This was done due to the company's wish to create a title for the international market.[11]

Many early localizations, like other RPGs both then and in more recent years, made heavy use of antiquated speech patterns and archaic nouns such as "thee" and "thou".[6] Square was not greatly focused on their localizations before the worldwide commercial success of Final Fantasy VII. In later years, the original translators were joined by editors to catch grammar and spelling errors.[2] Prior to the development of Final Fantasy XIII-2, the standard localization process for a title involved dual development between the company's sound and localization departments, which meant that difficulties could arise because of constant changes to dialogue. For XIII-2 and future large-scale titles, an in-house development tool called Moomle was developed to ensure all parts of the process were properly synchronized and centralized.[12] The development of Moomle was initialized due to the troubled localization of Final Fantasy XIII, and spearheaded by the game's translator Slattery and his Japanese counterpart Teruaki Sugawara.[7] In recent years, localization teams have tended to adopt two different approaches to translation and localization: either they remain quite faithful to the original Japanese, or they can make large changes as long as the story outline remains the same. The former method was adopted for Final Fantasy XIII and its sequels, although some alterations were made in order to make the English dialogue sound natural.[13] In choosing voice actors, the company prefers to avoid well-known film and television actors, citing Ellen Page's casting in Beyond: Two Souls as a counterexample.[14]

Experiences

Honeywood described Xenogears, his first translation project at Square and the first to be handled internally by the company, as "pure hell".[1][15] He stated that he started to change the company's approach to localization after that game, moving booths to always work very closely with the original development teams, improving communication with them, and introducing full-time editors.[3][8] Woolsey also had a troublesome time while localizing Secret of Mana, which he said "nearly killed [him]".[16] The translation was completed within a month of the Japanese release as Square wanted to catch the 1993 holiday season.[17][18] Final Fantasy XIII's localization, handled by Slattery and Sugawara, was also quite chaotic. According to Slattery, the lack of deadlines, poor communication and synchronization between the various departments, and continuing changes to the script and to cutscenes led to a turbulent development. Due to the script changes, large sections of dialogue needed to be re-translated by Slattery and re-recorded by the English actors due to lack of necessary emotional drive for the scenes.[7] In contrast, Smith had a good working relationship with Yasumi Matsuno during the localization of titles like Vagrant Story, Final Fantasy XII and the 2010 re-release of Tactics Ogre: Let Us Cling Together. The two worked closely to ensure that the western versions were faithful to Matsuno's vision.[6] A challenging localization was Final Fantasy X, the first Final Fantasy title to feature voice acting. There, the team faced problems in both making the dialogue more compatible with an English-speaking audience and lip-synching it roughly with in-game characters, whose lip-movement was still for the original Japanese dialogue.[19]

Changes

When translating its video games, Square Enix tries to take into account the cultural differences between Japan and western territories. This sometimes involves rewriting dialogue or altering graphics, animations, and sounds. For instance, in Chocobo Racing, visual references to the Japanese folk heroes Momotarō and Kiji were changed to depict Hansel and Gretel, since the game was designed mainly for children, and Hansel and Gretel are better known in the west than Momotarō and Kiji.[3] According to Honeywood, trying to explain to the original development teams why some changes are needed can range from "frustrating to downright hilarious". Generally, older development teams trust the translators with making changes while newer teams can be more reluctant, though they usually build up trust gradually.[3] The localization team for The World Ends with You chose to preserve the Japanese elements to ensure the game's cultural aspect remained intact.[4] While localizing Final Fantasy XII, Smith worked to preserve the original script's meaning while using English dialects to reproduce the Japanese dialects found in the original version.[20][21] He and translator Joseph Reeder also ended up using different accents to identify factions within the game.[9]

Final Fantasy VII's script was done by a small team, resulting in a rough script and inconsistencies. One of the more famous of these was the name of Aerith Gainsborough: the name was originally meant to be a merging of "Air" and "Earth", but her name in the original game was translated as "Aeris".[2] During his localization of Secret of Mana, Woolsey was forced to trim down vast amounts of character dialogue due to an awkward fixed text font, later stating that he was satisfied with the result.[16] Vagrant Story has been recognized as a high-quality localization: whereas the original Japanese text was rather bland, the English version made use of archaic Medieval and Old English words and dialogue.[6][22] With ports and remakes of older games, dialogue can be changed or added by the team, as in the case of Final Fantasy VI.[7] The title can also be altered for various reasons. Final Fantasy IV and VI were released in western regions as Final Fantasy II and III. This was due to the fact that the original II and III had not received a western release.[17] The Final Fantasy Legend was originally to be called The Great Warrior Saga, but changed it to its current title to tie in with the Final Fantasy series, which was well-known and popular in the west.[23][24] Dragon Quest, one of the earliest successful Japanese role-playing games, had its title changed to Dragon Warrior so as not to confuse it with the similarly-titled tabletop role-playing game DragonQuest.[25][26] The DragonQuest title was discontinued in 1987,[26] and Square Enix registered the Dragon Quest trademark for their use in 2003.[27] Also due to copyright issues, The World Ends with You could not be released under its original Japanese title It's a Wonderful World.[4]

Gameplay may be altered when it is felt that a game might be too easy or difficult for the Western audience.[1] Some of the older Final Fantasy titles, such as Final Fantasy IV, were altered to be more easy to play in the West than in Japan, though their remakes and ports have generally restored the difficulty.[3][28] Einhänder's gameplay also received notable cuts for its North American release.[29] On the other hand, Final Fantasy XII: Revenant Wings was made more difficult in localized versions because the Western market was judged "more familiar" with the real-time strategy genre than the Japanese market.[30] For the western release of Dissidia Final Fantasy, the game was changed to suit western players, including removing several RPG elements to make it more akin to an action game.[31] Censorship can also affect the localized versions of the games and require obscuring mature themes, rewriting risque remarks or phrases, altering graphics or removing parts of some scenes. This was common in the NES and SNES eras but less drastic later on once video game content rating systems were established.[3] Original western releases of early games in the Final Fantasy and Dragon Quest featured multiple occurrences of this form of censorship.[17][25][32] Final Fantasy VIII also received some censorship for its European release, including the removal of a Nazi-like uniform.[33] Less commonly, this also goes the other way, for instance with Final Fantasy XII, in which a sequence involving violence against a female character was censored in the Japanese version but restored in the American and European releases.[1] References to religion can also be removed, as in Final Fantasy IV and VI.[34][35] Such references in Xenogears caused Square to consider not releasing it in North America.[36]

Releases

In 2008, Square Enix expressed willingness to make worldwide "simultaneous releases the norm".[37] Concerning Final Fantasy XI, at the time of the original English-only European release in 2004, producer Hiromichi Tanaka had stated that while Japanese/North American/Australian simultaneous releases are possible due to translating only Japanese to English, it was not possible for European countries due to the difficulty of finding good Japanese-to-European-languages translators, and the fact that second-hand translations from the English would be akin to "Chinese whispers".[38] However, the team later integrated full-fledged French and German localization teams, achieving simultaneous release from the Japanese for three different languages from 2007 on.[39][40] Another example of synchronized localization is Final Fantasy XIII: the company started the localization process alongside the game's development to lessen the delay between the local and international releases.[41][42]

Final Fantasy XIV: A Realm Reborn was localized in-house by Square Enix under supervision by Naoki Yoshida and Koji Fox. Compared to its predecessor, which featured English-only voice-overs, A Realm Reborn featured English, Japanese, German and French similar to Final Fantasy XI. The game featured voice work in a low number of cutscenes: this was explained by the fact that the team did not want new voice recording to dominate the creation of new content after the initial release.[43] The western release of Lightning Returns: Final Fantasy XIII was delayed by over two months because of the large amount of dialogue, which changes due to the game's time mechanic, that needed to be translated and recorded.[44]

The viability of a game's platform can also affect both the localization and the release, as in the case of the PlayStation Portable-exclusive Final Fantasy Type-0, which would eventually come west as a high definition port for PlayStation 4 and Xbox One,[45][46] and Seiken Densetsu 3, which was not localized due to undefined technical problems.[47][48] The company has also recently started releasing Japanese voice tracks as downloadable content, as in the case of Lightning Returns: Final Fantasy XIII[49] and one of the titles it has published, the Access Games-developed Drakengard 3.[50] Another aspect of Square Enix's policy concerning the western release of games was to make games that appealed to both western and Japanese audiences, but the worldwide success of the Japan-aimed Bravely Default caused them to rethink their strategy.[51]

Additional content

The localized versions sometimes expand on the original games. For example, when Honeywood found contradictions in the story of Chrono Cross, he worked with Masato Kato, the director and scenario writer of the game, to rewrite sections and add explanatory dialogue which was not in the original version. For Dragon Quest VIII: Journey of the Cursed King, voice-overs and orchestral music were recorded for the Western releases, while the original Japanese version did not have them.[3] Generally, gameplay content left out of the original game due to time constraints may be completed and added in the localized versions.[1] Sometimes, the expanded localized versions of games from series like Kingdom Hearts and Final Fantasy are re-released in Japan. The re-releases are usually based on a direct port of the North American releases, with only text translated back in Japanese and Japanese subtitles to English dialogue. They can also include features and tweaks previously only available in the western version alongside other additions.[52][53][54][55][56]

Reception

1UP.com's Wesley Fenlon praised Square Enix for the high quality of its translations, especially as space allocated for text and dialogue had been expanded with new and re-released versions of games.[2] Jeremy Parish, writing for the same site, said that the quality of Square Enix's localizations had "gone from laughable [...] to some of the best around."[57] Both praise and criticism has been given to individual games for the quality of their localizations. Xenogears, the company's first game to feature voice acting, drew criticism in regard to its audio presentation,[58][59] while The Bouncer received a fairly positive response.[60] Final Fantasy X received praise, although poor lip-synching and some aspects of the actors' performances were criticized.[61][62][63][64] The English release of X-2 ended up receiving the Seventh Annual Academy of Interactive Arts & Sciences award in 2004 for Outstanding Achievement in Character Performance.[65] Final Fantasy XII and Vagrant Story were both highly praised for the qualities of their localizations.[22][66][67][68]

References

  1. 1.0 1.1 1.2 1.3 1.4 1.5 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 2.4 2.5 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 Lua error in package.lua at line 80: module 'strict' not found.
  5. "Final Fantasy XII Developer Interviews". Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 6.3 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 7.3 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 17.2 Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Interview with Alexander O. Smith Lua error in package.lua at line 80: module 'strict' not found.
  22. 22.0 22.1 Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.
  26. 26.0 26.1 Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.