Babel Makepot: Translator comments have been extracted from the file#9440
Babel Makepot: Translator comments have been extracted from the file#9440aduth merged 4 commits intoWordPress:masterfrom
Conversation
|
|
@swissspidy what's the future of |
|
Confusing indeed. For reference, the treatment of the I'll defer to you two on this one, and the referenced documentation seems to reaffirm the correction. I've force-pushed a rebased copy of the branch to be able to add a CHANGELOG entry as a fix. I contemplated whether to consider the |
…9440) * Comments have been extracted from the file * Update POT comment behavior in PHP file generation * Convert function names * Babel Plugin Makepot: Add CHANGELOG entry for translator -> extracted
…9440) * Comments have been extracted from the file * Update POT comment behavior in PHP file generation * Convert function names * Babel Plugin Makepot: Add CHANGELOG entry for translator -> extracted
Description
In the POT file generated by Gutenberg the translator comments are extracted into regular comments (denoted with just a
#) while they should be denoted with a#.This is a mixup on the term "translator" comments. As can be seen in section "2.2.1 Extracted Comments" of The PO Format, the comments denoted with
translators:are actually called "extracted comments" in the PO file format.How has this been tested?
npm run buildto create the POT file in languages/gutenberg.potnpx pot-to-php ./languages/gutenberg.pot ./languages/gutenberg-translations.php gutenbergto generate the PHP fileTypes of changes
Janitorial
Checklist: