I have made a mistake to delete the post. So I re-post.
The report I submit might not be a bug.
The topic has been disscussed in octave bug tracker.
https://savannah.gnu.org/bugs/?49135
set terminal windows
set title "title" font ":Bold,15"
plot x
This does not give no warning.
However if I use enhanced mark like "^"
set terminal windows
set title "title^1" font ":Bold,15"
plot x
The above gives warnings:
Warning: font ":Bold" not available, trying "Arial" instead.
Warning: font ":Bold" not available, trying "Arial" instead.
Warning: font ":Bold" not available, trying "Arial" instead.
Warning: font ":Bold" not available, trying "Arial" instead.
Warning: font ":Bold" not available, trying "Arial" instead.
However,
set terminal windows
set title "{/:Bold tilte^1}" font ",15"
plot x
and
set terminal windows
set title "{/:Bold=15 tilte^1}"
plot x
does not give warnings.
Is the above behavior a bug or a feature?
BTW, in case of wxt terminal,
set terminal wxt
set title "title" font ":Bold,15"
plot x
gives Pango-WARNING
(gnuplot.exe:5012): Pango-WARNING **: couldn't load font "Bold Not-Rotated 300", falling back to "Sans Bold Not-Rotated 300", expect ugly output.
However, on cygwin and linux, the above does not give Pango-WARNING.
Like windows terminals
set terminal wxt
set title "{/:Bold tilte^1}" font ",15"
plot x
or
set terminal wxt
set title "{/:Bold=15 tilte^1}"
plot x
does not give warning.
In the case of wxt, behavior onwindows perhaps reply on fontconfig settting.
On the qt terminal, no warnigs appeared in all cases shown in the above.
I do not know reason but the above is not reproduced now at any version of ver.5.
Perhaps some windows update are related.
Last edit: Tatsuro MATSUOKA 2017-03-03
Indeed the warning message is an error. An empty font face should be accepted. The reason why the message disappeared in 5.1 is that the message was only triggered by the GDI code path, which the default 5.0 GDI+ still used for enhanced text.
Now fixed in CVS.
Thanks for the fix. I have confirmed that the issue disappeared in the current cvs.
Will this correction be applied to the 5.0 branch source (for 5.0.7)?
Yes. It already is applied to 5.0, too.