Dolphin Translation - moving to Transifex

[JosJuice]

(11-23-2020, 07:10 AM)Mewster Wrote: Ohh nice feature, didn't know this one. Thanks.

Well, it is new Maybe it will show up in the next progress report.

[Mewster]

I don't fully know how transifex works, anyway a lot of strings have been update with only their tags having changed (%s -> {0}) (pic attached).

Is it normal?

[JosJuice]

(12-05-2020, 05:57 AM)Mewster Wrote: I don't fully know how transifex works, anyway a lot of strings have been update with only their tags having changed (%s -> {0}) (pic attached).

Is it normal?

This is because Dolphin is currently migrating to a new string formatting library which uses different syntax. An advantage for translators with the new system is that the arguments can be reordered however you want. Apologies for the large number of changed strings, but it's necessary for making the switch.

[Mewster]

Don't worry.

Is the string "Action Replay: Normal Code 0: Invalid Subtype {0:08x} ({1})" correct? Shouldn't it be "{0}" ?

[JosJuice]

(12-05-2020, 06:22 PM)Mewster Wrote: Don't worry.

Is the string "Action Replay: Normal Code 0: Invalid Subtype {0:08x} ({1})" correct? Shouldn't it be "{0}" ?

It's correct. ":" tells the formatting system to use additional specifiers, "08" is a specifier that means "pad to 8 digits by adding leading zeroes", and "x" is a specifier that means "print in hexadecimal". It is possible to use {0} instead of {0:08x} here, but if you do that the number will be printed in decimal with no leading zeroes, which is less user-friendly since AR codes normally are written in hexadecimal.

[Mewster]

(12-05-2020, 07:58 PM)JosJuice Wrote: It's correct. ":" tells the formatting system to use additional specifiers, "08" is a specifier that means "pad to 8 digits by adding leading zeroes", and "x" is a specifier that means "print in hexadecimal". It is possible to use {0} instead of {0:08x} here, but if you do that the number will be printed in decimal with no leading zeroes, which is less user-friendly since AR codes normally are written in hexadecimal.

uh, no, I was referring to the "Normal Code 0" part, since I saw later that there is a "Normal Code {1}" string too

[JosJuice]

Ah, you mean it should say "Normal Code {0}" instead of "Normal Code 0"? It seems like that was intentional on the part of whoever wrote the code, though I can't say I understand Action Replay stuff well enough to say why it's like this.

[Mewster]

(12-06-2020, 07:31 AM)JosJuice Wrote: Ah, you mean it should say "Normal Code {0}" instead of "Normal Code 0"? It seems like that was intentional on the part of whoever wrote the code, though I can't say I understand Action Replay stuff well enough to say why it's like this.

Yes, that one.
Ok then, I'll leave it as is