<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user">
    <title>gmane.comp.fonts.freetype.user</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4774"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4773"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4772"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4771"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4770"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4769"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4768"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4767"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4766"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4764"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4763"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4762"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4761"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4760"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4759"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4758"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4757"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4756"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4755"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4754"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4774">
    <title>Re: [ft] True Type Collection (TTC) shared glyph tables</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4774</link>
    <description>&lt;pre&gt;

There is a misconception of how TTCs work: As soon as you select a
face index, you can't distinguish the data from a TTF.  In other
words, it is not possible to specify where a glyph comes from.  Most
TTCs share a single `glyf' table for all subfonts.  However, some
fonts (most notably on the Mac) have more than a single `glyf' table.
Assuming that font 1 in the TTC accesses `glyf' table 1, and font 2
accesses `glyf' table 2, there is no possibility that you can get
glyphs from `glyf' table 2 while accessing font 1.


Which font?  Are you *sure* that Windows doesn't use a fallback font
for displaying this glyph?


Try the ftview demo program without command line option `-e'; the font
faces in the TTC are then accessed by glyph indices instead of
character codes, bypassing the cmap table.


I strongly suggest that you read TTC section in the TrueType
specification:

  http://www.microsoft.com/typography/otspec/otff.htm


    Werner
__________________________________________&lt;/pre&gt;</description>
    <dc:creator>Werner LEMBERG</dc:creator>
    <dc:date>2013-05-17T14:46:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4773">
    <title>[ft]  True Type Collection (TTC) shared glyph tables</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4773</link>
    <description>&lt;pre&gt;
If I use a True Type Collection (TTC) font file when initializing my FreeType
Face, is there anything special I need to do to render a character that is
part of the shared table in the TTC (but not part of the individual TTF)?

At the moment FT_Get_Char_Index is returning 0 for the CJK Ideograph at
U+7380, and the error symbol is being used.  However, if I open this font
file in Windows' Character Map program it shows that this character is part
of the font.  Additionally, another program I installed called Typograf will
show that this character exists in the font.  I've tested a few other font
programs (like FontForge, Font Creator, and dp4 Font Viewer) and none of
these programs recognize that this character exists in the font, though.  So
I am led to believe that this character is part of the shared glyph table,
and only some of these programs are set up to look there.

Is there a way for me to verify that this character actually is part of the
shared TTC table?  Additionally, is there a way for me to ac&lt;/pre&gt;</description>
    <dc:creator>awiederman</dc:creator>
    <dc:date>2013-05-16T20:10:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4772">
    <title>[ft]  True Type Collection (TTC) shared glyph tables</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4772</link>
    <description>&lt;pre&gt;
If I use a True Type Collection (TTC) font file when initializing my FreeType
Face, is there anything special I need to do to render a character that is
part of the shared table in the TTC (but not part of the individual TTF)?

At the moment FT_Get_Char_Index is returning 0 for the CJK Ideograph at
U+7380, and the error symbol is being used.  However, if I open this font
file in Windows' Character Map program it shows that this character is part
of the font.  Additionally, another program I installed called Typograf will
show that this character exists in the font.  I've tested a few other font
programs (like FontForge, Font Creator, and dp4 Font Viewer) and none of
these programs recognize that this character exists in the font, though.  So
I am led to believe that this character is part of the shared glyph table,
and only some of these programs are set up to look there.

Is there a way for me to verify that this character actually is part of the
shared TTC table?  Additionally, is there a way for me to ac&lt;/pre&gt;</description>
    <dc:creator>awiederman</dc:creator>
    <dc:date>2013-05-16T20:09:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4771">
    <title>[ft]  True Type Collection (TTC) shared glyph tables</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4771</link>
    <description>&lt;pre&gt;
If I use a True Type Collection (TTC) font file when initializing my FreeType
Face, is there anything special I need to do to render a character that is
part of the shared table in the TTC (but not part of the individual TTF)?

At the moment FT_Get_Char_Index is returning 0 for the CJK Ideograph at
U+7380, and the error symbol is being used.  However, if I open this font
file in Windows' Character Map program it shows that this character is part
of the font.  Additionally, another program I installed called Typograf will
show that this character exists in the font.  I've tested a few other font
programs (like FontForge, Font Creator, and dp4 Font Viewer) and none of
these programs recognize that this character exists in the font, though.  So
I am led to believe that this character is part of the shared glyph table,
and only some of these programs are set up to look there.

Is there a way for me to verify that this character actually is part of the
shared TTC table?  Additionally, is there a way for me to ac&lt;/pre&gt;</description>
    <dc:creator>awiederman</dc:creator>
    <dc:date>2013-05-16T20:03:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4770">
    <title>Re: [ft] Issue compiling FT 2.4.12 on linux</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4770</link>
    <description>&lt;pre&gt;Ok, i found my problem. It was not an other library that was the problem,
but the previous version of freetype that i was trying to upgrade. Its
headers were in my custom include directory, so the build must have taken
the old headers of freetype first to try to compile the new one.


2013/5/15 Werner LEMBERG &amp;lt;wl&amp;lt; at &amp;gt;gnu.org&amp;gt;




&lt;/pre&gt;</description>
    <dc:creator>Olivier BARTHELEMY</dc:creator>
    <dc:date>2013-05-16T07:39:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4769">
    <title>Re: [ft] Issue compiling FT 2.4.12 on linux</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4769</link>
    <description>&lt;pre&gt;

Good. :-)


I don't think so.  You might also try `make devel; make' to compile
without the `configure' script.


    Werner
&lt;/pre&gt;</description>
    <dc:creator>Werner LEMBERG</dc:creator>
    <dc:date>2013-05-15T16:21:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4768">
    <title>Re: [ft] Issue compiling FT 2.4.12 on linux</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4768</link>
    <description>&lt;pre&gt;Ok, so i tried to do manually what my compilation script does (i'm updating
my coompilation script from FT2.4.6 to 2.4.12):

./configure
make

And it worked.
Looking at the compile arguments difference, i notice that i have an
additional -I brought by CFLAGS that points to a directory of includes to
other libraries i build myself. Removing that includes path makes my
automated build work too.
But the only library i see in that path that could impact freetype is zlib
(1.2.5 in my own include path, 1.2.3 found by default on the system). Does
freetype depend on a specific version of zlib or some other library? I'm
using centos 5 32bit with gcc 4.1


2013/5/15 Werner LEMBERG &amp;lt;wl&amp;lt; at &amp;gt;gnu.org&amp;gt;




&lt;/pre&gt;</description>
    <dc:creator>Olivier BARTHELEMY</dc:creator>
    <dc:date>2013-05-15T16:15:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4767">
    <title>Re: [ft] Issue compiling FT 2.4.12 on linux</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4767</link>
    <description>&lt;pre&gt;

We need a way to reproduce your problem.  How do you compile?  Please
give more details.


    Werner
&lt;/pre&gt;</description>
    <dc:creator>Werner LEMBERG</dc:creator>
    <dc:date>2013-05-15T15:37:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4766">
    <title>[ft] Issue compiling FT 2.4.12 on linux</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4766</link>
    <description>&lt;pre&gt;Hi,
I'm getting an error while i try to compile freetype on linux (but not on
windows)

The first 'visible' error (in base/ftinit.c:245) is that gcc says thet the
symbol FT_ERR_PREFIXUnimplemented_feature is undeclared.
It seems ERR_CAT concatenated the FT_ERR_PREFIX without replacing it with
it's value.
After some test, it seems that FT_ERR_PREFIX is not defined for some (all?)
of the c files in the base subdirectory. I tried including fterrors.h from
there, but somehow FT_ERR_PREFIX is not defined by doing this (even though
-DFT2_BUILD_LIBRARY is on the compile command). Manuually defining it at
the beginning of the c files to nothing correctly does the concatenation
but still gives undeclared symbols. Defining it do FT_Err_ seems to allow
the compilation of the files.

Is there some config i am not doing to get those errors, or is the linux
build not working for v2.4.12?



&lt;/pre&gt;</description>
    <dc:creator>Olivier BARTHELEMY</dc:creator>
    <dc:date>2013-05-15T14:53:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4764">
    <title>Re: [ft] I need help understanding the use of face_index in FT_New_Face.</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4764</link>
    <description>&lt;pre&gt;

Please point to places in the documentation which are unclear so that
we can improve it.  Or you might provide patches after you've
understood the issue :-)


A standard TrueType (TTF) or OpenType (OTF) font has *always* a single
face.  However, a TrueType (TTC) or OpenType (OTC) collection font has
more.  Take for example the standard Windows math font, `cambria.ttc',
which has two faces: Index 0 is for normal typesetting (`Cambria
Regular'), and index 1 is for mathematical formulae (`Cambria Math
Regular').  So in case you want to handle TTCs and OTCs, you *must*
support multiple faces.


Yes, this is something not used on Windows normally.


Usually, it makes fonts smaller, since the fonts can share common
TrueType tables.  In the Cambria example, the glyph shapes for most
characters are exactly the same, but some of them are different, and
the glyph metrics differ partially.

In case of Macintosh suitcases, however, it's rather to reduce the
number of files of a given font family.  Actually, it's quite&lt;/pre&gt;</description>
    <dc:creator>Werner LEMBERG</dc:creator>
    <dc:date>2013-05-01T03:48:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4763">
    <title>[ft] I need help understanding the use of face_index in FT_New_Face.</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4763</link>
    <description>&lt;pre&gt;I'm writing a font cache based on freetype. I'm creating an OpenGL text rendering library and need to textures of the glyphs. This is the first time that I have ever had the need to delve into fonts and unfortunately, the freetype documentation seems to make the assumption that those using the library have a deep understanding of fonts.

I'm developing the cache on Windows, but it needs to be cross platform. Since I cannot find a good example of different faces within a font, and the fact that most Windows TrueType fonts have only one face, I was just going to ignore the face_index parameter and leave it at zero. Then while trudging through the freetype source, I noticed a comment that when loading a Macintosh suitcase, the face_index corresponds to regular, bold, italic, etc., variants within the suitcase. :/ Because of this, I made a couple of functions to enumerate the number of faces within a font and to allow the user to switch faces.

My question is how to I document this? I don't fully understand why &lt;/pre&gt;</description>
    <dc:creator>Mark Speir</dc:creator>
    <dc:date>2013-05-01T01:38:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4762">
    <title>[ft] git repository for FreeType documentation</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4762</link>
    <description>&lt;pre&gt;
Folks,


the git repository of all FreeType documentation files is now
available online:

  http://cgit.freedesktop.org/freetype/freetype-web


    Werner
&lt;/pre&gt;</description>
    <dc:creator>Werner LEMBERG</dc:creator>
    <dc:date>2013-04-22T05:43:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4761">
    <title>Re: [ft] Building FT2 for embedded architectures</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4761</link>
    <description>&lt;pre&gt;
On Apr 19, 2013, at 11:06 AM, Wolfgang Draxinger &amp;lt;Wolfgang.Draxinger&amp;lt; at &amp;gt;physik.uni-muenchen.de&amp;gt; wrote:


You might like to try the amalgamated version; it's awesome.

https://github.com/vinniefalco/FreeTypeAmalgam

Best wishes,

Tom

文林 Wenlin Institute, Inc.        Software for Learning Chinese
E-mail: wenlin&amp;lt; at &amp;gt;wenlin.com     Web: http://www.wenlin.com
Telephone: 1-877-4-WENLIN (1-877-493-6546)
☯




_______________________________________________
Freetype mailing list
Freetype&amp;lt; at &amp;gt;nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
&lt;/pre&gt;</description>
    <dc:creator>Tom Bishop, Wenlin Institute</dc:creator>
    <dc:date>2013-04-19T17:22:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4760">
    <title>Re: [ft] Building FT2 for embedded architectures</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4760</link>
    <description>&lt;pre&gt;

Definitely not. I'm successfully compiling and linking programs using 
this very compiler. I put the blame on the brain dead automake/autoconf 
system that tries to execute the generated binary on the compiler system 
which of course will not work.

Preferrably there would be no configure script running at all. I'd 
really prefer to configure the build myself, specific to my needs. Any 
automagic is a No-Go in this project anyways.


Here's the Makefile of the small test program I started with.

### Makefile ###
all:
         arm-none-eabi-gcc -I. -c -fno-common -O0 -g -mcpu=cortex-m3 
-mthumb main.c
         arm-none-eabi-ld -Tstm32.ld -nostartfiles -o main.elf main.o
         arm-none-eabi-objcopy -Obinary main.elf main.bin

flash: main.bin
         stm32_flash.pl main.bin

clean:
         rm main.o main.elf main.bin

### Makefile (END) ###

stm32_flash.pl is a small Perl script talking to OpenOCD, to flash the 
image via JTAG. Anyway, the linker produces a valid ELF.

dw&amp;lt; at &amp;gt;hilbert: ~/…/stm32f_test &amp;gt; fil&lt;/pre&gt;</description>
    <dc:creator>Wolfgang Draxinger</dc:creator>
    <dc:date>2013-04-19T17:07:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4759">
    <title>Re: [ft] Building FT2 for embedded architectures</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4759</link>
    <description>&lt;pre&gt;
Ahh, according to the log file,


your arm-non-eabi-gcc seems to have a difficulty to
make a binary executable. If you want to make a hello-world
binary executable for the target system, how do you compile
it?

Regards,
mpsuzuki



On 2013年04月20日 00:46, Wolfgang Draxinger wrote:
&lt;/pre&gt;</description>
    <dc:creator>suzuki toshiya</dc:creator>
    <dc:date>2013-04-19T16:36:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4758">
    <title>Re: [ft] Building FT2 for embedded architectures</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4758</link>
    <description>&lt;pre&gt;
Here you go:

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by FreeType configure 2.4.11, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure --host=arm-none-eabi --without-zlib --without-bzip2
--without-fsspec --without-fsref --without-ats --disable-shared
--enable-static

## --------- ##
## Platform. ##
## --------- ##

hostname = hilbert
uname -m = x86_64
uname -r = 3.2.0-3-rt-amd64
uname -s = Linux
uname -v = #1 SMP PREEMPT RT Mon Jul 23 03:37:45 UTC 2012

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /home/dw/.local/bin
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/local/games
PATH: /usr/games
PATH: /opt/bin
PATH: /u&lt;/pre&gt;</description>
    <dc:creator>Wolfgang Draxinger</dc:creator>
    <dc:date>2013-04-19T15:46:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4757">
    <title>Re: [ft] Building FT2 for embedded architectures</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4757</link>
    <description>&lt;pre&gt;Hi,

Could you post config.log generated by passing the --host option
to ./configure?

Regards,
mpsuzuki

Wolfgang Draxinger wrote:
&lt;/pre&gt;</description>
    <dc:creator>suzuki toshiya</dc:creator>
    <dc:date>2013-04-19T15:13:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4756">
    <title>[ft] Building FT2 for embedded architectures</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4756</link>
    <description>&lt;pre&gt;Hi,

I'd like to build FT2 for the ARM Cortex-M3 architecture to use it for 
text output on a display. My naive attempt to make it use the available 
cross-compiler by passing the --host option to ./configure did (of 
course) not yield a working result; we'll can't blame for for trying ;)

I'd like to build FT2 specific to my needs, that are:

- static library
- no builtin zlib, lzw and bzip2 (some compression library will be 
linked into the firmware image eventually)
- selecting the supported font formats

Most of the configuration will probably hand tailored to the target 
system anyway. So what I look for is some pointers in how to manually 
configure the FT2 build without the assistance of some autoconf/automake 
build system.


Regards

Wolfgang
&lt;/pre&gt;</description>
    <dc:creator>Wolfgang Draxinger</dc:creator>
    <dc:date>2013-04-19T15:06:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4755">
    <title>Re: [ft] FreeType and Export control</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4755</link>
    <description>&lt;pre&gt;

You mean export to different countries?  Since no encryption code is
used, there shouldn't be any limitations AFAIK.


    Werner
&lt;/pre&gt;</description>
    <dc:creator>Werner LEMBERG</dc:creator>
    <dc:date>2013-04-18T10:07:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4754">
    <title>[ft] FreeType and Export control</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4754</link>
    <description>&lt;pre&gt;Hi all,
I have some question related to Freetype and export control.
Could you tell me if FreeType need some specific authorizations for export? If so, which is the regulation to apply.
Thanks in advance for your help.
Regards

Karine Ducrocq

[&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; THALES GROUP INTERNAL &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;]

_______________________________________________
Freetype mailing list
Freetype&amp;lt; at &amp;gt;nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
&lt;/pre&gt;</description>
    <dc:creator>DUCROCQ Karine</dc:creator>
    <dc:date>2013-04-18T09:49:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4753">
    <title>Re: [ft] Help finding glyphs in TTF files</title>
    <link>http://permalink.gmane.org/gmane.comp.fonts.freetype.user/4753</link>
    <description>&lt;pre&gt;

Hope you can find the real issue soon!


    Werner
&lt;/pre&gt;</description>
    <dc:creator>Werner LEMBERG</dc:creator>
    <dc:date>2013-04-02T13:19:07</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.fonts.freetype.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.fonts.freetype.user</link>
  </textinput>
</rdf:RDF>
