gmane.comp.fonts.freetype.user

Re: [ft] Outline decomposition of composed glyph

Infro — 2012-05-11T17:36:28

I'm completely uncertain, but you are probably wanting to draw "e with 
circumflex" instead of "e" and then adding a circumflex/hat.  Normally 
hex code 0x88.

[ft] Outline decomposition of composed glyph

ANTONCZYK Maxence — 2012-05-11T12:39:04

Hello

I want to render a glyph "e with circumflex" with freetype outline.

In Windows 7, Arial font is Opentype Font and this glyph is composed 
with 3 outlines, which are references of other glyph, 2 outlines in the 
same "glyph cell [e]" and 1 in an other "glyph cell [^]".

When I use FT_Outline_Decompose in order to draw "e with circumflex", in 
Windows 7 circumflex is left border aligned.

Did I forget something in order to get circumflex centered over glyph "e"?

Thanks for your replies.

ANTONCZYK Maxence
BROADCAST-BOX
1, rue de la banque
F-71000 Chalon sur Saône

Re: [ft] ttfautohint error: broken table

Werner LEMBERG — 2012-05-10T21:52:43


Fixed in git.  Thanks for the report!


    Werner

Re: [ft] ttfautohint error: broken table

Khaled Hosny — 2012-05-10T10:45:03

Ah, I see, there is a near horizontal line that FontForge turned into a
huge number of points when converting from cubic to quadratic splines,
fixing that gets rid of the error.

Regards,
 Khaled

Re: [ft] ttfautohint error: broken table

Werner LEMBERG — 2012-05-10T10:54:13

But neither FontForge nor ttx nor FreeType complain.  This means that
there is a bug in ttfautohint...


    Werner

Re: [ft] ttfautohint error: broken table

Werner LEMBERG — 2012-05-10T10:32:15


Ah, ok.  The problem is glyph `four' (which looks *veeeery* strange),
but it seems to be a bug in ttfautohint.  Will investigate.


    Werner

Re: [ft] ttfautohint error: broken table

Khaled Hosny — 2012-05-10T07:53:45

Thank you, but this still does not help my case, this fixes the error
message when processing CFF-flavoured fonts, which was:

  Error code `0x06' while autohinting font:
    invalid argument

But the error I'm getting is with the Crimson-Bold.ttf font (error code
0x08 not 0x06).

Regards,
 Khaled

Re: [ft] ttfautohint error: broken table

Werner LEMBERG — 2012-05-10T05:49:14

Thanks for the report; this is now improved in the git repository.
The new error message is

  This font is not a valid font in SFNT format with TrueType outlines.
  In particular, CFF outlines are not supported.


      Werner

[ft] ttfautohint error: broken table

Khaled Hosny — 2012-05-09T22:21:30

I'm trying to hint Crimson font[1] with ttfautohint, but I'm getting an
error with bold and semibold fonts:

  Error code `0x08' while autohinting font:
    broken table

It would be nice if ttfautohint would give more information so I can
debug the font, at least the name of the offending table.

[1] http://crimsontext.svn.sourceforge.net/viewvc/crimsontext/trunk/builds/

Regards,
 Khaled

Re: [ft] Help:How can i build freetype for win64

suzuki toshiya — 2012-05-02T14:04:32

In my case, I use MinGW cross compiler for Win64 which is running on GNU/Linux.
The packages by original developers for MinGW64 are still available from:
http://sourceforge.net/projects/mingw-w64/
But the latest cygwin distributes MinGW64 cross compilers in their packages
http://cygwin.com/packages/

Regards,
mpsuzuki

clive wrote:

Re: [ft] Help:How can i build freetype for win64

Infinality — 2012-05-02T12:55:45

You might try this project.  I haven't used it personally, but it may be 
helpful for you:
http://code.google.com/p/gdipp/


On 05/02/2012 07:07 AM, clive wrote:
_______________________________________________
Freetype mailing list
Freetype< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype

[ft] Help:How can i build freetype for win64

clive — 2012-05-02T12:07:37

Hi, my friends
I have searched many articles, but i haven't found any way to build freetype for win64
I have tried in follow ways:
1. to build with cygwin, but the cygwin do not surpport for x64
2. to build with mingw, but the gnu make for x64 just in planning
 
Finally, i use the freetype project for win32, add x64 platform in configuration manager,  and build success on window64 operate system.
I dumpbin -headers the lib, it shows mechine(x64). but i do not sure the lib will work well.
So i come here for help.
Thanks
 
 
 _______________________________________________
Freetype mailing list
Freetype< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype

Re: [ft] glyphs' metrics and positioning

Werner LEMBERG — 2012-04-30T17:14:54


Yes, I think so.


Well, a non-integer value is meaningless for pixmaps.


`Corrected'?  What shall be corrected?


