|
Fri May 8 13:33:56 2020, comment #7:
The build process is mainly about generating of .htf and .4ht files anyway. Binaries are prepared by Karl separately, I believe.
|
Fri May 8 13:21:14 2020, comment #6:
Michal: maybe we should open another issue « native MSW support » to discuss this. Actually I had only tested the .4ht file generation from the litterate programming files, and I did not go further in the installation.
|
Fri May 8 12:26:55 2020, comment #5:
I am actually surprised that it worked in Windows except for symlinks. I try to avoid Windows as much as I can. Even with WSL there are some things, especially regarding keyboard support, that drive me crazy every time I try to do anything with it.
|
Wed May 6 08:51:48 2020, comment #4:
FYI, quite some time ago, I had made a trial with Msys which is a native MSWindow bash and it worked more or less.
The only problem was rather with my SVN client that did not keep the smylinks, so I had to create them manually (Modern MSWindow has mklink dos command for that, but creating the symlink programmatically needs more effort, Msys ln command by default makes copies not symlink, you have to configure both MSWindows and Msys for the ln to create symlinks.
|
Tue May 5 20:49:29 2020, comment #3:
Hello Vincent,
I've updated the sources before you uploaded the patch. But your vesion is better, so we will use it.
The scripts are used only in the build process, when the .4ht files are generated from the literate sources. I don't think we support Windows, but I think this is not that big issue today, as it is possible to use WSL and have working Linux shell in Windows 10.
|
Tue May 5 20:16:48 2020, comment #2:
Hello Michal,
I had attached a patch. as file #339 readme-patch.diff
I think that the statement about the PATH should also be updated.
Maybe my patch is not OK, and one should say « provided that the scripts or any symlink thereof can be found by the shell through the PATH variable »
Anyway, this also means that these scripts should be in some pdflatex/xelatex configuration file so that they can be accessed is reduced shell escape mode.
You also need in *nix to have the correct chmod, and in mswindow the file extension should be in PATHEXT
Sorry, but I am not an expert in using shell escape, so I cannot really provide good text.
|
Tue May 5 19:51:46 2020, comment #1:
Thanks for the report, Vincent. I've updated the README file. The new version of the text is:
The directory `extra-bin` contains do-nothing scripts named xmllint and vcss, which are called for validation via tex4ht-env.tex. (Of course they won't be used unless . is early enough in PATH.) The real xmllint can take a long time to run, and fails to find the DTD on the tex4ht-docbook*.html output, for no apparent reason.
|
Tue May 5 19:22:27 2020, original submission:
This README file contains this statement
This directory contains do-nothing scripts named xmllint and vcss
However this scripts are indeed not in this directory, but in a extra-bin subdirectory.
|
Related Recipes:
tex4ht - Bugs: bug #459, False path in lit/README