I tested a number of fonts in vDosXy and used the full filenames, e.g.,
FreeMonoBold.ttf,
Paul
Paul Lagasse
pglagasse@xxxxxxxxxxx
On 06/13/2016 09:19 PM, Wengier W (Redacted sender wengierwu for DMARC)
wrote:
Hi Carl,
I am not sure about vDosXy but it is certainly not true for vDos-lfn. The file Nouveau_IBM.ttf (in its original name) is shipped with recent builds of vDos-lfn and works very well with it. Indeed, vDos-lfn is in no way limited to 8.3 names (remember that "lfn" stands for long file names). Thus, you can safely revert to the original file name with the vDos-lfn for XyWrite installation.
Sincerely,
Wengier
On Monday, June 13, 2016 9:02 PM, Carl Distefano <cld@xxxxxxxxxx> wrote:
Reply to note from Wengier W <wengierwu@xxxxxxxxx <mailto:wengierwu@xxxxxxxxx>> Tue, 14 Jun 2016
00:28:46 +0000 (UTC)
Wengier,
I was wondering about the Nouveau_IBM font filename as well. I added
that font to the package when vDosXy first came out in the Fall of
2014. I was under the impression that CONFIG.TXT at that time required
8.3 filenames, so I renamed it to NOUVEAU1.TTF. Maybe that is not true
with vDos-lfn. If CONFIG.TXT under vDos-lfn accepts LFNs, then I think
we should go with the original filename of Nouveau_IBM.ttf.
Best,
Carl
