bugThe FreeType Project - Bugs: bug #33660, Remove automatic addition of...

 
 

bug #33660: Remove automatic addition of extensions to ft2demo tools

Submitted by:  Christopher Yeleighton <yecril71pl>
Submitted on:  Mon 27 Jun 2011 01:05:44 PM UTC  
 
Severity: 3 - NormalItem Group: None
Status: FixedPrivacy: Public
Assigned to: Werner LEMBERG <wl>Open/Closed: Closed
Planned Release: 2.4.9

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission Jump to the original submission)

Fri 02 Mar 2012 09:33:25 PM UTC, comment #18:

This is now implemented in git.

Werner LEMBERG <wl>
Project AdministratorIn charge of this item.
Sat 20 Aug 2011 06:41:27 AM UTC, comment #17:

I'll slightly change the implementation for AFM: Instead of checking the extension, I'll add code to test whether the font format is Type 1. Then a file with extension .afm or .pfm gets added if available. Interestingly, I've never seen AFM files without extension `.afm'. Since PFM files are part of Windows, the extension `.pfm' is mandatory.

Werner LEMBERG <wl>
Project AdministratorIn charge of this item.
Sat 20 Aug 2011 06:28:59 AM UTC, comment #16:

OTOH, I believe that the real reason the font finder was implemented was to pull the associated font metrics where available. Since the font metrics is provided as a separate file, we cannot get rid of this feature completely unless we extend the command line to accept the metrics file as a separate parameter.

Christopher Yeleighton <yecril71pl>
Sat 20 Aug 2011 06:21:18 AM UTC, comment #15:

In view of that, it would be good to advertise the existence of docs/formats.txt in the help message instead (I did not know it exists until you directed me to it).

Christopher Yeleighton <yecril71pl>
Sat 20 Aug 2011 05:54:26 AM UTC, comment #14:

Thanks for the links. I think that CPI fonts have no importance for FreeType, but I invite you to write a driver which I can add then :-)

FOT files are definitely no fonts; the information contained in those files are of no importance to FreeType. See http://www.fileinfo.com/extension/fot for an explanation what those files are good for.

IntelliFont is proprietary, no public specification is available. Consequently there is no support.

Regarding extensions, there are much more which are of interest, and many of them are even important: .pfr, .otf, .pcf.gz, .pcf.Z, .pcf.bz2, .cff, .cid, ...

Your constant nagging (which is good!) has eventually convinced me to remove the automatic addition of extensions. It's just confusing, and the benefit is very small.

Werner LEMBERG <wl>
Project AdministratorIn charge of this item.
Fri 19 Aug 2011 08:16:00 AM UTC, comment #13:

My bad, s/CGI/CPI/ (unsupported, editable with DFE.EXE). FreeDos has them compressed to CPX.

I do not know what FOT [1] is, except that it accompanies TrueType fonts in Microsoft Windows.

IFT is Intellifont [2], used in Amiga and by mtex.

Apple FNT resources (suitcase) is not supported.

AIUI, the additional font formats supported are thus BDF, PCF and FON (three). Not too many to mention, IMHO, given the space occupied by the explanation regarding scalable fonts.

_
[CPI] <URL: http://www.win.tue.nl/~aeb/linux/kbd/font-formats-3.html >
[FOT] <URL: http://support.microsoft.com/kb/84651 >
[IFT] <URL: http://en.wikipedia.org/wiki/Intellifont >

Christopher Yeleighton <yecril71pl>
Thu 18 Aug 2011 09:46:46 PM UTC, comment #12:

If you look into the file docs/formats.txt, you can see all supported file formats.

FON is supported (but not its vector format). What is FOT? CGI is not supported – is the specification available somewhere? I've never heard of this format before. With `DVI' you probably mean TeX's PK and GF font formats, right? These formats are not supported since they are too special; in particular, they don't have a mapping from character codes to its glyph indices.

Borland fonts are proprietary, and no specification is available, AFAIK. I don't know what IFT is. ChiWriter fonts are proprietary also, AFAIK, and probably no specification either.

Werner LEMBERG <wl>
Project AdministratorIn charge of this item.
Thu 18 Aug 2011 11:00:03 AM UTC, comment #11:

Oh, I forgot about ChiWriter fonts :-)

Christopher Yeleighton <yecril71pl>
Thu 18 Aug 2011 10:57:09 AM UTC, comment #10:

I was, and still am, unable to figure out what these other font file types are. FOT? FON? CGI? DVI fonts? Borland Turbo fonts?
IFT? Do you support any of these?

Christopher Yeleighton <yecril71pl>
Thu 18 Aug 2011 04:38:15 AM UTC, comment #9:

Hmm. I don't like to mention BDF and PCF expliticly. There are many other font file extensions in the wild...

What about this:

