zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: Agron Selimaj <as9902613@gmail.com>, zsh-workers@zsh.org
Subject: Re: Is there any desire to support languages other than English in zsh?
Date: Wed, 7 Jun 2023 19:56:37 -0700	[thread overview]
Message-ID: <CAH+w=7aLzRKhbsApRXSAe5gNETCZwpWYkasZDwJAX-rLJpkb1w@mail.gmail.com> (raw)
In-Reply-To: <964331068.5072751.1686066885601@mail.virginmedia.com>

On Tue, Jun 6, 2023 at 8:54 AM Peter Stephenson
<p.w.stephenson@ntlworld.com> wrote:
>
> > On 06/06/2023 16:20 Agron Selimaj <as9902613@gmail.com> wrote:
> > However, I am not sure the zsh project supports gettext (and POEdit) throughout.
> > So, in order to support localization in general, we first must use gettext everywhere.
> > Is this something this team is willing to do?
>
> This is certainly a useful thing to do, however previous discussions suggest there is
> no one around to do the considerable amount of work that supporting databases on this
> scale would require.

Having previously overseen the gettext-ification of a piece of
software of similar original vintage and complexity, I would say that
supporting the databases is often the least of the issues.  Sentence
structure varies, which requires converting catenated substrings into
snprintf formats or sets of alternatives; pluralization may differ,
requiring 0 / 1 / >1 conditionals even with gettext intervention; etc.
Also, because of the pervasive changes required, we found it necessary
to merge all outstanding code changes and call a halt to other
development until the "l10n" pass was complete, or we couldn't track
deltas accurately (though we were stuck with CVS for version control
at the time).

This is definitely not something we would want to dive into until
after whatever the next zsh release is, is done.


  reply	other threads:[~2023-06-08  2:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 15:20 Agron Selimaj
2023-06-06 15:54 ` Peter Stephenson
2023-06-08  2:56   ` Bart Schaefer [this message]
2023-06-08  3:52     ` Agron Selimaj
2023-06-08  6:53       ` zeurkous
2023-06-08  7:46         ` FU: " zeurkous
2023-06-08 10:13       ` Oliver Kiddle
2023-06-08 10:26         ` Peter Stephenson
2023-06-08 11:02           ` zeurkous
2023-06-08 10:44         ` zeurkous

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='CAH+w=7aLzRKhbsApRXSAe5gNETCZwpWYkasZDwJAX-rLJpkb1w@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=as9902613@gmail.com \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).