unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mattias Engdegård" <mattiase@acm.org>
To: Jean Forget <J2N-FORGET@orange.fr>
Cc: Glenn Morris <rgm@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
	19174@debbugs.gnu.org
Subject: bug#19174: Wishlist/suggestion for emacs/lisp/calendar/cal-french.el
Date: Thu, 10 Jun 2021 11:09:14 +0200	[thread overview]
Message-ID: <764F506B-30E1-460A-8D41-8BE56C58DED9@acm.org> (raw)
In-Reply-To: <39726481-0edd-453c-1143-98fbf0363a95@orange.fr>

10 juni 2021 kl. 07.40 skrev Jean Forget <J2N-FORGET@orange.fr>:

> http://datetime.mongueurs.net/Histoire/tit/titre-g.en.html
> 
> When you read the pages for the additional days, you see that
> they are printed with a day number and a day-of-week name.

Thank you, that is a primary source! Of course we know little about the context: it may have been written that way for sake of a uniform presentation. However, being no scholar of the republican calendar I will leave that judgement to you.

> About lower case vs upper case: The French convention for
> Revolutionary names may be different from the French convention
> for Gregorian names. Most often, the revolutionary month names
> and day names are printed with an initial capital letter.
> Yet, there are exceptions. See the front page (link above)
> which mentions the "9 floréal an 7" with a lower case "f".

Yes, it is a fair assumption that the usage conventions were less rigid in those days, and it can have been a matter of whether the words occurred in a title or in running text. The (French) Wikipédia article uses predominantly lower case but it obviously follows modern conventions. Again, your call.

Feel free to base your changes on my previously posted diff, but give it a good read-through so that the changes are indeed exactly those that you intended. Also, we'd be happy if you wrote some tests; test/lisp/calendar/cal-french-tests.el would be a suitable place.






  reply	other threads:[~2021-06-10  9:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 21:01 bug#19174: Wishlist/suggestion for emacs/lisp/calendar/cal-french.el Jean Forget
2014-11-26 19:14 ` Glenn Morris
2021-05-28  2:00 ` Lars Ingebrigtsen
2021-06-07 19:32   ` Jean Forget
2021-06-08  9:34     ` Lars Ingebrigtsen
2021-06-08 17:47       ` Jean Forget
2021-06-09 10:07         ` Lars Ingebrigtsen
2021-06-10  5:56           ` bug#19174: JEAN FORGET Jean Forget
2021-06-09 14:11 ` bug#19174: Wishlist/suggestion for emacs/lisp/calendar/cal-french.el Mattias Engdegård
2021-06-10  5:40   ` Jean Forget
2021-06-10  9:09     ` Mattias Engdegård [this message]
2021-06-15  5:55       ` Jean Forget
2021-06-15 10:29         ` Mattias Engdegård
2021-06-15 13:58           ` Lars Ingebrigtsen
2021-07-23 13:27             ` Lars Ingebrigtsen

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=764F506B-30E1-460A-8D41-8BE56C58DED9@acm.org \
    --to=mattiase@acm.org \
    --cc=19174@debbugs.gnu.org \
    --cc=J2N-FORGET@orange.fr \
    --cc=larsi@gnus.org \
    --cc=rgm@gnu.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).