gnuplot-beta — Developers and beta testers of new gnuplot code

Re: Qt term enhancements

[Tatsuro M. <tma...@ya...>]

Hello Mike

Your proporsal new enhancement of qt terminal is really good.
However, your proprosal is better to be carried out in the Patches ticket.

https://sourceforge.net/p/gnuplot/patches/

Tatsuro 

> ----- Original Message -----
> 
> From: "m sutton" 
> To: "gnuplot-beta
> Date: 2022/02/10 木 10:42
> Subject: Qt term enhancements
> 
> 
> Hi All,
> 
> I modified the qt term so you can  set three options that are currently 
> on the tools dialog.
> 
> The change will allow you to specify rounded|butt, {no}replotonresize 
> and {no}antialias.  These are temporary settings.
> 
> This also fixed a bug with the {no}ctrl option.  If multiple "set term 
> qt" command were given before the plot window was opend, the {no}ctrl 
> setting would be lost.
> 
> The attached diff is based on v5.4.1.  Let me know if something needs 
> changed.
> 
> Once again, many thank to all of you that make Gnuplot so awesome.
> 
> Regards,
> 
> MikeS
> 
> 
> 
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Qt term enhancements

[m s. <mw...@us...>]

Hi All,

I modified the qt term so you can  set three options that are currently 
on the tools dialog.

The change will allow you to specify rounded|butt, {no}replotonresize 
and {no}antialias.  These are temporary settings.

This also fixed a bug with the {no}ctrl option.  If multiple "set term 
qt" command were given before the plot window was opend, the {no}ctrl 
setting would be lost.

The attached diff is based on v5.4.1.  Let me know if something needs 
changed.

Once again, many thank to all of you that make Gnuplot so awesome.

Regards,

MikeS

Re: How to get the previous image of git of master baranch

[Tatsuro M. <tma...@ya...>]

Ethan

Thank you for your help.
The origin fo my trouble does not reply on the gnuplot source but on the local environment.
On copied cygwin environments gnuplot runs without problem.

I will reconstruct the cygwin enviromments. 

> ----- Original Message -----
> 
> From: "Ethan A Merritt" <me...@uw...>
> To: "beta" <gnu...@li...>
> Cc: "Tatsuro MATSUOKA" <tma...@ya...>
> Date: 2022/02/04 金 09:44
> Subject: Re: How to get the previous image of git of master baranch
> 
> 
> On Thursday, 3 February 2022 14:38:34 PST Tatsuro MATSUOKA wrote:
> > Please show me tbe way to get the previous image git go master branch.
> 
> Go back exactly one commit:
> 
>      git checkout HEAD~1
> 
> Go back to a commit that you know by number
> 
>      git checkout b992a505
> 
> Restore the state to where you started
> 
>      git checkout master
> 
> Ethan
> 
> > 
> > For my cygwin build of gnuplot on the development source, gnuplot does not run 
> > $ src/gnuplot
> > (nothing happen) 
> > $ 
> > (back to prompt)
> > 
> > I exucute gnuplot via gdb and set back trace to main but gnuplot ends.
> > 
> > I want to get the previous git source to see from what change causes the issue.
> > I note thar I could execute gnuplot 5.4.3 built myself.
> > 
> > Thank for advance.
> > 
> > Tatsuro
> 
> 
> 

Re: How to get the previous image of git of master baranch

[Ethan A M. <me...@uw...>]

On Thursday, 3 February 2022 14:38:34 PST Tatsuro MATSUOKA wrote:
> Please show me tbe way to get the previous image git go master branch.

Go back exactly one commit:

     git checkout HEAD~1

Go back to a commit that you know by number

     git checkout b992a505

Restore the state to where you started

     git checkout master

Ethan

> 
> For my cygwin build of gnuplot on the development source, gnuplot does not run 
> $ src/gnuplot
> (nothing happen) 
> $ 
> (back to prompt)
> 
> I exucute gnuplot via gdb and set back trace to main but gnuplot ends.
> 
> I want to get the previous git source to see from what change causes the issue.
> I note thar I could execute gnuplot 5.4.3 built myself.
> 
> Thank for advance.
> 
> Tatsuro

Re: Unicode in the postscript terminal

[Ethan A M. <me...@uw...>]

On Thursday, 3 February 2022 14:18:57 PST Tatsuro MATSUOKA wrote:
> A post was made for plot of unicode chracter.
> https://sourceforge.net/p/gnuplot/mailman/gnuplot-info/thread/66152bfa-127c-bb35-7068-91b0f215e705%40kaniuk.co.uk/#msg37602226
> 
> For interactive terminal it seems to be a problem of font selection.
> However,  in the postscript terminal,unicode character is not represented.

The PostScipt language does not support multi-byte encodings.
Therefore it does not support UTF-8 or any other "reasonable"
way to reference Unicode code points in general.

It is technically possible to extract a subset of Unicode entities
from a suitable font (probably *.ttf) and match them to PostScript
glyph assignments.  There are instructions and examples in the
file .../term/PostScript/unicode_maps.README

However it is not worth it.  Really it is not worth it.
The procedure is difficult, fragile, and does not extend well
to handle large numbers of Unicode gplyphs.

If you really require a *.ps file for some reason, it is better
to create a *.pdf file from gnuplot and then convert it from
pdf to PostScript in a separate step.  This has the added benefit
that PDF support transparency, which PostScript doesn't, and
the conversion will take care of that also.

But for most purposes it would be better to use the *.pdf file
and forget about PostScript.

set terminal pdf
set output 'myplot.pdf'
set encoding utf8
plot [1:10] \
    0.9*x w lp t "POINT"   pt "◎", \
    0.5*x w lp t "UNICODE" pt "\U+25CE", \
    0.2*x w lp t "HASH"    pt "#"
