From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: [PATCH (new version)][ox-latex.el] Allow AUTO argument to org-latex-guess-babel-language. Date: Thu, 06 Jun 2013 09:46:11 +0200 Message-ID: <868v2nof5o.fsf@somewhere.org> References: <87sj12bwzj.fsf@pank.eu> <8661xvprju.fsf@somewhere.org> <87ehcj9uh7.fsf@pank.eu> <8638sz1e3b.fsf@somewhere.org> <87obbn8c36.fsf@pank.eu> <86wqqae5n4.fsf@somewhere.org> <87ppw26xe2.fsf_-_@pank.eu> <87y5aollyh.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hello, Nicolas Goaziou wrote: >> It changes behavior for your setup in that you can define a LANGUAGE >> that isn't a known abbreviation. > > While I think your patch is overall an improvement, I'm not convinced by > this particular point. Indeed #+LANGUAGE: expects a language code as > value, not just any string. This is important since latex backend is not > the only one to use that keyword. > > For example, imagine a user in need for german smart quotes. How do you > explain to him than #+language: german will not work, but #+language: de > will? > > I think special Babel needs can be handled elsewhere. That makes me think of another point: how do I say that the HTML exported document is in American English? By having a #+LANGUAGE: en-us specification. But that's not a valid language for Babel when exporting to LaTeX. So, I think we'd need some sort of alist with allowed values, and their equivalent for LaTeX and for HTML (and for other uses?), don't we? Best regards, Seb -- Sebastien Vauban