The FreeType Project - Bugs: bug #41411, Deprecated OS X functions
You are not allowed to post comments on this tracker with your current authentication level.
bug #41411: Deprecated OS X functions
Submitter: | Miroslav Andel <miran82> | ||
Submitted: | Fri 31 Jan 2014 12:36:50 PM UTC | ||
Severity: | 3 - Normal | Item Group: | None |
Status: | None | Privacy: | Public |
Assigned to: | mpsuzuki | Open/Closed: | Open |
Planned Release: | None |
Fri 31 Jan 2014 05:07:25 PM UTC, comment #2: |
suzuki toshiya <mpsuzuki> |
Fri 31 Jan 2014 02:52:56 PM UTC, comment #1: Toshiya-san, please comment. |
Werner LEMBERG <wl> |
Fri 31 Jan 2014 12:36:50 PM UTC, original submission:
A lot of functions used in freetype are deprecated when compiling with xcode. Some examples are are: ATSFontGetFileReference, ATSFontFindFromName, FSCompareFSRefs, FSRefMakePath, FSPathMakeRef, FSOpenResourceFile, FSOpenResFile, ResError, etc.
|
Miroslav Andel <miran82> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2014-01-31 | wl | Assigned to | None | mpsuzuki |
Powered by Savane 3.13-cf05.
Corresponding source code
Dear Miroslav,
Thank you for comment.
FT2 functions using deprecated OS X functions are kept
for back compatibility (rather, just to avoid the unresolved
symbol problem). In conventional Unix development (by
configure && make), they would be disabled by default.
I will try to disable them by default in Xcode environment.
Is it okay for you?
I think we should not introduce CTFont replacements of
them into FT2. There was a long history;
the original introduction of MacOS specific functions was
in MacOS 8 era. There was a reasonable background that
Classic MacOS provided no ANSI C or POSIX functions to
access the resource fork of so-called "suitcase font",
so we had to use MacOS specific functions at that time.
But, there was a mistake that a few FT2 functions using
MacOS specific data type (to interplay the font family
names, QuickDraw's font descriptor, and FT2 object) was
introduced accidentally.
In later, Mac OS X promoted full UNIX-like environment
and a migration from QuickDraw to ATS. We thought
providing the replacements from QD-based API to ATS-
based API was important, and introduced ATS-based APIs.
However, I found that such ATS-based APIs were not
required anymore. Under Mac OS X, fontconfig is more
useful to obtain a font file descriptor from the font family
name. If you need CT-based replacements, please let me
know more detailed background. I'm questionable to
introduce CT-based functions in FT2, but I will discuss
the appropriate solution.