From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rares Pop Subject: Re: export TODO keyword Date: Mon, 16 Aug 2010 18:10:08 +0300 Message-ID: References: <1FFE9A72-8651-4461-B8C5-C54B7F94569A@gmail.com> <87r5hyir9n.fsf@gmx.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1234955928==" Return-path: Received: from [140.186.70.92] (port=35135 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ol1KI-0006Di-1m for emacs-orgmode@gnu.org; Mon, 16 Aug 2010 11:10:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Ol1KE-0003Ip-6n for emacs-orgmode@gnu.org; Mon, 16 Aug 2010 11:10:13 -0400 Received: from mail-pw0-f41.google.com ([209.85.160.41]:32844) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Ol1KD-0003Ih-TV for emacs-orgmode@gnu.org; Mon, 16 Aug 2010 11:10:10 -0400 Received: by pwi3 with SMTP id 3so2078083pwi.0 for ; Mon, 16 Aug 2010 08:10:09 -0700 (PDT) In-Reply-To: <87r5hyir9n.fsf@gmx.de> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastian Rose Cc: emacs-orgmode@gnu.org, Carsten Dominik --===============1234955928== Content-Type: multipart/alternative; boundary=0016364586da6d2651048df23ac1 --0016364586da6d2651048df23ac1 Content-Type: text/plain; charset=ISO-8859-1 >From what I found so far there are no macros involved here. I'll perform the upgrade to the latest version and see how if it's fixed. Thanks to all, Rares On Mon, Aug 16, 2010 at 5:08 PM, Sebastian Rose wrote: > Rares Pop writes: > > Carsten, > > > > I've found part of the problem but I don't know the cause. > > The *.tex file was generated with curly brackets > > (e.g. \section{\textbf\{TODO\} Task 1}) - i've attached the *.tex file > > And if I remove the slashes(*\ \)* signs the latex code will be something > > like this (e.g \section{\textbf{TODO} Task 1}) > > and by exporting it to PDF it looks ok. > > > Hi Rares, > > > are you sure, you did not try to define a Macro the wrong way or > something like that? I cannot reproduce this either. > > > Sebastian > > > > > > > The value of the variable *Org Export Latex Todo Keyword Markup* is * > > \textbf{%s}* > > * > > * > > So it seems that somewhere on the road some slash signs are added without > > permission. > > > > Thanks again, > > Rares > > > > > > > > I've attached also my *.emacs* file and the tex file output from the org > > file. > > > > On Mon, Aug 16, 2010 at 1:36 PM, Carsten Dominik > > wrote: > > > >> Hi, > >> > >> I cannot reproduce this problem. > >> > >> Best wishes > >> > >> - Carsten > >> > >> > >> On Aug 16, 2010, at 11:06 AM, Rares Pop wrote: > >> > >> Hi Carsten, > >>> > >>> I've attached the org file and the exported PDF file. > >>> > >>> I'm using org-6.35i and export settings are the default ones. > >>> > >>> Thanks again for trying to help, > >>> Rares > >>> > >>> On Mon, Aug 16, 2010 at 11:45 AM, Carsten Dominik < > >>> carsten.dominik@gmail.com> wrote: > >>> > >>> On Aug 16, 2010, at 10:39 AM, Rares Pop wrote: > >>> > >>> Hello, > >>> > >>> sorry for the beautifier question. > >>> I'm trying to export an org document with some TODO tasks to a PDF > file. > >>> And I get the output in the PDF file for the TODO keyword like this: > >>> {TODO} > >>> > >>> But i want it simple > >>> > >>> TODO or [TODO]. > >>> > >>> I don't want to have those curly brackets at the beginning and the end > of > >>> the TODO keyword. > >>> > >>> Hi Rares, > >>> > >>> how about you post an example file for people to reproduce the issue? > >>> And then say exactly how you exported it, with what setup? > >>> > >>> - Carsten > >>> > >>> > >>> > >>> > >> > >> - Carsten > --0016364586da6d2651048df23ac1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable From what I found s= o far there are no macros involved here.

I'll perform the upgr= ade to the latest version and see how if it's fixed.

Than= ks to all,
Rares

On Mon, Aug 16, 2010 at 5:08 P= M, Sebastian Rose <sebastian_rose@gmx.de> wrote:
Rares Pop <rare= s.pop@gmail.com> writes:
> Carsten,
>
> I've found part of the problem but I don't know the cause.
> The *.tex file was generated with curly brackets
> (e.g. \section{\textbf\{TODO\} Task 1}) - i've attached the *.tex = file
> And if I remove the slashes(*\ \)* signs the latex code will be someth= ing
> like this (e.g \section{\textbf{TODO} Task 1})
> and by exporting it to PDF it looks ok.


Hi Rares,


are you sure, you did not try to define a Macro the wrong way or
something like that? =A0 I cannot reproduce this either.


=A0 Sebastian



>
> The value of the variable *Org Export Latex Todo Keyword Markup* is *<= br> > \textbf{%s}*
> *
> *
> So it seems that somewhere on the road some slash signs are added with= out
> permission.
>
> Thanks again,
> Rares
>
>
>
> I've attached also my *.emacs* file and the tex file output from t= he org
> file.
>
> On Mon, Aug 16, 2010 at 1:36 PM, Carsten Dominik
> <carsten.dominik@gmail= .com>wrote:
>
>> Hi,
>>
>> I cannot reproduce this problem.
>>
>> Best wishes
>>
>> - Carsten
>>
>>
>> On Aug 16, 2010, at 11:06 AM, Rares Pop wrote:
>>
>> =A0Hi Carsten,
>>>
>>> I've attached the org file and the exported PDF file.
>>>
>>> I'm using org-6.35i and export settings are the default on= es.
>>>
>>> Thanks again for trying to help,
>>> Rares
>>>
>>> On Mon, Aug 16, 2010 at 11:45 AM, Carsten Dominik <
>>> carsten.dominik@g= mail.com> wrote:
>>>
>>> On Aug 16, 2010, at 10:39 AM, Rares Pop wrote:
>>>
>>> Hello,
>>>
>>> sorry for the beautifier question.
>>> I'm trying to export an org document with some TODO tasks = to a PDF file.
>>> And I get the output in the PDF file for the TODO keyword like= this:
>>> =A0{TODO}
>>>
>>> But i want it simple
>>>
>>> TODO or [TODO].
>>>
>>> I don't want to have those curly brackets at the beginning= and the end of
>>> the TODO keyword.
>>>
>>> Hi Rares,
>>>
>>> how about you post an example file for people to reproduce the= issue?
>>> And then say exactly how you exported it, with what setup?
>>>
>>> - Carsten
>>>
>>>
>>> <test.pdf><test.org>
>>>
>>
>> - Carsten

--0016364586da6d2651048df23ac1-- --===============1234955928== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============1234955928==--