Auto-fill with Google translate, for further tweaking

[fruktansvärt]

If you are struggling with ${actplayer} and ${you}, just open 2 windows, find each term, and start translation. It makes the progress way faster.
${player_name} is much easier. Search and copy '${player_name}', then no need to copy the entire text in most cases.

I'm more thinking of phrases like

${subject_fullname} commented on <a href="/${news_subject_type_name}?id=${news_subject_id}#news${news_id}" class="displayNews" data-news-id="${news_id}">this publication</a>

In PARKS, for example, there were quite a few phrases with several variables.

[ufm]

Such cases are relatively rare. It is not frequent enough to adopt auto-copy feature for all available strings.
And it is even worse than Google auto-translate in most cases.

FYI I translated all PARKS strings in Korean by myself, and still didn't copy and paste the whole raw texts that much.
Don't forget you can also copy a part of or a whole translated string.
For example, texts starting by [SITE${siteId}]: ${player_name} visits [PARK${parkId}] ~ are simple.
Copy the front part of a translated string, paste it, and fill other parts in. Way faster than copying the entire raw text and editing it.
(Try Railways of the World: there are plenty of strings but translating it is easier than it looks)

[kytbell]

Has BGA considered implementing translation memory (TM) for the strings? This would eliminate the need to copy/paste as the TM would suggest them.

[KongKing123]

Has BGA considered implementing translation memory (TM) for the strings? This would eliminate the need to copy/paste as the TM would suggest them.

Well this is just a board game website, so I think the cost-benefit on that is quite negative.

[kytbell]

Considering some TM are free and others are EXCEPTIONALLY low cost (think as low as 20 USD a year), not necessarily. Are you with BGA giving this as a definite answer or is this just your opinion, thanks?

[KongKing123]

Just a moderately informed opinion, seeing as we're on a forum here.

"Costs" are not just buying the software, but also (and much more importantly) setting it up, testing it and maintaining it. Not to mention the opportunity costs of investing time into this that could be spent on other, more generally useful projects (do remember that this site has fewer than 5 developers).

Combine that with the limited benefits for the type of translations on this site and significant obstacles: https://en.wikipedia.org/wiki/Translati ... n_memories

I'm not seeing the case here.

[Een]

I'm not seeing the case here.

I didn't know about this translation memory concept, but I agree with KongKing123. I don't see a practical use case for this for BGA. It would be quite a big investment for an uncertain result, that would likely be of the same order or inferior to auto-filling with Google Translate as we can do today (without even considering the difficulty to setup and maintain a TM database in so many languages, and the fact that every game being different in theme and mechanisms makes pretty much for a case where the concept would have almost no bearing by nature).

[kytbell]

I'm not sure of everyone's roles here (new to the boards), but I would ask you to at least learn what it is before you dismiss it.

As an FYI, I owned an international translation company for a decade. I served as the North American rep to the international trade board as well as on the US national board. I also advised the (former US president) Obama administration on translation's impact on policy & business. In other words, I know what I'm talking about.

So, all this said, translation memory is exactly what it sounds like a "memory" of translations BGA volunteers have already done. When any volunteer translates something, the system saves that in a central repository. It saves both the source (the original language) as well as the target (the new language). Turn it on, and when you're translating, it offers these saved translations as suggestions, together with a percentage chance that they have of being correct for the new string. (This is especially important when languages that have agreement with number or gender are paired with ones that don't — or declination. Note this is different from machine translation, which simply does the translation for you. Translation memory allows you to reuse your own work, as well as the work of others on your team. In other words, it keeps you from having to translate the exact same words or phrases over and over and over. That's why it would be helpful here: Other posters on this thread are having to copy and paste code. Just load the code in the TM and the TM will do it for you. It's how every professional website on earth is done.