In certain circumstances a leading space has to be preverved to allow it
to be used to create a text space node to insert before this element to
preserve the view in a browser.
And added a note asking why is ParseTag called with a hardcoded
IgnoreWhitespace when some effort above has set the mode variable to
MixedContent in certain cases, but need to think about this 2nd change.
Also added some MSVC Debug output when this leading text is used to insert
such a created text node before the element just to be reminded of this
special event.
Such debug is OFF by default, and only added by defining DEBUG_MEMORY. And
is only available for the Debug configuration compiled with MSVC, but this
could be easily extended...
Not sure how this has lasted so long, but I guess there are not too many
users wanting to specifically use the static tidy library.
Now it is possible to define TIDY_STATIC and the TIDY_EXPORT macro will
just be 'external', suitable for linking with the static library, instead
of adding the _imp_ MSVC __declspec( dllimport )...
This fix does not effect other than the WIN32 platform build.
First many other projects do this, and it seems a good choice.
Due mainly to windows where the static and shared libraries have the same
name, appended an 's' to the static library.
The tidy console app will use the static library, since to build the man
page tidy may need to be run before the shared libraries are installed.
And this makes the windows tidy exe a stand-alone app. No DLL install
issue.
This addresses issue #194, and possibly #190
Thought there may be some comments on this but nothing for a week.
So have merged to master hoping more people will test it, and any
remaining issues resolved.
Now it will be present from version 4.9.29 onwards.
It was not intended that this cmd file be run separately. It is invoked by
alltest1.cmd which in turn is invoked by alltest.cmd. This 'chain' is
requierd to set up the appropriate environmnet variables.
This is particularly for the anchor tag which in html5 mode is parsed in
ParseBlock. That is retain a leading space, in case it needs to be
moved to in front of the block to keep space rendering.
The recommended place to run cmake is in the build/cmake directory,
but have changed a relative path to an absolute path which should
allow cmake to be run ANYWHERE!. See bottom of Issue #193
Also a few other minor tweak to CMakeLists.txt
