unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: emacs-devel@gnu.org
Subject: font-backend branch merged into the trunk
Date: Wed, 14 May 2008 11:04:05 +0900	[thread overview]
Message-ID: <E1Jw6Ld-0006R5-H1@etlken.m17n.org> (raw)

I've just merged the font-backend branch into the trunk.

But, I forgot to add Jason's these changes in the CVS log.
So, I tried "cvs admin -m...." but it seems that I don't
have the right to do that.  Could someone please add these
to the CVS log of each file?

2008-05-14  Jason Rumney  <jasonr@gnu.org>

	* font.h (struct font) [WINDOWSNT]: Remove codepage member.

	* w32font.h (w32font_open_internal): Update declaration.

	* w32font.c (w32font_open_internal): Change last argument from
	w32font_info struct to font object.  Fill in font object from
	font_entity.  Get Outline metrics if possible.  Use them to
	calculate underline position and thickness.  Use xlfd name as name
	property.  Don't set codepage.
	(w32font_open): Pass font_object to w32font_open_internal.  Don't
	update dpyinfo->smallest_font_height and
	dpyinfo->smallest_char_width.
	(w32font_draw): Use s->font.
	(clear_cached_metrics): Don't clear non-existent blocks.

	* w32term.c (w32_compute_glyph_string_overhangs): Don't compute if
	font was not found.
	(x_draw_glyph_string): Use underline position and thickness from
	font.

	* w32uniscribe.c (uniscribe_open): Pass font_object to
	w32font_open_internal.

---
Kenichi Handa
handa@ni.aist.go.jp




             reply	other threads:[~2008-05-14  2:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  2:04 Kenichi Handa [this message]
2008-05-14  2:19 ` font-backend branch merged into the trunk Stefan Monnier
2008-05-14  3:10   ` Eli Zaretskii
2008-05-14 18:03     ` Eli Zaretskii
2008-05-15  1:42       ` Kenichi Handa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Jw6Ld-0006R5-H1@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).