Nicolas Goaziou writes:
>> 1. we can add a function `(defun org-latex-add-deriverd-class (class
>> exist-class) ...) to menupulate `org-latex-classes
>> 2. My patch's approach.
>> 3. others.
>
> We can modify `org-latex-classes' docstring (e.g. by adding examples) so
> it is easier to understand
Hello,
Feng Shu writes:
> Not all the org-mode users are expert of lisp and not all of the org-mode
> users are well in English, so finding the variable `org-latex-classes can
> customize latex class and adding a lisp block to it may be not a easy
> things for many users.
I understand, and I
Nicolas Goaziou writes:
> Hello,
>
> Feng Shu writes:
>
>> #+LATEX_CLASS: article
>>
>> %%output:
>>
>> \documentclass[11pt]{article}
>>
>> ...
>>
>> --
>>
>> #+LATEX_CLASS: article
>> #+LATEX_CLASS_NAME: ctexart
>>
>> %%output:
>>
>> \documentclass[11pt]{ctex
Hello,
Feng Shu writes:
> #+LATEX_CLASS: article
>
> %%output:
>
> \documentclass[11pt]{article}
>
> ...
>
> --
>
> #+LATEX_CLASS: article
> #+LATEX_CLASS_NAME: ctexart
>
> %%output:
>
> \documentclass[11pt]{ctexart}
>
>
Thanks for your patch.
Though, i
On Fri, Jun 14, 2013 at 05:55:56PM +0800, Feng Shu wrote:
>
> CLASS and class-name are confusing, I think LATEX_CLASS should rename
> to LATEX_CLASS_FORMAT or LATEX_CLASS_TEMPLATE, but this will break
> compatibility.
IMO compatibility is a big and important issue, and not to be taken
lightly.
Rasmus writes:
> Feng Shu writes:
>
>> #+LATEX_CLASS: article
>> #+LATEX_CLASS_NAME: ctexart
>
> I'm not sure this is the right approach. . . I can certainly see the
> value of generating classes on the fly, though. But somehow the
> proposed syntax just seems to counter-intuitive. I'm not su
Nick Dokos writes:
> Rasmus writes:
>
>> Feng Shu writes:
>>
>>> #+LATEX_CLASS: article
>>> #+LATEX_CLASS_NAME: ctexart
>>
>> I'm not sure this is the right approach. . . I can certainly see the
>> value of generating classes on the fly, though. But somehow the
>> proposed syntax just seems t
Nick Dokos writes:
>> as e.g. the INCLUDE command. Of course (*) is somewhat different from
>> how stuff like this is usually handled, cf. e.g. LATEX_CLASS_OPTIONS.
>>
> ...but this sounds a bit more promising: maybe LATEX_CLASS_OPTIONS can
> be eliminated in favor of LATEX_CLASS with arguments:
Rasmus writes:
> Feng Shu writes:
>
>> #+LATEX_CLASS: article
>> #+LATEX_CLASS_NAME: ctexart
>
> I'm not sure this is the right approach. . . I can certainly see the
> value of generating classes on the fly, though. But somehow the
> proposed syntax just seems to counter-intuitive. I'm not su
Feng Shu writes:
> #+LATEX_CLASS: article
> #+LATEX_CLASS_NAME: ctexart
I'm not sure this is the right approach. . . I can certainly see the
value of generating classes on the fly, though. But somehow the
proposed syntax just seems to counter-intuitive. I'm not sure how to
overcome this, but
Feng Shu writes:
> #+LATEX_CLASS: article
>
> %%output:
>
> \documentclass[11pt]{article}
>
> ...
>
> --
>
> #+LATEX_CLASS: article
> #+LATEX_CLASS_NAME: ctexart
>
> %%output:
>
> \documentclass[11pt]{ctexart}
Hi:
If possible, please merge this patch to maste
#+LATEX_CLASS: article
%%output:
\documentclass[11pt]{article}
...
--
#+LATEX_CLASS: article
#+LATEX_CLASS_NAME: ctexart
%%output:
\documentclass[11pt]{ctexart}
--
>From 338ce85c306ae400ba8c62bfaecaf8973346faa0 Mon Sep 17 00:00:00 2001
From: Feng
12 matches
Mail list logo