James Harkins writes:
[...]
> Ok, based on this and Marcin's comments, I'll do it the LaTeX way (which was
> my first choice anyway).
I think this is a good choice. It's what I try to do whenever
possible. And for cases where the submission is meant to be "camera
ready", the latex produced
Dnia 2013-04-30, o godz. 01:57:51
James Harkins < jamshar...@gmail.com> napisał(a):
> Ok, based on this and Marcin's comments, I'll do it the LaTeX way
> (which was my first choice anyway).
Now I'll feel responsible for your LaTeX problems;).
Seriously, though: should you run into LaTeX problems
mohamed gmail.com> writes:
> I used both aproaches :
> - Usually I customize the org options (latex templates) to meet the
> requirements of the final document. It is convenient for me to stay in
> emacs. For the gray hairs, you do it once and thus you have minor
> modifications.
>
> - But some
Dnia 2013-04-29, o godz. 07:22:23
James Harkins napisał(a):
> Or, export to ODT and let LibreOffice turn that into a PDF. I hesitate
> to do this, when LaTeX is a far superior typesetter. (But, tweaking
> all the formatting details in LaTeX is quite likely to give me some
> more gray hairs...)
W
James Harkins gmail.com> writes:
>
> Actually, let me take a few steps back from my specific question about
> the title command. There are some other workflow questions that might
> make that question redundant.
>
> This journal (for some reason unknown to me) has designed the
> publication for
Actually, let me take a few steps back from my specific question about
the title command. There are some other workflow questions that might
make that question redundant.
This journal (for some reason unknown to me) has designed the
publication format in MS Word, and there are some specific
requir