Non-English user feedback

[Torsten Zabka]

Hi all, could you help us identify areas which aren’t localized but you feel should be, or situations where the experience for non-English speaking users is generally poor/difficult?

https://docs.google.com/spreadsheets/d/1UUpUhgtv8wh2HlB9YOPZSV6Ft9-AMDJFsZgOqQ1CZtw

[Enzo]

I take advantage of the new CS:GO update to bump this thread (several strings are still not added :( ) and to add two new strings not uploaded on STS: http://i.imgur.com/jOulRkT.png - Thanks!

[Mathisca]

http://puu.sh/ncVOU.png -> "Status Incomplete" is not localized (on STS), and the actual french translation means nothing

[Berna]

Początkowo opublikowane przez Enzo:

I take advantage of the new CS:GO update to bump this thread (several strings are still not added :( ) and to add two new strings not uploaded on STS: http://i.imgur.com/jOulRkT.png - Thanks!

Wait, I just checked csgo_english and it's not "not uploaded on STS", but "those strings aren't tokenized" (aka the text themselves, and not a #token, are in the UI resource files). Did I miss them in the file?

=============================================

Also, about CS: the new formatting for quests isn't very good, mostly because of quests related to the "Score" (quest_commandverb_default) and "Execute" (quest_commandverb_execute) verbs. The biggest problem is that the string for %action% is used also in the details section (quest_totalgoal_points_desc), which makes us choose between either making the description weird or the details weird.

I remember in the Operation Bloodhound we kind of skirted around this since there were quest-specific strings, like Quest_Kills_Map_desc — we just removed the %actions% variable from them and replaced them with a more adequate translation, so the action variable itself would only appear in the details.

The suggestion I'd make is to keep the current quest_action strings only for quest_totalgoal_points_desc and add specific strings for the descriptions, such as "Execute bomb plants or defusals", which would help in making the localizations more natural. Then the quest_default_%_items_desc would have %verbcommand% and %actions% replaced with only %actions% or whatever the variable is called. :p

Also, since I talked about quest strings, quest_default_%_items_desc (so, quest_default_0_items_desc to quest_default_4_items_desc) have a space surround both sides of %target%, even though it seems — at least in my Operation Journal — it's not used, which makes a double space happen before the %action% string.

EDIT: As Mr. Fusion, from Hungarian, pointed out about quest_commandverb_default:

Apparently, this string is also used, erroneously, as a table header instead of SFUI_LeaderboardHeading_AverageScore, which is a problem since this "score" is a verb, while that other score needs to be a noun, and the tho are not interchangeable in some languages.

[uzikus]

I complained about this CS:GO quest variable hell during the last Operation and it happened again, but it's even worse now. When will Valve devs learn that not all languages work the same? Why can't we just get full strings (excluding integers, map names and game modes)? This is atrocious.

[KillahInstinct]

Początkowo opublikowane przez uzikus:

I complained about this CS:GO quest variable hell during the last Operation and it happened again, but it's even worse now. When will Valve devs learn that not all languages work the same? Why can't we just get full strings (excluding integers, map names and game modes)? This is atrocious.

I didn't see that yet, than again I didn't translate it yet. Do you've some examples? Just curious what to look out for and probably helps people to teach them what they did wrong.

[uzikus]

Początkowo opublikowane przez KillahInstinct:

I didn't see that yet, than again I didn't translate it yet. Do you've some examples? Just curious what to look out for and probably helps people to teach them what they did wrong.

Sure, here's an example generic string with 8 variables:

"%commandverb% %target% %actions% with any <i>%item_quality%</i> <b>%item1%</b> in <b>%gamemode%: %location%</b> matches."

Then there's variables such as "Deal" (command verb), "rifle" (item type), "hostage rescues or rescuers killed" (action), "someone else's" (weapon possession). I can't bring up any solid in-game example, because I don't own the Operation Pass, but even without it anyone can see that it's not going to work well in languages that contain declension as a core element.

[Doc]

It might be possible to come up with a solution if you play around with the variables a bit.

In our case, I decided to simply replace the verb variable with "Objective:" and switch around the other variables.

For example, let's take a look at the following string:

Początkowo opublikowane przez quest_default_1_items_desc:

%commandverb% %target% %actions% with any %item_quality% %item1% in %gamemode%: %location% matches.

Which is used in the mission:

Początkowo opublikowane przez YOINK! mission:

Score kills with any enemy's weapon in Casual:Op Wildfire Group matches.

I translated the generic string as something like:

Początkowo opublikowane przez rough solution variables:

Objective: %actions% %target% with a %item1% <i>%item_quality% in gamemode %gamemode%: %location%.

which will in turn lead to:

Początkowo opublikowane przez rough solution:

Objective: Kills with a weapon (The weapon must belong to an enemy) in game mode Casual:Op Wildfire Group

Something like this should work for all missions. Of course, it's also important to translate other separate variable strings in a specific way with brackets (In this case, the separate string "enemy's" was translated as "(The weapon must belong to an enemy)".

As far as I know, the variable %target% is only used for the combination "chicken kills" (%target% %actions%) so you'll probably want to use brackets for the chicken string too.


I hope that was helpful and not complicated at all. I'll be honest: I don't really think the dev team will be bothered to make new strings for each mission... so I'd say it's worth a try in your case.

[Enzo]

Matt Wood recently set up a feedback e-mail where we can contact the CS:GO Team: [e-mail] - maybe we could try to contact the team and let them know about this issue?

[Berna]

Początkowo opublikowane przez Enzo:

Matt Wood recently set up a feedback e-mail where we can contact the CS:GO Team: [e-mail] - maybe we could try to contact the team and let them know about this issue?

I don't think there's something that could be accomplished by emailing that that couldn't be by posting here and telling T about it. Only my opinion, of course.

[uzikus]

Początkowo opublikowane przez Doc:

*Lots of text*

Thanks man, but it's not going to do much in most cases. I can't even get this part right of your example without making it sound weird:

Początkowo opublikowane przez rough solution:

Kills with a weapon

[Berna]

What about the suggestion I made (that everyone seemingly ignored)?

[uzikus]

Początkowo opublikowane przez Berna:

What about the suggestion I made (that everyone seemingly ignored)?

I already e-mailed my local admin, we'll see how it goes.

[Enzo]

Początkowo opublikowane przez Berna:

What about the suggestion I made (that everyone seemingly ignored)?

Yup, I think that's the best thing we can have. If the worst comes to the worst, I prefer to localize every single objective so players could profit of a good localization instead of having variables everywhere.

[uzikus]

Początkowo opublikowane przez Enzo:

I prefer to localize every single objective so players could profit of a good localization instead of having variables everywhere.

This is basically what I'm asking for. It's better to have tens of strings that look similar. We could easily utilize the auto-replacement tool.

[MeGAct]

Poor experience for Spanish users (now that you "hired" a professional translator)
https://dl.dropboxusercontent.com/u/4771059/sts/sts/20160229011206.jpg

"Ahora" means "Now" not "save" (even Google translate knows that)

Completa su colección: "su" is wrong there, it must be "tu", if you want to maintain "su" it should be "Complete su colección" but is too formal.

I'm absolutely certain that there will be more mistakes like that.

Some more:
https://dl.dropboxusercontent.com/u/4771059/sts/sts/20160229050919.jpg
Notes over the capture.

https://dl.dropboxusercontent.com/u/4771059/sts/sts/20160229051407.jpg
"En el juego de base", really? It should be, "En el juego base" or "En el juego básico" (not recommended).