The previous location was fine when saving the output stream, but it led to
unset character when using node interrogation, which _also_ uses the pretty
printers to get text. This is a more appropriate location to set the character.
This is the first instance of our cool Swift wrapper API tester catching an
issue for us. Nice!
Proof that the automated API
Naked groups of LI in HTML5 mode will now have an inferred UL applied to
them consistent with HTML4 and earlier modes.
Test case added.
Note that three regressions were updated in favor of this corrected behavior.
Instead of recursive calls for each nested level of HTML, the next level is
pushed to a stack on the heap, and returned to the main loop. This prevents
stack overflow at _n_ depth (where _n_ is operating-system dependent). It's
probably still possible to use all of the heap memory, but Tidy's allocators
already fail gracefully in this circumstance.
Please report any regressions of your own HTML!
NOTE: the XML parser is not affected, and is probably still highly recursive.
- Updated links with working https versions from http.
- Removed rotten links.
- Updated links that have since resolved to new addresses.
- Generated all new po's and pot from existing headers.
- Updated the regression tests to account for the new https:// URLS, and the
changed reference to specification.
User-specified settings were being fiddled with by tidy internally. User
settings set by the user should always be able to be read back by the
user, but `AdjustConfig()` would change them. This change contributes
toward fixing the situation by using `AdjustConfig()` at the only point
that it's needed, as well by NOT automatically reverting to the snapshot
after outputting a buffer (which should be stateless, but caused PHP to
break because it tried to save buffer more than once, so subsequent calls
would use non-fiddle settings.).
Error made when merging LOADING Is. #879, PR #902
And merging SLOT PR #848
Also added a BIG warning over attribute_defs table to try to avoid this
in future.
* Is. #896 - make 'bear' docs match code
* Is. #487#462 add warn msg and do not get stuck until eof
The warning message could perhaps be better worded, and maybe there
should be another msg when a '>' is encountered while looking for a ']'
in a MS Word section, and perhaps the section should be discarded...
And perhaps it should be an error, to force the user to fix...
But the fix is good as it is, and these issues can be dealt with
later...
And this fix is piggy backed on this PR, but it is likewise related to
'word-2000' option...
