unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: juri@jurta.org, eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Possible change to startup.el
Date: Fri, 15 Apr 2005 01:40:05 +0200	[thread overview]
Message-ID: <85ll7l0vxm.fsf@gnu.org> (raw)
In-Reply-To: <E1DM9cq-0007VP-7x@fencepost.gnu.org> (Richard Stallman's message of "Thu, 14 Apr 2005 15:03:40 -0400")

Richard Stallman <rms@gnu.org> writes:

>     > Until multi-language menus are supported, perhaps we should
>     > change the menu item to say
>     >
>     >      Emacs Tutorial (in YOUR-LANGUAGE)
>     >
>     > where YOUR-LANGUAGE stands for the language name.  This should
>     > be done only for those languages that indeed have a translated
>     > tutorial.  The tooltip should also hint about that.
>
>     I think we should do that only for those languages that can't be
>     shown in the menu.  Since this depends on a complex interaction
>     of platform, fonts and locales, I think the programmer wanting
>     to put something into a menu can't be reasonably expected to
>     make a guess.
>
>     So I think that we should add something like
>     (defun menu-string-supported-p STRING &optional DISPLAY)
>     that will tell a programmer whether a given platform is supposed to
>     be able to display a given string.
>
> This might be ok in theory, but I'd rather do something simpler.

It is a reoccuring problem, and it will become more prevalent in
future.

For example, AUCTeX has an option that will enable the use of Unicode
math characters in menus.  How can I know when to enable it by
default?  I need to know for every platform that Emacs might be
running on, and this might even depend on your settings for the menu
font and the locale.

The necessary knowledge when to enable this option and when not is so
complicated to gather that we should provide an interface that
reflects our current wisdom.  The proposed interface has the advantage
that it is easy to use in my opinion (though I'll be glad to hear
something simpler).  Of course it is not simple to implement, but the
reason for that is that the task _is_ not simple, and it makes sense
to solve it once in Emacs instead of anew for every application.

If you have an idea that is also simpler to _use_, I'll be glad to
hear about it.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-04-14 23:40 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-03 10:31 Possible change to startup.el Thien-Thi Nguyen
2005-04-07  6:55 ` Juri Linkov
2005-04-08  3:22   ` Richard Stallman
2005-04-08  6:31     ` Marcelo Toledo
2005-04-08  7:27       ` Kenichi Handa
2005-04-08 18:32       ` Juri Linkov
2005-04-08 18:43         ` Marcelo Toledo
2005-04-10  1:54         ` Richard Stallman
2005-04-08 10:44     ` Eli Zaretskii
2005-04-08 18:32       ` Juri Linkov
2005-04-09  8:00         ` Eli Zaretskii
2005-04-13 23:58           ` David Kastrup
2005-04-14  4:02             ` Eli Zaretskii
2005-04-14  9:46               ` David Kastrup
2005-04-15  8:15                 ` Eli Zaretskii
2005-04-14 19:03             ` Richard Stallman
2005-04-14 23:40               ` David Kastrup [this message]
2005-04-17  1:49                 ` Richard Stallman
2005-04-17  9:31                   ` David Kastrup
2005-04-17 19:20                     ` Richard Stallman
2005-04-17 19:51                       ` David Kastrup
2005-04-10  1:54         ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2005-03-31 12:01 Thien-Thi Nguyen
2005-03-31 12:59 ` Kim F. Storm
2005-03-31 13:43   ` David Kastrup
2005-03-31 22:19     ` Kim F. Storm
2005-04-01  4:10   ` Richard Stallman
2005-04-01  4:03 ` Juri Linkov
2005-04-03  5:20   ` Richard Stallman
2005-03-31 11:37 Thien-Thi Nguyen
2005-03-31 12:05 ` Miles Bader
2005-03-31 13:32   ` Thien-Thi Nguyen
2005-03-31 14:29     ` Miles Bader
2005-03-31 16:15       ` Thien-Thi Nguyen
2005-03-31 22:23         ` Miles Bader
2005-04-01  4:10   ` Richard Stallman
2005-03-30 22:47 Thien-Thi Nguyen
2005-03-30 23:38 ` David Kastrup
2005-04-01  4:11   ` Richard Stallman
2005-03-31  1:40 ` Miles Bader
2005-03-31  1:02   ` Marcelo Toledo
2005-03-31  3:20     ` Miles Bader
2005-03-31  2:21       ` Marcelo Toledo
2005-03-31  6:59 ` Juri Linkov
2005-04-01  4:11 ` Richard Stallman
2005-03-25 18:07 Thien-Thi Nguyen
2005-03-27  3:52 ` Richard Stallman
2005-03-27 23:15   ` Juri Linkov
2005-03-28 22:53     ` Richard Stallman
2005-03-29 20:19       ` Thien-Thi Nguyen
2005-03-30  4:08         ` Marcelo Toledo
2005-03-30  9:42           ` Thien-Thi Nguyen
2005-03-24 10:49 Thien-Thi Nguyen
2005-03-24 19:05 ` Miles Bader
2005-03-25  6:43 ` Richard Stallman
2005-03-21 18:44 David Kastrup
2005-03-21 20:50 ` Thien-Thi Nguyen
2005-03-21 21:10   ` David Kastrup
2005-03-21 21:25     ` Andreas Schwab
2005-03-21 22:14       ` David Kastrup
2005-03-22  0:03         ` Andreas Schwab
2005-03-22  1:38         ` David Hansen
2005-03-23 18:25         ` James Cloos
2005-03-27  3:53           ` Richard Stallman
2005-03-22  4:55   ` Eli Zaretskii
2005-03-22  6:24     ` Miles Bader
2005-03-22  8:15       ` Kenichi Handa
2005-03-22  8:27         ` Miles Bader
2005-03-22 10:40           ` David Kastrup
2005-03-22 12:44             ` Jason Rumney
2005-03-22 20:31             ` Werner LEMBERG
2005-03-22 11:23           ` Kenichi Handa
2005-03-22 12:33           ` Juri Linkov
2005-03-22 19:32       ` Eli Zaretskii
2005-03-22 10:18     ` David Kastrup
2005-03-22 19:34       ` Eli Zaretskii
2005-03-22 22:24         ` David Kastrup
2005-03-22 20:44   ` Richard Stallman
2005-03-22 22:32     ` Thien-Thi Nguyen
2005-03-23  6:21       ` Richard Stallman
2005-03-23 13:55         ` Juri Linkov
2005-03-23 18:01           ` Werner LEMBERG
2005-03-25 12:51             ` Kenichi Handa
2005-03-23 20:25           ` Richard Stallman
2005-03-22 13:57 ` Richard Stallman

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=85ll7l0vxm.fsf@gnu.org \
    --to=dak@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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).