unset output
system("pdf2ps myplot.pdf myplot.ps")

	Ethan


> 
> The test script is :
> 
> #!/usr/bin/gnuplot -persist
> reset session
> set encoding utf8
> set terminal wxt 1 nopersist enhanced font 'Dejavu Sans'
> 
> unset key; set key on inside left
> 
> set samples 20
> 
> plot [1:10] \
> 0.9*x w lp t "POINT"   pt "◎", \
> 0.5*x w lp t "UNICODE" pt "\U+25CE", \
> 0.2*x w lp t "HASH"    pt "#"
> 
> set terminal push
> set terminal postscript eps enhanced color size 20 cm, 10 cm
> set output "test-pt.eps"
> replot
> set output
> set terminal pop
> #EOF    
> 
> I thouht that the postscript terminal cannot handle unicode.
> However Norwid provided the detailed analysis of eps file (test-pt.eps) created by the above script
> https://sourceforge.net/p/gnuplot/mailman/message/37602883/
> 
> With Inkscape (version 1.1.1) by internal import, one can see the unicode characters on the plot.
> (On Evince and Inksapce with poppler/cairo import (default), we cannot see unicode character. 
> In addtion, I also cannot see unicode chracters on gv , eps viewer and adobe reader (after coverted to pdf file))
> 
> Anyway, in the current state, the postscipt terminal cannot treat the unicode character properly.
> Am I right?
> 
> Tatsuro

How to get the previous image of git of master baranch

[Tatsuro M. <tma...@ya...>]

Please show me tbe way to get the previous image git go master branch.

For my cygwin build of gnuplot on the development source, gnuplot does not run 
$ src/gnuplot
(nothing happen) 
$ 
(back to prompt)

I exucute gnuplot via gdb and set back trace to main but gnuplot ends.

I want to get the previous git source to see from what change causes the issue.
I note thar I could execute gnuplot 5.4.3 built myself.

Thank for advance.

Tatsuro

Unicode in the postscript terminal

[Tatsuro M. <tma...@ya...>]

A post was made for plot of unicode chracter.
https://sourceforge.net/p/gnuplot/mailman/gnuplot-info/thread/66152bfa-127c-bb35-7068-91b0f215e705%40kaniuk.co.uk/#msg37602226

For interactive terminal it seems to be a problem of font selection.
However,  in the postscript terminal,unicode character is not represented.

The test script is :

#!/usr/bin/gnuplot -persist
reset session
set encoding utf8
set terminal wxt 1 nopersist enhanced font 'Dejavu Sans'

unset key; set key on inside left

set samples 20

plot [1:10] \
0.9*x w lp t "POINT"   pt "◎", \
0.5*x w lp t "UNICODE" pt "\U+25CE", \
0.2*x w lp t "HASH"    pt "#"

set terminal push
set terminal postscript eps enhanced color size 20 cm, 10 cm
set output "test-pt.eps"
replot
set output
set terminal pop
#EOF    

I thouht that the postscript terminal cannot handle unicode.
However Norwid provided the detailed analysis of eps file (test-pt.eps) created by the above script
https://sourceforge.net/p/gnuplot/mailman/message/37602883/

With Inkscape (version 1.1.1) by internal import, one can see the unicode characters on the plot.
(On Evince and Inksapce with poppler/cairo import (default), we cannot see unicode character. 
In addtion, I also cannot see unicode chracters on gv , eps viewer and adobe reader (after coverted to pdf file))

Anyway, in the current state, the postscipt terminal cannot treat the unicode character properly.
Am I right?

Tatsuro

Re: Translation of the manual into Italian

[Ethan A M. <me...@uw...>]

On Friday, 21 January 2022 08:24:18 PST s.lopoeta--- via gnuplot-beta wrote:

> we have translated the manual of Gnuplot version 5.4 into Italian
> and we have made it available on our website at the following page
> 
> https://www.bielle.it/opensource/gnuplot
> 
> We would love to see the URL added on the Gnuplot page
> 
> http://www.gnuplot.info/help.html
> 
> It's possible ?
> 
> The translation was done by Alice Lopoeta.

Translation of the manual into Italian

[<s.l...@bi...>]

Hello,

we have translated the manual of Gnuplot version 5.4 into Italian
and we have made it available on our website at the following page

https://www.bielle.it/opensource/gnuplot

We would love to see the URL added on the Gnuplot page

http://www.gnuplot.info/help.html

It's possible ?

The translation was done by Alice Lopoeta.

We hope there are no problems (copyright or otherwise) if so
tell us what needs to be done.

-- 
Stefano LOPOETA

BI ELLE Srl
Via Fattori, 75 -- 10141 TORINO
Tel. +39 0117725111
www.bielle.it

Re: Gnuplot Version 5.4.3 Release

[Tatsuro M. <tma...@ya...>]

I have built on windows in usual windows manner.
Build was successful and I confirmed windows terminal bug #2412 is fixed.

Tatsuro

> ----- Original Message -----
> 
> From: "Ethan A Merritt" <me...@uw...>
> To: "gnu...@li..." <gnu...@li...>
> Date: 2022/01/08 土 12:14
> Subject: Gnuplot Version 5.4.3 Release
> 
> 
> Release 5.4.3 is now out
> 
> Source tarball
> 
>     https://sf.net/projects/gnuplot/files/gnuplot/5.4.3/gnuplot-5.4.3.tar.gz
> 
> There is nothing special in this minor release. Mostly small fixes to
> individual terminals, configuration of byte-array data for little-endian
> platforms, and a few items back-ported from the development version.
> For a slightly more complete list of changes see the Release Notes.
> 
>     http://gnuplot.sourceforge.net/ReleaseNotes_5_4_3.html
> 
> 	happy gnuplotting,
> 
> 		Ethan 
> 
> 
> 
> 
> 
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Gnuplot Version 5.4.3 Release

