Skip to content
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.

updated wording of UTF-8 file load error. #7932

Merged
merged 4 commits into from
May 30, 2014
Merged

updated wording of UTF-8 file load error. #7932

merged 4 commits into from
May 30, 2014

Conversation

h1w4y
Copy link
Contributor

@h1w4y h1w4y commented May 24, 2014

addresses Issue #7850
When opening a non UTF-8 file, the second and third sentences of the error message will now read: "The file is not UTF-8 encoded text. Brackets currently only supports UTF-8 encoded text files."

@@ -37,7 +37,7 @@ define({
"NO_MODIFICATION_ALLOWED_ERR" : "The target directory cannot be modified.",
"NO_MODIFICATION_ALLOWED_ERR_FILE" : "The permissions do not allow you to make modifications.",
"CONTENTS_MODIFIED_ERR" : "The file has been modified outside of {APP_NAME}.",
"UNSUPPORTED_ENCODING_ERR" : "The file is not UTF-8 encoded text.",
"UNSUPPORTED_ENCODING_ERR" : "Brackets currently only supports UTF-8 encoded text files.",
Copy link
Contributor

Choose a reason for hiding this comment

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

We should somehow make clear the opened file isn't UTF-8.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

How's this?
"The file is not UTF-8 encoded text. Brackets currently only supports UTF-8 encoded text files."

Copy link
Contributor

Choose a reason for hiding this comment

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

That's easy, but ok with me.

@h1w4y h1w4y changed the title updated wording of UF-8 file load error. Issue #7850 updated wording of UF-8 file load error. May 24, 2014
@h1w4y
Copy link
Contributor Author

h1w4y commented May 24, 2014

oops! Thanks. I better start reading the code ;)

@bchintx bchintx changed the title updated wording of UF-8 file load error. updated wording of UTF-8 file load error. May 27, 2014
@redmunds
Copy link
Contributor

@njx I think this is a good idea, but can you give this string change a quick review?

@njx
Copy link
Contributor

njx commented May 28, 2014

I think we wanted to just replace the second sentence instead of appending to it. It feels a bit redundant with both. (I guess that's what @HighwayChile had originally.)

@SAplayer - it seems to me like saying "The file foo.js could not be opened. Brackets currently only supports UTF-8 encoded text files." makes it pretty clear that the reason the file couldn't be opened is that it's not a UTF-8 text file. Do you think the extra sentence is necessary?

@marcelgerber
Copy link
Contributor

@njx Ah yes, I didn't think about the first sentence ("The file foo.js could not be opened."). I'm ok with it either way.

@njx
Copy link
Contributor

njx commented May 28, 2014

Cool. @HighwayChile, sorry for the churn - if you could change it back to just the Brackets currently only supports... sentence that would be great.

@h1w4y
Copy link
Contributor Author

h1w4y commented May 29, 2014

@njx I'll be happy to make that change.

@redmunds
Copy link
Contributor

Thanks. Merging.

redmunds added a commit that referenced this pull request May 30, 2014
updated wording of UTF-8 file load error.
@redmunds redmunds merged commit 3727e31 into adobe:master May 30, 2014
@h1w4y h1w4y deleted the 7850 branch May 30, 2014 22:13
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants