Closed laralem closed 2 years ago
Thank you very much, I'll have a look at it. As for the "non-translatable" strings:
var_speed
This indeed doesn't need to be translated in my opinion, as it resolves e.g. to 4x
.fast_forward
Here the issue is mainly the limited space because the button is so small. But I like your suggestion about with using >
.dps
This should be the abbreviation of the unit for damage per second. The full text could also lead to some space issues.* `dps` This should be the abbreviation of the unit for damage per second. The full text could also lead to some space issues.
Anyway may be that could be translated (every translator should always think in interface limited space), and although in Portuguese the abbreviation is the same (Dano Por Segundo = dps), "dps" it's not common (even in games) in Portuguese so no one will understand it's meaning. I've just figure out while translating it. Of course the same will happen in other languages.
I've translated comparing another existing string in same screen (Dano causado) already translated in the actual version installed in my phone with the new translation (Dano por seg.) and it seems it fits (of course it depends on font but they are a bit similar like in the next example): Dano causado Dano por seg.
So it seems it fits. But can be translated even shorter: Dano causado Dano p/seg.
probabily / shuld have a escape character like \ / right? So the translation is Dano p\/seg
Picked up the original in English and translated it since the existing one was missing many strings.
Some strings have
translatable="false”
can we translate this? Except in one of them, I've translated the other two.I would suggest to change the original string
<string name="fast_forward" translatable="false”>FF</string>
fromFF
to>
so it can be understandable in every language and there is no need to translate it.