unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: grischka <grishka@gmx.de>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: Bidi reordering engine upgraded
Date: Fri, 17 Oct 2014 16:30:05 +0300	[thread overview]
Message-ID: <83vbni259e.fsf@gnu.org> (raw)
In-Reply-To: <544117E3.4030201@gmx.de>

> Date: Fri, 17 Oct 2014 15:21:39 +0200
> From: grischka <grishka@gmx.de>
> Cc: emacs-devel@gnu.org
> 
> martin rudalics wrote:
> >  > This is because to the human eye pixels are similar to points in math
> >  > (i.e.has location, does not have extent).  Therefor, a mental 
> > "magnifying
> >  > glass" (in order to be useful) needs to preserve the point-like property
> >  > of pixels unaffected from the "zoom factor".
> >  >
> >  > Which means that what counts for line length is not number of pixels
> >  > but the spaces between.  See line of length 10, magnified:
> >  >
> >  >      0   1   2   3   4   5   6   7   8   9   0
> >  >      *   *   *   *   *   *   *   *   *   *   *
> > 
> > I doubt my eye (and whatever there's left behind it) would consider
> > 
> >   0
> >   *
> > 
> > having zero extent.
> 
> Nobody would consider a single pixel to mean anything in particular.
> For that to happen it needs to be placed in relation to other pixels.
> 
> For example two pixels can make a line already.

We are talking about a single-pixel vertical line (whose height is
more than 1 pixel).  Such a line definitely means something.



  reply	other threads:[~2014-10-17 13:30 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 11:12 Bidi reordering engine upgraded grischka
2014-10-17 11:42 ` martin rudalics
2014-10-17 11:47   ` David Kastrup
2014-10-17 13:21   ` grischka
2014-10-17 13:30     ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-10-15 14:51 Eli Zaretskii
2014-10-15 15:22 ` Dmitry Antipov
2014-10-15 15:47   ` Eli Zaretskii
2014-10-15 16:00     ` Dmitry Antipov
2014-10-15 16:31       ` Eli Zaretskii
2014-10-15 17:28         ` Eli Zaretskii
2014-10-15 17:50           ` Eli Zaretskii
2014-10-16  3:55             ` Dmitry Antipov
2014-10-16  7:21               ` Eli Zaretskii
2014-10-16  9:42                 ` Thien-Thi Nguyen
2014-10-16 10:15                   ` Eli Zaretskii
2014-10-16 13:27                     ` Thien-Thi Nguyen
2014-10-16 13:51                       ` Eli Zaretskii
2014-10-17  5:42                         ` Thien-Thi Nguyen
2014-10-17  6:16                           ` Eli Zaretskii
2014-10-17  7:50                             ` Thien-Thi Nguyen
2014-10-17  8:25                               ` Eli Zaretskii
2014-10-17 10:27                                 ` Thien-Thi Nguyen
2014-10-17 10:31                                   ` Eli Zaretskii
2014-10-16  9:51                 ` Dmitry Antipov
2014-10-16 10:20                   ` Eli Zaretskii
2014-10-16 11:28                   ` Eli Zaretskii
2014-10-17  6:46                 ` Eli Zaretskii
2014-10-17 17:45                 ` Jan Djärv
2014-10-17 18:45                   ` Eli Zaretskii
2014-10-17 19:32                     ` Stefan Monnier
2014-10-18 12:34                     ` Jan Djärv
2014-10-18 12:54                       ` Eli Zaretskii
2014-10-18 13:13                         ` Eli Zaretskii
2014-10-19 11:45                           ` Jan Djärv
2014-10-19 13:19                             ` Eli Zaretskii
2014-10-19 11:49                           ` Jan Djärv
2014-10-19 13:20                             ` Eli Zaretskii

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=83vbni259e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=grishka@gmx.de \
    --cc=rudalics@gmx.at \
    /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).