emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: [new exporter] latex-date-timestamp-format not adhering #+LANGUAGE
Date: Wed, 06 Mar 2013 15:02:01 +0100	[thread overview]
Message-ID: <87lia0fwyu.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87mwugznnm.fsf@gmail.com

Hi Nicolas,

thanks for taking this up!

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>
>> I'd very much like to see org-latex-timestamp-format adhere to a
>> possibly present #+LANGUAGE setting.
>
> There is no such variable as `org-latex-timestamp-format'.
>

Of course I meant 'org-latex-date-timestamp-format'.

>> If I set org-latex-timestamp-format to "%A, %Y-%m-%d" the following org
>> file produces
>> "Donnerstag, 2013-03-07" on my system, where I'd prefer
>> "Thursday, 2013-03-07".
>>
>> #+begin_src org
>> #+TITLE: Some Document
>> #+DATE: <2013-03-07 Do>
>> #+LANGUAGE: en
>>
>>
>> * Some test document
>> With some content
>> #+end_src
>>
>> Would such a change be possible?
>
> It is difficult.
>
> "%A" depends on a locale built within glibc. Assuming we know the locale
> associated to the language string, it may or may not be available in
> glibc. Also, `format-time-string' is a primitive, so even if local is
> available, you cannot change it locally easily.

I understand.

>
> A proper implementation would, IMO, not rely directly on
> `format-time-string'. There could be a `org-format-time-string'
> accepting the same arguments as `format-time-string' but replacing
> locale related placeholders beforehand, according to a dictionary.
>

That sound quite tedious and boring work...

And while I still think, that setting the #+LANGUAGE in org should
ideally be reflected in the export -- also for the date formatting -- I
found a solution to my problem that I use now: It does not use orgmode's
date and date-formatting facilities, but moves the work to LaTeX.  Thus, the
bad side is that it is backend specific.

#+begin_src org
#+TITLE: Some Document
#+DATE: \printdate{2013-03-07}
#+LANGUAGE: en
#+LaTeX_HEADER: \usepackage[english]{isodate}

* Some test document
With some content
#+end_src

vs.

#+begin_src org
#+TITLE: Some Document
#+DATE: \printdate{2013-03-07}
#+LANGUAGE: en
#+LaTeX_HEADER: \usepackage[german]{isodate}

* Some test document
With some content
#+end_src

Regards,
Andreas

  reply	other threads:[~2013-03-06 14:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 12:36 [new exporter] latex-date-timestamp-format not adhering #+LANGUAGE Andreas Leha
2013-03-06 13:02 ` Nicolas Goaziou
2013-03-06 14:02   ` Andreas Leha [this message]
2013-03-06 19:52     ` Achim Gratz
2013-03-06 21:37       ` Andreas Leha

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lia0fwyu.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@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/org-mode.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).