For many players who spent the 1990s and early 2000s with Capcom games, the name Takuya "Tom" Shiraiwa may have passed by quietly in the end credits. It was the kind of name most people saw for only a few seconds before moving on, especially in an era when players were less likely to pause and study every credit. Yet behind that small line of text was a person doing work that helped Capcom’s games travel beyond Japan at a time when the company was still learning what that process should even look like.
Shiraiwa’s name came back into focus through a chain of retro-game curiosity. Research into Slip Stream, Capcom’s unusual 1995 racing game and one of the rare third-party releases for Sega’s System 32 hardware, led to a wider look at his career. From there, his translation and support work connected to some of Capcom’s best-known series, including Marvel vs. Capcom and Resident Evil. That path turns a small credit into a larger story about how games were prepared for other markets before localisation had become a polished department with formal tools, processes, and job titles.
Shiraiwa did not enter Capcom through a modern localisation route. At the time, he was already deeply into games, and that mattered as much as his language ability. Inside the company, there were not many people who could speak English and also understand how video games worked. Because he had both pieces, even in a rough form, development teams began turning to him when they needed help with English text. The work was not yet framed with the word "localisation." It was treated more simply as text translation, even though the job was already becoming much broader than that.
His English improved because the situation demanded it. When visitors from overseas came to Capcom’s office, Shiraiwa would be brought into meetings. Then, as he remembered it, his boss might leave the room, and he would suddenly be alone with people who did not speak Japanese. In that kind of moment, silence was not an option. He had to find a way to communicate, whether through limited English, gestures, or whatever words he could reach for. It was not smooth, but it was practical, and that practical pressure became part of his training.
After two years at Capcom, Shiraiwa was sent to Sunnyvale, California, where he worked with Capcom USA, also known as Capcom Entertainment. He spent two years there as a liaison, and the experience helped his English a great deal. Just as important, it put him in the middle of the conversation between Japan and the overseas branches. He was not only changing Japanese words into English. He was helping information move back and forth between people who were building the games and people who understood how those games might land in the United States and Europe.
The Capcom he describes from that period feels young, busy, and unusually direct. This was around the period after Final Fight had arrived, a game he remembered as being extremely popular. Capcom was still a relatively young company, and Shiraiwa described it as amateurish in a positive sense. The word was not meant as an insult. It pointed to a place where people cared intensely about the games they were making, and where the main concern was not simply profit. In his memory, the priority was to create games that players would genuinely want to play.
That attitude is a useful window into why his role grew so naturally. Capcom already had a United States subsidiary, and Shiraiwa became one of the people connecting that side of the business with the Japanese teams. Alongside in-game text translation, he carried feedback and suggestions from the American and European offices back to the developers in Japan. That made him a translator in a larger sense: not just of language, but of expectations, market concerns, and practical requests. In the pre-modern localisation era, those responsibilities could sit on one person’s desk simply because that person could make the conversation happen.
The actual text work came with strict technical limits. When a team asked Shiraiwa to translate, they would also give him the available space, the number of letters that could fit, and the character limit for each line. He had to return the English with line breaks already placed so the words would fit into the box the game allowed. This sounds small until you remember how much more room English often needs compared with Japanese. A sentence that looked compact in Japanese could become awkward, crowded, or impossible once it had to be expressed in English inside the same tiny space.
Shiraiwa’s answer was to push for more room. He often told teams that English needed at least twice the space of the original Japanese text. Without that, he felt there was no realistic way to translate properly. Eventually, according to his memory, the developers began listening and gave him that doubled space. Even then, the job remained difficult. This is one of those hidden retro problems that players rarely notice when it goes well. A clean menu line or message box can look obvious on screen, but someone had to fight the limits of the interface to make it feel that way.
Some of Shiraiwa’s early credits appear in special thanks sections rather than under a simple translation label, and that reflects how mixed the work could be. Games such as Dungeons & Dragons: Tower of Doom and Goof Troop were not only internal Capcom projects in the usual sense. They involved outside rights holders, which meant that someone had to help the development teams communicate with partners and follow outside rules. Shiraiwa became involved in that kind of bridge work too, helping Capcom deal with companies connected to major properties, including TSR and Disney.
Goof Troop is a clear example of that responsibility. Disney had detailed rules for how its characters should and should not be handled. Shiraiwa had to translate that style guidance for the Capcom team so the developers understood the boundaries. Then, when the team came up with gameplay ideas, he translated those ideas into English and sent them to Disney for approval. That process shows how localisation-adjacent work could stretch far beyond finished game text. It could include character rules, proposal language, approvals, and the careful handling of licensed worlds that already had strong identities outside games.
Marvel brought its own challenges. When Capcom began working with Marvel Comics, Shiraiwa remembered that the rules around the characters were very specific. Marvel had clear ideas about behaviour and personality, and those ideas could collide with the needs of an action game. Shiraiwa found himself acting as the middle person again, trying to explain what a fighting game required while also respecting the character rules coming from the licence holder. It was a delicate position: Capcom needed freedom to make the game work, while Marvel wanted its characters to stay recognisable and consistent.
One memory captures the problem especially well. Shiraiwa recalled a discussion about whether a character could jump. From a game-design point of view, a head-to-head fighter needed jumping as a basic action. From the licence side, the rule was stricter, and the answer he received was that the character would not jump even if faced with a large gap. Instead, the character would fall in and keep running after landing. Shiraiwa accepted the explanation, but the practical issue remained. This was a fighting game, and the character needed to perform the moves the genre expected.
Those early Marvel conversations caused plenty of headaches, but the tone changed after Capcom released one or two Marvel fighting games and they became highly successful. Shiraiwa remembered that the restrictions loosened dramatically, to the point where the response became much more open and Capcom could do what it wanted. That shift left him wondering why the rules had been so strict at first. His dry conclusion was that money can change the conversation. It is a small but revealing detail about licensed games: creative limits are often firm until success proves that a different approach can work.
Taken together, Shiraiwa’s memories show a version of game localisation that was personal, improvised, and surprisingly wide in scope. He translated text, adjusted lines to fit limited screens, carried overseas feedback back to Japan, explained style guides, prepared gameplay ideas for approval, and negotiated the practical needs of game design against the rules of famous characters. Today, many of those jobs would be separated across teams. In Capcom’s younger days, they could gather around one bilingual game fan who happened to be in the room when people needed help.
That is what makes his story feel so valuable from a retro-history point of view. Credits can make old games look neat and finished, but the work behind them was often messy in the most human way. Shiraiwa’s path through Capcom sits at the point where translation, production, licensing, and player experience all met. His name may have been easy to miss on a scrolling screen, but the work connected to it helped shape how Capcom’s games spoke to players outside Japan during a defining stretch of the company’s history.
