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

Update en-GB.json #53

Merged
merged 1 commit into from
Jul 24, 2023
Merged

Update en-GB.json #53

merged 1 commit into from
Jul 24, 2023

Conversation

purcell-lab
Copy link
Contributor

The en-GB.json provided appears to be written in American English. The differences between American English (en-US) and British English (en-GB) often involve spelling, terminology, and occasionally punctuation, but not so much in syntax or grammar. In the case of the provided JSON file, most of the text seems to be written in a neutral way that could apply to both American and British English.

However, there are a few phrases that could be more culturally aligned to British English. This PR is the slightly adjusted version with a few cultural changes.

The changes are minimal and mainly involve using a more British English style of phrasing:

In the "description" field, "allows" has been changed to "lets", which might be slightly more common in British English.

In the "instruction" field, "primary" has been used instead of "main", which is a common alternative in British English. "Color" has been changed to "colour" in the "chargerImage" and "theme" fields, reflecting the British English spelling. In the "instruction" field, "attempt" has been used instead of "try", and "goes wrong" instead of "fails", to align more with British English phrasing. Remember, these changes are very subtle and may not even be necessary. The original text was already in a very clear and neutral form of English that would be understood by speakers of both American and British English.

The rest of the JSON file could remain the same, as it is not specific to any particular dialect of English. It is important to note that most of the text here is quite technical and specific to the application itself (like error messages, status updates, etc.), which would generally be the same across different English dialects.

The en-GB.json provided appears to be written in American English. The differences between American English (en-US) and British English (en-GB) often involve spelling, terminology, and occasionally punctuation, but not so much in syntax or grammar. In the case of the provided JSON file, most of the text seems to be written in a neutral way that could apply to both American and British English.

However, there are a few phrases that could be more culturally aligned to British English. This PR is the slightly adjusted version with a few cultural changes.

The changes are minimal and mainly involve using a more British English style of phrasing:

In the "description" field, "allows" has been changed to "lets", which might be slightly more common in British English.

In the "instruction" field, "primary" has been used instead of "main", which is a common alternative in British English.
"Color" has been changed to "colour" in the "chargerImage" and "theme" fields, reflecting the British English spelling.
In the "instruction" field, "attempt" has been used instead of "try", and "goes wrong" instead of "fails", to align more with British English phrasing.
Remember, these changes are very subtle and may not even be necessary. The original text was already in a very clear and neutral form of English that would be understood by speakers of both American and British English.

The rest of the JSON file could remain the same, as it is not specific to any particular dialect of English. It is important to note that most of the text here is quite technical and specific to the application itself (like error messages, status updates, etc.), which would generally be the same across different English dialects.
@purcell-lab purcell-lab mentioned this pull request May 14, 2023
@tmjo tmjo merged commit b96b5d4 into tmjo:master Jul 24, 2023
@tmjo
Copy link
Owner

tmjo commented Jul 24, 2023

Really sorry for the delay, but added in v0.2.7.

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