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

Provide a script to do GRD string upgrades for Chromium rebasing #365

Merged
merged 1 commit into from
Jun 15, 2018

Conversation

bbondy
Copy link
Member

@bbondy bbondy commented Jun 15, 2018

Fix #364

This replaces the following steps in the Brave wiki with a single command npm run chromium_rebase_l10n:


Chromium rebase wiki steps getting replaced:

cd brave
cp ../chrome/app/chromium_strings.grd app/brave_strings.grd

Open up app/brave_strings.grd and replace settings_chromium_strings.grdp with settings_brave_strings.grdp
Also apply these replacements:

%s/Google Chrome/Brave/g
%s/Chromium/Brave/g
%s/Chrome/Brave/g
%s/Google/Brave/g
%s/The Brave Authors. All rights reserved./Brave Software Inc. All rights reserved./g
%s/The Brave Authors/Brave Software Inc./g

cp ../chrome/app/settings_chromium_strings.grdp app/settings_brave_strings.grdp
Open up the file and apply these replacements:

%s/Google Chrome/Brave/g
%s/Chromium/Brave/g
%s/Chrome/Brave/g
%s/Google/Brave/g

cp ../components/components_chromium_strings.grd ./app/components_brave_strings.grd
Open up the file and apply these replacements:

%s/Google Chrome/Brave/g
%s/Chromium/Brave/g
%s/Chrome/Brave/g
%s/Google/Brave/g

Submitter Checklist:

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Ran git rebase -i to squash commits (if needed).
  • Tagged reviewers and labelled the pull request as needed.
  • Request a security/privacy review as needed.

Test Plan:

Reviewer Checklist:

  • New files have MPL-2.0 license header.
  • Request a security/privacy review as needed.
  • Adequate test coverage exists to prevent regressions

Fix #364

This replaces the following steps in the Brave wiki with a single command `npm run chromium_rebase_l10n`:

---

Chromium rebase wiki steps getting replaced:

```
cd brave
cp ../chrome/app/chromium_strings.grd app/brave_strings.grd
```

Open up `app/brave_strings.grd` and replace `settings_chromium_strings.grdp` with `settings_brave_strings.grdp`
Also apply these replacements:

```
%s/Google Chrome/Brave/g
%s/Chromium/Brave/g
%s/Chrome/Brave/g
%s/Google/Brave/g
%s/The Brave Authors. All rights reserved./Brave Software Inc. All rights reserved./g
%s/The Brave Authors/Brave Software Inc./g
```

`cp ../chrome/app/settings_chromium_strings.grdp app/settings_brave_strings.grdp`
Open up the file and apply these replacements:

```
%s/Google Chrome/Brave/g
%s/Chromium/Brave/g
%s/Chrome/Brave/g
%s/Google/Brave/g
```

`cp ../components/components_chromium_strings.grd ./app/components_brave_strings.grd`
Open up the file and apply these replacements:

```
%s/Google Chrome/Brave/g
%s/Chromium/Brave/g
%s/Chrome/Brave/g
%s/Google/Brave/g
```
@bbondy bbondy added this to the Releasable builds milestone Jun 15, 2018
@bbondy bbondy self-assigned this Jun 15, 2018
@bbondy bbondy requested a review from emerick June 15, 2018 20:10
Copy link
Contributor

@emerick emerick left a comment

Choose a reason for hiding this comment

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

LGTM

@bbondy bbondy merged commit e366b5d into master Jun 15, 2018
@cezaraugusto cezaraugusto deleted the grd-strings branch July 9, 2018 15:24
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.

2 participants