unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: master e4e1e268c8e 2/2: Set a default locale on Android
Date: Thu, 07 Dec 2023 20:11:03 +0200	[thread overview]
Message-ID: <83sf4d2894.fsf@gnu.org> (raw)

> branch: master
> commit e4e1e268c8e9f7de6fe5d4b05beb595a1781c02c
> Author: Po Lu <luangruo@yahoo.com>
> Commit: Po Lu <luangruo@yahoo.com>
> 
>     Set a default locale on Android
>     
>     * doc/emacs/android.texi (Android Environment): Revise for
>     change.
>     
>     * src/android.c (initEmacs): Set LANG to either en_US.utf8 or C,
>     subject to whether the system is newer than Android
>     5.0 (inclusive).

Is this the best we can do on Android?  AFAIU, the issue here is that
the locales available on Android are different from those recognized
by the C library.  But cannot we solve this by implementing a mapping
from Android locales to libc locales?  If not, why not?

I think arbitrarily using en_US.utf8 could surprise users and worse,
could produce effects that break UX.  For example, LANG defines the
default spell-checking dictionary, so the above basically forces users
of non-English locales to manually change the dictionary each time,
or customize their Emacs to do that, something they don't have to do
on other platforms.

We solved a similar problem on MS-Windows, so why cannot we solve it
on Android?



             reply	other threads:[~2023-12-07 18:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 18:11 Eli Zaretskii [this message]
2023-12-08  0:11 ` master e4e1e268c8e 2/2: Set a default locale on Android Po Lu
2023-12-08  6:43   ` Eli Zaretskii
2023-12-08  6:49     ` Po Lu
2023-12-08  7:08       ` Eli Zaretskii
2023-12-08  7:24         ` Po Lu
2023-12-08  7:45           ` Eli Zaretskii
2023-12-08 10:30             ` Po Lu
2023-12-08 12:27               ` Eli Zaretskii
2023-12-08 13:40                 ` Po Lu
2023-12-08 14:31                   ` 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=83sf4d2894.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    /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).