Re: [Tuxpaint-devel] UI font configuration

[Bill K. <nb...@so...>]

On Sat, Jun 03, 2023 at 11:07:34PM +0900, Shin-ichi TOYAMA wrote:
> Hi!
> 
> >> [Tux Paint Config]
> >> * It would be benefical if user could select a font from available font list.
> >
> >Done.  I opted for an Fl_Hold_Browser, which was much better
> >than trying to use a pulldown menu (Fl_Choice), as I have
> >around 450 fonts installed!  I couldn't get Fl_Input_Choice
> >to do what I want... not at <checks clock> 2am in the morning. :)
> 
> Now it looks perfect for me. Thanks!
> 
> But, unfortunately, it's uifont configuration has become no longer
> effective.
> 
> On the other hand, using --uifont option seems to has no problem.
> 
> I enabled debug message and saw the result as follows.
> 
> ----
> Requested UI font described by ""GJGothicPNSubset""
> Actual UI font will be "$B#M#S(B $B%4%7%C%/(B"
> ----
> 
> I think double "doube quatation" around the font name is suspicious.

Ah, I had to make sure font names were quoted, EVEN IN THE
CONFIG FILE, because I guess the `parse` code we use would
stop when it hit a space.

So e.g. if I had this in my ~/.tuxpaintrc

  uifont=DejaVu Sans

It was doing this:

  Requested UI font described by "DejaVu"
  Actual UI font will be "Noto Sans"

So please `git pull` the master branch of the "tuxpaint"
repo and rebuild.  If it still doesn't work, let me know,
and I'll blame it on another late-night coding session. ;)

Tux Paint Config. does NOT use the same "parse" code, so
it will now trim quotes IF it finds them at the beginning
and end of the "uifont=" setting, but ALSO always ADD THEM.

I should update OPTIONS docs to make this explicit.
I also now wonder about other options that might need quotes
(e.g., "printcmd", admittedly rarely, if ever, used in the
wild, I assume) and never had them! :^o

-- 
-bill!
Sent from my computer