Hi Nicolas,
maybe first have to get clear what you mean by "not accepting raw commands".
Would that mean that if I write \vspace in the buffer, the LaTeX exporter
would then give me \textbackslash{}vspace, for example, because i thinks that
I want that text to appear in the output?
- Carsten
On 19 sep. 2012, at 17:55, Nicolas Goaziou <n.goaz...@gmail.com> wrote:
> Hello,
>
> Carsten Dominik <carsten.domi...@gmail.com> writes:
>
>> These are all valid arguments. However, I did design
>> Org-mode to be LaTeX-near to make sure that it becomes
>> easy and fast to type as a notes environment. In my mind, a user
>> expecting \cite{...} to work in other backends is not necessarily
>> a wrong expectation, and if we introduce a syntax for doing citations
>> in HTML, why not using the LaTeX syntax for it?
>>
>> So actually, it seems I do not fully agree with your *consistency*
>> argument. While you are right that it is the logical and clean thing
>> if you view Org as a markup language created for export, it is not
>> necessarily the right solution for a convenience point of view.
>
> My point is not about removing anything related to LaTeX syntax. I'm
> fine with a \cite{...} (although I think [[cite:...]] may be cleaner) as
> long as it really is accepted by most major export back-ends.
>
> But I think accepting raw commands like \vspace, \hfill and al. is not
> necessary (as long as there's still a way to send them to the export
> back-end). We shouldn't trick users into thinking these commands will be
> obeyed in any situation.
>
> Moreover, I don't think that they belong to an easy and fast to type
> notes environment.
>
>
> Regards,
>
> --
> Nicolas Goaziou
- Carsten