[Ethan A M. <me...@uw...>]

Release 5.4.3 is now out

Source tarball

    https://sf.net/projects/gnuplot/files/gnuplot/5.4.3/gnuplot-5.4.3.tar.gz

There is nothing special in this minor release. Mostly small fixes to
individual terminals, configuration of byte-array data for little-endian
platforms, and a few items back-ported from the development version.
For a slightly more complete list of changes see the Release Notes.

    http://gnuplot.sourceforge.net/ReleaseNotes_5_4_3.html

	happy gnuplotting,

		Ethan 

Re: Test report for "make gnuplot-ja.pdf" on cygwin64

[Tatsuro M. <tma...@ya...>]

New modifications were carried out by Batian to config/mingw/Makefile etcs.

Now I could build gnuplot.pdf and gnuplot-ja.pdf on native windows using the MiKTeX and TeXLive on the cygwin64.

Thanks!

Tatsuro

> ----- Original Message -----

> On Wednesday, 5 January 2022 15:27:48 PST Hans-Bernhard Bröker wrote:
> > Am 05.01.2022 um 23:42 schrieb Ethan A Merritt:
> > > On Wednesday, 5 January 2022 13:26:09 PST Hans-Bernhard Bröker wrote:
> > 
> > >> * It doesn't work for out-of-source-tree builds, because of missing
> > >> $(srcdir)/ prefixes and a lack of TEXINPUTS addition of $(srcdir)
> > > 
> > > My understanding is that TEXINPUTS is disrecommended for luatex.
> > > Has that changed?
> > 
> > Dis-recommended or not, it simply doesn't work without it, because it 
> > cannot find title-ja.tex.  With the TEXINPUTS set, it works.
> 
> Maybe be some Windows quirk?
> 
> As noted in the commit message, this new rule for building the Japanese
> docs does not make any provision for building out of tree.
> It works fine for me as it is under linux, and Tatsuro Matsuoka reports
> that it works for him under Cygwin.
> I'm still tweaking the handling of cross-references, since the ad hoc
> rules in doc2tex were written assuming English text.
> 
> Prior to this, the method for processing the Japanese documentation
> was entirely outside of our build system.
> It used locale-customized packages that work with EUC-JP encoding.
> I never managed to get that mechanism working, so this was a fresh start.
> 
> If someone else has a need to extend it to other platforms, I leave it to them.  
> 
> 
> > There might be other methods to achieve this (copy title-ja.tex around, 
> > change the sed command to point to it with a path, ...), but that one 
> > seemed to fit in best with what we've been doing in the other cases.
> 
> 	cheers,
> 
> 		Ethan
> 
> 
> 
> 
> 
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

'license' directory. in windows package

[Tatsuro M. <tma...@ya...>]

In README-Windows.txt on windows package for 5.5 branch,
I found the decription

Licenses of these runtime libraries can be
  found in the 'license' directory.

zip or 7z archives does not have license directory
installer have license directory but it has only gnuplot copyright.

I have forgotten how license of other libraries were treated.
Those should be prepared in license direcory in extradist?

Thank you for advance.

Tatsuro 

Re: Test report for "make gnuplot-ja.pdf" on cygwin64

[Ethan A M. <me...@uw...>]

On Wednesday, 5 January 2022 15:27:48 PST Hans-Bernhard Bröker wrote:
> Am 05.01.2022 um 23:42 schrieb Ethan A Merritt:
> > On Wednesday, 5 January 2022 13:26:09 PST Hans-Bernhard Bröker wrote:
> 
> >> * It doesn't work for out-of-source-tree builds, because of missing
> >> $(srcdir)/ prefixes and a lack of TEXINPUTS addition of $(srcdir)
> > 
> > My understanding is that TEXINPUTS is disrecommended for luatex.
> > Has that changed?
> 
> Dis-recommended or not, it simply doesn't work without it, because it 
> cannot find title-ja.tex.  With the TEXINPUTS set, it works.

Maybe be some Windows quirk?

As noted in the commit message, this new rule for building the Japanese
docs does not make any provision for building out of tree.
It works fine for me as it is under linux, and Tatsuro Matsuoka reports
that it works for him under Cygwin.
I'm still tweaking the handling of cross-references, since the ad hoc
rules in doc2tex were written assuming English text.

Prior to this, the method for processing the Japanese documentation
was entirely outside of our build system.
It used locale-customized packages that work with EUC-JP encoding.
I never managed to get that mechanism working, so this was a fresh start.

If someone else has a need to extend it to other platforms, I leave it to them.  


> There might be other methods to achieve this (copy title-ja.tex around, 
> change the sed command to point to it with a path, ...), but that one 
> seemed to fit in best with what we've been doing in the other cases.

	cheers,

		Ethan

Re: Test report for "make gnuplot-ja.pdf" on cygwin64

[Hans-Bernhard B. <HBB...@t-...>]

Am 05.01.2022 um 23:42 schrieb Ethan A Merritt:
> On Wednesday, 5 January 2022 13:26:09 PST Hans-Bernhard Bröker wrote:

>> * It doesn't work for out-of-source-tree builds, because of missing
>> $(srcdir)/ prefixes and a lack of TEXINPUTS addition of $(srcdir)
> 
> My understanding is that TEXINPUTS is disrecommended for luatex.
> Has that changed?

Dis-recommended or not, it simply doesn't work without it, because it 
cannot find title-ja.tex.  With the TEXINPUTS set, it works.

