Bug #78877 [Fbk->Csd]: LIBXML_PARSEHUGE output formatting
Edit report at https://bugs.php.net/bug.php?id=78877&edit=1
ID: 78877
Updated by: cmb@php.net
Reported by: kieran at miami-nice dot co dot uk
Summary: LIBXML_PARSEHUGE output formatting
-Status: Feedback
+Status: Closed
Type: Bug
Package: DOM XML related
PHP Version: 7.3.12
Assigned To: cmb
Block user comment: N
Private report: N
New Comment:
Thanks for the swift reply! Closing then.
Previous Comments:
------------------------------------------------------------------------
[2021-09-15 10:08:30] kieran at supportpal dot com
@cmb yeah this looks OK on Docker 7.4.23-cli-bullseye which is using libxml 2.9.10
Must have been a bug in libxml <2.9.10
Happy for you to close.
------------------------------------------------------------------------
[2021-09-15 09:12:57] cmb@php.net
I just run the test script with PHP-7.4 on Windows (libxml2
2.9.10), and there LIBXML_PARSEHUGE does not make a difference
(the output matches the input for either). So this looks like a
libxml2 issue to me. Can you check that with a more recent
version than libxml2 2.9.4?
------------------------------------------------------------------------
[2019-12-14 16:49:17] drtechno at mail dot com
I would try uninstalling it and making sure it has a path assigned, then reinstall it.
like this:
Centos:
pip uninstall lxml
Ununtu:
sudo apt-get purge lxml
add the parsers to the PATH:
export
PATH=/home/hsundara/packages_installed/libxslt-1.1.28/bin:/home/hsundara/packages_installed/libxml2-2.9.1/bin:$PATH
then install:
Centos:
pip install lxml --install-option="--auto-rpath"
Ubuntu:
sudo apt-get install lxml --install-option="--auto-rpath"
------------------------------------------------------------------------
[2019-11-28 15:57:25] kieran at miami-nice dot co dot uk
> it's about the different output with and without LIBXML_PARSEHUGE
Correct
------------------------------------------------------------------------
[2019-11-28 14:12:42] cmb@php.net
Ah, I thought it was about the differences between PHP < 7.3.0 and
>= 7.3.0! If it's about the different output with and without
LIBXML_PARSEHUGE, it can't be related to the mentioned bug fixes,
since these have only been applied to PHP 7.3+.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=78877
--
Edit this bug report at https://bugs.php.net/bug.php?id=78877&edit=1
Thread (7 messages)