Carsten Dominik writes:
> On 23.9.2012, at 10:30, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> Carsten Dominik writes:
>>
>>> On 22.9.2012, at 10:52, Nicolas Goaziou wrote:
If the LaTeX command doesn't require an argument, you can always add it
to `org-entities-user'.
>>>
>>> Yes, even
On 23.9.2012, at 10:30, Nicolas Goaziou wrote:
> Hello,
>
> Carsten Dominik writes:
>
>> On 22.9.2012, at 10:52, Nicolas Goaziou wrote:
>>> If the LaTeX command doesn't require an argument, you can always add it
>>> to `org-entities-user'.
>>
>> Yes, even though this is not very clean by itse
Hello,
Carsten Dominik writes:
> On 22.9.2012, at 10:52, Nicolas Goaziou wrote:
>> If the LaTeX command doesn't require an argument, you can always add it
>> to `org-entities-user'.
>
> Yes, even though this is not very clean by itself.
This is debatable. Entities are perfectly integrated into
Carsten Dominik writes:
> On 22.9.2012, at 10:52, Nicolas Goaziou wrote:
>
>> Hello,
>>
>> Carsten Dominik writes:
>>
>>> The only thing is: I do use Org to draft documents intended to
>>> be later fine-tuned as LaTeX documents, while I don't usually
>>> do this for other backends. So the ab
On 22.9.2012, at 10:52, Nicolas Goaziou wrote:
> Hello,
>
> Carsten Dominik writes:
>
>> The only thing is: I do use Org to draft documents intended to
>> be later fine-tuned as LaTeX documents, while I don't usually
>> do this for other backends. So the ability to put in naked
>> LaTeX form
Hello,
Carsten Dominik writes:
> The only thing is: I do use Org to draft documents intended to
> be later fine-tuned as LaTeX documents, while I don't usually
> do this for other backends. So the ability to put in naked
> LaTeX formatting commands does have value and convenience for
> me pers
On 20 sep. 2012, at 13:57, Nicolas Goaziou wrote:
> Hello,
>
> Carsten Dominik writes:
>
>> 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, f
Hello,
Carsten Dominik writes:
> 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 i
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
Aloha all,
Bastien writes:
> Hi,
>
> Nicolas Goaziou writes:
>
>> 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 a
Hi,
Nicolas Goaziou writes:
> 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, \hfil
Hello,
Carsten Dominik 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 expect
On 19 sep. 2012, at 15:15, Nicolas Goaziou wrote:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I'm not sure about support for \hfill{}, etc. The new latex and html
>> exporters pass \hfill{} through unchanged, which might be what the latex
>> author wants, or what the html author
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> I'm not sure about support for \hfill{}, etc. The new latex and html
> exporters pass \hfill{} through unchanged, which might be what the latex
> author wants, or what the html author writing about latex commands
> wants.
It would not change anyth
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I'm probably doing something silly here, but can't figure it out. Using
>> the new LaTeX exporter, and with org-entities-user defined as below,
>> this:
>>
>> \C14 \frac12 \Omacron
>>
>> exports as:
>>
>> \C14 \text
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
> I'm probably doing something silly here, but can't figure it out. Using
> the new LaTeX exporter, and with org-entities-user defined as below,
> this:
>
> \C14 \frac12 \Omacron
>
> exports as:
>
> \C14 \textonehalf{} \={O}
>
> Why isn't my C14 enti
Aloha all,
I'm probably doing something silly here, but can't figure it out. Using
the new LaTeX exporter, and with org-entities-user defined as below,
this:
\C14 \frac12 \Omacron
exports as:
\C14 \textonehalf{} \={O}
Why isn't my C14 entity being exported correctly?
All the best,
Tom
Value
17 matches
Mail list logo
