When mdbook-i18n-normalize is used on a PO file, we currently leave the metadata alone. However, this can cause problems for publishing pipelines like the one in Comprehensive Rust: there we expect that the POT-Creation-Date field has changed if any of the msgid fields change.
To handle this situation in a smooth way, I propose incrementing the timestamp by 1 second, if possible. This means: parse the field, increment it by 1 second if it's a valid timestamp, and finally write it back to the file. If it's missing or invalid, then leave it along.
When
mdbook-i18n-normalizeis used on a PO file, we currently leave the metadata alone. However, this can cause problems for publishing pipelines like the one in Comprehensive Rust: there we expect that the POT-Creation-Date field has changed if any of themsgidfields change.To handle this situation in a smooth way, I propose incrementing the timestamp by 1 second, if possible. This means: parse the field, increment it by 1 second if it's a valid timestamp, and finally write it back to the file. If it's missing or invalid, then leave it along.