The goal of this and the following lectures is to understand how to use classification to accurately determine the translation requirements even if the client didn't provide them. Basically, how to play Nostradamus and predict what could go wrong during the translation process. Specifically in this lecture, we will talk about how content type and quality blogs are interconnected. It's easiest to explain this methodology in practice. Let's take the case of localizing a small app from Google Play which helps people keeps their eyes healthy by taking breaks from working on the computer and complete an asset of exercises to relax the eye muscles and improve their vision. Then, it wasn't translated by professional which plays into our hands because we can see the problems that may arise from certain errors. Here we'll look at the difference between the translation of the interface and the app's description in Google Play. If you'd like you can take a look at the app's page in the store. Let's classify boss of the texts and based on the methodology that I described in the second lecture. First, let's determine the subject area of the text. I will remind you that the subject area is what the text is about and this case it's simple and the topic is stated right in the Google Play. It's health and fitness. We can add that to it's also ophthalmology since the app is dedicated to pie house. This tells us and which we all should say are translator-specialized if your browser wants to professional localize the app. Let's note that the subject area will be the same for the app user interface and its store description. But as I have already mentioned, completely different texts can created for the same thing. So that application and container will be different. The application will be answered to questions. What is the goal of the text? Why was it written? The goal of the app is to teach people how to take care of their eyes. Accordingly, application is definitely education. But the app description has a completely different goal in mind. It doesn't teach anything to anyone. It's needed to tell all users what the app is about and ideally convince them to download it. This means that the application for description is promotion. It means advertisement or marketing. As you remember, the application sets forth their requirements for the translation style. For educational content, it's important to clearly and concisely explain the necessary topic. Advertisement texts need to be convincing and should show the product or service in the best light possible. This means that the translator working on these two types of texts will need to have a different experience, and ability to work on different writing styles. Finally, we'll talk about the container. In one case, this is user interface or UI which is basically the text strings from the app. In the other, it's a text from the website. So we see the container sets the formal requirements for translation. When translating UI, the lengths of the strings is often very limited because the screen a user is looking at has limited space. The translation can also use placeholders and variables from the source code. Maybe in numbers, dates, times, and so on into the localized. Luckily, this specific app that doesn't have many of such issues. But remember that when translating any UI, you need to pay special attention to this requirements. Or in worst case scenario, the incorrect translation may actually break the source code. Can this be problems which translate to website texts? In this specific case, most likely not because there's almost no formatting here, which means we would just need to translate the text. But if the author decided to highlight certain vowels and phrases using vault or italic font, or insert tables and lists, the text for translation would include HTML tags creating the task for the translator of setting the text in relevant places in the target text. To do this, the translator would need to have at least basic knowledge of HTML. If this knowledge is lacking in the best case scenario, the target text won't be formatted properly. In the worst case, the structure of HTML texts will be broken and the pages won't appear open at all or it will include art effects. So by classifying the content, we can quite accurately emulate what requirements the translation may have. Moreover, using such classification we can predict what can go wrong if translator doesn't pay attention to the requirements.
