Untranslatable strings

Untranslatable strings

Postby Wuzzy » 21 Apr 2014, 12:00

This thread is for collecting strings in Stunt Rally which are currently untranslatable.

Struck through text are strings which won’t be made translatable.

  • The README - NOPE, OMG
  • Track descriptions - NOPE
  • Most of the tweak menu in the editor (unlikely) - NOPE
  • Editor warnings - Nope
  • Most names in general - Nope
  • -
  • Camera names (shown on Hud at the bottom right) - No
  • Decimal point (some languages don’t use a point, eg. “1,2” instead of “1.2”) - No
  • [done] Editor mode (The small text on the bottom left: “Gui”, “Cam”, “Edit”)
  • -
  • [done] These editor info window captions: “Terrain Deform”, “Terrain Height”, “Terrain Filter”
  • [done] Texture settings: “Bilinear”, “Trilinear”, “Anisotropic”
  • [done] Triplanar setting: “max 2” - it is already, max is used elsewhere too
  • [done] Loading text “Initializing ...”
  • -
  • [done] Contents of editor tool windows: Car start, Water, Objects ..
  • [done] Car stats value units (e.g.: “123 Nm at 2345 rpm”)
  • These slider labels in the “boost” tab of the “game” tab in the quick game menu: “max”, “min.”, “per km”, “add per sec”.
  • Camera settings: “FOV max” and “FOV smooth” (these strings are actually built from 2 strings but should be 1 string each. Doing otherwise assumes the translation would always contain a space, which is not the case)
  • Shortcut key texts (often next to checkboxes). There are languages which don’t use “ctrl”, “shift” or “alt”.

Nothing of this is too pressing, but it would be nice if it would be done at some point in the future.
I like bitcoins: 17fsUywHxeMHKG41UFfu34F1rAxZcrVoqH :-)
User avatar
Wuzzy
 
Posts: 802
Joined: 28 May 2012, 23:13

Re: Untranslatable strings

Postby CryHam » 05 May 2014, 16:13

I edited your post and put Nope's first. Will never be translated.

As for others, very likely Nope to:

  • Camera names - too many, ofc could be much longer after transl. and would go outside screen etc.
  • Editor mode - that's the beauty of it, 3-4 letters, I can't imagine that staying so after translating, and nope, I don't want to make the area 2x bigger, it's just a mode, not a crucial message to read is now an image
  • decimal point - no idea how and really no difference
  • shortcut keys - I agree but, would mean translating again like half of the editor gui (which is already translated) or some weird editing on launchpad to get them back
Rest is todo, I agree.
User avatar
CryHam
SR Moderator
 
Posts: 697
Joined: 25 Nov 2012, 08:40

Re: Untranslatable strings

Postby CryHam » 10 May 2014, 15:43

I did a search in all files (cpp,h,layout) and filtered results, here is the file with all texts without being translated.
(I marked with -- before file names that I don't care, e.g. tweaking, graphs, etc).
Attachments
aaa.c
all untranslatables
(17.07 KiB) Downloaded 508 times
User avatar
CryHam
SR Moderator
 
Posts: 697
Joined: 25 Nov 2012, 08:40

Re: Untranslatable strings

Postby dimproject » 11 May 2014, 20:15

{l Code}: {l Select All Code}
fo << "Mass\n" << fToStr(pCar->GetMass(),0,4) << " kg\n";
fo << "Max Torque\n" << fToStr(maxTrq*m,0,3) << " Nm at " << fToStr(rpmMaxTq ,0,4) << " rpm\n";
fo << "Max Power\n"  << fToStr(maxPwr*m,0,3) << " bhp at " << fToStr(rpmMaxPwr,0,4) << " rpm\n";
fo << "Top Speed\n" << fToStr(maxVel,0,3) << " kmh at " << fToStr(tiMaxVel,1,4) << " s\n";
fo << "Time 0 to 100 kmh\n" << fToStr(t0to100,1,4) << " s\n";
fo << "Time 0 to 160 kmh\n" << fToStr(t0to160,1,4) << " s\n";
fo << "Time 0 to 200 kmh\n" << fToStr(t0to200,1,4) << " s\n";
fo << "Stop time 100 to 0 kmh\n" << fToStr(tMaxTo0-tMaxTo100,1,4) << " s\n";

How about " kg",
" Nm at ",
" rpm",
" bhp at ",
" kmh at ",
" s",
"kmh",
"mph"?

"Time 0 to 100 kmh"? (showing "Time to 100 kmh")
"Stop time 100 to 0 kmh"? (showing "Stop time from 100 kmh")

"kmh" and "mph".
For show.zip
(687.71 KiB) Downloaded 498 times
dimproject
 
Posts: 212
Joined: 18 Jul 2013, 13:51

Re: Untranslatable strings

Postby Wuzzy » 12 May 2014, 12:55

Oh, dimproject. That looks like a bug and it not directly related to translation.

Besides, how about “km/h” instead of “kmh” or the even more silly “kph”?
I like bitcoins: 17fsUywHxeMHKG41UFfu34F1rAxZcrVoqH :-)
User avatar
Wuzzy
 
Posts: 802
Joined: 28 May 2012, 23:13

Re: Untranslatable strings

Postby CryHam » 04 Jul 2014, 09:11

Hmm km/h would be proper unit yeah, but it's 1 char more. fixed
Someday all units and all key shorcuts (shift,ctrl,alt) should be dealt with, but not a priority for me.

I was thinking of changing the editor mode ("Cam","Edit","Gui") to an image, what do you think about it ?
Using the icons we have: that camera from replay, cog/gear from options in main menu, and idk a small gui window.
All colored to blue, green, yellow, since it's easier to catch that by color not image or even text.
Or maybe even with a text next to image ? (Camera, Edit, Gui) Or even gui setting to choose any.
User avatar
CryHam
SR Moderator
 
Posts: 697
Joined: 25 Nov 2012, 08:40

Re: Untranslatable strings

Postby CryHam » 13 Jul 2014, 15:25

OK all units are now translatable.
User avatar
CryHam
SR Moderator
 
Posts: 697
Joined: 25 Nov 2012, 08:40

Re: Untranslatable strings

Postby CryHam » 21 Jul 2014, 16:47

So now ed has mode as image (no text Cam,Edit,Gui).
Also status text is translatable.

http://imgur.com/iQS8tlf
http://imgur.com/9AfYQWV
http://imgur.com/vW1zlD9
User avatar
CryHam
SR Moderator
 
Posts: 697
Joined: 25 Nov 2012, 08:40

Who is online

Users browsing this forum: No registered users and 1 guest