Re: [ft-devel] Documentation guidelines file
> > Ah, this is only reproducible on Chrome. Firefox ignores word break > > rules. A little searching and experimenting gave me the answer. > > Should be fixed now! > > Thanks a lot! Have you already pushed the changes to the repository? > Not yet, will do it today. Oh, and is there anything left to add in the `DOCUMENTATION' file? -- Nikhil ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] Upcoming changes in the GF driver.
Hi all, Following are the changes to be completed in the GF driver, which I will be implementing in the coming days: 1. Solving the `cmap' problem. 2. Adding artificial glyphs in the GF driver. 3. Using the `xxx' and `yyy' information to derive the `cmap' scheme. Please suggest any more changes required. Thank you Parth ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Documentation guidelines file
>> Attached is another example from the `note' section of the description >> of `FT_GlyphSlotRec' (100% default size using Chrome). > > Ah, this is only reproducible on Chrome. Firefox ignores word break > rules. A little searching and experimenting gave me the answer. > Should be fixed now! Thanks a lot! Have you already pushed the changes to the repository? Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Documentation guidelines file
> >> BTW, I see > >> > >> face- > >> >num_charmaps > >> > >> i.e., a line break after the `-' (within ...). This > >> is bad. Can this be fixed in CSS? > > > > I'm not able to reproduce this at any zoom level, can you send a > > screenshot? > > Attached is another example from the `note' section of the description > of `FT_GlyphSlotRec' (100% default size using Chrome). > > > https://www.dxdy.ooo/freetype-web-jekyll/docs/reference/ft2-base_interface.html#ft_glyphslotrec > Ah, this is only reproducible on Chrome. Firefox ignores word break rules. A little searching and experimenting gave me the answer. Should be fixed now! -- Nikhil ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel