Localization / Internationalization by the Infinity Community

I’m in. Sent Russian subtitles for the first two videos.

1 Like

done, you can upload the russian translation into transifex.

3 Likes

Nnope. I can send another request. To join the project. xД

1 Like

I’ve uploaded my Strings.csv and it looks like it worked. Here’s the package.
0.7.1.0_RU_REV-02-TX_Mars_Type.rar (44.6 KB)

UPD: thicker font
0.7.1.0_RU_REV-02-TX_Roboto_Condensed.rar (20.1 KB)

3 Likes

Hi guys, I’m new around here (just learned about this game yesterday).
I’m up for some assistance with the closed captions. Currently reviewing EN captions (added a couple of “,” on the 1st video already).

My native language is European Portuguese (will work on this later), but I’m also pretty good with English and around 85% fluent in French from France (not sure about differences with Belgian/Swiss French besides the numbers 70-90) (Work with both EN&FR everyday, though more with English).

After I do a pass on the EN captions, I’ll focus on pt-pt. If there are any friends from Brazil around here, you’re welcome to give a hand with pt-br captions (I guess it’s a similar situation as fr-eu and fr-canada) - Same language, but with some differences in grammar, expressions, orthography and so on. And people love to have proper localization and not only one of the language variations. I’d say pt-br is even more important than pt-pt, because the Brazilian market is bigger and most people in Portugal are fluent in EN, so they default to it when pt-pt is not an option. :wink: hope I can give a positive contribute to make this project shine!

