unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arthur Miller <arthur.miller@live.com>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: Stefan Kangas <stefan@marxist.se>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Swedish calendar localization in official release (sv-kalender.el)?
Date: Thu, 08 Jul 2021 04:23:38 +0200	[thread overview]
Message-ID: <AM9PR09MB49775EB3B7872925CE19F26B96199@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <m28s2ixkjg.fsf@fastmail.fm> (Filipp Gunbin's message of "Wed, 07 Jul 2021 17:31:31 +0300")

Filipp Gunbin <fgunbin@fastmail.fm> writes:

>> Would it be an idea to have those array for names in separate
>> files from hollidays and maybe shipped with Emacs. I can
>> machine-generate those for ~200 languages, and they are really small. I
>> am thinking of a file structure like: "lisp/calendar/locale/". In locale
>> directory would be one file per language named something like
>> "names-countrycode.el" (for example names-fi.el, names-sv.el,
>> names-ar.el etc). A content would be just names of days and
>> months. Content of each file would like in code belove the email.
>
> There're countries in which multiple languages are in use, so it's not
> sufficient to map country code to a file.  Rather, a language should be
> mapped to a file.

Yes, of course, that is what I actually meant, a file per language, but
wrote clumsy in speed country. If you check ls output from folder with
generated languages or pasted code, these are language files, not
country files: for example names-ar.el is for arabic language, names-sv
is for swedish etc.

There are entire iso standards to deal with locales, their names etc and
I don't think that calendar.el needs to implement entire ICU. I just
wish to automate parts that can be easily automated.

@Stefan, those files could be distributed as an Elpa package, they don't
need to be shipped with Emacs itself.



  reply	other threads:[~2021-07-08  2:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-04 11:40 Swedish calendar localization in official release (sv-kalender.el)? Arthur Miller
2021-07-05 11:51 ` Stefan Kangas
2021-07-05 13:00   ` Teemu Likonen
2021-07-05 21:02     ` Arthur Miller
2021-07-05 20:58   ` Arthur Miller
2021-07-06  7:55   ` Teemu Likonen
2021-07-06  9:38     ` Arthur Miller
2021-07-06 10:30       ` Teemu Likonen
2021-07-06 13:38         ` Arthur Miller
2021-07-06 16:38           ` Stefan Kangas
2021-07-06 17:23             ` Arthur Miller
2021-07-07 14:31               ` Filipp Gunbin
2021-07-08  2:23                 ` Arthur Miller [this message]
2021-07-08 14:27                   ` Filipp Gunbin
2021-07-09  9:00                     ` Arthur Miller
2021-07-06 12:20     ` Stefan Kangas

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=AM9PR09MB49775EB3B7872925CE19F26B96199@AM9PR09MB4977.eurprd09.prod.outlook.com \
    --to=arthur.miller@live.com \
    --cc=emacs-devel@gnu.org \
    --cc=fgunbin@fastmail.fm \
    --cc=stefan@marxist.se \
    /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).