It sounds like you are theorizing here without a real example.  Have
you actually looked into the demo programs and checked how they work?
You don't need fractional pixel coordinates for blending!  FreeType
itself shifts the glyph appropriately to the non-integer position if
necessary, and you blend the glyph's pixmap using the integer offsets.

Maybe I really don't understand what you are complaining.  Most likely
this indicates confusing documentation, so please help improve that.


     Werner

Re: [ft] glyphs' metrics and positioning

Wojciech Mamrak — 2012-04-30T12:36:16

Thanks for the reply,

so slot->metrics.horiBearingX and slot->bitmap_left base on the same
value, but later start to differ due to filters, and additionally the
latter is rounded to integer pixel coordinates even when hinting is
disabled? Is there a way to get values corrected due to above?


I know that resulting pixmap is aligned to the pixel grid and that I
need to alter it. Maybe I wasn't clear enough here.
The question is: since bitmap_left is always (even with hinting
disabled) rounded to integer pixel coordinates, it can't be used to
calculate the offset required to create the blending, because together
with advance it is responsible for accurate positioning of glyphs (as
in the cited example).

regards

2012/4/23 Werner LEMBERG <wl< at >gnu.org>:

Re: [ft] Problem rendering Arabic Text.

Sauron Sauri — 2012-04-25T10:38:16

Thanks for your help.
I will try with some of mentioned libraries.


________________________________
 De: Werner LEMBERG <wl< at >gnu.org>
Para: sauron1666< at >yahoo.es 
CC: freetype< at >nongnu.org 
Enviado: Miércoles 25 de abril de 2012 12:31
Asunto: Re: [ft] Problem rendering Arabic Text.
 


This is beyond FreeType's scope.  You need a higher-level library like
ICU, Pango, or Qt for handling complex scripts.


    Werner_______________________________________________
Freetype mailing list
Freetype< at >nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype

Re: [ft] Problem rendering Arabic Text.

suzuki toshiya — 2012-04-25T10:32:38

Hi,

Blaine1666 wrote:

Do you mean as: the glyph shapes of Arabic script should be appropriately changed
for their positions, like, head-of-word, middle-in-word, tail-of-word (and
separated), but at present you cannot realize it by FreeType2?

If so, please consider to use complex text layout libraries, like, Pango, HarfBuzz,
ICU, m17n etc. FreeType2 itself does not support complex text layout feature.

Regards,
mpsuzuki

Re: [ft] Problem rendering Arabic Text.

Werner LEMBERG — 2012-04-25T10:31:03


This is beyond FreeType's scope.  You need a higher-level library like
ICU, Pango, or Qt for handling complex scripts.


    Werner

[ft] Problem rendering Arabic Text.

Blaine1666 — 2012-04-25T08:07:06

I've an application that uses SDL, SGE and Freetype libraries to render text
on Screen. Latin text works fine, but Arabic text appears from left to
right. This is a complex language, is RTL and the glyphs are different
depending on the possition, and my application doesn't care.

Is there a solution to Load and render each character but deppending if text
is RTL/LTR and drawing the correct character deppending if is Arabic  etc..? 

I don't know how can I solve this. Here is the source code that render a
unicode texts and draw them on screen with SGE and SDL libraries:

//==================================================================================
// TT Render (unicode)
// Returns an 8bit or 32bit(8/8/8/8-alpha) surface with TT text
//==================================================================================
SDL_Surface *sge_TTF_RenderUNICODE(sge_TTFont *font,const Uint16 *text,
SDL_Color fg, SDL_Color bg)
{
int xstart, width;
int w, h;
SDL_Surface *textbuf;
SDL_Palette *palette;
int inde

Re: [ft] Getting error text

Werner LEMBERG — 2012-04-24T09:06:15


See documentation in `fterrors.h'.


    Werner

[ft] Getting error text

Mike Gresens — 2012-04-23T07:05:03

Hallo,

in the include file "fterrdef.h" you have associations between error 
code and error text, e.g.:

   FT_ERRORDEF_( Cannot_Open_Resource,                        0x01, \
                 "cannot open resource" )

How can i get the error text from the error code?!

Best regards

Re: [ft] glyphs' metrics and positioning

Werner LEMBERG — 2012-04-23T08:40:21


This is an artifact of the LCD rendering (you are using
FT_LCD_FILTER_DEFAULT).  From the description of
FT_Library_SetLcdFilter:

  If this feature is activated, the dimensions of LCD glyph bitmaps
  are either larger or taller than the dimensions of the corresponding
  outline with regards to the pixel grid.  For example, for
  FT_RENDER_MODE_LCD, the filter adds up to 3 pixels to the left, and
  up to 3 pixels to the right.


This is the same issue, I think.


Yes.


No.  The subpixel positioning is specified on the input side; on the
output side, you always get pixmaps aligned to the pixel grid which
can be easily blended into the target pixmap.  Note that you really
must do blending and not simply overwriting; the latter would possibly
cut off the right side of the previous glyph (assuming left-to-right
writing direction).


    Werner