Re: [tex4ht] compiling java in a single place

Summary of change: Fix dependencies with do_java=0 or 1, and compile xtpipes.jar only with compilation in tex. Le lun. 15 juin 2020 à 10:02, Vincent Belaïche a écrit : > > Sorry for I should have written that my contribution needed some fix, > but you were more reactive than me. >

Re: [tex4ht] compiling java in a single place

Sorry for I should have written that my contribution needed some fix, but you were more reactive than me. I made a fix and added some comments. With this, typing repeatedly make won't trigger any recompilation. V. Le dim. 14 juin 2020 à 00:37, Karl Berry a écrit : > > Subject: compiling

Re: [tex4ht] java modules

Feedback embedded below… Le dim. 7 juin 2020 à 23:04, Karl Berry a écrit : > [...] > That is not a problem in principle. A given source file can be specified > to generate multiple outputs. > > foo.class bar.class: foo.java >javac ... > OK, make can handle several outputs foo.class and

[tex4ht] compiling java in a single place

Hello Karl, I did the change for java compilation to happen in a single place or to be disabled. Attached is the patch file. Contrary to my speculation, this change does not solve the issue that you never get to make answering « nothing to be done », but probably that goes in the right

Re: [tex4ht] xmllint calls, so many

Maybe instead of doing system calls to xmllint one could record the file list into some file (maybe the .fls file produced by the -recorder option is OK for that), and then one would do something like this to make the syntax checking. awk '/^OUTPUT.*\.xml$/ { $1 =""; print}' record_file.fls |

Re: [tex4ht] java modules

Concerning the make problem, this is one thing, probably we can find some dependency error somewhere in the make file, or more likely I speculate that the issue is that with do_java=1 we compile the java sources in two places, in the Makefile and in the t4ht system calls. As make can run several

Re: [tex4ht] java modules

Here is a fix for the problem that you observed. I did not have the same thing. Probably my cp version is not the same and does not cause an error when the wildcard expansion is empty. That is strange because I tried some "cd /tmp ; mkdir toto; cp I-dont-exist/* toto" in sh and it did not work. I

Re: [tex4ht] java modules

I am not sure whether it is OK or not as I kept the java compilation in the .tex system calls. Is that what you wanted ? Le ven. 5 juin 2020 à 00:06, Vincent Belaïche a écrit : > > Step № 3 > > Le jeu. 4 juin 2020 à 18:28, Karl Berry a écrit : > > > >

Re: [tex4ht] java modules

Step № 3 Le jeu. 4 juin 2020 à 18:28, Karl Berry a écrit : > > Attached is step 2 patch. > > No problem there, installed (r719). -k step3.diff Description: Binary data

Re: [tex4ht] java modules

Attached is step 2 patch. BR, V. Le mar. 2 juin 2020 à 22:55, Karl Berry a écrit : > > OK, enclosed is the 1st step, that which generates tex4ht-dir.tex from > tex4ht-dir.m4. > > That's the part I already committed (with your additional Makefile > changes). Please send step 2 :). > >

Re: [tex4ht] java modules

Just make me know if you agree with the content, and then I can make the commit. Le mar. 2 juin 2020 à 22:07, Vincent Belaïche a écrit : > > OK, enclosed is the 1st step, that which generates tex4ht-dir.tex from > tex4ht-dir.m4. > V. > > Le lun. 1 juin 2020 à 23:01, K

Re: [tex4ht] java modules

OK, enclosed is the 1st step, that which generates tex4ht-dir.tex from tex4ht-dir.m4. V. Le lun. 1 juin 2020 à 23:01, Karl Berry a écrit : > > I attached the whole diff, but I wish to split it into several > elementary steps. > > Sounds good. > > 1) the first step is that

Re: [tex4ht] java modules

Oh, I didn't have really noticed that I was included. I attached the whole diff, but I wish to split it into several elementary steps. Because there are several different objectives that should be each in a different change. 1) the first step is that tex4ht-dir.tex is renamed to tex4ht-dir.m4 and

[tex4ht] java modules

Dear all, When I try to compile under lit, the compilation fails because there are still many absolute path like /home/4/gurari/..., and also a few minor issues with the java code. Another source of errors is that the \MakeDir macro looping prematurely stops because of some double slash in the

