kc3-lang/libxml2/result/errors/754947.xml.err
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
8d0aaf4b | 2023-12-19 20:47:36 | parser: Remove xmlErrEncoding Use xmlFatalErr or xmlCtxtErrIO. | |
|
bbd918b2 | 2023-08-29 15:56:37 | parser: Fix detection of null bytes Also suppress misleading extra errors. Fixes #122. | |
|
76c6da42 | 2022-12-04 23:01:00 | error: Make sure that error messages are valid UTF-8 This has caused issues with the Python bindings for a long time. Should fix #64. | |
|
de5b624f | 2021-05-08 20:21:29 | Fix handling of unexpected EOF in xmlParseContent Readd the XML_ERR_TAG_NOT_FINISHED error on unexpected EOF which was removed in commit 62150ed2. This commit also introduced a regression for direct users of xmlParseContent. Unclosed tags weren't checked. | |
|
62150ed2 | 2019-09-23 14:46:41 | Make xmlParseContent and xmlParseElement non-recursive Split xmlParseElement into subfunctions. Use nameNsPush to store prefix, URI and nsNr on the heap, similar to the push parser. Closes #84. | |
 |
4a5d80ad | 2015-09-18 15:06:46 | Fix a bug in CData error handling in the push parser For https://bugzilla.gnome.org/show_bug.cgi?id=754947 The checking function was returning incorrect args in some cases Adds the test to teh reg suite and fix one of the existing test output |