emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Georgios Kaklamanos <georgios.kaklamanos@gwdg.de>
To: emacs-orgmode@gnu.org
Subject: Re: How to avoid \title{} and \date{} in latex export
Date: Thu, 11 Apr 2019 09:26:02 +0200	[thread overview]
Message-ID: <2d0783ad-7a38-ede4-3acf-38a930464051@gwdg.de> (raw)
In-Reply-To: <877ec1b37h.fsf@alphaville.usersys.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 4042 bytes --]

Hi,

+1 for not supporting Elsevier.

Nonetheless, if you *have* to use this template, or if you encounter
similar issues with another one, I've used the following workaround in
the past:
- export just the body of the article (hitting C-b at the export frame)
- input that at your tex file using \input{}

Cheers,
Georgios

On 11/04/2019 06:01, Nick Dokos wrote:
> Flavio Leonardo Cavalcanti de Moura <contato@flaviomoura.mat.br> writes:
> 
>> Hi Jilius, 
>>
>> Thank you very much for your reply. It is a good idea, but the latex
>> class I am using (entcs) has its own \title and \date, and by
>> renewing the command I overwrite both... 
>>
>> I am removing these lines by hand from the tex file generated by the
>> export engine... but it is not nice. Any help is very much
>> appreciated!
> 
> If I were you, I would write it all using the article class, then once
> satisfied, I would export it to a latex file, make the necessay
> changes (article -> entcs, frontmatter included) and then process it
> through latex one final time. It is just not worth fighting against
> the peculiarities of the entcs class or trying to bring it into
> submission: it's just a badly written class.
> 
> But I would also suggest that you consider publishing your paper in a
> different journal. Elsevier is a toxic publisher and is being
> boycotted by many prominent scientists.  See
> 
>     http://thecostofknowledge.com/
> 
> and Timothy Gowers' blog:
> 
>     https://gowers.wordpress.com/category/elsevier/
> 
>>
>> Best regards, 
>> Flávio.
>>  
>>
>>         Hi  Flávio,
>>    
>>         perhaps you could add something like (untested)
>>    
>>         #+LATEX_HEADER: \renewcommand{\title}[1]{} \renewcommand{\date}[1]{}
>>    
>>         to your org-file? It's not exactly what you asked for, but it might
>>    
>>         alleviate your problem.
>>    
>>         HTH,
>>    
>>         Julius
>>    
>>         Am 10.04.19 um 18:10 schrieb Flavio Leonardo Cavalcanti de Moura:
>>    
>>         > Hello,
>>    
>>         >
>>    
>>         > My org file uses a latex class that, after exporting, is in conflict with
>>    
>>         > the lines \date{} and \title{} automatically generated by orgmode latex
>>    
>>         > export. I already tried the following headings for the org file:
>>    
>>         >
>>    
>>         > 1.
>>    
>>         > #+TITLE:
>>    
>>         > #+DATE:
>>    
>>         >
>>    
>>         > 2.
>>    
>>         > #+TITLE:
>>    
>>         > #+option: date:nil
>>    
>>         >
>>    
>>         > 3.
>>    
>>         > #+option: title:nil date:nil
>>    
>>         >
>>    
>>         > But in all cases the lines
>>    
>>         > \title{}
>>    
>>         > \date{}
>>    
>>         > are in the tex file automatically generated by the export engine. Is there
>>    
>>         > a way to prevent the addition of these lines?
>>    
>>         >
>>    
>>         > Best regards,
>>    
>>         > Flávio.
>>    
>>         >
>>
> 

-- 
------------------------------------------------------------------
Georgios Kaklamanos
Doctoral Student, e-Science Group, GWDG
mailto: georgios.kaklamanos@gwdg.de
Telefon: 0551 201-26803
------------------------------------------------------------------
GWDG - Gesellschaft für wissenschaftliche
Datenverarbeitung mbH Göttingen
Am Faßberg 11, 37077 Göttingen, Germany

WWW: www.gwdg.de    mailto: gwdg@gwdg.de
Phone: +49 (0) 551 201-1510
Fax:   +49 (0) 551 201-2150
------------------------------------------------------------------
Geschäftsführer: Prof. Dr. Ramin Yahyapour
Aufsichtsratsvorsitzender: Prof. Dr. Christian Griesinger
Sitz der Gesellschaft: Göttingen
Registergericht: Göttingen
Handelsregister-Nr. B 598
------------------------------------------------------------------
Zertifiziert nach ISO 9001
------------------------------------------------------------------


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5358 bytes --]

  reply	other threads:[~2019-04-11  7:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 21:27 How to avoid \title{} and \date{} in latex export Flavio Leonardo Cavalcanti de Moura
2019-04-11  4:01 ` Nick Dokos
2019-04-11  7:26   ` Georgios Kaklamanos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-10 16:10 Flavio Leonardo Cavalcanti de Moura
2019-04-10 18:30 ` Julius Dittmar
2019-04-11  1:15 ` Leslie Watter
2019-04-10 15:24 Flavio Leonardo Cavalcanti de Moura
2019-04-11 19:32 ` Jeremie Juste
2019-04-11 20:58   ` Flavio Leonardo Cavalcanti de Moura

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2d0783ad-7a38-ede4-3acf-38a930464051@gwdg.de \
    --to=georgios.kaklamanos@gwdg.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).