Translator comments are sometimes missed out

[notnownikki]

Describe the bug

When generating languages/gutenberg.pot, sometimes the built files are used instead of the original source files and translator comments get missed.

In packages/editor/src/components/block-list/block.js we have this on lines 382-384:

		const blockType = getBlockType( blockName );
		// translators: %s: Type of block (i.e. Text, Image etc)
		const blockLabel = sprintf( __( 'Block: %s' ), blockType.title );

This gets built to this in packages/editor/build-module/components/block-list/block.js:

      var blockType = getBlockType(blockName); // translators: %s: Type of block (i.e. Text, Image etc)

      var blockLabel = sprintf(__('Block: %s'), blockType.title); // The block as rendered in the editor is composed of general block UI

and when translations are generated, the build-module version's translation entry is used and the translator comment is not included.

To Reproduce

Run npm run build and see that build-module versions of files are referenced in languages/gutenberg.pot

Expected behavior

Only the original src versions should be referenced, and all translator comments should be included.

[mayukojpn]

I also found 3 translator comments in packages/keycodes/src/index.js:L124 are not imported to GlotPress. I don't know why :(

[00travelgirl00]

I translate strings to german right now and also found some missing translator comments:

• Archives (can be singular or plural in englisch. in german those are different words.)

and the most strings which are still open:

https://translate.wordpress.org/projects/wp-themes/twentynineteen/de/default?filters%5Bstatus%5D=untranslated&sort%5Bby%5D=priority&sort%5Bhow%5D=desc

[swissspidy]

This should be mostly solved now that Gutenberg has merged into WordPress core and WP-CLI is used to extract the strings and comments. There are only a few exceptions: wp-cli/i18n-command#106

See #9440.

[youknowriad]

Should we close this @swissspidy?