*" withnative (TrueType) hinting enabled."* How do I enable it?
Also,do I have to use FT_FACE_FLAG_TRICKY ? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=oa-2115-c> Checked by Avast Antivirus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=oa-2115-c> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Mar 10, 2016 at 12:26 PM, Werner LEMBERG <[email protected]> wrote: > >> FreeType doesn't take care of localization in any way. You need a > >> higher-level library like Pango or ICU to activate locale handling > >> (i.e., selecting script and language for OpenType features). > > > > Thanks for that info. Though I see in the docs glyph-to-script-map > > (a) This is for the auto-hinter only. > > (b) Unfortunately, it is currently unmaintained. It's also out of > date, since I have added a large bunch of scripts. > > > I have another question regarding Chinese CJK glyph maps. When I > > try to read outlines of such a glyph the coordiantes looks weird and > > when I render the shapes (triangulating it before that) it looks > > screwed. [...] > > It seems that you are looking at a composite fonts where the subglyphs > are scaled and shifted with bytecode instructions. > > > Is there a way to handle this type of maps with Freetype to get > > correct path? > > Please don't use the word `map'. It's rather called `outline data'. > > We call such fonts `tricky', which you can test with the > `FT_IS_TRICKY' macro. To get outlines of such a font that can be > processed further, you should render the glyphs with calls to > FT_Load_Glyph at the font's ppem resolution (e.g., 1024 or 2048), with > native (TrueType) hinting enabled. > > > Werner > -- Michael Ivanov Krios Software kriosoftware.com Tel:+972 54 4962254
_______________________________________________ Freetype mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype
