FreeType2 support these operators:
# 0x010f: -Reserved- # XXX force_bold_threshold for FreeType2
# 0x0110: -Reserved- # XXX lenIV for FreeType2, Type 1 fonts
# 0x0118: -Reserved- # XXX multiple_master for FreeType2
# 0x0119: -Reserved- # XXX blend_axis_types for FreeType2
However
- Werner LEMBERG w...@gnu.org wrote:
I noted in the FreeType sources (src/sfnt/sfobjs.c) this check on the
version parameter:
if ( tag != 0x0001UL
tag != TTAG_ttcf
tag != TTAG_OTTO
tag != TTAG_true
tag != TTAG_typ1
tag !=
- Manlio Perillo manlio.peri...@gmail.com wrote:
I noted in the FreeType sources (src/sfnt/sfobjs.c) this check on the
version parameter:
if ( tag != 0x0001UL
tag != TTAG_ttcf
tag != TTAG_OTTO
tag != TTAG_true
tag != TTAG_typ1
tag !=
- Werner LEMBERG w...@gnu.org wrote:
So, does this means that you have seen OpenType fonts with CFF data
having multiple font?
This is not possible. According to people from both Adobe and
Microsoft (as discussed on the OpenType mailing list, IIRC), a CFF
font in an SFNT wrapper can
On Fri, 2008-08-29 at 04:23, [EMAIL PROTECTED] wrote:
Also, I introduced a boolean is_sfnt_ps to avoid the
installation of bytecode interpreter for sfnt-wrapped
CID-keyed fonts. Maybe it is NOT essential.
Note that there are also sfnt wrapped type1 fonts which also use the
typ1 version. They
On Sun, 2008-06-15 at 12:01, Werner LEMBERG wrote:
I believe you that this fix is necessary -- you certainly have a font
which exhibits this behaviour. However, the fact that it is possible
to have NULL values in the `BaseRecord' table (similar to the
`ComponentRecord' table as used in GPOS
I believe there is a bug in the opentype validator.
If I have a MarkToBase table with multiple mark classes and multiple
bases, and where at least one base is missing an attachment site
(anchor) for at least one mark class, then the validator will still
attempt to validate the missing anchor.
On Thu, 2008-05-08 at 14:52, Werner LEMBERG wrote:
the PS language reference manual the following for CID-keyed PS fonts:
At glyph rendering time, the glyph coordinate system is defined by
the concatenation of the FontMatrix entry in the selected FDArray
dictionary with the FontMatrix
On Sat, 2008-05-03 at 10:14, Deron Kazmaier wrote:
This is probably not a freetype problem, but maybe someone here can
point me in a direction that helps. I have a couple of fonts in which
the OS2 structure contains bogus weights. For example, a (Mac)
Helvetica.dfont that the Helvetica Bold
This is a far cry from a minimal case with a small bit of code to
display the problem, so feel free to ignore it.
A user reported to me that fontforge would crash when rasterizing a
certain glyph in a font. He provided a patch which caused fontforge to
use the grey-scale rasterizer. Same glyph.
On Sun, 2008-03-30 at 10:22, Werner LEMBERG wrote:
FT_Get_{First,Next}_Char are walking over cmaps, not over glyph
indices. Except for subsetted CID-keyed CFFs (which use CIDs instead
of glyph indices), the range for glyph indices is *always* contiguous.
Er... and sort of ttc files where glyph
On Wed, 2008-01-09 at 00:24, Donn wrote:
.PFA files
These are a new twist, just found one today. I do not know if they also get
matched with some metric file. I see many .AFM files around and in one
folder:
PFA files contain exactly the same data as a PFB, they are a hex (ASCII)
dump rather
On Tue, 2008-01-08 at 23:38, [EMAIL PROTECTED] wrote:
There is a scenario that I don't want to think:
TrueType font has multiple cmap subtables with same platform
ID and platform-specific encoding ID but different language IDs.
This is indeed possible.
Apple made a mistake when they assigned
On Fri, 2007-10-19 at 04:04, David Turner wrote:
By the way, where can I find the spec for cmap format 14 and the
variant selector things ?, I could not find anything on the
Internet.(yes, I've seen the description in src/sfnt/ttcmap.c)
This was posted on the opentype list:
On Tue, 2007-10-09 at 23:56, Werner LEMBERG wrote:
if called on a format 14 charmap (which
shouldn't be possible in the first place). Instead a new routine
FT_Get_Char_Variant_Index
I believe the following patch will add cmap14 support to freetype.
(based on the cvs tree as it
On Tue, 2007-10-09 at 23:56, Werner LEMBERG wrote:
I have no opinion here. If you think this is the route to go, let's
do this. However, I could imagine to have
FT_Get_Chars_Of_Variant
FT_Get_Variants_Of_Char
FT_Get_Variant_Selectors
I like this much better (I was just trying to be
Out of curiosity...
are there any plans afoot to support 'cmap' format 14 (the variant
selector table)?
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
On Mon, 2007-10-08 at 07:46, Werner LEMBERG wrote:
I've skimmed the specs but didn't look more closely. Do you
volunteer? It seems that we need a special interface for that, right?
I would think so... I haven't paid attention to freetype's 'cmap' code.
I'll look at it and see what I can do.
On Sun, 2007-09-30 at 20:16, [EMAIL PROTECTED] wrote:
As I've shown in previous post, Apple Unicode cmap in the
sample font is NOT broken from the viewpoint of data
structure, I think. To detect broken cmap as you say,
it's required to investigate cmap, loca, glyf subtables
content
On Fri, 2007-08-17 at 08:56, Werner LEMBERG wrote:
Applied. However, I think there is a mistake for the
SingleSubstFormat1 case:
idx = otv_Coverage_get_first( Coverage ) + DeltaGlyphID;
if ( idx 0 ||
idx +
I blush to admit that I miscounted the number of constants in one of the
tables (there are 56 not 57).
Please apply the otvmathconstant patch
On Wed, 2007-08-08 at 11:24, Werner LEMBERG wrote:
Suzuki-san, what do you think and/or suggest?
I have a couple of general questions. Probably for
On Tue, 2007-08-07 at 15:35, Behdad Esfahbod wrote:
On Tue, 2007-08-07 at 18:06 -0400, George Williams wrote:
I am working on a validator for the MATH table to slot it in to otvalid.
Hi George,
Any spec on the MATH table available online?
Thanks
No, MS hasn't made it public yet
On Wed, 2007-06-20 at 08:31, Graham Asher wrote:
However, the definition of postscript.underlinePosition is (according to
http://www.microsoft.com/OpenType/OTSpec/post.htm):
This is the suggested distance of the top of the underline from the baseline
(negative values indicate below
I believe there is a bug in the SHZ instruction.
I believe SHZ should not move the phantom points in the zone.
The attached font contains one interesting glyph ~ and lots of glyphs
which are vertical bars and are included to show spacing.
The interesting glyph moves the zone by 4 pixels. In
On Fri, 2006-12-08 at 00:06, Werner LEMBERG wrote:
Greg Hitchcock from MS provided some information regarding the gasp
table format, version 1. I'm only listing the differences.
field description
version 1
rangeGaspBehaviorbit 3:
On Fri, 2006-12-08 at 00:06, Werner LEMBERG wrote:
Greg Hitchcock from MS provided some information regarding the gasp
table format, version 1. I'm only listing the differences.
field description
version 1
rangeGaspBehaviorbit 3:
I am trying to rasterize a rectangle which is centered around y==0.
I get a bitmap half as high as I expect.
More complicated tests suggest that everything below y==0 is clipped.
Test file included.
(Note: I do not have a Face open. I'm going directly from an FT_Outline
to an FT_Bitmap).
On Fri, 2006-08-25 at 23:48, David Turner wrote:
Could anyone remind me what these fonts are, and where I could find them
for analysis and testing ? I believe that nearly all of them were designed
by DynaLabs, but I'm a bit unsure about that.
David,
Here's another one: htst3.ttf
Apple sort of documents a bitmap only sfnt format in its truetype
documentation. There is a 'bhed' table which should be used instead of
the 'head' table in a bitmap only sfnt.
Apple's ftxvalidator insists that there should be no 'hhea' nor 'hmtx'
tables either.
This is not stated in Apple's
On Fri, 2006-06-16 at 13:32, Masatake YAMATO wrote:
Thank you for you suggestion.
I revised ftvalid.c to show messages and exit if validate modules is not
present. I also improved help message. Now it shows each validate module
is implemented or not.
Excellent! Thank you very much.
I tried ftvalid for the first time today.
At first it just told me that every font I fed it was invalid. I
discovered this was because the default freetype does not include the
validation modules. After changing modules.cfg everything passed.
I wonder... would it be possible to have
On Wed, 2006-02-22 at 13:29, Tom Kacvinsky wrote:
Werner is good at that kind of stuff. :-) And I did not know that
FontForge now had TT byte code stepping. Sweet!
It has had it since 2003. It is simply a front-end to freetype's
interpreter and shows you all of David's hard work.
On Mon, 2006-02-20 at 01:56, david turner wrote:
If this function's purpose is to determine wether the bytecode
interpreter is activated in a given
FreeType build, I'd rather like to see a specific API that returns a
boolean, or an enum, instead
Can't you avoid even that by using
On Wed, 2006-02-15 at 17:31, Werner LEMBERG wrote:
- do the required modifications, encapsulating each of the old
internals in a configuration macro
(e.g. FT_CONFIG_OPTION_OLD_INTERNALS)
Sounds good. We should mention in the docs that these steps are
performed only *once*, and that
On Thu, 2006-02-16 at 06:15, Werner LEMBERG wrote:
As the author of a rogue client for which no patch is contemplated
(and for which we decided last year that there was no good way to
provide a patch) I must beg that
TT_RunIns
remain reachable.
We add `TT_RunIns' manually to the
On Thu, 2006-02-16 at 07:08, david turner wrote:
I still don't understand why you absolutely want the ability to
dynamically peek into the
internals of the libfreetype installed on the system, especially since
it will not have the
bytecode interpreter on most distros anyway...
I want
Once upon a time, about last October, the thought of a freetype
testsuite appeared yet again on the list.
I've been working on a function in fontforge to make fontforge's
testsuite (such as it is) more capable, and I realized that this same
thing could be used to test freetype.
If anyone cares
On Mon, 2006-01-23 at 01:53, david turner wrote:
Perhaps we shall *rename* the library to, say, `libft2', instead of
`libfreetype',
Um this will break everybody's builds and will mean we can't have
something that builds with either 1.10 or 2.0 without fancy configure
scripting. I'm not sure
On Sun, 2005-12-18 at 18:20, Chia-I Wu wrote:
FT_Get_BDF_Fontname(face)
FT_Get_BDF_Comments(face)
Couldn't they just be treated like normal properties?
Well they aren't in the bdf file format, they are handled quite
differently, so the bdf parser handles them differently.
The pcf file format
On Sun, 2005-12-18 at 18:20, Chia-I Wu wrote:
FT_Get_BDF_Fontname(face)
FT_Get_BDF_Comments(face)
Couldn't they just be treated like normal properties?
Ok, I have removed those entry points and made them behave like normal
properties.
This is incompatible with previous behavior. But since
On Sat, 2005-12-17 at 18:42, Chia-I Wu wrote:
I suggest the following APIs, making iterator merely an iterator:
/* to iterate... */
FT_Get_BDF_Iterator( face, iter );
while ( FT_Iterare_BDF_Property( face, iter, name, aprop ) )
{
/* do something; */
}
/* to get property count...
Drat.
PCF fonts include the FONT keyword and value in the list of
properties. Strictly speaking FONT is not a bdf property (it comes
outside of the STARTPROPERTIES list) -- however to do round trip
conversion it is necessary.
The value is available internally as face-bdffont-name, but I don't
see
Werner I stumbled on a case where I'd like to get a black white
image out of FT_Outline_Get_Bitmap rather than the grey scale output
that is currently returned.
== Justification ==
When FF is in debug mode it displays a raster showing what pixels
On Wed, 2005-11-02 at 10:11, Rajeev Pahuja wrote:
Does some one has Type1 PFM file specifications other than one
available for CJK at
Last time I looked I could find no PFM spec on the web aside from
Adobe's CJK info.
There used to be one on MicroSoft's site, but they removed it about the
time
On Fri, 2005-10-28 at 03:54, Ulrich wrote:
This is correct but I still think that this fact doesn't imply that it isn't
possible to set up a test suite. As far as I understand FreeType will
generate a certain rasterisation result depending on the parameter settings
and the environment it
On Fri, 2005-10-28 at 14:38, Ulrich wrote:
It's more than just shape. It's the difference between a pixel having
0xfe and 0xfd.
Sorry for using the wrong term shape. It should have been result. I
assume that every single change in the result has to be checked as one pixel
being on or
On Thu, 2005-10-27 at 10:38, Steven Johnson wrote:
I think that compiler also had extended as a reserved word (as a
96-bit floating point type, to match Motorola hardware of the time).
I worked on an early version of the MPW compiler (when the work was
outsourced from Apple). There was indeed an
On Mon, 2005-10-10 at 16:37, Fujinaka, Todd wrote:
I may have done something wrong, but those tests take an incredibly long
time.
Oh, they never end. It keeps churning out random tests and saving the
few that cause problems.
I think the tests we need are just something to test to see that all
On Sat, 2005-10-08 at 01:49, Ulrich wrote:
Sure, but as long as FreeType deterministically produces its results
depending on certain parameter settings (including the automatically
detected environment) testing is still a matter of deciding whether these
results are still the same compared
On Sun, 2005-09-18 at 13:23, David Somers wrote:
Please find attached a patch against freetype-2.1.10, which allows SING
glyphlet font files to be opened by Freetype.
Can you provide an example fontlet file for testing?
___
Freetype-devel mailing
On Fri, 2005-09-02 at 01:28, Turner, David wrote:
As far as I understand, this warning only applies to
code that reads the resource fork directly and doesn't
try to read fields in cpu-independent order.
Yes... It uses mac specific calls to handle the resource fork.
But it also adds some calls,
On Thu, 2005-09-01 at 14:39, Werner LEMBERG wrote:
Any volunteers? Neither David nor I use a Mac...
I looked into it and was able to fix a few issues, but I've never
bothered to learn the new mac calls and got stuck (it used to be
possible to get a filename from an open file descriptor but I
src/truetype/ttgload.c: says
/* Maximum recursion depth we allow for composite glyphs.
* The TrueType spec doesn't say anything about recursion,
* so it isn't clear that recursion is allowed at all. But
* we'll be generous.
*/
#define
On Fri, 2005-08-26 at 05:44, Werner LEMBERG wrote:
I seem to remember talk about testing FreeType on randomly corrupted
fonts; has any work on this been done?
AFAIK, George has started with some work. For my part, I've done
nothing, alas.
I have a little program which
makes a
There has been an argument running on the OpenType list about Digital
signatures.
I must confess I fail to understand the need for them on a linux/unix
platform. Perhaps someone can illuminate me, or perhaps linux/unix is
different enough from Windows/Mac that font validation isn't as
important.
On Wed, 2005-08-24 at 09:41, Sean McBride wrote:
I am writing here to report a 'bug' of sorts. Basically, it seems the
freetype implementation on the Mac is somewhat antiquated. I receive the
following warnings about the use of deprecated functions:
- FSSpecs should be replaced with FSRefs
On Thu, 2005-08-25 at 06:59, Sean McBride wrote:
Well, from the look of FMCreateFontFamilyIterator's docs, FreeType
already needs Mac OS 9.
The mac code contains #ifdefs and there is an #ifdef enabling MAC_OS8.
Whether it works any more I haven't the faintest idea (probably not
because the
On Thu, 2005-08-25 at 09:25, Sean McBride wrote:
Or you could deprecate FT_New_Face_From_FSSpec() and add a new analogous
API FT_New_Face_From_FSRef().
Obviously. But that changes freetype's API too.
___
Freetype-devel mailing list
On Mon, 2005-08-22 at 23:17, [EMAIL PROTECTED] wrote:
As written in README,
some of TrueType GX tables (mort, feat, prop) are widely used,
others (lcar, opbd) are very rare, and there are a few tables
(kern format1) we cannot find samples.
I have one example font containing a kern format 1
On Tue, 2005-08-23 at 08:18, [EMAIL PROTECTED] wrote:
Based on your detailed analysis (thanks again), I removed the line
- state transition diagram uses undefined glyph ID
from the essential error list, and add following paragraph
into the section. If I'm misunderstanding, please let me
On Tue, 2005-08-23 at 14:50, George Williams wrote:
a) 14 fonts uses too-large feature number (out of defined range).
b) 67 fonts uses feature number which should not be used.
c) 117 fonts set wrong feature range (nSetting).
this infraction is found in mort/morx
On Mon, 2005-08-08 at 22:50, Werner LEMBERG wrote:
This snippet is in deciding the mac scale of component offsets. It
is commented out because the result is bad. But in this page
http://developer.apple.com/fonts/TTRefMan/RM06/Chap6glyf.html, the
algorithm described is slightly different
On Mon, 2005-08-01 at 21:56, Chia I Wu wrote:
I'm looking for truetype fonts with apple's variation tables
The standard example I use is Skia, a font that ships with the mac. I've
seen others mentioned but don't know where to find them.
or with
composite glyph constructed with various
63 matches
Mail list logo