The font file(s) to display, including the extension.
For files with extension `.pfa' or `.pfb',
ftview also tries to attach the corresponding metrics file
(with extension `.afm' or `.pfm').
If the extension is omitted, ftview tries to append one
of the following suffixes:
`.ttf', `.ttc', `.otf', `.pfa', `.pfb'.

Werner LEMBERG <wl>
Project AdministratorIn charge of this item.
Tue 16 Aug 2011 02:58:05 PM UTC, comment #8:

font The font file(s) to display; if the extension is omitted,
ftview tries to append one of the following suffixes:
`.ttf', `.ttc', `.otf', `.pfa', `.pfb'.
For `.pfa' or `.pfb' files, ftview also tries to attach
the corresponding metrics file (with extension
`.afm' or `.pfm'). Use the full file name for BDF and PCF fonts.

Christopher Yeleighton <yecril71pl>
Tue 16 Aug 2011 02:47:10 PM UTC, comment #7:

You are obviously missing the important part:

if the extension is omitted

If you don't omit the extension, it should work just fine.

Since you obviously misunderstand this, can you suggest a better formulation?

Werner LEMBERG <wl>
Project AdministratorIn charge of this item.
Tue 16 Aug 2011 02:43:13 PM UTC, comment #6:

Here is the new usage message from bin/ftview:

font The font file(s) to display; if the extension is omitted,
ftview tries to append one of the following suffixes:
`.ttf', `.ttc', `.otf', `.pfa', `.pfb'.
For `.pfa' or `.pfb' files, ftview also tries to attach
the corresponding metrics file (with extension
`.afm' or `.pfm').

As you can see, BDF support is not mentioned; your improvements have been irrelevant to this bug.

Christopher Yeleighton <yecril71pl>
Sun 14 Aug 2011 06:26:33 AM UTC, comment #5:

I've now improved the usage messages of ftstring, ftgrid, and ftview in the git repository. Please check.

Werner LEMBERG <wl>
Project AdministratorIn charge of this item.
Mon 25 Jul 2011 10:11:47 AM UTC, comment #4:

Since I was unable to start the program, there was no "within" :-( You need a supported font file to start it.

Christopher Yeleighton <yecril71pl>
Tue 28 Jun 2011 03:18:34 PM UTC, comment #3:

Well, these programs are just demo programs, nothing more. People should study its source code :-)

To be serious: Do you want to contribute some documentation?
Within the program, if you press key `h', you should get a help screen. Isn't this sufficient?

Werner LEMBERG <wl>
Project AdministratorIn charge of this item.
Tue 28 Jun 2011 08:49:12 AM UTC, comment #2:

This bug is invalid then; however, your comment granted me the right to file bug #33663, q.v.
[NB: Except for your comment and the syntax message, ftview is fully undocumented: no manual page, no decription in README, no description in the source code.]

Christopher Yeleighton <yecril71pl>
Tue 28 Jun 2011 05:22:51 AM UTC, comment #1:

Why? Do you have BDF or PCF files which don't have a .bdf or .pcf extension? For PS and (raw) CFF files it is rather common that there is no extension, but for TTF and TTC it actually never happens because Windows always needs proper extensions...

I personally don't like this automatic addition of extensions very much (inspite of having written and extended this code by myself)...

Note that viewing BDF and PCF files is fully supported in ftview; just use the full file name as an argument

Werner LEMBERG <wl>
Project AdministratorIn charge of this item.
Mon 27 Jun 2011 01:05:44 PM UTC, original submission:

{ ftview; } says:

font The font file(s) to display; if no extension is given,
ftview tries to append one of the following suffixes:
`.ttf', `.ttc', `.otf', `.pfa', `.pfb'.
For `.pfa' and `.pfb' files, ftview also tries to
attach the corresponding metrics file (with extension
`.afm' or `.pfm').

Please add PCF and BDF to the list of supported font file types.

Christopher Yeleighton <yecril71pl>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by wl (Posted a comment)
  • -unavailable- added by yecril71pl (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 12 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Fri 02 Mar 2012 09:33:25 PM UTCwlStatusIn Progress=>Fixed
      Open/ClosedOpen=>Closed
      Planned ReleaseNone=>2.4.9
    Sat 20 Aug 2011 05:57:05 AM UTCwlOpen/ClosedClosed=>Open
      Planned Release2.4.7=>None
    Sat 20 Aug 2011 05:54:26 AM UTCwlStatusFixed=>In Progress
      SummaryPlease add BDF support to ftview=>Remove automatic addition of extensions to ft2demo tools
    Sun 14 Aug 2011 06:26:33 AM UTCwlStatusNeed Info=>Fixed
      Open/ClosedOpen=>Closed
      Planned ReleaseNone=>2.4.7
    Tue 28 Jun 2011 03:18:34 PM UTCwlStatusNone=>Need Info
      Assigned toNone=>wl

    Back to the top


    Powered by Savane 3.1-cleanup1