bugThe FreeType Project - Bugs: bug #44550, Distinguish real missing...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #44550: Distinguish real missing character from real character with glyph index 0

Submitter:  Dimitrios Papadopoulos <dipapado>
Submitted:  Mon 16 Mar 2015 01:09:14 PM UTC
   
 
Severity:  3 - Normal Item Group:  Wishlist
Status:  Invalid Privacy:  Public
Assigned to:  wl Open/Closed:  Closed
Planned Release:  None

Mon 16 Mar 2015 04:54:56 PM UTC, comment #1: 

Such a question belongs to the FreeType user mailing list, not to the bug tracker...

You are misunderstanding the interface.

If you try to access a font by character code with FT_Get_Char_Index, return value 0 means that there is no glyph in the font for this character code.

If you try to access a font by glyph index with FT_Load_Glyph, a value larger than the number of glyphs makes this function return an error.

Finally, if you try to access a font by glyph name with FT_Get_Name_Index, return value 0 means that there is no glyph in the font with this name.

In case you still have questions please discuss this on the mailing list.

Werner LEMBERG <wl>
Group administrator
Mon 16 Mar 2015 01:09:14 PM UTC, original submission:  

I would like to know if a character exists on the font or not.
With the current implementation we can not know if it is really missing character or it is real character with glyph index 0.

Can we define something like FT_INDEX_NOT_FOUND 0xFFFFFFFFU and return it in case of real missing character? Or something that inform us that the character doesn't exist on the font.

A new function is also welcome.

Dimitrios Papadopoulos <dipapado>

 

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

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

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

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2015-03-16 wl StatusNone Invalid
        Assigned toNone wl
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code