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 ef334bab1c477c09955a2615c0d84b7f8a62c971..1037d40259d8e7e12b1f3e1ea27c865847460d09 100644
--- a/chrome/app/generated_resources.grd
+++ b/chrome/app/generated_resources.grd
@@ -15445,6 +15445,24 @@ After you create a new supervised user, you can manage their settings at any tim
       </message>
     </if>
 
+      <!-- Audio device strings. -->
+      <message name="IDS_DEFAULT_AUDIO_DEVICE_NAME" desc="Name representing the system default audio device (i.e. microphone or loudspeaker). This is typically presented to users in a drop-down list of device choices. Selecting it means the system will decide which device to use.">
+          Default
+      </message>
+      <if expr="is_win">
+        <message name="IDS_COMMUNICATIONS_AUDIO_DEVICE_NAME" desc="Name representing the system default communications audio device (i.e. microphone or loudspeaker). This is typically presented to users in a drop-down list of device choices. Selecting it means the system will decide which device to use for communications.">
+          Communications
+        </message>
+      </if>
+      <if expr="chromeos">
+        <message name="IDS_BEAMFORMING_ON_DEFAULT_AUDIO_INPUT_DEVICE_NAME" desc="Name representing the default audio input device (i.e. microphone), but with beamforming audio processing enabled. This is typically presented to users in a drop-down list of device choices. Selecting it means the system will decide which device to use, but with beamforming enabled. This will generally cause only the user in front of the device to be picked up by the microphones.">
+          Default (pick up just one person)
+        </message>
+        <message name="IDS_BEAMFORMING_OFF_DEFAULT_AUDIO_INPUT_DEVICE_NAME" desc="Name representing the default audio input device (i.e. microphone), but with beamforming audio processing disabled. This is typically presented to users in a drop-down list of device choices. Selecting it means the system will decide which device to use, but with beamforming disabled. This will generally cause everything in the vicinity to be picked up by the microphones.">
+          Default (pick up everything)

[jungshik at Google, 2015/09/17 21:56:43]

I wonder if we can come up with 'better' wording than 'pick up {one person,
everything}'. Translators often do not read this long description and may
translate "(...)" to something unrelated. 

+ainslie for that.

[ajm, 2015/09/17 22:42:04]

Happy to entertain suggestions. See crbug.com/497001 for the discussion,
specifically #17 - #21.

Also let me know if a more concise description would help.

[jungshik at Google, 2015/09/18 22:33:48]

Thank you for the reference. For me, 'listen to {everything, just you}' seems
better in terms of the chance of being translated correctly. 
What we can do is to use 'pick up ....' as is now, but change the description
(hoping that translators read the description. They really should, but not
always). 
 
To translators, 'beamforming audio processing en/disabled' (well, they can be
pretty tech-savvy, too, but ...) may not help much. How about this?

* Default audio input device (microphone) with a narrow angle coverage. Only the
user in front of the device (i.e. you) will be listened to. This is typically
presented to users in a drop-down list of device choices.
* Default audio input device (microphone) with a wide angle coverage. All the
sounds in the vicinity will be picked up. This is typically presented to users
in a drop-down list of device choices. 

[ajm, 2015/09/21 19:49:26]

Sounds good, except that I also used "listened to" rather than "picked up" in
the second description, which I think was your intention.

To be clear, I also now changed "Default (pick up just one person)" to "Default
(pick up just you)". I think the former is closer to what will really happen,
but the latter is probably more clear for users. What do you think?

+        </message>
+      </if>
+
     </messages>
   </release>
 </grit>