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.

Sign up for GitHub

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

Jump to bottom

[i18n] Regenerate original.json strings #3807

Merged
merged 2 commits into from
Oct 10, 2022
Merged

[i18n] Regenerate original.json strings #3807

merged 2 commits into from
Oct 10, 2022

Conversation

bgptr
Copy link
Collaborator

@bgptr bgptr commented Sep 8, 2022

Closes #3806

@bgptr bgptr force-pushed the regenerate-original.json-strings branch from 062a67e to 7480f9d Compare September 8, 2022 06:53
@xaur
Copy link
Contributor

xaur commented Sep 9, 2022

Thanks for picking it up so soon! When this is merged we can ping more translators to update their stuff based on new English strings.

Can you please re-add the meta block to original.json? It is used by translator.html

"meta": {
    "version": "v1.7.5-pre"
  }

I don't know the exact meaning of version yet but that should be good enough for a contrast with v1.7.0 that is in the previous_original.json.

@xaur xaur mentioned this pull request Sep 30, 2022
Closed
@alexlyp alexlyp merged commit b6dd4b9 into decred:master Oct 10, 2022
alexlyp pushed a commit that referenced this pull request Oct 12, 2022
@bgptr @alexlyp
[i18n] Regenerate original.json strings (#3807)
72ade34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alexlyp alexlyp alexlyp approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[i18n] Regenerate original.json strings
3 participants
@bgptr @xaur @alexlyp