You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Every time we translate our apps, we have the same source strings in our iOS and Android apps, except one detail: In our Android app we use %s and in our iOS app we use %@.
Describe the solution you'd like
The thing would be about comparing both source string, and if the only changes is the %s/%@, take the same translation but with the correct symbol.
Describe alternatives you've considered
Currently, we manually copy translations and replace %s to %@ (or %@ to %s depending on what was translated first)
Additional context
We have an automatic propagation for same strings, please add support for this little details that will change everything.
Example:
We translate this in our iOS app component:
Hello %@ -> Bonjour %@
Automatic propagation would do the same in our Android app component
Hello %s -> Bonjour %s
(which is already existing for strings without %s/%@ changes)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Every time we translate our apps, we have the same source strings in our iOS and Android apps, except one detail: In our Android app we use %s and in our iOS app we use %@.
Describe the solution you'd like
The thing would be about comparing both source string, and if the only changes is the %s/%@, take the same translation but with the correct symbol.
Describe alternatives you've considered
Currently, we manually copy translations and replace %s to %@ (or %@ to %s depending on what was translated first)
Additional context
We have an automatic propagation for same strings, please add support for this little details that will change everything.
Example:
We translate this in our iOS app component:
Automatic propagation would do the same in our Android app component
(which is already existing for strings without %s/%@ changes)
The text was updated successfully, but these errors were encountered: