Fontconfig currently stores cached information about fonts in
per-directory files called 'fonts.cache-version'. These are stored
right in the font directories which means they'll get copied and managed
automatically as people move fonts around.
However, storing cached information in what is
Hi,
I think I've some opinion on this ~
However, storing cached information in what is ostensibly a read-only
directory is unfriendly and violates the FSH guidelines. This data is
just cached versions of data available from the font files themselves and
so the FSH says it should
Hi,
I have recently read the Li18nux2K. The globalization spec. from li18nux.org.
but it seems
that, there is no any relation between fontconfig/Xft and this spec.
IMHO, Li18nux2K regulate and standardize the direction of i18n while,
fontconfig/Xft is
complete
On Sat, Sep 07, 2002 at 09:54:31AM +0800, Zenith Lau wrote:
I have recently read the Li18nux2K. The globalization spec. from
li18nux.org. but it seems that, there is no any relation between
fontconfig/Xft and this spec.
IMHO, Li18nux2K regulate and standardize the
Around 9 o'clock on Sep 7, Zenith Lau wrote:
Any directories not matching a configured prefix would map to themselves;
this makes the existing configuration and cache files compatible.
How do you resolve any fonts which doesn't located under /usr/share/fonts ?
The prefix mapping would be
Hi,
Any directories not matching a configured prefix would map to themselves;
this makes the existing configuration and cache files compatible.
How do you resolve any fonts which doesn't located under /usr/share/fonts ?
The prefix mapping would be configurable; add a map from
Around 12 o'clock on Sep 7, Zenith Lau wrote:
Cursor.c: In function `XRenderCreateCursor':
Cursor.c:39: `X_RenderCreateCursor' undeclared (first use in this
Hmm. This is a new request, but it should be defined in the 'render.h'
file included with fcpackage. You may have to
Around 13 o'clock on Sep 7, Zenith Lau wrote:
Sorry, do you mean that, store the mapping table in the file system,
you are talking about the first idea?
I can either use a sequence of directories to encode the source font path,
or I can create a file which maps path names to file names.
