Skip to main content
7 events
when toggle format what by license comment
Mar 30, 2016 at 15:32 comment added Tyler Strange, if I use #+LANGUAGE: fr on it's own, it is ignored - the output LaTeX is in English. If I use it and #+LATEX_HEADER: \usepackage[english]{babel}, the resulting LaTeX includes the line \usepackage[english, frenchb]{babel}. And if I only use #+LATEX_HEADER: \usepackage[french]{babel}, without setting LANGUAGE:, what actually gets inserted is \usepackage[frenchb, english]{babel}. None of them change the PDF, it's always English.
Mar 30, 2016 at 15:19 history edited Tyler CC BY-SA 3.0
fixed typo in code
Mar 30, 2016 at 15:19 comment added Tyler @foki sorry, I was missing a colon :. I've corrected my answer.
Mar 30, 2016 at 12:13 comment added yujaiyu @JeanPierre I've just noticed a weird behavior. Tyler's approach don't work for me, but behavior manifested using JeanPierre's is even more interesting - I have declared both, #+LANGUAGE: fr and #+LATEX_HEADER: \usepackage[english]{babel} and in this case Latex export respects the first setting and translates strings in French counterparts. If I declare de in the first and french or frenchb in the second - de is used. I've also noticed that in described cases exporter does not use org-export-dictionary, more likely it use Latex languages. Have any idea?
Mar 27, 2016 at 13:45 comment added JeanPierre When exporting to LaTeX, you'd better use LaTeX's own handling of languages \usepackage[mylanguage]{babel}.
Mar 27, 2016 at 8:27 comment added yujaiyu I currently don't have LATEX environment set so I can't try it with PDF. Now I want to export to ODT and HTML so LATEX command doesn't help here (tell me if I'm wrong).
Mar 26, 2016 at 22:31 history answered Tyler CC BY-SA 3.0