Work around syntax error caused by the pot-to-php script

[swissspidy]

This is an attempt to fix #1416 for the time being.

I still have to look into how the pot-to-php script handles comments exactly and how it can be solved. We likely don't need that script anymore in the long run though.

Also, I need to find some time to look into the WP-CLI command. It should be possible to skip the file comment entirely by using --file-comment="" instead of using a somewhat hacky --file-comment="*/\'\'/*" workaround. This would also mostly eliminate the need to fix the pot-to-php script.

Fixes #1416.

[westonruter]

@swissspidy the fix doesn't seem to be working:

<?php
/* THIS IS A GENERATED FILE. DO NOT EDIT DIRECTLY. */
$generated_i18n_strings = array(
	/* translators: *//* */
,

	/* Plugin Name of the plugin */
	__( 'AMP', 'amp' ),

Checking syntax:

php -l build/languages/amp-translations.php
PHP Fatal error:  Cannot use empty array elements in arrays in build/languages/amp-translations.php on line 5

[westonruter]

Adding more slashes fixes the problem: e301ee6.

[swissspidy]

Thanks for the review!

The slashes might be an environment thing. I thought it worked fine when I tested it the other day...

In the meantime I submitted a PR to the WP-CLI command to make --file-comment="" work: wp-cli/i18n-command#82