chrome/app/generated_resources.grd

Index: chrome/app/generated_resources.grd
diff --git a/chrome/app/generated_resources.grd b/chrome/app/generated_resources.grd
index b463e4e56139110680514521778b24c4c26363aa..f01038b512e4ceba2de2398f8e92a6585b03c998 100644
--- a/chrome/app/generated_resources.grd
+++ b/chrome/app/generated_resources.grd
@@ -5230,7 +5230,7 @@ Keep your key file in a safe place. You will need it to create new versions of y
       <message name="IDS_FLAGS_SAVE_PAGE_AS_MHTML_DESCRIPTION" desc="Description of the 'Save Page as MHTML' lab.">
         Enables saving pages as MHTML: a single text file containing HTML and all sub-resources.
       </message>
-      
+
       <!-- Flag and values for MHTML Geenrator options lab. -->
       <message name="IDS_FLAGS_MHTML_GENERATOR_OPTION_NAME" desc="Name of the 'MHTML Generator Options' lab.">
         MHTML Generation Option
@@ -11272,6 +11272,9 @@ Your profile could not be opened correctly.
 
 Some features may be unavailable.  Please check that the profile exists and you have permission to read and write its contents.
       </message>
+      <message name="IDS_COULDNT_SWITCH_PROFILE_ERROR" desc="Error displayed when the profile to be switched to can not be opened correctly due to problems reading or writing files in it.">

[Peter Kasting, 2016/06/13 04:43:20]

Why does this message need to be separate from IDS_COULDNT_OPEN_PROFILE_ERROR? 
The two are nearly identical.  Can't we unify on a single message for both?

The reason I could see to have two would be if this one was more like "The
profile '<username>' could not be opened."  But it might make sense to provide
the profile name on the other message anyway.

[WC Leung, 2016/06/13 08:06:45]

I see. Let me check the context of the other message. (It appears the error that
results in the other message is currently being discussed in chrome-dev group.)

[WC Leung, 2016/06/15 13:08:38]

In the other CL Brett is giving similar comments. I'll just use the current
message unmodified in this CL, because adding some $1 into the string results in
non-trivial modifications of two files. See
https://cs.chromium.org/search/?q=IDS_COULDNT_OPEN_PROFILE_ERROR&sq=package:c...

+        Your profile could not be opened correctly. Please check that the profile directory exists and you have permission to read and write its contents.
+      </message>
       <message name="IDS_REFUSE_TO_RUN_AS_ROOT" desc="Short error message displayed in an error dialog on startup if the user tries to run Chrome as root">
         <ph name="PRODUCT_NAME">$1<ex>Google Chrome</ex></ph> can not be run as root.
       </message>