There might be other methods to achieve this (copy title-ja.tex around, 
change the sed command to point to it with a path, ...), but that one 
seemed to fit in best with what we've been doing in the other cases.

Re: Test report for "make gnuplot-ja.pdf" on cygwin64

[Ethan A M. <me...@uw...>]

On Wednesday, 5 January 2022 13:26:09 PST Hans-Bernhard Bröker wrote:
> 
> The correct solution would be to call doc2tex like it's done in the rule 
> for gnuplot.pdf:
> 
> 	./doc2tex

OK.
 
> The new production rule for gnuplot-ja.pdf has a few other problems 
> beside that:
> 
> * It doesn't work for out-of-source-tree builds, because of missing 
> $(srcdir)/ prefixes and a lack of TEXINPUTS addition of $(srcdir)

My understanding is that TEXINPUTS is disrecommended for luatex.
Has that changed?

	Ethan


> * It doesn't list prerequisite doc2tex$(EXEEXT), so
> 
> 	make clean
> 	make gnuplot-ja.pdf
> 
>    will fail.
> 
> Generally this rule should be re-done to be much closer to that for 
> gnuplot.pdf.
> 
> 
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Re: Test report for "make gnuplot-ja.pdf" on cygwin64

[Hans-Bernhard B. <HBB...@t-...>]

Am 05.01.2022 um 07:57 schrieb Tatsuro MATSUOKA:
> Ethan
> 
> In development branch, make gnuplot-ja.pdf was supported.
> I tried the make on cygwin64 and  build and report the result.
> 
> cd docs
> make gnuplot-ja.pdf
> 
> iconv -f EUC-JP -t UTF-8 gnuplot-ja.doc > ja.doc
> doc2tex -figures ja.doc | sed 's/titlepag.tex/title-ja.tex/' > gnuplot-ja.tex
> /bin/sh: doc2tex: command not found
> 
> I confirmed doc2tex.exe is generated in docs direcotory .
> Workaorund is
> 
> cd docs
> PATH=$PATH:./ make gnuplot-ja.pdf
> 

The correct solution would be to call doc2tex like it's done in the rule 
for gnuplot.pdf:

	./doc2tex

The new production rule for gnuplot-ja.pdf has a few other problems 
beside that:

* It doesn't work for out-of-source-tree builds, because of missing 
$(srcdir)/ prefixes and a lack of TEXINPUTS addition of $(srcdir)

* It doesn't list prerequisite doc2tex$(EXEEXT), so

	make clean
	make gnuplot-ja.pdf

   will fail.

Generally this rule should be re-done to be much closer to that for 
gnuplot.pdf.

Test report for "make gnuplot-ja.pdf" on cygwin64

[Tatsuro M. <tma...@ya...>]

Ethan

In development branch, make gnuplot-ja.pdf was supported.
I tried the make on cygwin64 and  build and report the result.

cd docs
make gnuplot-ja.pdf

iconv -f EUC-JP -t UTF-8 gnuplot-ja.doc > ja.doc
doc2tex -figures ja.doc | sed 's/titlepag.tex/title-ja.tex/' > gnuplot-ja.tex
/bin/sh: doc2tex: command not found

I confirmed doc2tex.exe is generated in docs direcotory .
Workaorund is

cd docs
PATH=$PATH:./ make gnuplot-ja.pdf

Then I could get gnuplot-ja.pdf.

Thanks!

Tatsuro

Re: inquiry make documentation on native windows

[Hans-Bernhard B. <HBB...@t-...>]

Am 04.01.2022 um 08:04 schrieb Bastian Märkisch:

> I second that. But CMake could also (mostly) replace the automake/conf
> build mechanism and hence unify the build system.

IMHO, "mostly" is equivalent to "not" in this case.  As long as we still 
need some parts of the auto-foo stuff, we're better off keepin all of 
it.  It works, it does a lot for us, and covers a lot of corner cases.

I see CMake as useful only for those platforms that cannot use auto-foo,
most evidently Windows.

> For me, this at first started as a project to get to know CMake. 

Same here.

Re: Aw: Re: inquiry make documentation on native windows

[Dima K. <gn...@di...>]

> For me, this at first started as a project to get to know CMake. I
> propose to join efforts now to see if it turns out to be a viable and
> complete option. Personally, I use a private github repo at the
> moment. Hans-Bernhard, please let me know your thoughts on this.

Wait. Are we talking about redoing the whole gnuplot build system? If
so, can we please consider vanilla GNU Make? Makefiles are
straightforward to work with, and it's really nice to throw out the
cruft that cmake and autotools give you. I can put together a prototype,
if that's helpful.

Aw: Re: inquiry make documentation on native windows

[Bastian M. <bma...@we...>]

> Gesendet: Sonntag, 02. Januar 2022 um 14:18 Uhr
> Von: "Hans-Bernhard Bröker" <HBB...@t-...>
>
> Am 02.01.2022 um 08:56 schrieb Ethan A Merritt:
> 
> > Is it this file?
> >     .../config/mingw/Makefile >
> > How is that file generated?
> 
> It's not. All the actual makefiles in the "config" sub tree are 
> hand-written, except for the source file lists they import from the 
> generated src/makefile.all and src/makefile.awc.  The Makefile.am in 
> there is just for organizing the tarball.
> 
> There's a case to be made that a CMake setup could replace a large part 
> of those, particularly mingw, cygwin, msvc.  Among other things, that 
> could reduce the extra work of maintaining them all.

I second that. But CMake could also (mostly) replace the automake/conf 
build mechanism and hence unify the build system.
 
> I have a CMake script here that does most of what config/cygwin and 
> config/msvc achieve.  I haven't yet tried to add the extra work as done 
> by config/mingw: no TeX, no Japanese docs, etc.

