all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Göktuğ Kayaalp" <self@gkayaalp.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Jean-Christophe Helary <jean.christophe.helary@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Before l10n, better practices for (message) ?
Date: Sun, 28 May 2017 02:27:31 +0300	[thread overview]
Message-ID: <ygm1sr9c23g.fsf@xi> (raw)
In-Reply-To: <87vaon2b7r.fsf@jane> (Marcin Borkowski's message of "Sat, 27 May 2017 06:08:24 +0200")

On 2017-05-27 06:08 +02, Marcin Borkowski <mbork@mbork.pl> wrote:
> On 2017-05-23, at 04:55, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> Just replace it with 2 different spellings dispatched by the number.
>
> I guess you are aware that 2 different spellings are not enough for
> certain languages...?
>
> In Polish:
>
> 0 pakietów
> 1 pakiet
> 2, 3, 4 pakiety
> 5, 6, ..., 21 pakietów
> 22, 23, 24 pakiety
> etc.
>
> Good luck with l10n.
>
> (I do not want to discourage work on it.  But I'm afraid it's more
> difficult than many people think...  OTOH, if a reasonable
> infrastructure is introduced in Emacs, I might be tempted to provide
> some translations for Polish.)

Hi,

I don't know whether or not I'm supposed to post here, but just thought
that I'd add my two cents as a mostly-user:  I'd rather have all of
Emacs in English.  These are my reasons:

- Some packages will have translations, some won't, and thus some
  messages will be in my language, and some English, which will be
  confusing (and annoying).

- The manuals will have to be translated too.

- It will undermine online discussion, as people will start posting
  (error) messages in their locales, and others will have to decode
  them.  Also, using online documentation will become harder as now one
  will need to translate.

- Emacs probably has way more strings to be translated than most
  applications out there, which will hinder the translations and make it
  more error prone.  Also, the community is not large enough that the
  messages will always be up-to-date and correct.

I believe most users would just use Emacs in English even if the strings
were translated, as many have their LC_MESSAGES or entire OS in English:
It's just more convenient for a power user.  The Emacs community is
mostly anglophone already anyways, and I doubt having translations will
change that at all.  Also, given the size of our community and the
amount of work (translating Emacs is translating a programming language
runtime + a collection of applications), it may result to be too much of
a burden on it.

Nevertheless, if translations happen, I'll try to help with Turkish (my
mother tongue) translations.  And please excuse me if I weren't supposed
to post here as I'm not the most experienced user and have only a bunch
of patches in Emacs.

Best,
        gk.



  parent reply	other threads:[~2017-05-27 23:27 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 23:30 Before l10n, better practices for (message) ? Jean-Christophe Helary
2017-05-23  0:59 ` Tino Calancha
2017-05-23  1:18   ` Jean-Christophe Helary
2017-05-23  2:55     ` Eli Zaretskii
2017-05-23  3:38       ` Jean-Christophe Helary
2017-05-23 18:36         ` Eli Zaretskii
2017-05-23 22:00           ` Jean-Christophe Helary
2017-05-24  2:32             ` Eli Zaretskii
2017-05-24  2:40               ` Jean-Christophe Helary
2017-05-24  4:22                 ` Paul Eggert
2017-05-24  8:08                   ` Jean-Christophe Helary
2017-05-24 19:12                     ` Eli Zaretskii
2017-05-24 21:29                       ` Jean-Christophe Helary
2017-05-26  3:50                         ` Richard Stallman
2017-05-24 22:09                       ` Paul Eggert
2017-05-24 22:35                         ` Jean-Christophe Helary
2017-05-26  8:07                           ` Eli Zaretskii
2017-05-24 23:51                         ` Jean-Christophe Helary
2017-05-23  7:52       ` Jean-Christophe Helary
2017-05-23 18:42         ` Eli Zaretskii
2017-05-23 22:03           ` Jean-Christophe Helary
2017-05-26  8:14             ` Eli Zaretskii
2017-05-26 14:21               ` Jean-Christophe Helary
2017-05-26 14:44                 ` Eli Zaretskii
2017-05-26 18:08                   ` Yuri Khan
2017-05-26 19:00                     ` Eli Zaretskii
2017-05-27  1:52                       ` Jean-Christophe Helary
2017-05-26 18:54               ` Etienne Prud’homme
2017-05-26 19:06                 ` Eli Zaretskii
2017-05-26 19:15                   ` Etienne Prud’homme
2017-05-26 19:27                     ` Eli Zaretskii
2017-05-26 21:57                       ` Etienne Prud’homme
2017-05-27  7:22                         ` Eli Zaretskii
2017-05-27  1:16                 ` Jean-Christophe Helary
2017-05-27  7:43                   ` Eli Zaretskii
2017-05-27  4:08       ` Marcin Borkowski
2017-05-27  7:49         ` Eli Zaretskii
2017-05-28  4:00           ` Marcin Borkowski
2017-05-27 23:27         ` Göktuğ Kayaalp [this message]
2017-05-28  0:44           ` Jean-Christophe Helary
2017-05-28 14:44             ` Göktuğ Kayaalp

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=ygm1sr9c23g.fsf@xi \
    --to=self@gkayaalp.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@gmail.com \
    --cc=mbork@mbork.pl \
    /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.