Viola Tsai's Portfolio

Life shrinks or expands in proportion to one's courage

Month: December 2018

LPM Group Project: Localizing Beat Saber

In the course Localization Project Management, I grouped up with 5 classmates to implement a localization project throughout the semester. We chose Hyperbolic Magnetism, an indie game studio based in Czech Republic, as our client in this project, and our goal was to localize the press release of one of their games Beat Saber into six languages.

Our workflow in this project can be divided into three phases: pre-production, production, and post-production.

The actions in the pre-production stage are listed as follow:

  • Setting up our LPM office by creating Trello checklists and Dokuwiki pages for our team, the client, and the project
  • Creating specification template and draft the specification for our project
  • Creating quote template and quote for our client
  • Setting up talent screening standard and search for talents for our project
  • Creating translation projects, TM, and TB in Memsource for the translators
  • Creating WO and PO templates
  • Drafting the general style guide for six languages
  • Sending the translator’s kit (including the translation project, TM, TB, WO, PO, and style guide) to translators

The actions involved in the production stage are listed as follow:

  • Translating: translate the source document into six languages in Memsource and export the deliverables
  • Editing: run QA check and spell check, ensure terminology matches the term base, check for accuracy and fluency of the translated text
  • Proofreading: run spell check again, check for correct number and formatting
  • Conducting final verification: confirm the formatting and naming of the files are correct

The actions in the post-production stage are listed as follow:

  • Updating TM and TB
  • Handing in the deliverables to the client
  • Sending invoice to client and translators
  • Having post-mortem meeting the the team

Among all the things I’ve learned from the project, one thing really stood out from my perspective, which is the importance of paying attention to details. This lesson is learned via two challenges we encountered in our project.

First of all, we had to use Top Tracker to track our time while working on the project so that we could distinguish billable and non-billable time. However, when we reexamined our time record, we noticed that sometimes we didn’t create a new time slot when we switched from one task to another. This made it difficult to determine the exact time we spent on certain tasks, which undermined our creditability while charging the client for our time spent on billable working hours.

In addition, while we were in the proofreading stage, a segmentation issue popped up. We didn’t notice this issue because the translations seemed fine when viewed as a whole. However, if we adopt the problematic segmentation, it will mess up the translation memory. Therefore, we had to fix the segmentation to avoid troubles with the TM in the future. As a result, we did a lot of rework during the TEP stage and spent a decent amount of extra time on the project, which will definitely increase our cost.

In hindsight, we should have been more careful with details in every stage in our project. We should have been more mindful with the activity labels in time tracker, as it will affect our ability to back up our invoice to the client with organized time record. We would not have to redo our translation if we had examined the translation project more closely while we were on it. In short, I realize that the best way to carry out the localization project efficiently is to be careful with the details in the first place.

Finally, although there are some small bumps along the way, I truly enjoy working with my teammates. Even though the workload was formidable and sometimes stressful, our team managed to pull off the project by supporting each other. When everyone is willing to go an extra mile for the team, a strong sense of trust is developed among us. Therefore, we can count on others to do their parts and won’t be afraid to ask for help. In short, this is exactly what dream team is like. I would love to apply what I’ve learned about teamwork in this project to my future work.

 

 

Website Localization Final Project: Tower Building Game

Below are the links to the live demo of the game Tower Building and the source code on Github:

Live demo: https://Violatsai.github.io

Source code: https://github.com/Violatsai/Violatsai.github.io

 

For the website localization final project, my teammates and I decided to localize a game called Tower Building from Simplified Chinese into English. We chose this game for the following reasons:

  • Tower Building is an open-source game on Github, which means that the source code of this game can be easily accessed.
  • Tower Building is primarily built with HTML5 and JavaScript. Therefore, as we have built and localized our websites using these programming languages during the class, we are more confident with localizing this game.

 

When we were assessing the source code of the game, we noticed that most of the strings in the game are embedded in the images. Since we haven’t learned Desktop Publishing, this problem became the biggest challenge in the localization process.

In order to solve this problem, we did some research on how to localize the strings in images. According to the article What You Need To Know About Graphic Localizationthe best practice for the localization of graphics containing text is to obtain the “original” artwork, which contains editable text layers. However, in our case, the source artwork files with editable text layers cannot be accessed. Thus, we had to photoshop every image containing text.

Hence, we started working on the localized version of the images with Photoshop. Nevertheless, as we weren’t very adept at using Photoshop, it took us a while to figure out how to remove original text and add the translated text to the images. Meanwhile, Hannah found a quick fix for this problem: If there is only one background color in the image, we can simply use the preview in Mac to edit the image.

After we finished editing the images, we duplicated all the files in the original folder and put them in a new folder (named en-us) in which we keep the localized content. Then we added the hreflang to the HTML files to distinguish two versions of the website. Next, we translated a few strings and swapped out all the images in the localized HTML file. At this point, both the original and the localized HTML files seemed fine. So far so good.

Nevertheless, we hit a wall when we tried to link the original website to the localized website. We adopted the approach used in our previous localization assignment, which is using a language selector to go back and forth between the websites. However, we couldn’t get the language selector to appear on the homepage of the game. Then I realized it was because we forgot to put the span tag inside a div, so the computer didn’t know where to insert the language selector. After this problem was fixed, the language selector finally showed up on the webpage.

Shortly after fixing the issue, we were faced with another problem: the language selector javascript file could not function properly. We didn’t know what was wrong with the code, so we adopted an alternative approach, which is connecting the original webpage and the localized webpage with hyperlink. It works, but we weren’t satisfied with this solution, as it is not scalable if we were to localize the game into more languages.

Therefore, we were determined to fix the problem with the language selector. After thoroughly examining the code, we realized that the problem was the directories in the JavaScript file. Because in our previous assignment, the language selector was designed to localize the website from Chinese into English . Therefore, the localized folder was named zh-tw instead of en-us. Therefore, the language selector could not find the correct HTML file because the folder name was incorrect. The language selector finally works after we fixed this problem.

In short, I think the greatest lesson I learn from this project is to be perseverant. It is very important to have grit while facing one challenge after another, because the process of troubleshooting and debugging can be very frustrating. We could have taken the easy way out by settling down with the hyperlink approach. However, we wanted to figure out why it didn’t work, so we got to the bottom of this and resolved the issue. Hence, I believe the lesson here is that, if we are determined in pulling through a difficult task, we can achieve our goal and really grow from the experience.

 

 

CAT team project: translating an article for the New York Times

In this project, my teammates and I implemented a translation project with the skills and knowledge we learned from the course.

Acting as a Language Service Provider, we go through the entire translation process, which includes:

  • Setting up a LSP office
  • Drafting a Statement of Work and Quotes for our client. For more details, please refer to our CAT_proposal

Continue reading

What I’ve learned from “Intro to CAT”

In the course “Introduction to Computer Assisted Translation,” I’ve learned the basic features of several Translation Environment tools, such as Trados 2019 and MemoQ, from the perspectives of translators, editors, and project managers. Through lectures and hands-on practices, I’ve acquired the following CAT tool-related skillset:

  • Creating project and packages with customized settings
  • Creating TM and TB
  • Managing terminology
  • Customizing QA settings and performing QA checks
  • Editing translation
  • Generating quotes and project report based on Trados analysis

Continue reading