This repository has been archived by the owner on Jun 17, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 45
Add translations for info icon in market based price input field #38
Merged
ManfredKarrer
merged 1 commit into
bisq-network:master
from
ripcurlx:add-info-tooltips-for-offer-table
Mar 28, 2018
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ripcurlx, these translations look OK from a native speaker's point of view, but I'm not sure why there is a "sell at / buy at" vs "get / pay" difference. Why not do the following instead?
I am assuming that the
{0}
placeholder will be replaced with a percent value, btw. e.g. "You will sell at 2% less than the current market price..."There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, the placeholder is replaced by the absolute percentage distance.
Regarding buy/sell vs. get/pay: I wasn't sure if it might be easier for the user to understand if I use get/pay in some cases instead of buy/sell e.g.
instead of
But it's just a personal feeling (and I'm no native speaker)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd favor being consistent. I don't think this is really about native-speaker nuance here, just the general principle that it's better to say the same thing one way versus two ways.
I might make the same point about using the phrase "above the current market price" vs. "more than the current market price", but I don't feel super strongly about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm also a big fan of consistency, but based on some comments on different issues, I have the feeling that it always takes a lot of thinking to understand if above/below in combination with buy/sell is good or bad for me. I think I should start to do more user testing soon to get a better feeling on the biggest pain points within the upcoming release.