From: "Drew Adams" <drew.adams@oracle.com>
To: "'Kenichi Handa'" <handa@m17n.org>, <3564@emacsbugs.donarmstrong.com>
Subject: bug#3564: 23.0.94; compose-region doc string
Date: Mon, 15 Jun 2009 06:14:37 -0700 [thread overview]
Message-ID: <AAD7FAEDDC0649708F012EA7C77B39BF@us.oracle.com> (raw)
In-Reply-To: <E1MG5uI-0003m1-9A@etlken>
That helps a lot; thanks.
See inline for English suggestions. But I'm ignorant of this area, so hopefully
someone else will speak to the correct terminology to use - I don't know it.
> From: Kenichi Handa Sent: Sunday, June 14, 2009 11:43 PM
> +Characters are composed relatively, i.e. composed by overstriking
> +or stacking depending on ascent, descent and other metrics values
> +of glyphs.
"other metrics" or "other metric values"
> +For instance, if the region has three characters \"XYZ\", X is
> +regarded as BASE glyph, and Y is displayed:
> + (1) above BASE if Y's descent is not positive,
> + (2) below BASE if Y's ascent is not positive,
I wonder if "descent" and "ascent" shouldn't be "descender" and "ascender" or
something like that? Need to check with someone who knows typography
terminology, unless you're sure about "descent" and "ascent".
> + (3) over BASE (at the same position of BASE) otherwise.
"on BASE" or "at BASE" or "on top of BASE" or "at the BASE position"
> +and Z is displayed with the same rule while regarding the whole
> +XY glyphs as BASE.
>
> When called from a program, expects these four arguments.
Sounds good. Without that, I understood nothing. Now, I understand a little.
Thx.
next prev parent reply other threads:[~2009-06-15 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 19:30 bug#3564: 23.0.94; compose-region doc string Drew Adams
2009-06-15 6:43 ` Kenichi Handa
2009-06-15 13:14 ` Drew Adams [this message]
2009-06-16 0:36 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AAD7FAEDDC0649708F012EA7C77B39BF@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=3564@emacsbugs.donarmstrong.com \
--cc=handa@m17n.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.