headers
Ian Britten | 1 Oct 2008 15:07
Favicon

Re: [ft] Acknowledgement of using freetype

Werner LEMBERG wrote:

>>   We will use freetype in our product as binary module.
> 
> Thanks.  However, there is a misunderstanding.  You shouldn't send an
> acknowledgement to us but acknowledge the FreeType Project in the
> documentation of your product.  As written earlier in FTL.TXT:
> 
>     o You may not pretend that  you wrote this software.  If you use
>       it, or  only parts of it,  in a program,  you must acknowledge
>       somewhere  in  your  documentation  that  you  have  used  the
>       FreeType code. (`credits')

[ Sorry for the late reply... ]

Hi all (Mostly the FT developers though),

Can I request a clarification of what you expect for this, both in
terms of wording/content, and also what types of "documentation" need
this content?  (Note this is coming from the perspective of a
Commercial product)

Is it enough to include relevant information in some sort of 'credits'
file within the actual installation/distribution?  Or is the end-user
required to actually *see* the credit, implying it would need to be
in the 'About' dialog, or the EULA (Assuming people actually read
those ;) ), or something similar?
What about marketing brochures, websites, etc?  Or is the requirement
only for _users_ (Meaning someone who has actually bought a copy of
the Commercial software)?
(Continue reading)

Permalink | Reply | 1 comment |
headers
Werner LEMBERG | 1 Oct 2008 23:08
Picon

Re: [ft] Acknowledgement of using freetype


> > o You may not pretend that you wrote this software.  If you use
> >   it, or only parts of it, in a program, you must acknowledge
> >   somewhere in your documentation that you have used the FreeType
> >   code. (`credits')
>
> Can I request a clarification of what you expect for this, both in
> terms of wording/content, and also what types of "documentation"
> need this content?  (Note this is coming from the perspective of a
> Commercial product)

Mhmm, we don't have anything more specific.

> Is it enough to include relevant information in some sort of
> 'credits' file within the actual installation/distribution?

This is OK.

> Or is the end-user required to actually *see* the credit, implying
> it would need to be in the 'About' dialog, or the EULA (Assuming
> people actually read those ;) ), or something similar?

This would be even better.

> What about marketing brochures,

No.  I don't consider such brochures `documentation' :-)

> websites,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Hartwig Wiesmann | 12 Oct 2008 09:02
Picon
Favicon

[ft] ftmac.c

I have found two time the file ftmac.cp in the directory structure:

  - src/base/ftmac.c
  - builds/mac/ftmac.c

The one in builds/mac seems to be older than the one in src/base but  
do I need the one in builds/mac anywhere?

Hartwig
Permalink | Reply | 5 comments |
headers
mpsuzuki | 12 Oct 2008 09:17
Picon

Re: [ft] ftmac.c

Hi, I'm a maintainer of ftmac.c in FreeType2.

On Sun, 12 Oct 2008 09:02:58 +0200
Hartwig Wiesmann <hartwig.wiesmann <at> wanadoo.nl> wrote:

>I have found two time the file ftmac.cp in the directory structure:
>
>  - src/base/ftmac.c
>  - builds/mac/ftmac.c
>
>The one in builds/mac seems to be older than the one in src/base but  
>do I need the one in builds/mac anywhere?

src/base/ftmac.c is only for Mac OS X and does not
work with Classic MacOS anymore. If you build FreeType
via command line on Mac OS X, src/base/ftmac.c is used.

builds/mac/ftmac.c supports both of Mac OS X and Classic
MacOS, but it includes countless ifdef conditionals
and difficult for recent Mac OS X users to maintain.
If you build FreeType by MPW, builds/mac/ftmac.c is used.

In future, src/base/ftmac.c would be removed and
builds/mac/ftmac.c would be left, because Mac OS X enables
to implement important features of ftmac.c with only
POSIX, and without Carbon frameworks.

Regards,
mpsuzuki
(Continue reading)

Permalink | Reply | 4 comments |
headers
mpsuzuki | 13 Oct 2008 17:10
Picon

CodeWarrior project file is not ready to build (Re: [ft] Mac Build - Desperate)

Dear CodeWarrior users,

In this weekend, I was trying to improve a project file
for CodeWarrior IDE builds/mac/ftlib.prj.xml to support
3 architechtures: CFM MSL, Mach-O MSL, Mach-O BSD. And,
I found that CW project file (both of traditional binary
and XML formats) could not store the pathnames of source
files. When I copy the project file to vanilla source
tree of FreeType2, CW starts to scan the source tree and
determine which source files should be compiled.

This is the root of the problem reported by RJJ (2 years ago, sorry):

	Why CW tries to compile builds/amiga/src/base/ftsystem.c
	instead of src/base/ftsystem.c?

When a CW project file tells CW to load a source file
named "ftsystem.c", it cannot specify the directory
including the file. The CW crawls all directories (maybe
in the alphabetical order) and loads the first file named
"ftsystem". Therefore, builds/amiga/src/base/ftsystem.c
is prioritized than src/base/ftsystem.c.