I, too, have a prototype of a build system using CMake which currently 
(sort of) works for me with gcc on *nix, MinGW, MSVC, and OpenWatcom on
Windows, as well as gcc on OS/2. MacOS and Cygwin shouldn't be too hard to add.
Right now, it only covers building gnuplot and outbord terminals. It does not
cover packaging (sources, binaries, or installer), nor any documentation or
help files yet. It also still misses a number of tests.

For me, this at first started as a project to get to know CMake. I propose
to join efforts now to see if it turns out to be a viable and complete option.
Personally, I use a private github repo at the moment.
Hans-Bernhard, please let me know your thoughts on this.

  Bastian

Re: inquiry make documentation on native windows

[Tatsuro M. <tma...@ya...>]

Ethan

Thank you for updating the config/mingw/Makefile in the master branch.
https://sourceforge.net/p/gnuplot/gnuplot-main/ci/b838ebe0e44a28561f9193f307f15f3301cf654e/

Now we can build document by MiKTeX or TeXLive on windows environments in current development branch.

Tatsuro


> > ----- Original Message -----
> > 
> > 
> > 
> > On Sunday, 2 January 2022 14:36:59 PST Tatsuro MATSUOKA wrote:
> > > Ethan
> > > 
> > > Thank you for your reply again
> > > 
> > > Unfortunately the below patch gives a different error.
> > > On MikTeX
> > > 
> > > (f:\programs\MiKTeX\tex/latex/tools\longtable.sty)
> > > 
> > > LaTeX Warning: \include should only be used after \begin{document} on input lin
> > > e 42.
> > 
> > I have never seen that error message.
> > Perhaps this is a difference between MiKTeX and TexLive?
> > You could try changing the word "include" to "input" on line 42 of titlepag.tex
> > 
> >    % This is only needed if you want to embed figures
> > -  \include{gpinsetfigure}
> > +  \input{gpinsetfigure}
> 
> The change makes the warining disappeared 
> but even if  the change does not apply, results are the same.
> 
> 
>  
> > 
> > > (gpinsetfigure.tex
> > > 
> > > ! LaTeX Error: Command \gpinsetfigure already defined.
> > >                Or name \end... illegal, see p.192 of the manual.
> > 
> > This one makes no sense to me.
> > Please check the content of gpinsetfigure.tex
> > It should look like this:
> > 
> > [~/git/gnuplot-main/docs] cat gpinsetfigure.tex
> > \usepackage{graphicx}
> > \usepackage{picins}
> > \newcommand{\gpinsetfigure}[1]{
> >   \parpic[r][rt]{\includegraphics[width=3in,keepaspectratio]{#1}}
> > }
> I found two type mistakes in your patch
> Two "gpinsetfigures.tex" are found (not "gpinsetfigure.tex")
> 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> diff --git a/config/mingw/Makefile b/config/mingw/Makefile
> index 3c578b27e..cc0adcce5 100644
> --- a/config/mingw/Makefile
> +++ b/config/mingw/Makefile
> @@ -953,8 +953,11 @@ gnuplot.ps: gnuplot.dvi
>  
>  gnuplot.pdf: gnuplot-figures.tex $(TOP)/VERSION $(D)toc_entr.sty $(D)titlepag.tex
>  	cp gnuplot-figures.tex gp_tex2.tex
> -	echo "\usepackage{graphicx}" > pdffigures.tex
> -	echo "\usepackage{picins}" >> pdffigures.tex
> +	echo "\usepackage{graphicx}" > gpinsetfigures.tex  #  should be gpinsetfigure.tex
> +	echo "\usepackage{picins}" >> gpinsetfigures.tex # should be gpinsetfigure.tex
> +	echo "\newcommand{\gpinsetfigure}[1]{" >> gpinsetfigure.tex ; \
> +	echo "  \parpic[r][rt]{\includegraphics[width=3in,keepaspectratio]{#1}}" >> gpinsetfigure.tex ; \
> +	echo "}" >> gpinsetfigure.tex
>  	# Call LaTeX three times to get the toc right.
>  	TEXINPUTS=.:$(TOP):$(D):${TEXINPUTS}: pdflatex gp_tex2.tex
>  	TEXINPUTS=.:$(TOP):$(D):${TEXINPUTS}: pdflatex gp_tex2.tex
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
> After type mistakes are corrected, "make docs "with both MiKTeX and TeXLive on cygwin on native windows build are successful.
> 
> Please push corrected patch to the master branch.
> 
> Tatsuro
> 
> 
> 
> 
> 
> > There should be no "\end" in the file, and the definition of
> > gpinsetfigure should appear only once.
> > 
> > 	Ethan
> > 
> > > See the LaTeX manual or LaTeX Companion for explanation.
> > > Type  H <return>  for immediate help.
> > >  ...
> > > 
> > > l.6 }
> > > 
> > > ?
> > > 
> > > On TeXLive on cygwin
> > > 
> > > (/usr/share/texmf-dist/tex/latex/tools/longtable.sty)
> > > \@input{gpinsetfigure.aux}
> > > (./gpinsetfigure.tex
> > > 
> > > ! LaTeX Error: Command \gpinsetfigure already defined.
> > >                Or name \end... illegal, see p.192 of the manual.
> > > 
> > > See the LaTeX manual or LaTeX Companion for explanation.
> > > Type  H <return>  for immediate help.
> > >  ...
> > > 
> > > l.6 }
> > > 
> > > ?
> > > 
> > > 
> > > Tatsuro
> > > 
> > > 
> > > > ----- Original Message -----
> > > > 
> > >  
> > > > On Sunday, 2 January 2022 05:20:28 PST Tatsuro MATSUOKA wrote:
> > > > > Ethan
> > > > > Thank you for your reply.
> > > > > > 
> > > > > I attached the above patch, situation will be better but is not complete yet,
> > > > > I met the error below in both MikTeX on windows and TeXLive2021 on the cygwin64.
> > > > > 
> > > > > ****************************************************************************
> > > > > (gpinsetfigure.tex
> > > > > 
> > > > > ! LaTeX Error: Command \gpinsetfigure already defined.
> > > > >                Or name \end... illegal, see p.192 of the manual.
> > > > 
> > > > 
> > > > I apologize.  The patch I gave was incomplete.
> > > > It should also have changed the previous two lines in the Makefile.
> > > > Here is a more complete patch:
> > > > 
> > > > 	Ethan
> > > > 
> > > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> > > > diff --git a/config/mingw/Makefile b/config/mingw/Makefile
> > > > index 3c578b27e..cc0adcce5 100644
> > > > --- a/config/mingw/Makefile
> > > > +++ b/config/mingw/Makefile
> > > > @@ -953,8 +953,11 @@ gnuplot.ps: gnuplot.dvi
> > > >  
> > > >  gnuplot.pdf: gnuplot-figures.tex $(TOP)/VERSION $(D)toc_entr.sty $(D)titlepag.tex
> > > >  	cp gnuplot-figures.tex gp_tex2.tex
> > > > -	echo "\usepackage{graphicx}" > pdffigures.tex
> > > > -	echo "\usepackage{picins}" >> pdffigures.tex
> > > > +	echo "\usepackage{graphicx}" > gpinsetfigures.tex
> > > > +	echo "\usepackage{picins}" >> gpinsetfigures.tex
> > > > +	echo "\newcommand{\gpinsetfigure}[1]{" >> gpinsetfigure.tex ; \
> > > > +	echo "  \parpic[r][rt]{\includegraphics[width=3in,keepaspectratio]{#1}}" >> gpinsetfigure.tex ; \
> > > > +	echo "}" >> gpinsetfigure.tex
> > > >  	# Call LaTeX three times to get the toc right.
> > > >  	TEXINPUTS=.:$(TOP):$(D):${TEXINPUTS}: pdflatex gp_tex2.tex
> > > >  	TEXINPUTS=.:$(TOP):$(D):${TEXINPUTS}: pdflatex gp_tex2.tex
> > > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> > > > 
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > 
> > 
> > 
> > 
> 
> 
> 
> _______________________________________________
> gnuplot-beta mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta
> 

Re: inquiry make documentation on native windows

[Tatsuro M. <tma...@ya...>]

> ----- Original Message -----
> 
> From: "Ethan A Merritt" <me...@uw...>
> To: "beta" <gnu...@li...>; "Tatsuro MATSUOKA" <tma...@ya...>
> Date: 2022/01/03 月 09:04
> Subject: Re: inquiry make documentation on native windows
> 
> 
> On Sunday, 2 January 2022 14:36:59 PST Tatsuro MATSUOKA wrote:
> > Ethan
> > 
> > Thank you for your reply again
> > 
> > Unfortunately the below patch gives a different error.
> > On MikTeX
> > 
> > (f:\programs\MiKTeX\tex/latex/tools\longtable.sty)
> > 
> > LaTeX Warning: \include should only be used after \begin{document} on input lin
> > e 42.
> 
> I have never seen that error message.
> Perhaps this is a difference between MiKTeX and TexLive?
> You could try changing the word "include" to "input" on line 42 of titlepag.tex
> 
>    % This is only needed if you want to embed figures
> -  \include{gpinsetfigure}
> +  \input{gpinsetfigure}

The change makes the warining disappeared 
but even if  the change does not apply, results are the same.


 
> 
> > (gpinsetfigure.tex
> > 
> > ! LaTeX Error: Command \gpinsetfigure already defined.
> >                Or name \end... illegal, see p.192 of the manual.
> 
> This one makes no sense to me.
> Please check the content of gpinsetfigure.tex
> It should look like this:
> 
> [~/git/gnuplot-main/docs] cat gpinsetfigure.tex
> \usepackage{graphicx}
> \usepackage{picins}
> \newcommand{\gpinsetfigure}[1]{
>   \parpic[r][rt]{\includegraphics[width=3in,keepaspectratio]{#1}}
> }
I found two type mistakes in your patch
Two "gpinsetfigures.tex" are found (not "gpinsetfigure.tex")

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
diff --git a/config/mingw/Makefile b/config/mingw/Makefile
index 3c578b27e..cc0adcce5 100644
--- a/config/mingw/Makefile
+++ b/config/mingw/Makefile
@@ -953,8 +953,11 @@ gnuplot.ps: gnuplot.dvi
 
 gnuplot.pdf: gnuplot-figures.tex $(TOP)/VERSION $(D)toc_entr.sty $(D)titlepag.tex
 	cp gnuplot-figures.tex gp_tex2.tex
-	echo "\usepackage{graphicx}" > pdffigures.tex
-	echo "\usepackage{picins}" >> pdffigures.tex
+	echo "\usepackage{graphicx}" > gpinsetfigures.tex  #  should be gpinsetfigure.tex
+	echo "\usepackage{picins}" >> gpinsetfigures.tex # should be gpinsetfigure.tex
+	echo "\newcommand{\gpinsetfigure}[1]{" >> gpinsetfigure.tex ; \
+	echo "  \parpic[r][rt]{\includegraphics[width=3in,keepaspectratio]{#1}}" >> gpinsetfigure.tex ; \
+	echo "}" >> gpinsetfigure.tex
 	# Call LaTeX three times to get the toc right.
 	TEXINPUTS=.:$(TOP):$(D):${TEXINPUTS}: pdflatex gp_tex2.tex
 	TEXINPUTS=.:$(TOP):$(D):${TEXINPUTS}: pdflatex gp_tex2.tex
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

After type mistakes are corrected, "make docs "with both MiKTeX and TeXLive on cygwin on native windows build are successful.

Please push corrected patch to the master branch.

Tatsuro





> There should be no "\end" in the file, and the definition of
> gpinsetfigure should appear only once.
> 
> 	Ethan
> 
> > See the LaTeX manual or LaTeX Companion for explanation.
> > Type  H <return>  for immediate help.
> >  ...
> > 
> > l.6 }
> > 
> > ?
> > 
> > On TeXLive on cygwin
> > 
> > (/usr/share/texmf-dist/tex/latex/tools/longtable.sty)
> > \@input{gpinsetfigure.aux}
> > (./gpinsetfigure.tex
> > 
> > ! LaTeX Error: Command \gpinsetfigure already defined.
> >                Or name \end... illegal, see p.192 of the manual.
> > 
> > See the LaTeX manual or LaTeX Companion for explanation.
> > Type  H <return>  for immediate help.
> >  ...
> > 
> > l.6 }
> > 
> > ?
> > 
> > 
> > Tatsuro
> > 
> > 
> > > ----- Original Message -----
> > > 
> >  
> > > On Sunday, 2 January 2022 05:20:28 PST Tatsuro MATSUOKA wrote:
> > > > Ethan
> > > > Thank you for your reply.
> > > > > 
> > > > I attached the above patch, situation will be better but is not complete yet,
> > > > I met the error below in both MikTeX on windows and TeXLive2021 on the cygwin64.
> > > > 
> > > > ****************************************************************************
> > > > (gpinsetfigure.tex
> > > > 
> > > > ! LaTeX Error: Command \gpinsetfigure already defined.
> > > >                Or name \end... illegal, see p.192 of the manual.
> > > 
> > > 
> > > I apologize.  The patch I gave was incomplete.
> > > It should also have changed the previous two lines in the Makefile.
> > > Here is a more complete patch:
> > > 
> > > 	Ethan
> > > 
> > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> > > diff --git a/config/mingw/Makefile b/config/mingw/Makefile
> > > index 3c578b27e..cc0adcce5 100644
> > > --- a/config/mingw/Makefile
> > > +++ b/config/mingw/Makefile
> > > @@ -953,8 +953,11 @@ gnuplot.ps: gnuplot.dvi
> > >  
> > >  gnuplot.pdf: gnuplot-figures.tex $(TOP)/VERSION $(D)toc_entr.sty $(D)titlepag.tex
> > >  	cp gnuplot-figures.tex gp_tex2.tex
> > > -	echo "\usepackage{graphicx}" > pdffigures.tex
> > > -	echo "\usepackage{picins}" >> pdffigures.tex
> > > +	echo "\usepackage{graphicx}" > gpinsetfigures.tex
> > > +	echo "\usepackage{picins}" >> gpinsetfigures.tex
> > > +	echo "\newcommand{\gpinsetfigure}[1]{" >> gpinsetfigure.tex ; \
> > > +	echo "  \parpic[r][rt]{\includegraphics[width=3in,keepaspectratio]{#1}}" >> gpinsetfigure.tex ; \
> > > +	echo "}" >> gpinsetfigure.tex
> > >  	# Call LaTeX three times to get the toc right.
> > >  	TEXINPUTS=.:$(TOP):$(D):${TEXINPUTS}: pdflatex gp_tex2.tex
> > >  	TEXINPUTS=.:$(TOP):$(D):${TEXINPUTS}: pdflatex gp_tex2.tex
> > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> 
> 
> 
> 

Re: inquiry make documentation on native windows

[Ethan A M. <me...@uw...>]

On Sunday, 2 January 2022 14:36:59 PST Tatsuro MATSUOKA wrote:
> Ethan
> 
> Thank you for your reply again
> 
> Unfortunately the below patch gives a different error.
> On MikTeX
> 
> (f:\programs\MiKTeX\tex/latex/tools\longtable.sty)
> 
> LaTeX Warning: \include should only be used after \begin{document} on input lin
> e 42.

I have never seen that error message.
Perhaps this is a difference between MiKTeX and TexLive?
You could try changing the word "include" to "input" on line 42 of titlepag.tex

   % This is only needed if you want to embed figures
-  \include{gpinsetfigure}
+  \input{gpinsetfigure}


> (gpinsetfigure.tex
> 
> ! LaTeX Error: Command \gpinsetfigure already defined.
>                Or name \end... illegal, see p.192 of the manual.

This one makes no sense to me.
Please check the content of gpinsetfigure.tex
It should look like this:

[~/git/gnuplot-main/docs] cat gpinsetfigure.tex
\usepackage{graphicx}
\usepackage{picins}
\newcommand{\gpinsetfigure}[1]{
  \parpic[r][rt]{\includegraphics[width=3in,keepaspectratio]{#1}}
}

There should be no "\end" in the file, and the definition of
gpinsetfigure should appear only once.

	Ethan

> See the LaTeX manual or LaTeX Companion for explanation.
> Type  H <return>  for immediate help.
>  ...
> 
> l.6 }
> 
> ?
> 
> On TeXLive on cygwin
> 
> (/usr/share/texmf-dist/tex/latex/tools/longtable.sty)
> \@input{gpinsetfigure.aux}
> (./gpinsetfigure.tex
> 
> ! LaTeX Error: Command \gpinsetfigure already defined.
>                Or name \end... illegal, see p.192 of the manual.
> 
> See the LaTeX manual or LaTeX Companion for explanation.
> Type  H <return>  for immediate help.
>  ...
> 
> l.6 }
> 
> ?
> 
> 
> Tatsuro
> 
> 
> > ----- Original Message -----
> > 
>  
> > On Sunday, 2 January 2022 05:20:28 PST Tatsuro MATSUOKA wrote:
> > > Ethan
> > > Thank you for your reply.
> > > > 
> > > I attached the above patch, situation will be better but is not complete yet,
> > > I met the error below in both MikTeX on windows and TeXLive2021 on the cygwin64.
> > > 
> > > ****************************************************************************
> > > (gpinsetfigure.tex
> > > 
> > > ! LaTeX Error: Command \gpinsetfigure already defined.
> > >                Or name \end... illegal, see p.192 of the manual.
> > 
> > 
> > I apologize.  The patch I gave was incomplete.
> > It should also have changed the previous two lines in the Makefile.
> > Here is a more complete patch:
> > 
> > 	Ethan
> > 
> > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> > diff --git a/config/mingw/Makefile b/config/mingw/Makefile
> > index 3c578b27e..cc0adcce5 100644
> > --- a/config/mingw/Makefile
> > +++ b/config/mingw/Makefile
> > @@ -953,8 +953,11 @@ gnuplot.ps: gnuplot.dvi
> >  
> >  gnuplot.pdf: gnuplot-figures.tex $(TOP)/VERSION $(D)toc_entr.sty $(D)titlepag.tex
> >  	cp gnuplot-figures.tex gp_tex2.tex
> > -	echo "\usepackage{graphicx}" > pdffigures.tex
> > -	echo "\usepackage{picins}" >> pdffigures.tex
> > +	echo "\usepackage{graphicx}" > gpinsetfigures.tex
> > +	echo "\usepackage{picins}" >> gpinsetfigures.tex
> > +	echo "\newcommand{\gpinsetfigure}[1]{" >> gpinsetfigure.tex ; \
> > +	echo "  \parpic[r][rt]{\includegraphics[width=3in,keepaspectratio]{#1}}" >> gpinsetfigure.tex ; \
> > +	echo "}" >> gpinsetfigure.tex
> >  	# Call LaTeX three times to get the toc right.
> >  	TEXINPUTS=.:$(TOP):$(D):${TEXINPUTS}: pdflatex gp_tex2.tex
> >  	TEXINPUTS=.:$(TOP):$(D):${TEXINPUTS}: pdflatex gp_tex2.tex
> > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> > 
> > 
> > 
> > 
> 
> 

Re: inquiry make documentation on native windows

[Tatsuro M. <tma...@ya...>]

Ethan

Thank you for your reply again

Unfortunately the below patch gives a different error.
On MikTeX

(f:\programs\MiKTeX\tex/latex/tools\longtable.sty)

LaTeX Warning: \include should only be used after \begin{document} on input lin
e 42.

(gpinsetfigure.tex

! LaTeX Error: Command \gpinsetfigure already defined.
               Or name \end... illegal, see p.192 of the manual.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
 ...

l.6 }

?

On TeXLive on cygwin

(/usr/share/texmf-dist/tex/latex/tools/longtable.sty)
\@input{gpinsetfigure.aux}
(./gpinsetfigure.tex

! LaTeX Error: Command \gpinsetfigure already defined.
               Or name \end... illegal, see p.192 of the manual.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help.
 ...

l.6 }

?


Tatsuro


> ----- Original Message -----
> 
 
> On Sunday, 2 January 2022 05:20:28 PST Tatsuro MATSUOKA wrote:
> > Ethan
> > Thank you for your reply.
> > > 
> > I attached the above patch, situation will be better but is not complete yet,
> > I met the error below in both MikTeX on windows and TeXLive2021 on the cygwin64.
> > 
> > ****************************************************************************
> > (gpinsetfigure.tex
> > 
> > ! LaTeX Error: Command \gpinsetfigure already defined.
> >                Or name \end... illegal, see p.192 of the manual.
> 
> 
> I apologize.  The patch I gave was incomplete.
> It should also have changed the previous two lines in the Makefile.
> Here is a more complete patch:
> 
> 	Ethan
> 
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> diff --git a/config/mingw/Makefile b/config/mingw/Makefile
> index 3c578b27e..cc0adcce5 100644
> --- a/config/mingw/Makefile
> +++ b/config/mingw/Makefile
> @@ -953,8 +953,11 @@ gnuplot.ps: gnuplot.dvi
>  
>  gnuplot.pdf: gnuplot-figures.tex $(TOP)/VERSION $(D)toc_entr.sty $(D)titlepag.tex
>  	cp gnuplot-figures.tex gp_tex2.tex
> -	echo "\usepackage{graphicx}" > pdffigures.tex
> -	echo "\usepackage{picins}" >> pdffigures.tex
> +	echo "\usepackage{graphicx}" > gpinsetfigures.tex
> +	echo "\usepackage{picins}" >> gpinsetfigures.tex
> +	echo "\newcommand{\gpinsetfigure}[1]{" >> gpinsetfigure.tex ; \
> +	echo "  \parpic[r][rt]{\includegraphics[width=3in,keepaspectratio]{#1}}" >> gpinsetfigure.tex ; \
> +	echo "}" >> gpinsetfigure.tex
>  	# Call LaTeX three times to get the toc right.
>  	TEXINPUTS=.:$(TOP):$(D):${TEXINPUTS}: pdflatex gp_tex2.tex
>  	TEXINPUTS=.:$(TOP):$(D):${TEXINPUTS}: pdflatex gp_tex2.tex
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> 
> 
> 
>