[new exporter] latex-date-timestamp-format not adhering #+LANGUAGE

[new exporter] latex-date-timestamp-format not adhering #+LANGUAGE

[Andreas Leha]

Hi all,

I'd very much like to see org-latex-timestamp-format adhere to a
possibly present #+LANGUAGE setting.

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?

Regards,
Andreas

Re: [new exporter] latex-date-timestamp-format not adhering #+LANGUAGE

[Nicolas Goaziou]

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'.

> 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.

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.


Regards,

-- 
Nicolas Goaziou

Re: [new exporter] latex-date-timestamp-format not adhering #+LANGUAGE

[Andreas Leha]

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

Re: [new exporter] latex-date-timestamp-format not adhering #+LANGUAGE

[Achim Gratz]

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.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: [new exporter] latex-date-timestamp-format not adhering #+LANGUAGE

[Andreas Leha]

Achim Gratz <Stromeko@nexgo.de> 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