Update: I have now completed an EN pass on all 8 tutorial videos. (just did some minor corrections here and there, mainly punctuation or making some words/expressions keep the same standard/syntax form across the different videos. (For e.g. “keybind”, “key bind”, “key-bind”). Tried to use official EN dictionaries for reference (mostly US based, so I’m not accounting for possible variations of some words/expressions in EN-UK, or EN-Canadian). Did the best I could by trying to follow “,” (comma) usage rules in EN, although this is sometimes tricky and can be complex (I was multitasking with my real work at the same time). :stuck_out_tongue:

Tried to follow rules from:

Next step, will work on the Portuguese European captions, using the time stamps already in the EN version (Kudos to the original worker on this one :D)

After that, if there’s no native French speaker around, I can try working on the French (France) captions (then Flavien can just quickly check it and correct possible errors) :wink:

3 Likes

Strange, I did not get any notifications and looking at it, my original contribution still stands. Only with another Google Account do I see the changes. So I guess no matter the amount of contributions, they won’t show up on the video until someone like @INovaeHutchings accepts them.

Don’t, I:B’s development time will be long. There is no rush. There was at launch, but not now.


I was right.

 INovaeFlavien: didn't have time for that
 INovaeFlavien: but it'll come before release
 INovaeFlavien: I just want to do it in one go
 - I:B Official Discord

I-Novae have said that they may update the tutorial videos. How much of em is up to @INovaeHutchings. Hopefully the transcripts will be saved.

Part of it goes to the Google’s auto-transcriber bot.

@Pendrokar Thanks for the feedback! :slight_smile:
I think someone at I-Novae studios, needs to approve this translations, for them to become available on Youtube. If you can reach them, let them know we are submitting them.

I have now completed and submitted, proper European Portuguese translations for the 1st video in the tutorial series.
(This takes longer than I expected to do properly) :wink:

I’ll keep working on the pt-pt translation of the series and then can actually take a look at doing a pt-br version. It might actually take less time for pt-br, since almost all proofing tools on the internet target pt-br, so I just need to auto translate and then manually make small adjustments (although almost everything is accepted in both languages, commonly used words and expressions differ a lot in each country).

After that is done, either I’ll get going with French, or jump directly into the actual game translation (that’ll take a while to complete). Might even start with pt-br there, since it might be more useful (market wise).

Again, if there’s any hidden Brazilians interested in helping out around here, it would be highly appreciated!

1 Like

I can take a look at the French part, and maybe for the tutorial vids too.

3 Likes

I’m not sure I’d recommend translating the tutorial videos. I mean, if you have time to lose, why not. But keep in mind that they’re already partially obsolete ( new HUD ), Dan has to record new ones when he has time. Even the new ones are going to get obsolete again in a few months.

The in-game text translation however is very useful, all languages are welcome. By order of importance ( considering our sales so far ) and excluding the existing ones ( English, German, Russian and Chinese ):

  • French
  • Japanese
  • Dutch
  • Swedish
  • Italian
  • Spanish
  • Korean

Other languages can be done too, but in terms of sales so far, they’re not as important.

Also, please keep in mind that the game’s still in development, so it’s not just a matter of doing the translation once and forgetting about it later. You have to be serious about updating it every few patches at least, otherwise sentences not translated will fall back to english.

3 Likes

Salut Flavien, merci de ton avis ! (Hi Flavien, thanks for the heads up!)
Then I’ll just finish translating the 6 remaining videos of the current tutorial series to pt-pt (for completion sake) and get started with the game translation. :wink:

You made a very good point (this is not a “fire and forget” thing). In light of that, I’ll focus mainly on pt-pt and/or pt-br for now (can give a hand in FR if needed, but more like a “backup”).

I don’t want to overdo it, by taking too much stuff on my plate and then end up disappointing people on the long run. (Work, family, kids - the usual drill :stuck_out_tongue:). I can comfortably translate/maintain one Portuguese variant and after completing it, it’ll be much faster/easier to complete the other (some things stay the same, while others are expressed in a completely different way (pt-pt/pt-br)). :smiley:

Cheers and lets do this!

Allright, that sounds good, thank you and good luck. Also, when you update future strings due to patches, make sure to use some kind of “diff” program to show the differences between the old and new file, it helps a lot.

2 Likes

Initial translation:


Some strings are not available for translation as can be seen in some screenshots. Some buttons are too small to fit a meaningful translation (eject and respawn, apply and save).
fr%20(1) fr%20(11) fr%20(13) fr%20(14) fr%20(15)

7 Likes

Du beau boulot, merci ! :wink:

I’ll see what I can do about widening some buttons / text areas. However, in general, you should try to find an equivalent translation with shorter / lesser words. I know that’s not always easy, but the layout has to stay the same for all languages. So try to see if you can find some better wording, and for the ones that really don’t fit, as long as it’s just a few more pixels, I can definitely enlarge the UI.

4 Likes

The same text fitting issues are present in the german translation aswell. I lowered the font size to 0.9 which helped a lot and also found some alternative translations for words which were way too long.
The only thing I can’t fit any way I try are:
“Apply and Save” it’s now only “save”.
“Eject and Respwan” it’s only “Eject”.
I also had to abbreviate the “speed” in “Match speed” because “Geschwindigkeit angleichen” is double the length.
One other thing I also did was to include the aviation related terms for control directions in the controls settings. Because “yaw” is correctly translated as “Gieren” in german (a word that probably is unknown to 90% of germans) I also added the word “(Rudder)” <-in german. And also the other terms in brackets (elevator, ailerons etc.).
It would help if we had the option to add a line break in the translation file so the game knows when to do that.
The translation for Match Speed for example would easily fit as two lines into the intended space on the radial menu. Also for Eject and Respawn if it then would extend the button height.

5 Likes

I’ll try that.

I’d rather avoid these workarounds because of the loss of precision.

Have you tried [br]? I don’t think it would be recognized though.

Edit: I noticed that the game reloads the translation files during play (I don’t know what triggers this), it’s quite handy for fine tuning.

1 Like

Yeah no that doesnt work unfortunately, haven’t found a command for that in the original file.

Yep it’s no ideal.

Hey there! Small correction: It’s “European Portuguese” (pt-pt), “Castilian” is linked to Spain, not Portugal :wink:

Tremendous work on that google docs file! It helps a lot while updating the game translation!

Just having some trouble with the “Ratio” (string size in comparison with the EN original):

I’ll test how it looks in game and if it gets misaligned, I’ll try to use accepted and commonly used abbreviations in pt-pt.

After I finish these, I can do pt-br, but would be cool to have someone from Brazil doing a pass to validate. (I’ll use official Brazilian dictionaries and proofing tools to assist, so I’ll try to make it as good and professional as I can).

P.S. - Had a lot of fun playing the game yesterday! Can’t wait to Jump in again (Although I felt a bit lost in the beginning) :wink:

2 Likes

Nice, thank you :wink: Just curious, what’s the diff between pt-br and pt-pt ? Unfortunately my third language was german so I don’t speak a word of portuguese :slight_smile:

1 Like

You knew this meme was coming:


Yet you were able to strike back:


It seems OK. Had checked the Russian average ratio and it stands at 1.36.

Two things about the Doc. Use the Tomorrow Medium font, Fjalla is the old one. C6 is an updated ratio formula, extend it to C7 & C(n), then it will get rounded to 2 digits.

5 Likes

European Portuguese (pt-pt) and Brazilian Portuguese (pt-br) have the same base (Portuguese), but evolved in different ways over the centuries. (Portuguese people tend to prefer English, if there’s only pt-br available, although we understand almost 100% of pt-br. This is not the same for Brazilians who have more trouble understanding European Portuguese - mainly spoken pt-pt).

Brazilian Portuguese, kept some rules and similarities to 16th-18th century Portuguese and evolved in a different direction.

This differences are always really hard to explain to foreigners (non portuguese speakers). My wife is Polish and when we met, she used to say European Portuguese sounded like a weird Russian dialect and that PT-BR was easier to understand and learn. (they kind of sing the words and separate each word more clearly, than we do).

I’d say a good comparison would be French from France vs French from Canada (Français Québécois). My brain melted when I first tried to figure out what “Clavardage” meant, or expressions like “Piquer une fouille” - (Quoi ?) lol.

Here’s some videos regarding the differences of pt-pt / pt-br:

Small precision regarding the use of “1st / 3rd person” (Tu / Você). In Portugal besides the example in the video, when in a context of a company addressing it’s customers, it highly depends on target demographics and product. So in a game like Infinity:Battlescape, 1st person (tu) is the norm, while “Life insurance” would use the 3rd person (você) and be much more formal. Again, similar to FR.