Spinning off an internal discussion, and from  Issue 836703 : it may be useful to rethink putting "..." at the end of strings for menu items and other actions, when those actions have an intermediate step (such as a dialog).

For example, on the Chrome menu, "Print..." has an ellipsis because it opens a dialog, rather than immediately printing the page. The "Print" button in the Print dialog does not have an ellipsis because it immediately prints. However, within the Print dialog, there is another button "Print using system dialog..." which has an ellipsis because it will open a secondary dialog.

This is a common pattern established for many decades in both (at least) Microsoft Windows and Apple macOS:

https://docs.microsoft.com/en-au/windows/desktop/uxguide/cmd-menus#using-ellipses
"Indicate a command that needs additional information (including a confirmation) by adding an ellipsis at the end of the label."

https://developer.apple.com/design/human-interface-guidelines/macos/menus/menu-anatomy/#menu-item-titles
"Use an ellipsis whenever choosing a menu item requires additional input from the user."

So we probably want to keep these, at least on Windows.

The private discussion from  Issue 836703  was focused on other languages, like German, where this may not make as much sense. While I'm not a native speaker of another language, my feeling is that "..." at the end of a command makes just as much sense in English as in German (i.e., not much as a language construct; this is more of a UX construct than language).

It doesn't look like Google's Material Design guidelines include this convention.

Questions for Shimi to answer:

1. Should the ellipsis be used at all in these menu items?
2. Should it be specific to certain platforms (i.e. Windows and macOS) where the convention is encoded in those platform guidelines, or all platforms?
3. Should it be specific to certain languages where it makes sense (e.g. it's been claimed that this convention doesn't make sense in German), or all languages? If the former, who is going to be the arbiter of which languages this convention makes sense, and which it doesn't?
4. Should we continue to embed the ellipsis in the internationalized strings (i.e., the GRD files), and the policy be enacted by string authors and translators, or should they be applied programmatically, and the policy enforced by code? [I think the answer to this depends upon how definitive the policy is, and whether exceptions are made per-language and perhaps per-string.]