I do not envy the #localisation team that worked on the #German #translation of #CitiesSkylines2.

Please, not the Gesundheitsfürsorgedienstleistungsgebäude!

#localization #games #gamedev

My best clients tend to be those who don't employ #LLMs or so-called #AI anywhere.

Even if an #LLM could effectively assist in #translation, knowing when, where and how to employ its services would be our job as language professionals, no? We're the ones they specifically hired for our #localisation expertise, after all.

Not to mention the aforementioned corporate espionage, IP and data security nightmare.

#localization #antiAI

It's quite silly how much #localisation clients (rightfully!) value our utmost confidentiality and their extensive NDAs, while *at the same time* using random MT software to send their *raw, classified project data* over to dozens of random #AI companies for pre-processing and 'assisting' us.

And then those MT results are swiftly disregarded by us translators anyway because it's garbage quality.

I wonder if that'll eventually have any consequences.
#localization #translation #LLMs #LLM #antiAI

Dear fellow #localisation and translation folks working with #German, can we agree to stop the silly obsession with hyphenation?

There's no reason that "Shadewood Cliffside Fortress" needs to be translated as "Schattenholz-Felswand-Festung".

"Sand Hollow Outpost" is not "Hohlsand-Außenposten", pleaaaaase.

Please be a bit more creative and look at real location names if possible. Prepositions aren't gonna eat your metrics!

#localization #translation #games #gaming #gamedev

I think MOST #localisation projects suffer from not providing a *general* style guide.

Style guides are usually only about the specific project ("keep skill names capitalised"). Translators are expected to handle the many daily micro decisions without any guidance.

Translators then often play safe and avoid rocking the boat, even if the safe solution isn't elegant. They won't split sentences, rephrase strings, or touch original names beyond the bare minimum.

(1/5)
#localization #translation

I am beginning to think that nobody ever gets credited in video game #localisation. It's a myth.

I've never played a game where the credits roll included anyone further down the line than some loc coordinator or LQA manager, if at all. Let alone freelancers.

Does anyone know of a single game that credits their individual translators?

#translation #localization #gameDev

✨ New blog post: "From Scripts to Systems: Why LangOps Needs Rapid Automation"
As localisation shifts from file handling to workflow orchestration, ops-level automation is becoming essential. ⚙️🤖
https://laurahargreaves.com/from-scripts-to-systems/?utm_source=mastodon&utm_medium=social&utm_campaign=autopost

#LangOps #Localisation #Automation #AI

Here's a question for people in #translation and #localisation:

How do you personally handle advertising your experience (for example, on your website or sites like #ProZ)?

You can't go with a traditional portfolio of projects you've contributed to when most of your work is under an NDA, a non-advertisement clause and you do not end up in the credits.

So, how do you deal with it?
Anonymising your past projects to the point it doesn't violate your NDA?

#localization #career #freelance #work

As someone who works in #translation and #localisation, people often assume that any bilingual could do my job.

My clients largely pay me for my experience. I know how to use industry-standard software and workflows. I know many common translation pitfalls and notoriously difficult words and phrases.

But I am not a walking dictionary. I still look up words on the daily.

The difference is that I know when, where and how to look up something, and how to judge the results.
(2/3)
#localization

Support with internationalisation, translation & localisation voor developers

https://video.ngi.eu/w/wmcZpzsFjunFMt9K9Jr7cA

SNT : Géolocalisation, comment s'y retrouver ?

https://tube-sciences-technologies.apps.education.fr/w/sM6VgZsPVoYfEMNnRx3sJ3

Little known high of #gameLocalization: The moment you realize you have a full dialogue scene with your favorite character ahead of you. I just love this guy's diction and getting to dive into his speech.

#gameLoc #localisation #translation

Hello, #PortfolioDay!

I am an EN/DE > FR translator with 14 years of experience. I am specialised in the fantasy genre, mainly for video games as you can see below.

I have also translated a 200-page sourcebook for The Dark Eye, the famous German TTRPG.

If you are looking for a French partner for localisation, or know somebody who might need one, let's talk!

📬Email: jps.translation@gmail.com
🎮Detailed portfolio: https://jpstraductions.wordpress.com/portfolio/

#localisation #translation #GameLoc #videogames

When I started working as a freelancer, I was squarely under the impression that I knew what localisation/translation was about and what I'd be doing all day.

I had no idea how many other kinds of language tasks there are that I'd be doing for clients!

Alignment tasks? Stand-off proofreading? Knowledge base maintenance? I had no idea our field was so diverse back when I started.

What about you? What were your expectation-reality surprises?

#localisation #localization #translation

Coffee? Brewed.
Work desk? Clean.
Computer? Booted up.
Mails? Checked.
Mental status? Locked on.

Alright, time for work!

... Aaand I'm not yet given permission to access the current client's translation software.
All machines halt!

#translation #localisation #localization #homeOffice #remoteWork

Yeah here's a "target string is equal" warning because you translated "Robert" as "Robert".

Here's a "missing apostrophe" mega-error! Because you translated "Don't go!" als "Geh nicht!"

Here's FOUR severe warnings!! Why? Because "Ch15" is translated as "Kap. 15", which is ENTIRELY MISSING the code "Ch15", and there's also a random extra number "15" in the translation! Also, "Kap." has no reference in the source!

...

#localisation #localization #translation

translation tool warnings, also known as "the boy who cried wolf"

#translation #localization #localisation

A #Fediverse tech idea I've been considering for a while.

Hashtags can sometimes be annoying, right? Their primary application is finding posts related to a certain topic, including following one. Therefore, if I look for "horses", I want to find everything horse-related.

The following hashtags should therefore lead to the same set of posts:
- #horse
- #horses
- #equines
- #equine
- #horsetodon

Right? But that's not a reality. Some people tag with one of them, with multiple, or with none at all.

Similarly, #Döner, #Doener and perhaps even #Doner should lead to the same set of posts, right? And what about British-American-splits like how #Localization is #Localisation, and perhaps even #l10n as well? And #LGBT, #LGBTQ, #LBGTQ+, #LGBT+, #LGBTQIA and so on and so on also really should be one hashtag.

So what to do?

I propose:
We should introduce a second symbol for something like "fuzzy hashtags". Not the '#' symbol, but another; perhaps '&' or '~'.

That way I could tag my post '~horse', and it could appear on all hashtag feeds concerning the different spellings of horses! Or I could search for such a fuzzy hashtag.

The different variants could be crowdsourced, or overridden by instance mods. You could also opt-out of that system - your posts showing up in fuzzy searches, most likely.

This would also fix languages like German, where you have many inflected forms: #Männer #Mann #Mannes #Manns #Männern #Männers and so on should all lead to the same result.

Behold what I have to do to sign off on this post:
#MarkupLanguages #MarkupLanguage #Markup

I have so much work lately! I'm thriving! Who said #localisation was dead?!

#localization #translation

🔥 we are almost releasing our game! For now, enjoy a little patch with more performance, achievements, visual updates and localisation!
https://steamcommunity.com/games/3628790/announcements/detail/738149224958394816?snr=2___
#profiling #unreal #crash #localisation