From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Leha Subject: Re: [new exporter] latex-date-timestamp-format not adhering #+LANGUAGE Date: Wed, 06 Mar 2013 22:37:04 +0100 Message-ID: <874ngofbwf.fsf@med.uni-goettingen.de> References: <87lia22fd6.fsf@med.uni-goettingen.de> <87mwugznnm.fsf@gmail.com> <87lia0fwyu.fsf@med.uni-goettingen.de> <87hakob90m.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:47218) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDM1Y-0002nn-Uf for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 16:37:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UDM1X-0003nl-OX for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 16:37:20 -0500 Received: from plane.gmane.org ([80.91.229.3]:60974) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDM1X-0003nZ-Hp for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 16:37:19 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UDM1r-0001yQ-NZ for emacs-orgmode@gnu.org; Wed, 06 Mar 2013 22:37:39 +0100 Received: from vpn-2097.gwdg.de ([134.76.2.97]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 06 Mar 2013 22:37:39 +0100 Received: from andreas.leha by vpn-2097.gwdg.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 06 Mar 2013 22:37:39 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Achim Gratz writes: > Andreas Leha writes: >> 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. > > Well, you could bounce this via Babel to the shell, set LANG and run the > date command with the appropriate format string and pull it back into > org, perhaps as a macro. That makes it not play well with pure Windows > where there is no locale setting per command and no date command (unless > you install Cygwin), but it isn't langage specific anymore. Thanks for the suggestion. I like the idea a lot and will follow it up, I think. Regards, Andreas