Build failures

[alfsb]

There are some warnings on doc-ja building. These warnings may be erasing parts of translation.

Failed XIncludes, manual parts will be missing. Inspect temp/xinclude-debug.xml for context. Failed targets are:
- domxpath.registerphpfunctions..errors
- domxpath.registerphpfunctions..errors

It's possible to use:

• php doc-base/scripts/translation/qaxml-entities.php --urgent
• php doc-base/scripts/translation/qaxml-attributes.php --urgent

to narrow down the problematic files.

There are also a lot of wrong/broken XML warnings. These are somewhat easy to fix, and I can submit an PR to fix these, if there is someone can review and apply then afterwards.

[jdkfx]

@alfsb

I'm not a maintainer, but I was also trying to fix the build issue and couldn't resolve it.

I understand the part about the XInclude failures, but I haven't had time to investigate further beyond that yet.

• make build でビルドできない jdkfx/phpdoc#4
• OSS Gate Workshop: PHP Lovers: 2025-07-20: jdkfx: jdkfx/phpdoc: Work log oss-gate/workshop#1964 (comment)

I've seen a few others mention the same build issue, so if there is any known solution or workaround, I would really appreciate it if you could share it.

[alfsb]

I've seen a few others mention the same build issue, so if there is any known solution or workaround, I would really appreciate it if you could share it.

There are three main issues. I will try to explain each on in separated comments. To make conversation easy.

(Portguese: Se você tem acesso a bons tradutores de português para japonês, me avise. Que daí eu escrevo em português, e assim evita ter de superar duas barreiras de linguagem.)

[alfsb]

Issue of Broken XML. For example, ja/reference/mysql_xdevapi/entities.functions.xml:

$ file ja/reference/mysql_xdevapi/entities.functions.xml
ja/reference/mysql_xdevapi/entities.functions.xml: ASCII text

$ file en/reference/mysql_xdevapi/entities.functions.xml
No such file or directory

doc-ja has files that do not exist in doc-en. You can open these Broken files to see there is no text in these files, only XML code.

Delete these files.

[alfsb]

Issue of Wrong XML file and XML file contains \r.

Most translations of PHP manuals are files with 100% \n as end of line. Some translations are 1% to 2% files with other codes as end of line.

The translations with some files with \r and \r\n end of line, suffer from mysterious errors, sometimes. To avoid these mystery errors, all files need to be converted to use only \n as end of line. dos2unix does that.

How to fix:

$ php doc-base/scripts/broken.php --dos2unix ja
   // lots of errors

$ php doc-base/scripts/broken.php --dos2unix ja
   // less errors

$ cd ja

$ git diff --name-only | wc
     76      76    2914

$ git diff -b | wc
      0       0       0

Running doc-base/scripts/broken.php --dos2unix ja will change a lot of files. These changes are only whitespace, there is no change in text.

These changes can be sent to git (commit, push).

[alfsb]

Issue of Failed XIncludes.

$ grep -ri "domxpath.registerphpfunctions..errors" en
en/reference/dom/domxpath/registerphpfunctionns.xml: <xi:include xpointer="domxpath.registerphpfunctions..errors" />
en/reference/dom/domxpath/registerphpfunctions.xml: <refsect1 role="errors" xml:id="domxpath.registerphpfunctions..errors">
en/reference/xsl/xsltprocessor/registerphpfunctionns.xml: <xi:include xpointer="domxpath.registerphpfunctions..errors" />
en/reference/xsl/xsltprocessor/registerphpfunctions.xml: <xi:include xpointer="domxpath.registerphpfunctions..errors" />

$ grep -ri "domxpath.registerphpfunctions..errors" ja
$ 

doc-en files have domxpath.registerphpfunctions..errors. Same doc-ja files do not have.

Change the files in doc-ja to have the same xml:id as doc-en.

[alfsb]

@mumumu About the comment of developing PHP manual in Windows, my translation team is a mixed one. Some in Linux, some in Windows, and we can develop normal. There as trick.

On Windows machines, we do git config core.autocrlf true. And on Linux machines, we do git config core.autocrlf input. Everything goes well after this. If doc-ja has some instructions, mention this configuration will make things go more easy.

I will also try to make this instruction go into doc building instructions.

See https://stackoverflow.com/a/37749424/6054186 and https://git-scm.com/book/be/v2/Customizing-Git-Git-Configuration for details.