[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] [GSoC'19] ftinspect questions
From: |
Werner LEMBERG |
Subject: |
Re: [ft-devel] [GSoC'19] ftinspect questions |
Date: |
Sat, 06 Jul 2019 19:23:31 +0200 (CEST) |
>> IMHO, `FT_Get_Char_Index' is sufficient. For displaying single
>> characters in `ftinspect' (or a bunch of them once in a separate
>> window for ftview-like stuff) you don't need a cache for speeding
>> up things.
>
> Let me know if I'm wrong but isn't it looks up the glyph index
> corresponding to the given char code in the char map but we are
> supposed to print all glyphs instead of getting a glyph index
> corresponding to a particular char code. Also, for getting the char
> code we would need glyph index. This function is perfect for
> rendering text string since we can look up for a particular
> character's glyph index but not sure how it would be used for
> getting all glyphs.
You were talking about caching the cmap stuff, right? Cmaps always
map character codes to glyph indices. Am I missing something?
Werner
- Re: [ft-devel] [GSoC'19] ftinspect questions, (continued)
Re: [ft-devel] [GSoC'19] ftinspect questions, Werner LEMBERG, 2019/07/03
Re: [ft-devel] [GSoC'19] ftinspect questions, Alexei Podtelezhnikov, 2019/07/04
Re: [ft-devel] [GSoC'19] ftinspect questions, Triplex, 2019/07/05
- Re: [ft-devel] [GSoC'19] ftinspect questions,
Werner LEMBERG <=