-
Notifications
You must be signed in to change notification settings - Fork 7.6k
updated wording of UTF-8 file load error. #7932
Conversation
@@ -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.", |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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."
There was a problem hiding this comment.
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.
oops! Thanks. I better start reading the code ;) |
@njx I think this is a good idea, but can you give this string change a quick review? |
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? |
@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. |
Cool. @HighwayChile, sorry for the churn - if you could change it back to just the |
@njx I'll be happy to make that change. |
Thanks. Merging. |
updated wording of UTF-8 file load error.
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."