Alt-F4 #20 - Retrospective 2: Electric Boogaloo
Table of Contents
Rounding out the first five months of issues, Alt-F4 #20 brings the second part of our retrospective and look behind the scenes. Nanogamer7 takes us through how the translation process got started and what some of the problems are that came up. But before that, Conor_ presents us with a sort of mission statement, which puts our thoughts on the project into a succinct form.
Alt-F4 isn’t Reddit. It isn’t the forum. It isn’t Discord. It also isn’t the FFF. These might seem like obvious statements but they have been a helpful guiding light, pointing us towards the type of content and presentation style we want to achieve. We want to be the place to go for polished writing related to the game we love so much. These stories might be about the UI design of an awesome Factorio mod, a tale of exploring the harsh and unforgiving galaxy, or even just us getting really nerdy with maths, but they’re all telling a story about what makes this game special for each of us. Each week we finish our releases with a call for contributions, and looking at that helps tell the story of what we want Alt-F4 to be:
If you have something interesting in mind that you want to share with the community in a polished way, this is the place to do it. If you’re not too sure about it we’ll gladly help by discussing content ideas and structure questions.
It shows that contributing to Alt-F4 shouldn’t feel like a chore or an obligation; We want it to be a collaborative process of us helping you to tell the story you want to tell, whatever it might be about. We regularly have long conversions in our Discord (which you should totally join if you haven’t!) with contributors about where we think they should take their writing. When I personally give feedback, it’s often a case of “I want more information about this really cool topic”, while trying to convey enthusiasm in the hopes that I can inspire more creativity.
We also do our darndest to make the barrier of entry as low as possible, making sure that anyone and everyone who wants to contribute can do so. We’ll take submissions in whatever form they come, good or great grammar, long or short, in fancy-pants markdown, a text file, or even handwritten! Everyone is welcome to contribute and I encourage all of you to think about whether there’s anything at all you want to write about, and if there is, come and chat with us about it, we’ll be happy to have you! I’ve personally never particularly enjoyed writing, but doing so for Alt-F4 in release #15 was great fun and I fully intend to write more in the future. For me, it makes it so much easier writing about something you are passionate about, and I think we’re all passionate about this silly little factory game.
The beginnings of Alt-F4 were small. One man, one issue, one language. The second week, there already were a dozen people eager to help. Looking desperately for something to do that wasn’t already someone else’s job, the idea of translations came up. With the multinational community that Factorio has, there quickly were a few interested translators for various languages, like German in my case, which I will focus on today. A single person has quite obvious limitations: For example, the workload can’t be split up, and while reviewing your own translation definitely helps with quality, having more eyes looking at it provides a far greater value. Coordinating multiple people poses interesting challenges of its own though; more on that later. First I’d like to give you an idea of how much translation we actually do.
I want to go into more detail regarding the German translation process as I think it’s a great example of some of the benefits of having multiple people working on one article, but also highlights some challenges that come up with both organisation and the translation itself. Also, I just don’t know that much about the other languages, seeing as I only work on the German one.
We got started as a group of three people, and after ironing out some initial technical hiccups, we were already going through the backlog of the first few issues. Then, the first new issue came up. For older issues it was fine for a single translator to work on it for however long it took him, but when the deadline is in 24 hours, we need to parallelise the work. Luckily it got apparent pretty quickly that individual articles could be provided earlier than the whole issue by the editorial team, and with the added benefit of more time to work on them, we already started to split the workload. But what do we do with our finished articles? Just sending them into our Discord channel without any versioning proved pretty chaotic early on, and our own GitHub repo was on the table but proved too big of a hassle for those without experience with git. So
_v1 version suffixes it was. With a (mostly) consistent naming scheme, and an online difference checking tool, we had everything we would need from GitHub, right there in our Discord channel.
“Great, they now sorted everything, and that’s it, no more problems, right?”, you might think. Wrong! You might be correct with technical issues, those mostly were sorted out indeed. But language isn’t just ‘right’ or ‘false’, there are way more nuances to it. You might have encountered different spellings between American and British English. Those often only have one letter changed though, and even if they are two completely different words, a Brit will still understand what an eggplant is. In German, however, there are many words an Austrian uses every day, but someone from northern Germany might have never heard of.
Even though regional differences might seem like the biggest troublemaker, what kills us are actually the more subtle quirks, like the fact that we have a formal and a more informal version for ‘you’, and those sometimes completely change the structure of a sentence. In some settings, it’s unambiguous which form you should use, but especially for a blog, there are great arguments for both sides. (This is also the reason why I don’t like dubbing, even big-budget films get it wrong all the time, and it just feels so unnatural when someone “Siezt” (formal ‘you’) a close friend.)
One case where it pays off to have different people working on the same thing though is synonyms. Well, technically ‘not-synonyms’, because even though some words might have a similar meaning to most people, especially in tech, some words sound a bit off, even though they translate to the same English word. For scenarios like this, it really pays off to have your translation proofread by up to four more people, all with other areas of expertise. This however is also were our biggest weekly challenge comes in:
Translating takes time. We don’t have that. Currently, articles come in on Thursday morning (Note: this isn’t always the case, but for most articles it is), we start translating at noon or in the afternoon, and have a first translation in the evening. But then someone wants to proofread it. And I can’t remember the last time we didn’t have corrections after someone went through a translation. Corrections might not always be better though, even though they were well-meant (we have a German word for that of course: “verschlimmbessern”, to worsen something by trying to improve it); thus we now always have the original translator read through the corrections. But you guessed it: that takes time too. If we have a good day, and everyone is available, we are sometimes less than half an hour before release still busy ironing out some hiccups, correcting errors, and fiddling with non-synonyms.
Sometimes these problems, especially the more technical ones, result in changes for all languages, sometimes even the original English text. For example, quotes are like they are now because we couldn’t figure out how to incorporate translations while still keeping the original quote. Most of the time Firerazer and Conor_ resolve those problems with their final reviews, right before merging and publishing the article.
I want to briefly talk about translating continuous text versus individual strings (TheEnemy42 touched upon this in his translating the game article). While it’s an art form in itself to translate Alt-F4 while staying within a reasonable length and keeping the meaning of the text as close to the original as possible, translating it in a way that conveys all the content while still being enjoyable to read is on a completely different level. Both suffer from a similar problem though, which stringweasel mentioned in the very same issue: jargon. A large part of a game’s jargon is composed of contractions and abbreviations of in-game terms and existing technical jargon from the real world, which often doesn’t translate to other languages, or even make any sense in them. So we try to find the words in our own language that convey the intended meaning as best as possible.
With how much I’ve complained, you might now wonder “Why do we even translate? Is it for the readers?”. Well, I mostly do it because I enjoy it. It’s sort of like programming, but instead of confusing flowcharts or messy thoughts in your head, we have an English text, and instead of translating to programming languages, we translate into real ones, which can be frustrating, as coding can be too, but all in all, is a fun puzzle.
In the end though, the readers are the reason why there even are translations, and we really think our work can bring ALT-F4 to a larger audience. So if you know people that are interested in more Factorio content, we’d be more than happy if you told them about this blog, whether they read the translated versions or not!
So hopefully these last two issues contained some interesting insight into the project and how it evolved to what it is today. We’re not done, of course, we’re planning to keep this going for as long as we enjoy putting it together and you enjoy reading it. To that end, I wanted to bring up that we need submissions from all of you to make this project work. All these processes are well and good, but it’s our goal to give community members a platform to make their voice heard and to present an interesting and enjoyable read to everyone. So if you got anything you’re passionate about that people should hear, please join the Discord and share it with us.
I want to thank everyone that contributed to the project, you are all amazing. Be it the translators, who spend many hours putting together their translations in a collaborative way so that the content can be enjoyed by many more people around the world, reaching non-English speaking communities in ways the FFF did not. Be it the writers who come up with some great ideas to write about, incorporating feedback and just being the lifeblood of the project in general. Be it the techies, who jump at our every request to allow us to present the content in a nicer way, and making it all as accessible as possible to all readers. Be it the editorial staff that puts in the effort to give good feedback to writers, polishing the weekly articles as much as possible, and for putting up with my personal nitpicks on things.
Factorio has the nicest community I have ever been a part of, and the subset that gathered for Alt-F4 is even nicer if such a thing is possible. I don’t think I had a single negative interaction this entire time. Seeing as how much of a toxic wasteland some gaming communities are, I’m so grateful ours is the way it is. Thanks to everyone for being such nice people, it really makes all this a joy to work on and makes it worth the effort.