psdoc: avoid missing characters in TeX font lasy
docs: airy Ai Bi
Here is a proper fix that avoids the missing characters.
Attached is a patch that removes the LASY10 column from the document. Does this work for you?
I can reproduce the error messages from texlive2025, but as you say the output pdf file seems correct. Switching to lualatex and font wasy yields similar error messages and a similar pdf output file. I take it you are invoking the "make pdf" from inside something else (rpmbuild?) Is there a way to tell it to ignore the error? Can you remove the .../docs/psdoc make target from your build script? I suspect that the entire mechanism being documented - embedding Type 1 fonts in a PostScript file output...
ps_fontfile_doc.pdf fails to build with texlive 20250308
plot style "with labels" silently ignores "noenhanced" setting
checking for plot title should not consume "noenhanced"
protect against segfault in test for nonlinear axis
differentiate between "replot" and "remultiplot"
Well, EUC-JP string "2025\xc7\xaf" are printed correctly for set encoding locale, set encoding "EUC_JP", and without "set encoding" command. The compound string of EUC-JP character and "\U+xxxx" are also printed correctly for the same situation. Thank you.
I tested current git version. Then the script all.dem stopped at the command "test palette" in pm3d.dem. gnuplot> set encoding EUC_JP ^ line 68: unrecognized encoding specification; see 'help encoding'. I tested on wxt terminal, then the same message appeared for the case "set encoding locale": gnuplot> set encoding default gnuplot> test palette # no problem gnuplot> set encoding locale gnuplot> test palette gnuplot> set encoding EUC_JP ^ line 68: unrecognized encoding specification; see 'help encoding'....
It would have been possible to add large parts of this patch directly to libgd, which indeed would have been the better solution, but gnuplot would still have to be patched to utilize the new capabilities. Additionally, the changes in how antialiasing with this patch works in general are significant and I found it quite unlikely that such a long-established library would adopt them. Also, I do not have a lot of experience with these kind of libraries and although I have tested this patch quite a...
I'm traveling and will have alook ar your patch when I return next week. In the meantime, just a question. IsYour code something that could be added to the libgd library itself? If so that would benefit not just gnuplot but all other users of the library. I have contributed fixes to libgd before so I know they are receptive. Thanks for your contribution.
Are patches still considered? Should I have posted this somewhere else?
As an example of what is possible with the new dashtype support, I have attached the output of the follwing example script: set samples 500 set xrange [0:4*pi] set yrange [-1.5:7.5] set xlabel "x" set ylabel "y" set title "Antialiased Dashed Lines Test" font ",14" set key right top box opaque set grid # Define line styles with different dash types and colors set style line 1 lc rgb "#E41A1C" lw 1 dt solid # Red - solid set style line 2 lc rgb "#377EB8" lw 2 dt 2 # Blue - dashed set style line 3 lc...
Full dashtype support for libgd terminals and improved antialiasing quality
plot style "with labels" silently ignores "noenhanced" setting
displaying key sample in "with pm3d" style with explicit fillcolor
'set mouse mouseformat' directly passing user defined format to 'snprintf()'
Do not disable mousing after a ^C
save axis mappings across a "reset" command
sixeltek: transparency and background options
allow plotting with dashtype specified by a numerical expression
malformed html on titlepage of html documentation
sixeltek terminal: transparency and background options
sixeltek: transparency and background options
Allow replacement of a single line in a data block
Thanks for catching that. It used to be k == 1, to at least have one sixel line written (and then it should now be k == ks) but from testing it seems the condition can be omitted entirely because a dash is output which moves to the next line. Incidentally, but I guess that is another ticket, the y-size should be a multiple of 6 for sixels. And setting the size to for example 640,366 the image is not complete with the "test" command; this used to be the correct with earlier gnuplot versions, before...
In file included from term.h:170, from term.c:1311: ../term/tek.trm: In function ‘SIXEL_text’: ../term/tek.trm:817:57: warning: self-comparison always evaluates to true [-Wtautological-compare] 817 | if (n < b_xsize-1 || pc != '?' || k == k) { /* do not output empty lines */ | ^~ What is the intent here?
sixeltek terminal: transparency and background options
The clear screen escape sequence is sent by term_reset(), which is invoked when you either (1) made another plot, (2) change the terminal type or settings, or (3) exit the program. I believe the intent was that the plot would remain visible on your screen until you did one of those things. However the "set output" / "unset output" commands are treated as changed the terminal settings. term_reset() appends the clear screen sequence to the output file when it is closed. This is/was probably not ideal...
ReGIS output cleared after display
Improvement of datablock size retrieval performance
Thank you for accepting the feature request and implementing the fix! I really appreciate it. This will make working with large datablocks much more practical.
The difference will go away if you tell the program to treat a coordinate whose value is found to be NaN the same as a coordinate that is missing from the input data. set datafile missing NaN The next question is obviously "why does $2*$1/$1 evaluate to NaN while $2+10 apparently does not?". Good question. When reading in a line of data, the program returns an error flag DF_MISSING to indicate that a required coordinate is missing. The test for that condition is trivial if the coordinate is simply...
Sorry, that should have been commit 7f0dfb24
I had to wrap the character array in a new structure typedef struct data_array { struct array_header header; char **data; } data_array; Commit 42849f98 It was not too messy, although it introduces additional steps in initializing the data block. I think I found everywhere that need modification, but I almost missed a spot in the "test palette" code so I worry a bit that I might also have missed some other non-obvious case. Timing is now equivalent for your test cases: [~/git/gnuplot/src] ./gnuplot...
wrap the lines of a datablock (or function block) in a structure
Improvement of datablock size retrieval performance
6.0.4 does not compile with BACKWARD_COMPATIBILITY
Thanks.
fix: compile failure if BACKWARD_COMPATIBILITY is defined
mouse zoom: The z-axis settings were lost during zoom
6.0.4 does not compile with BACKWARD_COMPATIBILITY
gd: EUC-JP to UTF-8 conversion for output to the gd terminals
qt: EUC-JP to UTF-8 conversion for output to the qt terminal
cairo terminals: Expand unicode escape sequences for non-utf8 encodings
I was thinking about it the wrong way. The cairo terminals already convert all text to UTF-8. Either it was recognized as UTF-8 or it was run through g_convert to make it UTF-8. So at that point it is OK to expand the Unicode escape sequences \U+acbd into more UTF-8. I made that change, and it seems to work. Your EUC-JP strings can now include Unicode escape sequences if the locale is recognized, but only for the cairo terminals. I will look to see if any other terminals can do something similar....
The current gnuplot seems to permit the \U+xxxx sequence only for S_ENC_UTF8. I agree that we can not use \U+xxxx for S_ENC_EUCJP. Because EUC-JP table include greek alphabets and some simple symbols, we cant put them directly. The user which wants to use any special character not in EUC-JP table may use "set encoding utf8" and UTF-8 script. Well, I found the function strlen_sjis() for gp_strlen() in encoding.c, so the function strlen_eucjp() may be need for S_ENC_EUCJP. Standard EUC-JP is 8bit 2byte...
cairo terminals: Expand unicode escape sequences for non-utf8 encodings
keep a copy of the encoding (LC_CTYPE) of the run environment
cairo terminals: fixup for recognition of EUC-JP encoding
I think I see an additional problem. How should we handle Unicode escape sequences? For example to create a label containing a Greek letter pi: 2π * x it should be possible to use an escape sequence set label "2\U+03C0 * x". The program knows how to convert this to a UTF-8 character sequence that would be accepted by the cairo terminals. But with this change in place the call to iconv would try to convert this byte sequence as if it were EUC-JP and give the error Unable to convert "2π": the sequence...
Thanks for your sooner reply and adding S_ENC_EUCJP. I tested modified code for the script set term wxt set encoding # set encoding locale # set encode default set title "2025[\xc7\xaf]" plot x They do not display japanese title correctly, and in the case "set encoding locale" gnuplot says warning: Error converting locale "ja_JP.eucJP" to codepage number Only in the case set encoding "EUC_JP" gnuplot displays the Japanese string correctly, because the name "EUC_JP" is added in encoding_names[] of...
You are correct that g_utf8_validate() should not be called if the current character encoding is known to be something other than utf8. I will need your assistance to figure out how to test for this correctly so that it handles your situation. Short answer I have added an internal value S_ENC_EUCJP and attempted to modify the code for set encoding locale so that it detects EUC-JP as the current encoding. The change works under linux but I cannot test under Windows. The git commit is d2ee58da8b6....
You are correct that g_utf8_validate() should not be called if the current character encoding is known to be something other than utf8. I will need your assistance to figure out how to test for this correctly so that it handles your situation. Short answer I have modified added an internal value S_ENC_EUCJP and attempted to modify the code for set encoding locale so that it detects EUC-JP as the current encoding. The change works under linux but I cannot test under Windows. The git commit is d2ee58da8b6....
cairo terminals: Try to handle a locale with encoding EUC-JP
You are correct that g_utf8_validate() should not be called if the current character encoding is known to be something other than utf8. I will need your assistance to figure out how to test for this correctly so that it handles your situation. Short answer I have modified added an internal value S_ENC_EUCJP and attempted to modify the code for set encoding locale so that it detects EUC-JP as the current encoding. The change works under linux but I cannot test under Windows. The git commit is d2ee58da8b6....
wxt terminal fails to display some Japanese (EUC-JP) string
</body></html> in the middle of gnuplot6.html in docs/html/
Yes, you are correct. Happy New Year!
malformed html on titlepage of html documentation
multiplot mousing: Save state to a datablock just prior to a multiplot
new function: save_set_to_datablock(char *datablock_name)
mouse zoom: The z-axis settings were lost during zoom
free-and-null() in unset.c
save: If the visible axis properties have not changed, save as "unset"
save: distinguish between blank axis label and no axis label at all
sixel, kitty: restore default terminal size on linux
gd: Revise font handling to match libgd 2.4.0 and libraqm 0.10.3
bump patchlevel to 6.0.5alpha to identify builds made between 6.0.4 and 6.0.5
Windows 6.03: unclear logic of gaps in the plot
allow "string"[i] as shorthand for "string"[i:i]
</body></html> in the middle of gnuplot6.html in docs/html/
mouse coordinate read-out in multiplot mode
sixel, kitty: restore default terminal size on linux
Warn about libgd font issues in the 6.0.4 Release Notes
unreadable label on y-axis in png output
Fixed in 6.1, but only confirmed for libgd version 2.4.0 and libraqm version 0.10.3 Some earlier versions of libgd also work, but only if they are configured to not use libraqm. I have not found any way to make gnuplot work around incompatible versions of libgd and libraqm. The libharfbuzz version may also be relevant (raqm uses it) but I did not pursue that.
gd: Revise font handling to match libgd 2.4.0 and libraqm 0.10.3
FWIW this is not specific to the Windows help, but applies also to gnuplot.gih, gnuplot's text-based help system. Many (none?) of the two-letter acronyms like "pt", "ps", "dt", "lc, "lt", "lw" seem to be indexed.
mingw/woa: fix installation of demo files
Colons need to be entered as tags for the OS/2 help
Test for ioctl.h header is not sufficient
os2: enforce C99 with old compilers and extend inttypes
os2: sync with configure.hin
djgpp: fix demo binary files and change defaults
djgpp: sync with configure.hin