Memuat
Memuat
Want to go deeper?
Join one of our courses or ask us directly on WhatsApp.
Picked from the software, topic, and level of “Claude from Zero to Expert Class #15: Translating and Adapting the Tone of Writing”.
Other ways we can help with Claude.
Learn with a mentor
Scheduled AI & Machine Learning courses with live guidance and a certificate.

Midjourney Course: Create Stunning AI Images from Text
★ 4.9

DALL-E Course: Creating Professional AI Images from Text
★ 4.9

Stable Diffusion Course: AI Art from Beginner to Professional
★ 4.9
Have it built for you
No time to learn Claude? Our team can do the project for you.

AI Image Creation with Stable Diffusion — Unlimited Custom Visual Production
★ 4.9

AI Image & Video Creation with Leonardo AI — All-in-One Visuals for Business
★ 4.9

AI Image Creation with Midjourney — Cinematic AI Art for Business
★ 4.9
Get notified about new Claude classes
At most one email a week. Unfollow anytime with one click.
The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.
Hi, and welcome back. This is the last episode of the Writing and Communication session, and we'll cover two skills that go hand in hand. First, translating with the right feel. Second, adapting your writing style for different readers, even when the language stays the same.
Have you ever read a translated restaurant menu that made you smile because it was too literal? Correct by the dictionary, but strange to the people reading it. Claude can do more than translate words. As long as we say who the readers are, Claude can adapt the feel of the language. This is very useful for small businesses. A menu for tourists, an email to a supplier abroad, or a caption for buyers in another region can be written without hiring a translator for every everyday text. Here's the first example, a line from Sunset Coffee in Indonesian. The word-for-word translation sounds odd: friend of going home work. The localized version becomes palm sugar iced latte, your after-work treat, which feels natural to English speakers. Second example: order through DM, yes. That little yes is a friendly Indonesian filler word, and it doesn't need translating. The localized version: send us a DM to order. Third example: an apology line from a formal email. English has its own standard phrase for it: we apologize for the inconvenience. So when you ask for a translation, don't just write translate. Say who the readers are and what it's for, such as tourists reading a menu, or a supplier reading a formal email.
More and more tourists from abroad are visiting Sunset Coffee. Laras asks for a bilingual menu with three rules: product names stay in Indonesian, each gets a short English explanation, and prices stay in rupiah. The right panel shows the menu. Names like kopi susu gula aren stay original, because that local touch is exactly what tourists look for. Next to each one is an easy-to-understand explanation. Laras wants tourists to know the delivery fee and opening hours too. She simply asks for them to be added at the bottom. Claude adds that information in both languages, without touching the menu table. Delivery is ten thousand rupiah, free above two hundred thousand, and the shop is open from eight in the morning to nine at night. Notice the role of those rules. Without them, Claude might translate gula aren as brown sugar, even though the taste is different, or convert the prices to dollars. From the menu example, we can draw three rules worth writing every time. First, what must not be translated, such as product names, brand names, and people's names. Second, who the readers are and what it's for. Tourists reading a menu in the shop need a description of the taste, while a supplier needs plain business language. Third, what must not change: prices, currency, dates, and units. Without this rule, Claude might convert prices or change the date format. These three rules take only a sentence or two at the start of the prompt, but they make a big difference to how accurate the translation is.
Now Dewi receives an email from a gel pen supplier abroad, Mr. Tan from Lim Stationery. The email is in English, which is Dewi's second language. It covers the minimum order quantity, a confirmation deadline, and the delivery schedule. Dewi understands the gist, but wants to be sure she hasn't missed anything. Terms like minimum order quantity, often shortened to MOQ, are very important in business. A small misunderstanding can get an order rejected. Dewi pastes the email and asks for two things: an explanation in plain words, then an English reply based on her own decision. Claude explains the content briefly, then writes a polite reply. There's one small addition: a request for a proforma invoice, which is a preliminary bill sent before the goods ship. Dewi adds one safety step called back-translation. She asks for the reply to be translated back into Indonesian, her first language. Reading the back-translation, Dewi is sure the meaning matches her decision. She also notices the proforma invoice request, and since she actually needs one, she keeps it. Back-translation is a simple way to check a language you don't fully master. Use whatever language you think in. If the meaning has shifted, you'll know before the email goes out.
Adapting style doesn't always mean changing languages. Mr. Hendra needs to announce a tutoring holiday to parents, to students, and on his WhatsApp status. Claude writes three versions of the same information. For parents, formal and polite. For students, casual and cheerful. For the WhatsApp status, just one sentence. The dates are exactly the same in all three versions. That's what we must always check: the style may change, the facts must not. This technique is useful at the office too. One new policy can be written formally for a memo, briefly for the team's WhatsApp group, and in more detail for new employees. If you translate often, build a glossary: a list of terms with their standard translations. First row: kopi susu gula aren always becomes palm sugar iced latte, never brown sugar. Cold brew doesn't need translating, because the term is already known everywhere. Paket hampers becomes gift box, and the contents can be mentioned when needed. Ongkir becomes delivery fee, and the amount stays in rupiah so it isn't confusing. Pesan lewat DM becomes send us a DM to order, used specifically for social media captions. Paste this glossary every time you ask for a translation. The result: your menu, captions, and emails all use the same terms, as if one person wrote them.
Before using a translation, run five checks. First, numbers, dates, units, and currency. Date formats and thousands separators can differ between languages. Second, product names, people's names, and place names must stay correct. Names don't get translated. Third, the terms follow the glossary you've built. Fourth, the back-translation still means the same as what you intended. Fifth, for official documents such as contracts, certificates, or legal papers, don't rely on Claude alone. Use a professional translator, or a sworn translator when one is required. For everyday writing like menus, captions, and routine emails, these five checks are enough. When you can, also ask a friend who's fluent in that language to skim it before you use it. This episode closes the Writing and Communication session. Let's gather the results. Template one, email: context, task, data, tone, plus a check before sending. Second, the caption template, with the brand voice guide at the start, so every post feels consistent. Third, the product description template: complete data, who the buyers are, the format, and limits on claims. Fourth, the summary template, which limits Claude to the text itself, complete with checking questions. Fifth, the translation template: name the readers and purpose, paste the glossary, then check with a back-translation. Keep all five templates in one document. The Claude screens in this video are simulations, so menu positions may differ slightly, but your templates will stay useful anytime.
We've learned the difference between translation and localization, made a bilingual menu, replied to an English email with a back-translation, written one message in several styles, and built a glossary. The writing session ends with five ready-to-use templates. In the next episode we start a new session, working with files. We'll upload a PDF and ask about its contents. See you there!
Try these on your own after watching to lock in what you learned.
Type a question or keyword; we find the part of this episode that explains it and jump the video there.
Notes are saved with the current video time and are only visible to you.
Stuck on a step? Ask here; the instructor and other learners can answer.
No questions yet.

Cerdas Inovasi Digital Team
Software developers, BIM & 3D engineers, and AI practitioners
We build software, BIM models, games and AI automations for clients every day, and turn that hands-on work into step-by-step classes: every step is shown on screen and comes with a PDF guide you can keep.
See our clients →