I could not find any switches to prevent or restrict this
scanning behaviour. It means - when the developers trying
to build FreeType2 by CW, they must remove unused files
from the source directories before importing the project
file. Maybe the expected building process for project file
would be "open a project file and start the building", but
it is almost impossible for FreeType2.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sivaprasad CG | 20 Oct 2008 13:21
Picon

[ft] Freetype2 functions


Dear All,

Is there any function in freetype2, which list out all the unicodes in the
given font. 
Suppose I am opening timesnewroman.ttf, can i get all the unicode values
that are supported by this font file using the Freetype2 functions. 

Is there any function in freetype2, in which i can query a particular
unicode value in a particular font file. 

Regards
Sivan
--

-- 
View this message in context: http://www.nabble.com/Freetype2-functions-tp20067250p20067250.html
Sent from the Freetype - User mailing list archive at Nabble.com.
Permalink | Reply | 1 comment |
headers
Werner LEMBERG | 21 Oct 2008 06:49
Picon

Re: [ft] Freetype2 functions

> Suppose I am opening timesnewroman.ttf, can i get all the unicode
> values that are supported by this font file using the Freetype2
> functions.

Check the documentation of FT_First_Char and FT_Get_Next_Char

> Is there any function in freetype2, in which i can query a
> particular unicode value in a particular font file.

Again, check the documentation!  -> FT_Get_Char_Index.

    Werner
Permalink | Reply | 0 comments |
headers
ayoub mejri | 29 Oct 2008 16:46
Picon

[ft] freetype question

Hello,
 
I still work with freetype cache but I have the following problem.
 
I have a text to parse that has  2 lines (first line with size 12 and second line with size 24)
 
While parsing, when I look up glyphs of the second line (size of 24), if it exist in cache (means found in first line),it is rendered with the size 12 and not 24 (I think beacause it is stored with the size of 12)
I am using always the lookup FTC_ImageCache_LookupScaler function
 
Please can you help me.
 
cdt
_______________________________________________
Freetype mailing list
Freetype <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype
Permalink | Reply | 1 comment |
headers
Werner LEMBERG | 29 Oct 2008 18:02
Picon

Re: [ft] freetype question


> While parsing, when I look up glyphs of the second line (size of
> 24), if it exist in cache (means found in first line),it is rendered
> with the size 12 and not 24 (I think beacause it is stored with the
> size of 12) I am using always the lookup FTC_ImageCache_LookupScaler
> function

Sample code, please -- you should provide a *minimal* example which
compiles fine with ANSI C (without graphics, of course).

    Werner
Permalink | Reply | 0 comments |
headers
Peter Weilbacher | 30 Oct 2008 12:45

[ft] Font broken or FreeType?

I encountered a problem with FT_Load_Glyph() using the "Helvetica Italic"
font (HELVI.PFB) that is included with OS/2. It fails for one glyph (499
starting from 0) with error code 0xa0 ("opcode syntax error"). The short
program below demonstrates it. I can easily provide the font, if needed.

Now, to find out if it's the font that is broken or FreeType just stumbles
over a quirk in a correct font, I tried to verify the problem with FontForge.
Perhaps I don't know how to properly handle that program, but it doesn't
expose any problems. (Just that FontForge seems to sort the glyphs
differently, 499 is not the one that I am trying to load, the ones around
it have different names, too).

Thanks in advance for any hints!
   Peter.

---------------------- brokenHelvI_test.c -----------------------

// sample output for broken font:
// $ brokenHelvI_test.exe HELVI.PFB 499
// 1: error=0xa0 for HELVI.PFB glyph 499
// 2: error=0xa0 for HELVI.PFB glyph 499

#include "ft2build.h"
#include FT_FREETYPE_H
#include <stdio.h>

int main(int argc, char *argv[])
{
  FT_Library ftlib;
  FT_Init_FreeType(&ftlib);

  FT_Face face;
  FT_Error error = FT_New_Face(ftlib, argv[1], 0, &face);
  if (error) {
    printf("error=0x%x loading %s\n", error, argv[1]);
    FT_Done_FreeType(ftlib);
    return 1;
  }
  error = FT_Load_Glyph(face, atoi(argv[2]), FT_LOAD_NO_SCALE | FT_LOAD_NO_HINTING |
FT_LOAD_NO_BITMAP | FT_LOAD_IGNORE_TRANSFORM);
  if (error) {
    printf("1: error=0x%x for %s glyph %d\n", error, argv[1], atoi(argv[2]));
  }
  error = FT_Load_Glyph(face, atoi(argv[2]), FT_LOAD_DEFAULT);
  if (error) {
    printf("2: error=0x%x for %s glyph %d\n", error, argv[1], atoi(argv[2]));
  }
  FT_Done_Face(face);

  FT_Done_FreeType(ftlib);
  return 0;
}
Permalink | Reply | 5 comments |

Gmane