From: Glenn Morris <rgm@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: calendar.el
Date: Sun, 23 Apr 2006 23:00:54 -0400 [thread overview]
Message-ID: <u0bqurpti1.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1FU7Au-0005GJ-00@barbucha.martin.net> (mar@centrum.cz's message of "Thu, 13 Apr 2006 21:08:16 +0200")
mar@centrum.cz wrote:
> In GNU Emacs 21.4.1 (i486-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
[...]
> calendar-month-name-array
> ["Leden" "Únor" "Březen" "Duben" "Květen"
> "Červen" "Červenec" "Srpen"
> "Září" "Říjen" "Listopad" "Prosinec"])
[...]
> everything in Emacs was fine, till i want to print a calendar (using
> commands 't y' and 't Y') -- the LaTeX output defined a commands for
> printing the months as used in my native language (so it was \Leden
> for January) but at the end of file, where the actual command is
> printed, the "\January" was typed out, for it is hardcoded in
> calendar.el. See the attachment please.
Thanks for the bug report, but I don't understand what you mean.
What do you mean by `"\January" was typed out, for it is hardcoded in
calendar.el'? I don't see "January" anywhere in the attachment you
sent, instead I see "Leden". As far as I can see, `t y' etc (except
for cal-tex-cursor-filofax-year) respect the value of
calendar-month-name-array.
> If i may suggest, i will leave the name for LaTeX commands in
> english, because other languages may use unusual characters -- so
> have two arrays for month/day -- one for LaTeX commands, one for
> localized strings to use by this commands.
I think what you're saying here is a separate issue; namely that a
user may have customized calendar-month-name-array to have unusual
characters that might not latex correctly?
prev parent reply other threads:[~2006-04-24 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 19:08 calendar.el mar
2006-04-24 3:00 ` Glenn Morris [this message]
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=u0bqurpti1.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=bug-gnu-emacs@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).