-
-
Notifications
You must be signed in to change notification settings - Fork 489
Let CSS do the uppercase transformation. #1521
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -61,10 +61,10 @@ export class CloudSketchbookTreeWidget extends SketchbookTreeWidget { | |
</div> | ||
</div> | ||
<button | ||
className="theia-button" | ||
className="theia-button uppercase" | ||
onClick={() => shell.openExternal('https://create.arduino.cc/editor')} | ||
> | ||
{nls.localize('cloud/GoToCloud', 'GO TO CLOUD')} | ||
{nls.localize('arduino/cloud/goToCloud', 'Go to Cloud')} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Changing the localization key from There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I have also thought about the impact of prior changes to the keys. It was previously discussed here: I think there is an impact, but it can't quite be described as "lose them" because the translations are still stored in the "translation memory" on Transifex. So they don't need to be translated over again from English, but I don't think this happens automatically, meaning there is still an impact. I believe the translators will still need to select the strings with changed keys and then accept the auto-completed translation offered by Transifex. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So it seems to me that we should avoid frivolous key changes, but also shouldn't feel locked into the existing key names in cases where there is a significant benefit to restructuring them. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this is the perfect time to make such changes. I do not want to maintain a key that does make sense in the next two decades. |
||
</button> | ||
<div className="center item"></div> | ||
</div> | ||
|