From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Change terminology to better align users’ experience with modern GUIs
Date: Tue, 23 Jul 2019 17:43:28 +0300 [thread overview]
Message-ID: <83pnm0q0a7.fsf@gnu.org> (raw)
In-Reply-To: <20190723104448.GD27308@tuxteam.de> (tomas@tuxteam.de)
> Date: Tue, 23 Jul 2019 12:44:48 +0200
> From: <tomas@tuxteam.de>
>
> So a good strategy, if you're really hot & willing to change
> things would be to grab the documentation, and perhaps write
> a companion to the documentation "Glossary" (let's call it
> "Anti-Glossary" which translates "current" terms into the
> Emacs terminology. So someone searching for "window", "pane",
> "cursor", etc. has a chance to hit on the relevant documentation.
There's no need for "Anti-Glossary". Our Glossary already includes
some terminology from "other applications", such as "cut", "paste",
and "syntax highlighting". It could easily accommodate a few more.
> A next step might be to cross-index those "current" terms
> with the "traditional" ones.
These are already in the Glossary.
next prev parent reply other threads:[~2019-07-23 14:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 6:46 Change terminology to better align users’ experience with modern GUIs 조성빈
2019-07-23 9:37 ` Jean Louis
2019-07-23 10:13 ` 조성빈
2019-07-23 17:03 ` Gerhard Wolfstieg
2019-07-23 19:17 ` tomas
2019-07-23 22:12 ` Stefan Monnier
2019-07-23 10:44 ` tomas
2019-07-23 14:43 ` Eli Zaretskii [this message]
2019-07-23 16:15 ` tomas
2019-07-23 16:48 ` Eli Zaretskii
2019-08-03 17:37 ` Emanuel Berg
2019-08-01 1:53 ` Emanuel Berg
2019-07-23 11:38 ` Noam Postavsky
2019-07-23 13:00 ` Stefan Monnier
2019-07-23 13:11 ` MBR
2019-07-23 13:40 ` tomas
2019-07-23 13:46 ` Noam Postavsky
2019-07-23 13:59 ` tomas
2019-07-23 14:38 ` Stefan Monnier
2019-08-03 17:12 ` Emanuel Berg
2019-08-01 1:55 ` Emanuel Berg
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=83pnm0q0a7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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 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.