[tex4ht] [bug #459] False path in lit/README

Follow-up Comment #6, bug #459 (project tex4ht): 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.

[tex4ht] Fwd: [bug #461] Formatting issues in doc/tex4ht-options.tex

-- Forwarded message - De : Vincent Belaïche Date: mer. 6 mai 2020 à 23:08 Subject: [tex4ht] [bug #461] Formatting issues in doc/tex4ht-options.tex To: Vincent Belaïche , URL: <http://puszcza.gnu.org.ua/bugs/?461> Summary: Formatting issues in doc/

[tex4ht] [bug #461] Formatting issues in doc/tex4ht-options.tex

URL: Summary: Formatting issues in doc/tex4ht-options.tex Project: tex4ht Submitted by: vincentb1 Submitted on: jeu. 07 mai 2020 00:08:33 EEST Category: None Priority:

[tex4ht] [bug #459] False path in lit/README

Follow-up Comment #4, bug #459 (project tex4ht): 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

[tex4ht] [bug #459] False path in lit/README

Follow-up Comment #2, bug #459 (project tex4ht): 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

[tex4ht] [bug #459] False path in lit/README

Additional Item Attachment, bug #459 (project tex4ht): File name: readme-patch.diff Size:0 KB ___ Reply to this item at: ___ Message sent

[tex4ht] [bug #460] Minor fix in Introduction to \Configure (missing >)

URL: Summary: Minor fix in Introduction to \Configure (missing >) Project: tex4ht Submitted by: vincentb1 Submitted on: mar. 05 mai 2020 22:43:49 EEST Category: None

[tex4ht] [bug #459] False path in lit/README

URL: Summary: False path in lit/README Project: tex4ht Submitted by: vincentb1 Submitted on: mar. 05 mai 2020 22:22:27 EEST Category: None Priority: 5 - Normal

[tex4ht] [bug #366] tex4ht-sty.tex does not test the presence of the local ./tex4ht.sty, but any tex4ht.sty in the TEXMF

Follow-up Comment #2, bug #366 (project tex4ht): Ooops... sorry for the problem in my patch. I had overlooked it because when you do the 1st pass w/o local tex4ht.sty it works. The problem is caused by subsequent \def\next while \next has been \let to \iffalse. Attached is another patch

[tex4ht] [bug #366] tex4ht-sty.tex does not test the presence of the local ./tex4ht.sty, but any tex4ht.sty in the TEXMF

URL: Summary: tex4ht-sty.tex does not test the presence of the local ./tex4ht.sty, but any tex4ht.sty in the TEXMF Project: tex4ht Submitted by: vincentb1 Submitted on: lun. 14 août 2017 13:49:40

[tex4ht] [bug #365] ProTex.sty and AlProTex.sty links do not work for me

Follow-up Comment #6, bug #365 (project tex4ht): Dear Karl, I noticed that you have closed this one. Let me please make some additional comment. >From Windows2000, MSWindows is able to handle symlinks provided that the user account is configured accordingly and that the console in which you

[tex4ht] [bug #365] ProTex.sty and AlProTex.sty links do not work for me

Follow-up Comment #3, bug #365 (project tex4ht): Dear Karl, It is not a matter of just « unix » vs « not unix ». I don't know how the link ../protex/ProTex.sty works, but I presume that this is dependant on the version control system. This means that anyway, if you don't apply that sort of

[tex4ht] [bug #365] ProTex.sty and AlProTex.sty links do not work for me

Follow-up Comment #1, bug #365 (project tex4ht): If you add me to the project, I can give a hand. ___ Reply to this item at: ___ Message posté via/par

[tex4ht] [bug #365] ProTex.sty and AlProTex.sty links do not work for me

URL: Summary: ProTex.sty and AlProTex.sty links do not work for me Project: tex4ht Submitted by: vincentb1 Submitted on: jeu. 27 juil. 2017 18:46:42 EEST Category: None

[tex4ht] [bug #200] fmtcount tex4ht conflicting

Follow-up Comment #3, bug #200 (project tex4ht): Hello, After some investigation, I think that I have some idea about what is happening : it seems that we have some edef that should be replaced by protected@edef to make it work better. Now, I would like to try that, but the thing is that I have

[tex4ht] [bug #208] lit/Makefile has extra space in latex argument confusing MikTeX latex

URL: http://puszcza.gnu.org.ua/bugs/?208 Summary: lit/Makefile has extra space in latex argument confusing MikTeX latex Project: tex4ht Submitted by: vincentb1 Submitted on: lun. 03 mars 2014 00:11:12 EET Category: None

[tex4ht] [bug #208] lit/Makefile has extra space in latex argument confusing MikTeX latex

Follow-up Comment #1, bug #208 (project tex4ht): Ok, I attached htlatex.bat.diff which is certainly a better patch to correct this issue than my previous patch in Makefile.diff (file #167) ___ Additional Item Attachment: File name:

[tex4ht] [bug #200] fmtcount tex4ht conflicting

Follow-up Comment #2, bug #200 (project tex4ht): Ok, I will try my best to find a fix. I let you know on this same thread. Vincent. ___ Reply to this item at: http://puszcza.gnu.org.ua/bugs/?200