Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it easier to translate trade roles #4969

Merged

Conversation

ripcurlx
Copy link
Contributor

@ripcurlx ripcurlx commented Dec 18, 2020

As the German translation was quite embarrassing I think it might be similar in other languages (see Angebotstyp).
Before
Bildschirmfoto 2020-12-18 um 16 24 23
After
Bildschirmfoto 2020-12-18 um 17 08 35

I changed the source to make it easier to translate (at least I hope so)

Copy link
Member

@sqrrm sqrrm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@sqrrm sqrrm merged commit b04a56e into bisq-network:master Dec 18, 2020
@Jakub-CZ
Copy link
Contributor

I agree that some strings are impossible to translate in a way so that they would read in a natural way, or be grammatically correct at least.

Going forward, I'd suggest to steer away from composing non-trivial strings (sentences or longer statements) from shorter substrings like this.

Alternatively, these composite strings shouldn't rely on shared tokens (e.g. shared.selling) that may be used in all kinds of grammatical forms and contexts. For example: had there been something like formatter.youAreAsMaker.selling=selling used only in this context and nowhere else, this PR could've been avoided, as the translators would've had much more freedom to translate the various combinations in any way they see fit.

From what I saw when reviewing the Czech translation, I think it would be perfectly manageable to have individual strings for each combination of buying/selling etc. Even translators would have an easier time as they wouldn't have to be thinking about how to rephrase the whole string just because they must use "buying" instead of "buys", "buy", "purchase", or whatever else would fit in better in that language and context.

Example:
instead of
formatter.youAreAsMaker=You are: {1} {0} (maker) / Taker is: {3} {2}
there are really only two options:
formatter.youAreBuyerAsMaker=You are: {0} buyer (maker) / Taker is: {1} seller
formatter.youAreSellerAsMaker=You are: {0} seller (maker) / Taker is: {1} buyer

@ripcurlx
Copy link
Contributor Author

ripcurlx commented Dec 21, 2020

Yes, I think so too. As a developer you just intuitively try to generalize stuff if it looks like close repetition. But in the case of translations it makes quite harder instead.

@ripcurlx ripcurlx deleted the improve-translations-in-trade-details branch July 16, 2021 07:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants