Missing directory warning with BDF-converted font in TEdit

[pamoroso]

I used READ-BDF to convert to displayfonts the ComicSans and Commodore 64 BDF fonts, which I saved under ~/il/fonts/ on my Linux Mint box. The resulting directory structure is:

├── fonts
│   ├── ComicSans
│   │   ├── c0
│   │   ├── c341
│   │   ├── c342
│   │   ├── c343
│   │   ├── c344
│   │   ├── c346
│   │   ├── c353
│   │   ├── c354
│   │   ├── c356
│   │   ├── c357
│   │   ├── c360
│   │   ├── c361
│   │   ├── c362
│   │   ├── c375
│   │   ├── c41
│   │   ├── c42
│   │   ├── c43
│   │   ├── c44
│   │   ├── c46
│   │   ├── c47
│   │   ├── c50
│   │   └── c56
│   └── Commodore
│       ├── c0
│       ├── c341
│       ├── c342
│       ├── c343
│       ├── c354
│       ├── c356
│       ├── c357
│       ├── c375
│       ├── c41
│       ├── c42
│       └── c43

In my init file I added the relevant directories to my DISPLAYFONTDIRECTORIES:

(SETQ DISPLAYFONTDIRECTORIES
      (APPEND '("{DSK}<home>paolo>il>fonts>Commodore>" 
                "{DSK}<home>paolo>il>fonts>ComicSans>"
                "{DSK}<home>paolo>il>fonts>")
              DISPLAYFONTDIRECTORIES))

However, when I click Other in TEdit's charlooks menu to load Comic Sans 15 I get this warning:

Can't enumerate {DSK}<home>paolo>il>fonts>c0>COMICSANS*-*C0.DISPLAYFONT;* because non such directory

Other than that, clicking APPLY does apply the change and the font is usable elsewhere on the system:

Why the warning? Medley seems to expect the font to be under ~/il/fonts/ rather than in subdirectories. Is there anything wrong with my setup?

[masinter]

This isn't an answer but a hint for where to look for the problem.

It looks like the problem has to do with the case of the directories -- ComicSans vs COMICSANS
Somewhere it is trying to enumerate the files in the directory ... Medley tries to mimic a case insensitive file system. Interlisp uses atoms (symbols) as file names and often uses EQ testing to see if two filenames match. But when you enumerate a directory you don't get EQ equivalence... that is, INFILEP is case insensitive, but (MEMB filename (DIRECTORY filedirectory)) is false.

[pamoroso]

I renamed the ComicSans and COMMODORE fonts to all caps and updated DISPLAYFONTDIRECTORIES but I still get the same warning.

[nbriggs]

Use the force, Paolo:

(TRACE INFILEP)
(CL:WITH-OPEN-FILE (*TRACE-OUTPUT* "{unix}/tmp/fonttrace.txt" :DIRECTION :OUTPUT)
   (FONTCREATE  'COMICSANS 15 'MRR 0 'DISPLAY T 0))
(UNTRACE INFILEP)

then go and look at /tmp/fonttrace.txt for what files it tried to open - relate those back to the font directories you have set up and see why it might not be looking in the place you put the fonts.

I suggest capturing the trace output in a file because it's probably longer than you can see in the (non-scrollable) trace window it would otherwise create.

[masinter]

you might also try TRACE DIRECCTORY too

[nbriggs]

Yes, TRACE DIRECTORY if you're doing FONTSAVAILABLE with the CHECKFILESTOO flg -- otherwise I believe it constructs exactly the possible names for the font file and checks each one.

[nbriggs]

I'm not sure if TEDIT just does FONTSAVAILABLE - that's something else to TRACE or BREAK when you're looking at what it did when you tried to set the font from TEDIT. I think it would be an error if TEDIT did its own enumeration, and given that you gave it a font name and it should have derived all other parameters from the font you were changing from, I think that FONTCREATE is the path it should have taken. @rmkaplan - comments?

[nbriggs]

I looked at the traces for DIRECTORY and FONTSAVAILABLE when called from TEDIT - FONTSAVAILABLE expects that every directory named on DISPLAYFONTDIRECTORIES will have a "Cnnn" (e.g., C0) subdirectory for any character set nnn that you might be asking for.
I would bet that "{DSK}paolo>il>fonts>" doesn't have a "c0" subdirectory... if it doesn't have any fonts at that level why is it on the DISPLAYFONTDIRECTORIES list?

[MattHeffron]

It looks to be under FONTSAVAILABLE however, I cannot reproduce this.
I created the full.sysout loadup from scratch
I added folders for each font family, with the character set folders beneath.

I edited DISPLAYFONTDIRECTORIES to include each of the family folders.

I opened an existing Tedit file. Opened the Character Looks expanded menu.
Entered SourceCodePro into the other family: {} field.
Clicked Other.
Set the Size to 10.
Selected some existing text in the document.
Clicked Apply in the menu.
The font change was applied with no warnings.

I wonder if it is getting confused by the entry that is the directory containing the FamilyName directories.

Edit: Now looking back at the message you're getting, that's what appears to be the problem.

[pamoroso]

With my initial font setup I used Nick's code to trace INFILEP and DIRECTORY and this is the output, but DIRECTORY wasn't called:

1 - Enter INFILEP:
          FILE = "<c0>c0>COMICSANS15-MRR-C0.DISPLAYFONT"
1 - Exit INFILEP =>
          NIL
1 - Enter INFILEP:
          FILE = "<c0>COMICSANS15>c0>COMICSANS15-MRR-C0.DISPLAYFONT"
1 - Exit INFILEP =>
          NIL
1 - Enter INFILEP:
          FILE = "<c0>c0>COMICSANS15-MRR-C0.DISPLAYFONT"
1 - Exit INFILEP =>
          NIL
1 - Enter INFILEP:
          FILE = "<c0>COMICSANS15>c0>COMICSANS15-MRR-C0.DISPLAYFONT"
1 - Exit INFILEP =>
          NIL
1 - Enter INFILEP:
          FILE = "{DSK}<home>paolo>il>fonts>Commodore>c0>COMICSANS15-MRR-C0.DISPLAYFONT"
1 - Exit INFILEP =>
          NIL
1 - Enter INFILEP:
          FILE = "{DSK}<home>paolo>il>fonts>ComicSans>c0>COMICSANS15-MRR-C0.DISPLAYFONT"
1 - Exit INFILEP =>
          {DSK}<home>paolo>il>fonts>COMICSANS>c0>ComicSans15-MRR-C0.DISPLAYFONT;1

Nick is right, "{DSK}paolo>il>fonts>" doesn't have any "Cnnn" subdirectories as /il/fonts contains only ComocSans and Commodore.

[pamoroso]

Interestingly, I get similar warnings also for Medley system fonts such as TimesRomand 36, not just BDF ones. But otherwise the fonts are used correctly.

[rmkaplan]

I'll just note that part of the medleyfont cleanup is to bring all the character sets for each font into a single file, and to depend on the subdirectory structure (hopefully, just during a transition period) only for legacy font files.

I think the tools for doing that, at least for the BDF fonts that can be created in MCCS from the start, are in the draft PR. I have to write and push the documentation.