Skip to content

Mark do-not-translate files#5657

Open
alfsb wants to merge 5 commits into
php:masterfrom
alfsb:ignore-xml-files
Open

Mark do-not-translate files#5657
alfsb wants to merge 5 commits into
php:masterfrom
alfsb:ignore-xml-files

Conversation

@alfsb

@alfsb alfsb commented Jul 6, 2026

Copy link
Copy Markdown
Member

Apply the new <?do-not-translate?> in doc-en files that are auto-generated, expected not translated, ot that not contains any translatable text.

In special, I would like to confirm/know:

  • docbookcs.xml should not be copied on translatoins?
  • en/appendices/license.xml is expected never translated.
  • where is the code that generates en/reference/datetime/timezones.xml, this the generator outputs the <?do-not-translate?> mark.

Things I considered:

  1. To remove the vi/vim comments and eof very small files, and from all version.xml files;

  2. To remove the top comment, and leave only at start:

<?xml version="1.0" encoding="utf-8"?>
<?do-not-translate?>

There still about 200 /*/versions.xml files, that I will change, directly, if and after this PR is merged. Plan to merge it in one week, if there is no hard oppositions.

@alfsb

alfsb commented Jul 6, 2026

Copy link
Copy Markdown
Member Author

Also, are there some other .xml files, besides versions.xml files, that I missed? I got this "list" from file exclusions of revcheck, that I expect is correct, but to be sure.

Comment thread appendices/license.xml Outdated
@jordikroon

Copy link
Copy Markdown
Member

docbookcs.xml may be copied. It's up to the translator if they want this in as it could be useful for them.
And I added this marker to #5658 as well.

@alfsb

alfsb commented Jul 8, 2026

Copy link
Copy Markdown
Member Author

Plan to merge this by friday, having a small cooldown from 5634.

@alfsb

alfsb commented Jul 8, 2026

Copy link
Copy Markdown
Member Author

docbookcs.xml may be copied. It's up to the translator if they want this in as it could be useful for them. And I added this marker to #5658 as well.

Then it needs a <!-- $Revision$ --> line after XML decl, so translations have a place where to replace for the revtag, without disturbing line counts or creating long lines.

Also, can you add some other XML comment, poining for documentation or a fast/small tutorial, of where the file is used and how it could be changed in translations?

@alfsb

alfsb commented Jul 8, 2026

Copy link
Copy Markdown
Member Author

Plan to merge this by next monday, and then after that, to mark all version.xml files. Last is to remove the ignore-by-name conventions in revcheck,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants