Around 8 o'clock on Nov 19, Brian Stell wrote:
An important feature in browsers is that the page display
begins *before* the entire page is received. This is important
for systems with phone modems where it can take a while for
larger documents.
Which is precisely why the Xft mechanism is
Around 9 o'clock on Nov 20, Brian Stell wrote:
Here is a possible set of choices/fallbacks given a desired
font name and desired font encoding-registry or language group (1).
1) Name and encoding-registry / TT language group
Best choice.
Have you found the TT language group
Around 23 o'clock on Nov 21, yao zhang wrote:
In terms of bitmap fonts, one thing you may consider is to make it
scalable. (You may mention this somewhere else, I don't remember
for sure.) Interpolated scaling can make the glyphs look like anti-aliased
outline font: at edges, the gray
Around 17 o'clock on Nov 30, Juliusz Chroboczek wrote:
That's interesting. Why is it different from doing xset fp ... from
your Xsession file?
Because 'xset fp default' would not have the same behaviour?
Keith PackardXFree86 Core TeamSuSE, Inc
are reasonably well covered by the font.
Keith PackardXFree86 Core TeamSuSE, Inc.
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
to be answered before we can design one:
+ What basic signalling mechanism should be used
+ Who has permission to signal apps
Suggestions are welcome, as this would be a useful addition to the
architecture.
Keith PackardXFree86 Core TeamSuSE, Inc
shared the same font configuration mechanism as
Xft, then they'd get updated information via the same route. Right now,
you can install new fonts, re-run 'mkfontdir' and then 'xset fp rehash'
and the X server will see the new fonts.
Keith PackardXFree86 Core TeamSuSE, Inc
as capable as possible.
The most important feature is that future improvements will not be so
severely handicapped by requirements to not change the X server -- I think
the Render extension provides the foundation for any number of future
experiments with text output.
Keith PackardXFree86 Core
isolate people left without Render
support.
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
existing font users. The immediate goal is to standardize how fonts are
located so that all fonts are available to all applications.
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED
idea than any amount of server-side
craziness.
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
.
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
configuration file be transitioned to XML as well; the ability to have
external agents edit the file without needing a complete understanding of
the syntax should be very useful.
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
!-- This is the Document Type Definition
space was more
likely to be preserved correctly within an attribute than with an element.
Given the xml:space attribute, perhaps this isn't an issue. Can I ensure
that white space remains unmolested within family names?
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
Around 2 o'clock on Jan 22, Gioele Barabucci wrote:
I'd also write dir/etc/X11/fonts/TTF/dir...
Ok, now that I believe I can preserve whitespace in those spots, I've
redone things as follows:
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
?xml version=1.0
impacting their tool.
I think a well designed XML DTD will be nearly as easy to use as the
existing Xft configuration language; certainly the semantics are the same,
only the syntax has changed.
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
new e-lisp code customized
for font configuration :-).
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
subsets to work; for the later, I have
a proposal that needs more consideration before it's ready to submit for
comment.
This code is all available from my CVS server (http://keithp.com has a
pointer), and I hope to get it into XFree86 shortly.
Keith PackardXFree86 Core TeamCompaq
the CSS2 matching algorithm? I
prefer to adopt an existing standard rather than developing my own.
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo
Around 14 o'clock on Feb 20, Juliusz Chroboczek wrote:
[Background: this is the XFree86 font list, and Keith Packard is
sort-of-seriously thinking about unifying the font configuration
mechanism in Xft with CSS 2.]
Mostly, I'm looking for a reasonable font matching scheme and CSS2
are significantly easier to
read than the Type1 Times.
Parts of CSS2 compliance will require correct configuration file
structure; I'd prefer to retain the current flexibility so that portions
of CSS2 in conflict with the users desires can be overridden.
Keith PackardXFree86 Core TeamCompaq
library provides client-side font support for
all X servers, making it possible for applications to take advantage of the
capabilities client-side fonts bring to every desktop. The Render extension
provides the infrastructure to do this with performance equivalent to
server-side fonts.
Keith Packard
could be ported to this API without significant effort or any loss
of functionality.
Let's use the ST teams expertise in international text layout to its
fullest and leave the underlying font management to existing mechanisms.
Keith PackardXFree86 Core TeamCompaq Cambridge Research
justification and typesetting algorithms require incrementally querying
the metrics of the entire line after adding each character. That's dozens
of round trips for each typeset line unless the client can precisely
compute the metrics of the text locally.
Keith PackardXFree86 Core Team
, but server side text can only be
implemented with an extension. Attempting to emulate server-side text
with client-side code doubles the configuration problem -- you must
configure client-side fonts for the emulation and server-side fonts for
the extension.
Keith PackardXFree86 Core
Around 15 o'clock on Mar 1, Erik van der Poel wrote:
I'm not 100% sure that it's going away, but Keith Packard and others
have been working on new ways of doing fonts, i.e. fontconfig and Xft.
Fontconfig uses a new naming scheme which is currently similar to CSS2
in design and will move
).
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
.
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
.
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
directions within XFree86.
It would be great if you could help us clarify the current state of the
Render specification and the server implementation, protocol and API.
Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab
___
Fonts
Around 20 o'clock on May 27, Owen Taylor wrote:
I'm not particularly happy with the way the Xft backend for Pango
works at the moment ... it's complex, memory hungry, and relatively
slow. (Pango shaping with Xft is about twice as slow as Pango shaping
with the old X backend.)
That's really
-scale bitmaps
for AA rendering. It should be quite easy to create an optimized version
of this given the fixed format for FreeType bitmaps.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED
Around 17 o'clock on May 28, Yu Shao wrote:
I tested Xft2 with some Chinese pcf fonts, like gb16fs.pcf.gz come with
Xfree86 4.2,
FreeType can't yet read PCF fonts that are compressed; it should be able
to read them if you uncompress them first.
Keith PackardXFree86 Core Team
to be
used to select preferred faces for each language tag.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
that I
store.
Hmm. We might find a way to discover patterns which are equal except for
size -- store that sizeless pattern along with the list of point-
pixel size mappings. Perhaps FcPatternEqual could take an include
object set and an exclude object set?
Keith PackardXFree86
it doesn't crash.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
of FreeType (2.0.9) doesn't
seem to find any non-BMP encodings in the type-4 table, it finds 30 type 4
segments in code2001.ttf, the last of which encodes glyph 65535.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts
-fontset mapping; that should be pretty
straightforward, perhaps give a few additional APIs in fontconfig to
generate hash values for patterns. Other than that, I think most
of the code here should run fast enough to be left uncached.
Keith PackardXFree86 Core TeamHP Cambridge
Around 22 o'clock on May 30, =?ISO-8859-1?Q?Joaqu=EDn?= Cuenca Abela wrote:
is it only me, or xft-config.in (line 92) should be:
libs=-lXft ...
Yes, that's correct -- someone else noted this a couple of days ago. The
fix is in CVS, but I haven't rebuilt the tarballs since then.
Keith
arabicasmo708 /* 61 */
#define FC_LANG_WE_LATIN_1 welatin1 /* 62 */
#define FC_LANG_US us/* 63 */
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
Around 0 o'clock on May 31, Keith Packard wrote:
I've updated the tarballs containing Xft and fontconfig bits and have
included Xrender and Xft1 sources as well. Those haven't been
'autoconf'ized yet, so they only build with xmkmf.
I forgot to include the path to the files; it's the same
scaling; that keeps broken
applications working while avoiding horrors on the screen, and eliminating
the scaling code from the server. Perhaps ':nearest'?
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL
the language tag to fontconfig and expect that the
matching rules will generate a reasonable match.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
except plug
X, fontconfig and FreeType together; a GL-specific library should be of
similar (if not smaller) size.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman
, but I'm willing to try.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
for
and share whole maps.
Yes, the sharing is recursive so that fonts which are sharing every page
end up sharing the top level as well. That's why the number of CharSets
is (significantly) less than the number of fonts.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
was somehow different
from UTF-16. Thanks for the clarification.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
that will be hidden to from the bulk
of Mozilla's current PUA codepoint adventure.
I'm currently busy getting pango and fontconfig talking sweetly, so I
won't be able to explore MathML right now.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
extends
that function.
That allows me to get from Unicode 3.2 codepoints to glyphs; now I need to
get from the mozilla PUA codepoints to Unicode 3.2 codepoints. A
definitive list of the PUA codepoints that are used would be very useful
here.
Keith PackardXFree86 Core TeamHP
the
information was available, I could pass it down.
(As you might guess, I'm a big fan of optically scaled fonts.)
I was unaware that any foundrys were spending the time and money to build
fonts in this fashion any more. It would be nice...
Keith PackardXFree86 Core TeamHP
that far from X-specific calls.
The Mozilla code follows the X core-font version which always uses pixel
sizes; the UI exposes pixel sizes in the configuration UI. I did't like
this, but followed along in the Mozilla patches.
Keith PackardXFree86 Core TeamHP Cambridge Research
are distinct from the set of
codepoitns suitable for the display of traditional Chinese. That would
be nicer than my current kludge of marking any font suitable for
traditional chinese as unsuitable for simplified Chinese.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
if (covers_almost_all_of (Big5))
font supports traditional Chinese
Thanks, this works just fine. I'm much happier with this solution.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL
with testing only a signifiant fraction,
for all other languages all chars must be tested.
Yes, the tolerance value given for the Han languages is 500 codepoints
while the value for non-Han languages is two orders of magnitude smaller.
Keith PackardXFree86 Core TeamHP Cambridge Research
in verifying it's
sensitivity and specificity are welcome to check it out and run:
$ FC_DEBUG=256 fc-cache -f
This will display the number of missing glyphs in each language for each
font and also display errors in the lang value relative to that specified
in the TrueType file.
Keith Packard
from the latin scripts; that should leave
all of them including only the alphabet.
I've also committed this whole mess to XFree86 CVS; the coverage
files can be found in xc/lib/fontconfig/fc-lang/*.orth
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
Around 22 o'clock on Jul 7, Yu Shao wrote:
It seems a typo and I think using FcCodePageSet is always safer?
Good catch, there was a typo, but that code has since been deleted in
favor of the new RFC 3066-based language detection.
Keith PackardXFree86 Core TeamHP Cambridge
based on the codePageRange bits.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
of this prohibits applications and users from explicitly
selecting a font which is inappropriate for their current locale or
document language -- explicit family names are now given greater weight
than language matching when selecting fonts.
Keith PackardXFree86 Core TeamHP Cambridge Research
of some random font most likely suitable for Latin
languages.
Or would this only lead to confusion and chaos?
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman
?
(no case conversion is necessary, FC_LANG comparisons are already case
insensitive).
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
with applications which haven't called
setlocale (LC_ALL, )? Do I:
a) call setlocal (LC_ALL, ) myself?
b) use $LANG or $LC_CTYPE?
c) Ignore the locale information and leave the
font language preference unset?
Keith PackardXFree86 Core
, then it
couldn't even distinguish between Ming and Sung forms.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
,
but applications using this font shouldn't care; they already need to load
multiple fonts if they want to display Georgian and Chinese at the same
time, that support obviously can handle adding another font for ASCII.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
that POSIX specifies the order in which these are used, and given
that all of my test programs don't call setlocale, I've added the trivial
code to fetch from the environment.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts
changes to the font database caching mechanism or
would require editing each font database entry at startup by running it
through some configuration.
Note that the format shown above nicely parallels the per-language font
configuration mechanism already used by Mozilla.
Keith Packard
rather automatically
extract all of the necessary information as this will be less prone to
user error.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo
of a trademarked font name which would then go
and match some other font.
We were allowed to make fontconfig aliases between the Lucidux and Luxi
families because of this.
If you can think of a way to reconcile these two requirements, please
suggest it.
Keith PackardXFree86 Core TeamHP
support only ASCII names?
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
Microsoft/Unicode entry.
I've started putting code together that ignores the FreeType family/style
values and walks the name table if available. I have an apple roman
transcoding table available and I'm not afraid to use it.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
Around 18 o'clock on Jul 12, Keith Packard wrote:
I'll add transcoding for apple-roman names. My intent is to prefer
english names, and failing that, to choose the first entry in a known
encoding.
Well, *that* was entertaining. It almost works. Except for MS Mincho.
For both
with a list of 150 languages.
This leaves us wondering how to display localized names for users of other
languages. I guess we'll assume they speak the modern lingua franca.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts
elements.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
of names to a name appropriate for the user is the only locale
-dependent step.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
with their languages. This can
be done with FcNameUnparse/FcNameParse which generate UTF-8
encoded strings for the font name.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http
of available fonts to match the ascii name. This would
have the (questionable) property where the application would find out that
configured fonts were missing.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
Around 12 o'clock on Jul 25, Owen Taylor wrote:
If you are using Qt with Xft, there are a couple of fixes on top
of qt3.diff you'll need; the attached are what we have in Rawhide
in a quick check.
Thanks for the update; I'll cut a new patch after I test this fix.
Keith Packard
intend to stabilize and ship this version in short order; I'm interested
in hearing about problems and concerns, but functional enhancements will
await a new version.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts
versions of Xft is probably only asking for trouble. I've
also not updated Qt3 in a few weeks making the patch somewhat stale at
this point.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED
a problem with that. Xft2/fontconfig are on a separate
release schedule from XFree86 making it possible to update them
independently.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http
I've built and tagged RC2 for fontconfig. The bits are available at:
http://keithp.com/fonts/pub/fcpackage.rc2.tar.gz
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
Major changes:
fontconfig:
The weird first/not-first hack for checking the font vs
verification. Otherwise, the directory is scanned and each file
checked against the cache. Again, the per-user cache is automatically
updated when this information changes, so the rescanning affects only the
first application to run after the filesystem has changed.
Keith Packard
debugging situations.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
in the generic alias and you'll have a uniform (if displeasing)
appearance across almost all text.
One explicit goal is to permit a global configuration which is generally
usable by everyone without change; any local customizations neeed to the
global configuration file should be considered bugs.
Keith
display garbage on the screen.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
and fontconfig to make it even easier.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
experience writing TrueType font files, help would be
greatly appreciated in building something that can create these new files.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http
?
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
the current Xserver/fontserver 'font' library to fontconfig,
we'll have done this for both applications.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo
news. There's no particular hurry for this, but it would be
nice to get things tested in Xft and fontconfig before XFree86 4.3 goes
out the door. Switching the main fonts in the release can wait until a
later day.
We eagerly await future developments in this area :-)
Keith Packard
, a proportional and monospaced version of the
same face.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
listing code can advertise
whatever DPI it likes.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
by
the font. This is quite common with GB18030 fonts which covers GB2312,
Big5 and JIS X 0208. A GB18030 font which includes only bit 18 in the
codePageRange bits will only be listed as supporting zh-cn and not zh-tw,
even though it nominally covers Big5.
Keith PackardXFree86 Core Team
font, but the right fix is to go and get reasonable fonts; the
alternate fix is to place the complete font first in the list.
I'll go dig up a unicode table for KSC-5607.1987 and replace the existing
ko map with that.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
at only a very few sizes.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
this, then will Xft now use the embedded bitmaps for
the non-antialiased sizes or will it try to use the outlines like
before?
Xft1 still has the old (broken) behaviour. The current version of Xft
uses bitmaps when antialiasing is disabled.
Keith PackardXFree86 Core TeamHP Cambridge
to
have some issues of this nature; I'm continuing to use the XFree86 copy
of 2.1.1 for now and have moved the debian versions out of the way.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL PROTECTED
/fonts-cache-1
Any directories not matching a configured prefix would map to themselves;
this makes the existing configuration and cache files compatible.
Does this seem like a good plan? Can anyone come up with a better way of
moving the storage of fonts.cache into /var/cache?
Keith Packard
/cache/fontconfig then. I don't really care.
Though, I think /var/cache/fonts should be the better, as I like the style
what fontconfig do.
To some extent, we can ask if a slight reinterpretation of the FSH can be
permitted in this case.
Keith PackardXFree86 Core TeamHP
to replace the render.h found
in /usr/X11R6/include/X11/extensions to get things to build. If so, let
me know and I'll see how I can fix the package.
Keith PackardXFree86 Core TeamHP Cambridge Research Lab
___
Fonts mailing list
[EMAIL
1 - 100 of 133 matches
Mail list logo
