I18n Game Content: Multilingual Audiosprites and Captions Workflow
I’ve started making a list in my head of things I feel strongly about in software. I18n is pretty high towards the top of that list. I wrote (and re-wrote) a post explaining why i18n is so darn important, but I couldn’t find a comfortable balance between all-out rant and something that felt hollow. In the meantime, I’m just going to say clearly: “Please internationalize your software.”
Here’s an example of I18n in the wild.
I was working on a game…
I’ve wanted to make a video game since I was a kid sitting at my dad’s Apple IIc thumbing through the Basic manual. I briefly toyed around with various attempts over the years but never really got very serious. Last year I finally devoted some real time into learning both Unity and Phaser. I ended up shelving game-dev for a bit, but it was fun exploring new challenges.
While I was prototyping an adventure game in Phaser, I wanted to build a robust audio and text dialogue system that supported multiple language locales. I ended up finding some neat technologies and creating a comfortably streamlined workflow.
You can check out the resulting audio engine prototype read on for the process.
- cross-browser compatible audio
- captions in multiple languages
- audio in multiple languages
- easy to create and update
- caption display timing synchronized with audio
(Note that the actual mechanics of dialogue bouncing between person A and person B won’t be covered here.)
Cross-browser compatible audio
Different browsers support different audio formats out of the box. If you want cross-browser compatible audio, you really want to serve your content in multiple formats. Don’t fret about bandwidth: clever frameworks (Phaser included) will only download the best format for the current browser.
In Phaser, you just pass an array of audio files.
1 2 3 4
You want ogg for Firefox and then probably m4a and/or ac3. You might want to avoid mp3 for licensing reasons, but I’m not a lawyer (I’m also not an astronaut).
Captions in multiple languages
For our purposes, captions are really just text displayed on the screen. In nearly every adventure game, the character will encounter a locked door. Attempting to walk through that door should result in our character explaining why that can’t happen yet.
Even if we didn’t care about internationalization, it would make sense to refer to the caption content by a key rather than hard-coding the full text strings throughout our game. Beyond just keeping our code clean, externalizing the strings will allow us to have all our content in one place for easy editing.
Here’s a very simple caption file in JSON format:
1 2 3 4 5
We’ll write a function to render the caption so that we only need to pass in the key:
1 2 3 4 5 6 7 8 9
And it renders something like this:
Localizing our captions is pretty straightforward. For each language we want to support, we copy an existing translation file and replace the JSON values (not the keys) with translated versions.
We’d do well to leverage convention over configuration. Keep all captions for a locale in a folder with the locale name.
1 2 3
Changing locales should change the locale folder being used. Your game is always loading “captions.json” and it just decides which copy to load based on the player’s locale.
Audio in multiple languages
This part doesn’t need to be overly clever. Record the same content in various formats for each language.
Consider the caption JSON from the previous section. It might make sense to have one JSON file per character. With some direction, a voice actor could read each line and you could save the line with a filename matching the key (e.g. the audio “Drats! The door is locked.” is saved as locked_door.wav).
We’ll store the encoded versions in locale-specific folders as we did with our captions.json
1 2 3 4 5
And then we can update our
say function to also play the corresponding bit of audio.
1 2 3 4 5 6 7 8 9 10 11 12
Easy to create and update
Have you ever played a game or watched a movie where the captions didn’t accurately reflect what was being said? This drives me crazy.
I’m guessing that the reason that audio and caption text fall out of sync is probably late content changes or the result of actors ad-libbing. Fortunately we’ve got a system that is friendly to rewrites from either side. Prefer the ad-lib? Update the caption file. Change the caption? Re-record the corresponding line.
The content workflow here is straightforward. To reiterate:
- Create a script as json with keys and text. Edit this until you’re happy. Tweak it as the game content progresses.
- Translate that file into as many locales as you care about.
- Losslessly record each line for each locale and save the line under the file name of the key.
- Tweak captions and re-record as necessary.
That’s all well and good, but now you’ve got a ton of raw audio files you’ll need to encode over and over again. And having a user download hundreds of small audio files is hardly efficient.
We can do better. Enter the Audio Sprite. You may already be familiar with its visual counterpart the sprite sheet, which combines multiple images into a single image. An audio sprite combines multiple bits of audio into one file and has additional data to mark when each clip starts and ends.
Using the audiosprite library, we can store all of our raw audio assets in a per-locale folder and run:
1 2 3 4 5 6 7 8 9 10 11 12 13
Awesome. This generated a single file that joins together all of our content and did so in multiple formats. If we peek in the generated JSON file we see
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Phaser supports audiosprites quite well. We tweak our engine a bit to use sprites instead of individual files and we’re good to go.
Caption display timing synchronized with audio
Now we turn to keeping the captions we’re displaying in sync with the audio being played. We have all the timing data we need in our audiosprite JSON.
We’ll update our
say function to clean up the dialog text after the audio has ended:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Aside: Not everyone reads at the same speed. You’ll probably want to consider having some sort of slider that acts as a multiplier for the caption duration. Readers who prefer to read more slowly can happily use 1.5X or 2X caption duration. You might not want to have the slider go less than 1X lest the captions disappear while the speech audio is still ongoing, but perhaps some portion of your audience will turn off audio in favor of reading quickly. The duration of the audio still makes sense to me as a starting point for caption duration.
The prototype code
The prototype code covers all you need to get rolling with Phaser and Audiosprites. It also has basic support for preventing people talking over each other. Hopefully you’ll find it instructive or at least interesting.
That concludes this random example of I18n in the wild. Stay global, folks.