Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 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). Commented Mar 27, 2016 at 8:27
  • 1
    When exporting to LaTeX, you'd better use LaTeX's own handling of languages \usepackage[mylanguage]{babel}. Commented Mar 27, 2016 at 13:45
  • @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? Commented Mar 30, 2016 at 12:13
  • @foki sorry, I was missing a colon :. I've corrected my answer. Commented Mar 30, 2016 at 15:19
  • 2
    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. Commented Mar 30, 2016 at 15:32