Re: [O] LaTeX export problem

2014-07-16 Thread Nicolas Goaziou
Hello,

t...@tsdye.com (Thomas S. Dye) writes:

 With a recent Org from git and this source:

   #+attr_latex: :width 0.8\textwidth :placement [htb]
   #+name: fig:harris-errors
   #+caption[Structural effects of false transitives]: Structural effects of 
 false transitives with the stratigraphic section in Figure [[fig:fig12-open]]:

 I get this incorrect LaTeX output:

[...]

 If I place a space between the final colon and the link on the
 first #+caption: line, then I get the output I'm expecting (although
 there is the extraneous space):

[...]


This is because regexp finding short captions is greedy. It thus catches
everything up to the last ]: in the first line, making the link
invalid.

 Is there a work-around?

Just make sure the line containing the short caption doesn't end with
]:, e.g.,

  ...
  #+caption[Structural effects of false transitives]:
  #+caption: Structural effects of false transitives with the stratigraphic 
section in Figure [[fig:fig12-open]]:
  ...


Regards,

-- 
Nicolas Goaziou



Re: [O] LaTeX export problem

2014-07-16 Thread Thomas S. Dye
Aloha Nicolas,

Nicolas Goaziou m...@nicolasgoaziou.fr writes:

 Hello,

 t...@tsdye.com (Thomas S. Dye) writes:

 With a recent Org from git and this source:

   #+attr_latex: :width 0.8\textwidth :placement [htb]
   #+name: fig:harris-errors
   #+caption[Structural effects of false transitives]: Structural effects of 
 false transitives with the stratigraphic section in Figure 
 [[fig:fig12-open]]:

 I get this incorrect LaTeX output:

 [...]

 If I place a space between the final colon and the link on the
 first #+caption: line, then I get the output I'm expecting (although
 there is the extraneous space):

 [...]


 This is because regexp finding short captions is greedy. It thus catches
 everything up to the last ]: in the first line, making the link
 invalid.

 Is there a work-around?

 Just make sure the line containing the short caption doesn't end with
 ]:, e.g.,

   ...
   #+caption[Structural effects of false transitives]:
   #+caption: Structural effects of false transitives with the stratigraphic 
 section in Figure [[fig:fig12-open]]:
   ...

Perfect.  Thanks!

All the best,
Tom

-- 
T.S. Dye  Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com



[O] LaTeX export problem

2014-07-13 Thread Thomas S. Dye
Aloha all,

With a recent Org from git and this source:

  #+attr_latex: :width 0.8\textwidth :placement [htb]
  #+name: fig:harris-errors
  #+caption[Structural effects of false transitives]: Structural effects of 
false transitives with the stratigraphic section in Figure [[fig:fig12-open]]:
  #+caption: /left/, a Harris Matrix of contexts adjacent to Context 1 with 
false transitives for Contexts 5 and 6;
  #+caption: /right/, a directed graph of contexts adjacent to Context 1 that 
excludes false transitives.
  #+caption: The observed stratigraphic relationships for the two diagrams are 
shown on Table [[tab:harris-errors]].
  
[[file:~/Public/projects/936-harris-matrix/figure/fig-12-harris-td-adj-1-tred-edited.pdf]]

I get this incorrect LaTeX output:

  \begin{figure}[htb]
  \centering
  
\includegraphics[width=0.8\textwidth]{/Users/dk/Public/projects/936-harris-matrix/figure/fig-12-harris-td-adj-1-tred-edited.pdf}
  \caption[Structural effects of false transitives]: Structural effects of 
false transitives with the stratigraphic section in 
Figure~[[fig:fig12-open]]{\label{fig:harris-errors}\emph{left}, a Harris Matrix 
of contexts adjacent to Context 1 with false transitives for Contexts 5 and 6; 
\emph{right}, a directed graph of contexts adjacent to Context 1 that excludes 
false transitives. The observed stratigraphic relationships for the two 
diagrams are shown on Table~\ref{tab:harris-errors}.}
  \end{figure}

If I place a space between the final colon and the link on the
first #+caption: line, then I get the output I'm expecting (although
there is the extraneous space):

 \begin{figure}[htb]
 \centering
 
\includegraphics[width=0.8\textwidth]{/Users/dk/Public/projects/936-harris-matrix/figure/fig-12-harris-td-adj-1-tred-edited.pdf}
 \caption[Structural effects of false 
transitives]{\label{fig:harris-errors}Structural effects of false transitives 
with the stratigraphic section in Figure~\ref{fig:fig12-open} : \emph{left}, a 
Harris Matrix of contexts adjacent to Context 1 with false transitives for 
Contexts 5 and 6; \emph{right}, a directed graph of contexts adjacent to 
Context 1 that excludes false transitives. The observed stratigraphic 
relationships for the two diagrams are shown on Table~\ref{tab:harris-errors}.}
 \end{figure}

Is there a work-around?

All the best,
Tom

-- 
T.S. Dye  Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com



Re: [O] LaTeX export, problem with quotes

2013-12-26 Thread Nicolas Goaziou
Hello,

t...@tsdye.com (Thomas S. Dye) writes:

 I'm having a problem with exporting quotes.  I have the #+OPTIONS ':t.

 This input in the Org mode file:

 [l]ater walls ...

 produces this in the tex file (open quote wrong, close quote OK):
 [l]ater walls ...''

 I'm expecting this in the tex file:
 ''[l]ater walls ...''

I fixed it in maint. Thank you for reporting it.

Nevertheless, there will always be failing cases in smart quote
detection (see `org-export-smart-quotes-regexps').


Regards,

-- 
Nicolas Goaziou



Re: [O] LaTeX export, problem with quotes

2013-12-26 Thread Thomas S. Dye
Aloha Nicolas,

Nicolas Goaziou n.goaz...@gmail.com writes:

 Hello,

 t...@tsdye.com (Thomas S. Dye) writes:

 I'm having a problem with exporting quotes.  I have the #+OPTIONS ':t.

 This input in the Org mode file:

 [l]ater walls ...

 produces this in the tex file (open quote wrong, close quote OK):
 [l]ater walls ...''

 I'm expecting this in the tex file:
 ''[l]ater walls ...''

 I fixed it in maint. Thank you for reporting it.

I'm getting the same incorrect result as before with:

Org-mode version 8.2.4 (release_8.2.4-391-g954168 @ 
/Users/dk/.emacs.d/src/org-mode/lisp/)


 Nevertheless, there will always be failing cases in smart quote
 detection (see `org-export-smart-quotes-regexps').

I can't comprehend the regular expression(s) there, unfortunately. If it
is the case that there will always be failing cases, and my goal is to
create a stable piece of reproducible research, would you recommend an
approach that sets org-entities-user appropriately at the file-local
level, or something else?

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com



Re: [O] LaTeX export, problem with quotes

2013-12-26 Thread Nicolas Goaziou
t...@tsdye.com (Thomas S. Dye) writes:

 I'm getting the same incorrect result as before with:

 Org-mode version 8.2.4 (release_8.2.4-391-g954168 @
 /Users/dk/.emacs.d/src/org-mode/lisp/)

Did you reload Org? I cannot reproduce the problem anymore.

 Nevertheless, there will always be failing cases in smart quote
 detection (see `org-export-smart-quotes-regexps').

 I can't comprehend the regular expression(s) there, unfortunately. If it
 is the case that there will always be failing cases, and my goal is to
 create a stable piece of reproducible research, would you recommend an
 approach that sets org-entities-user appropriately at the file-local
 level, or something else?

I mean that choosing between an opening quote, a closing quote, or
nothing is done with a regexp. It cannot cover all cases, and some
tricky situations will fool smart quote mechanism.

If that happens, and if `org-export-smart-quotes-regexps' cannot be
improved to handle the situation consistently, you will have to specify
LaTeX quote code manually (e.g. with an export snippet, or an entity).

I cannot see the link with reproducible research, though.


Regards,

-- 
Nicolas Goaziou



Re: [O] LaTeX export, problem with quotes

2013-12-26 Thread Thomas S. Dye
Nicolas Goaziou n.goaz...@gmail.com writes:

 t...@tsdye.com (Thomas S. Dye) writes:

 I'm getting the same incorrect result as before with:

 Org-mode version 8.2.4 (release_8.2.4-391-g954168 @
 /Users/dk/.emacs.d/src/org-mode/lisp/)

 Did you reload Org? I cannot reproduce the problem anymore.

Hmm, later and {l}ater both work for me, but [l]ater and (l)ater
both fail.  I'm exporting asynchronously.

 I mean that choosing between an opening quote, a closing quote, or
 nothing is done with a regexp. It cannot cover all cases, and some
 tricky situations will fool smart quote mechanism.

 If that happens, and if `org-export-smart-quotes-regexps' cannot be
 improved to handle the situation consistently, you will have to specify
 LaTeX quote code manually (e.g. with an export snippet, or an entity).

 I cannot see the link with reproducible research, though.

I'm perhaps too wary of regressions here.

All the best,
Tom

-- 
T.S. Dye  Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com



Re: [O] LaTeX export, problem with quotes

2013-12-26 Thread Thomas S. Dye
Aloha Nicolas,

Ah, I see what's happening now. I've set up asynchronous export to use
the Org mode that ships with Emacs, rather than the one from the git
repo. Of course, that doesn't track your changes.

In this case, where many potential users of my reproducible research
document aren't using the latest Org mode, a file-specific
org-entities-user entry looks like the best solution.

Thanks for your patience as I puzzled this out online.

All the best,
Tom

Nicolas Goaziou n.goaz...@gmail.com writes:

 t...@tsdye.com (Thomas S. Dye) writes:

 I'm getting the same incorrect result as before with:

 Org-mode version 8.2.4 (release_8.2.4-391-g954168 @
 /Users/dk/.emacs.d/src/org-mode/lisp/)

 Did you reload Org? I cannot reproduce the problem anymore.

 Nevertheless, there will always be failing cases in smart quote
 detection (see `org-export-smart-quotes-regexps').

 I can't comprehend the regular expression(s) there, unfortunately. If it
 is the case that there will always be failing cases, and my goal is to
 create a stable piece of reproducible research, would you recommend an
 approach that sets org-entities-user appropriately at the file-local
 level, or something else?

 I mean that choosing between an opening quote, a closing quote, or
 nothing is done with a regexp. It cannot cover all cases, and some
 tricky situations will fool smart quote mechanism.

 If that happens, and if `org-export-smart-quotes-regexps' cannot be
 improved to handle the situation consistently, you will have to specify
 LaTeX quote code manually (e.g. with an export snippet, or an entity).

 I cannot see the link with reproducible research, though.


 Regards,

-- 
T.S. Dye  Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com



[O] LaTeX export, problem with quotes

2013-12-25 Thread Thomas S. Dye
Aloha all,

I'm having a problem with exporting quotes.  I have the #+OPTIONS ':t.

This input in the Org mode file:

[l]ater walls ...

produces this in the tex file (open quote wrong, close quote OK):
[l]ater walls ...''

I'm expecting this in the tex file:
''[l]ater walls ...''

I'm using Org-mode version 8.2.4 (release_8.2.4-329-g149eaf @
/Users/dk/.emacs.d/src/org-mode/lisp/)

All the best,
Tom

-- 
T.S. Dye  Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com



Re: [O] LaTeX export problem

2012-09-26 Thread Nicolas Goaziou
Hello,

Alexander Vorobiev alexander.vorob...@gmail.com writes:

 The next problem I have is babel-related. I create results of
 execution of my source blocks in org format so they are enclosed in
 #+BEGIN_ORG ... #END_ORG which gets translated by the new exporter
 into \begin{org} \end{org} - which makes pdflatex unhappy because the
 org environment is not defined anywhere. The old exported did not do
 anything like that. What do I have to do to make it work in the new
 exporter?

Nothing. New exporter doesn't support #+begin_org blocks, which should
be removed in master anyway.


Regards,

-- 
Nicolas Goaziou



Re: [O] LaTeX export problem

2012-09-24 Thread Alexander Vorobiev
Nicolas,

Here is my configuration section (it goes at the end of the org file).
Nothing in the LaTeX_HEADER lines gets inserted into output tex
document. The old exporter just inserted them all verbatim.

#+STARTUP:align fold nodlcheck hidestars oddeven lognotestate
#+PROPERTY: exports results
#+TITLE: Test document
#+AUTHOR:
#+EMAIL: myem...@gmail.com
#+DATE:
#+DESCRIPTION:
#+KEYWORDS:
#+LANGUAGE:  en
#+OPTIONS:   H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:nil -:t f:t *:t :t
#+OPTIONS:   TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0
path:http://orgmode.org/org-info.js
#+EXPORT_SELECT_TAGS: export
#+EXPORT_EXCLUDE_TAGS: noexport
#+LINK_UP:
#+LINK_HOME:
#+XSLT:
#+LANGUAGE:   en
#+LaTeX_CLASS:koma-article
#+LaTeX_HEADER:\usepackage{color}
#+LaTeX_HEADER:\definecolor{spot}{rgb}{0,0.2,0.6}
#+LaTeX_HEADER:\definecolor{TUgreen}{RGB}{41,93,80}
#+LaTeX_HEADER:\setkomafont{section}{\color{TUgreen}\sffamily\bfseries}
#+LaTeX_HEADER:\renewcommand{\sfdefault}{jvn}
#+LaTeX_HEADER:\renewcommand*\familydefault{\sfdefault}
#+LaTeX_HEADER:\usepackage[automark,nouppercase]{scrpage2}
#+LaTeX_HEADER:\clearscrheadfoot
#+LaTeX_HEADER:\setheadwidth{paper}
#+LaTeX_HEADER:\setfootwidth{paper}
#+LaTeX_HEADER:\cohead[]{
#+LaTeX_HEADER:  \includegraphics[width=7.75in]{MyHeader.jpg}
#+LaTeX_HEADER:}
#+LaTeX_HEADER:\cofoot[]{
#+LaTeX_HEADER:  \includegraphics[width=7.75in]{MyFooter.png}
#+LaTeX_HEADER:}
#+LaTeX_HEADER:\pagestyle{scrplain}
#+LaTeX_HEADER:\AtBeginDocument{\vspace*{5\baselineskip}\thispagestyle{scrheadings}}
#+LaTeX_HEADER:\setlength{\topmargin}{-0.80in}
#+LaTeX_HEADER:\setlength{\textheight}{730pt}
#+LaTeX_HEADER:\makeatletter
#+LaTeX_HEADER:\renewcommand{\maketitle}{
#+LaTeX_HEADER:% \vspace*{5\baselineskip}%
#+LaTeX_HEADER: \vskip 2em%
#+LaTeX_HEADER: \begin{center}%
#+LaTeX_HEADER:  {\LARGE \@title \par}%
#+LaTeX_HEADER: \end{center}%
#+LaTeX_HEADER: \par} \makeatother

The new tex file just starts like this

% Created 2012-09-24 Mon 11:31
\author{}
\date{}
\title{Test document}
\hypersetup{
  pdfkeywords={},
  pdfsubject={},
  pdfcreator={Generated by Org mode 7.9.1 in Emacs 24.2.1.}}
\begin{document}

\maketitle

Thanks
Alex

On Sat, Sep 22, 2012 at 3:07 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
 Hello,

 Alexander Vorobiev alexander.vorob...@gmail.com writes:

 I tried the new exporter (using today's snapshot of the sources) and
 it produced invalid LaTeX (it calls hypersetup without loading
 hyperref package).

 The export back-end doesn't load any package on its own. You have to
 make sure hyperref is properly loaded (AFAIK, it is by default).

 It also ignored the #+LaTeX_CLASS: and all the
 #+LaTeX_HEADER:lines in my file.

 Those lines shouldn't be ignored. You probably don't have any matching
 entry in `org-e-latex-classes' for your #+LATEX_CLASS: specification.

 I'm not sure about #+LaTeX_HEADER: lines. Do you have an example?

 Are there any examples of org files which show how to customize the
 new LaTeX exporter?

 Try first:

 M-x customize-group RET org-export-e-latex RET


 Regards,

 --
 Nicolas Goaziou



Re: [O] LaTeX export problem

2012-09-24 Thread Nicolas Goaziou
Hello,

Alexander Vorobiev alexander.vorob...@gmail.com writes:

 Here is my configuration section (it goes at the end of the org file).
 Nothing in the LaTeX_HEADER lines gets inserted into output tex
 document. The old exporter just inserted them all verbatim.

 #+STARTUP:align fold nodlcheck hidestars oddeven lognotestate
 #+PROPERTY: exports results
 #+TITLE: Test document
 #+AUTHOR:
 #+EMAIL: myem...@gmail.com
 #+DATE:
 #+DESCRIPTION: #+KEYWORDS:
 #+LANGUAGE:  en
 #+OPTIONS:   H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:nil -:t f:t *:t :t
 #+OPTIONS:   TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
 #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0
 path:http://orgmode.org/org-info.js
 #+EXPORT_SELECT_TAGS: export
 #+EXPORT_EXCLUDE_TAGS: noexport
 #+LINK_UP:
 #+LINK_HOME:
 #+XSLT:
 #+LANGUAGE:   en
 #+LaTeX_CLASS:koma-article
 #+LaTeX_HEADER:\usepackage{color}
 #+LaTeX_HEADER:\definecolor{spot}{rgb}{0,0.2,0.6}
 #+LaTeX_HEADER:\definecolor{TUgreen}{RGB}{41,93,80}
 #+LaTeX_HEADER:\setkomafont{section}{\color{TUgreen}\sffamily\bfseries}
 #+LaTeX_HEADER:\renewcommand{\sfdefault}{jvn}
 #+LaTeX_HEADER:\renewcommand*\familydefault{\sfdefault}
 #+LaTeX_HEADER:\usepackage[automark,nouppercase]{scrpage2}
 #+LaTeX_HEADER:\clearscrheadfoot
 #+LaTeX_HEADER:\setheadwidth{paper}
 #+LaTeX_HEADER:\setfootwidth{paper}
 #+LaTeX_HEADER:\cohead[]{
 #+LaTeX_HEADER:  \includegraphics[width=7.75in]{MyHeader.jpg}
 #+LaTeX_HEADER:}
 #+LaTeX_HEADER:\cofoot[]{
 #+LaTeX_HEADER:  \includegraphics[width=7.75in]{MyFooter.png}
 #+LaTeX_HEADER:}
 #+LaTeX_HEADER:\pagestyle{scrplain}
 #+LaTeX_HEADER:\AtBeginDocument{\vspace*{5\baselineskip}\thispagestyle{scrheadings}}
 #+LaTeX_HEADER:\setlength{\topmargin}{-0.80in}
 #+LaTeX_HEADER:\setlength{\textheight}{730pt}
 #+LaTeX_HEADER:\makeatletter
 #+LaTeX_HEADER:\renewcommand{\maketitle}{
 #+LaTeX_HEADER:% \vspace*{5\baselineskip}%
 #+LaTeX_HEADER: \vskip 2em%
 #+LaTeX_HEADER: \begin{center}%
 #+LaTeX_HEADER:  {\LARGE \@title \par}%
 #+LaTeX_HEADER: \end{center}%
 #+LaTeX_HEADER: \par} \makeatother

 The new tex file just starts like this

 % Created 2012-09-24 Mon 11:31
 \author{}
 \date{}
 \title{Test document}
 \hypersetup{
   pdfkeywords={},
   pdfsubject={},
   pdfcreator={Generated by Org mode 7.9.1 in Emacs 24.2.1.}}
 \begin{document}

 \maketitle

You need a space after the colons in #+LATEX_HEADER: and #+LATEX_CLASS
lines.


Regards,

-- 
Nicolas Goaziou



Re: [O] LaTeX export problem

2012-09-24 Thread Alexander Vorobiev
Hi Nicolas,

Thanks a lot for the help, I configured the org-e-latex-classes and
now am getting somewhere - at least my LaTeX settings appear in the
output. The next problem I have is babel-related. I create results of
execution of my source blocks in org format so they are enclosed in
#+BEGIN_ORG ... #END_ORG which gets translated by the new exporter
into \begin{org} \end{org} - which makes pdflatex unhappy because the
org environment is not defined anywhere. The old exported did not do
anything like that. What do I have to do to make it work in the new
exporter?

Thanks
Alex

On Mon, Sep 24, 2012 at 4:15 PM, Nicolas Goaziou n.goaz...@gmail.com wrote:
 Hello,

 Alexander Vorobiev alexander.vorob...@gmail.com writes:

 Here is my configuration section (it goes at the end of the org file).
 Nothing in the LaTeX_HEADER lines gets inserted into output tex
 document. The old exporter just inserted them all verbatim.

 #+STARTUP:align fold nodlcheck hidestars oddeven lognotestate
 #+PROPERTY: exports results
 #+TITLE: Test document
 #+AUTHOR:
 #+EMAIL: myem...@gmail.com
 #+DATE:
 #+DESCRIPTION: #+KEYWORDS:
 #+LANGUAGE:  en
 #+OPTIONS:   H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:nil -:t f:t *:t :t
 #+OPTIONS:   TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc
 #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0
 path:http://orgmode.org/org-info.js
 #+EXPORT_SELECT_TAGS: export
 #+EXPORT_EXCLUDE_TAGS: noexport
 #+LINK_UP:
 #+LINK_HOME:
 #+XSLT:
 #+LANGUAGE:   en
 #+LaTeX_CLASS:koma-article
 #+LaTeX_HEADER:\usepackage{color}
 #+LaTeX_HEADER:\definecolor{spot}{rgb}{0,0.2,0.6}
 #+LaTeX_HEADER:\definecolor{TUgreen}{RGB}{41,93,80}
 #+LaTeX_HEADER:\setkomafont{section}{\color{TUgreen}\sffamily\bfseries}
 #+LaTeX_HEADER:\renewcommand{\sfdefault}{jvn}
 #+LaTeX_HEADER:\renewcommand*\familydefault{\sfdefault}
 #+LaTeX_HEADER:\usepackage[automark,nouppercase]{scrpage2}
 #+LaTeX_HEADER:\clearscrheadfoot
 #+LaTeX_HEADER:\setheadwidth{paper}
 #+LaTeX_HEADER:\setfootwidth{paper}
 #+LaTeX_HEADER:\cohead[]{
 #+LaTeX_HEADER:  \includegraphics[width=7.75in]{MyHeader.jpg}
 #+LaTeX_HEADER:}
 #+LaTeX_HEADER:\cofoot[]{
 #+LaTeX_HEADER:  \includegraphics[width=7.75in]{MyFooter.png}
 #+LaTeX_HEADER:}
 #+LaTeX_HEADER:\pagestyle{scrplain}
 #+LaTeX_HEADER:\AtBeginDocument{\vspace*{5\baselineskip}\thispagestyle{scrheadings}}
 #+LaTeX_HEADER:\setlength{\topmargin}{-0.80in}
 #+LaTeX_HEADER:\setlength{\textheight}{730pt}
 #+LaTeX_HEADER:\makeatletter
 #+LaTeX_HEADER:\renewcommand{\maketitle}{
 #+LaTeX_HEADER:% \vspace*{5\baselineskip}%
 #+LaTeX_HEADER: \vskip 2em%
 #+LaTeX_HEADER: \begin{center}%
 #+LaTeX_HEADER:  {\LARGE \@title \par}%
 #+LaTeX_HEADER: \end{center}%
 #+LaTeX_HEADER: \par} \makeatother

 The new tex file just starts like this

 % Created 2012-09-24 Mon 11:31
 \author{}
 \date{}
 \title{Test document}
 \hypersetup{
   pdfkeywords={},
   pdfsubject={},
   pdfcreator={Generated by Org mode 7.9.1 in Emacs 24.2.1.}}
 \begin{document}

 \maketitle

 You need a space after the colons in #+LATEX_HEADER: and #+LATEX_CLASS
 lines.


 Regards,

 --
 Nicolas Goaziou



Re: [O] LaTeX export problem

2012-09-22 Thread Nicolas Goaziou
Hello,

t...@tsdye.com (Thomas S. Dye) writes:

 (require 'org-special-blocks)

You can remove this line. `org-special-blocks' is obsolete with the new
exporter.


Regards,

-- 
Nicolas Goaziou



Re: [O] LaTeX export problem

2012-09-22 Thread Nicolas Goaziou
Hello,

Alexander Vorobiev alexander.vorob...@gmail.com writes:

 I tried the new exporter (using today's snapshot of the sources) and
 it produced invalid LaTeX (it calls hypersetup without loading
 hyperref package).

The export back-end doesn't load any package on its own. You have to
make sure hyperref is properly loaded (AFAIK, it is by default).

 It also ignored the #+LaTeX_CLASS: and all the
 #+LaTeX_HEADER:lines in my file.

Those lines shouldn't be ignored. You probably don't have any matching
entry in `org-e-latex-classes' for your #+LATEX_CLASS: specification.

I'm not sure about #+LaTeX_HEADER: lines. Do you have an example?

 Are there any examples of org files which show how to customize the
 new LaTeX exporter?

Try first:

M-x customize-group RET org-export-e-latex RET


Regards,

-- 
Nicolas Goaziou



Re: [O] LaTeX export problem

2012-09-21 Thread Bastien
Hi Alexander,

Alexander Vorobiev alexander.vorob...@gmail.com writes:

 Could you point us to any documentation on how to switch to the new
 exporter? 

Add contrib/lisp to your load-path.

(require 'org-e-latex)

then M-x org-export-dispatch RET to get a menu and be able to 
export to LaTeX from here.

 Is the tutorial
 http://orgmode.org/worg/org-tutorials/org-latex-export.html still
 relevant?

No, this tutorial is valid for the current exporter, not for 
Nicolas exporter.

HTH,

-- 
 Bastien



Re: [O] LaTeX export problem

2012-09-21 Thread Alexander Vorobiev
I tried the new exporter (using today's snapshot of the sources) and
it produced invalid LaTeX (it calls hypersetup without loading
hyperref package). It also ignored the #+LaTeX_CLASS: and all the
#+LaTeX_HEADER:lines in my file. Are there any examples of org files
which show how to customize the new LaTeX exporter?

Thanks
Alex

On Fri, Sep 21, 2012 at 3:48 AM, Bastien b...@altern.org wrote:
 Hi Alexander,

 Alexander Vorobiev alexander.vorob...@gmail.com writes:

 Could you point us to any documentation on how to switch to the new
 exporter?

 Add contrib/lisp to your load-path.

 (require 'org-e-latex)

 then M-x org-export-dispatch RET to get a menu and be able to
 export to LaTeX from here.

 Is the tutorial
 http://orgmode.org/worg/org-tutorials/org-latex-export.html still
 relevant?

 No, this tutorial is valid for the current exporter, not for
 Nicolas exporter.

 HTH,

 --
  Bastien



Re: [O] LaTeX export problem

2012-09-21 Thread Thomas S. Dye
Alexander Vorobiev alexander.vorob...@gmail.com writes:

 I tried the new exporter (using today's snapshot of the sources) and
 it produced invalid LaTeX (it calls hypersetup without loading
 hyperref package). It also ignored the #+LaTeX_CLASS: and all the
 #+LaTeX_HEADER:lines in my file. Are there any examples of org files
 which show how to customize the new LaTeX exporter?

 Thanks
 Alex

Aloha Alex,

I've been exploring the new exporter with a recent project. I have the
following probably too complex setup that lets me use biblatex in
conjunction with ebib.  I'm also using a customized setup for the Lucida
fonts (packages tsdlucida and lucidabr), which you'll most likely want
to change.

* Org-mode setup   :noexport:
This is a setup for Nicolas Goaziou's new exporter

#+name: setup
#+begin_src emacs-lisp :noweb yes :results silent
(require 'org-export)
(require 'org-e-latex)
(require 'org-e-html)
(setq org-export-latex-packages-alist nil)
(add-to-list 'org-export-latex-packages-alist 
'(colorlinks=true,urlcolor=SteelBlue4,linkcolor=Firebrick4,citecolor=Green4 
hyperref))
(add-to-list 'org-export-latex-packages-alist 
'(style=authoryear-comp,backend=bibtex8 biblatex))
(add-to-list 'org-export-latex-packages-alist '(x11names xcolor))
(add-to-list 'org-export-latex-packages-alist '( microtype))
(add-to-list 'org-export-latex-packages-alist '( graphicx))
(add-to-list 'org-export-latex-packages-alist '( ragged2e))
(add-to-list 'org-export-latex-packages-alist '( booktabs))
(add-to-list 'org-export-latex-packages-alist '( tabularx))
(add-to-list 'org-export-latex-packages-alist '( tsdlucida))
(add-to-list 'org-export-latex-packages-alist '( wasysym))
(add-to-list 'org-export-latex-packages-alist '( paralist))
(add-to-list 'org-export-latex-packages-alist 
'(altbullet,lucidasmallscale,expert,vargreek lucidabr))
(add-to-list 'org-export-latex-packages-alist '(T1 fontenc))
(add-to-list 'org-export-latex-packages-alist '(AUTO inputenc))
(setq org-entities-user nil) 
(add-to-list 'org-entities-user '(space \\  nil))
(add-to-list 'org-entities-user '(amacron \\={a} nil #0257 a a 
ā))
(add-to-list 'org-entities-user '(emacron \\={e} nil #0275 e e 
ē))
(add-to-list 'org-entities-user '(imacron \\={i} nil #0299 i i 
ī))
(add-to-list 'org-entities-user '(omacron \\={o} nil #0333 o o 
ō))
(add-to-list 'org-entities-user '(umacron \\={u} nil #0363 u u 
ū))
(add-to-list 'org-entities-user '(Amacron \\={A} nil #0256 A A 
Ā))
(add-to-list 'org-entities-user '(Emacron \\={E} nil #0274 E E 
Ē))
(add-to-list 'org-entities-user '(Imacron \\={I} nil #0298 I I 
Ī))
(add-to-list 'org-entities-user '(Omacron \\={O} nil #0332 O O 
Ō))
(add-to-list 'org-entities-user '(Umacron \\={U} nil #0362 U U 
Ū))
(setq org-e-latex-pdf-process '(texi2dvi --pdf --clean --verbose --batch 
%f))
(require 'org-special-blocks)
(define-key org-mode-map (kbd C-c e) 'org-export-dispatch)
(setq org-e-latex-tables-booktabs t)
(setq org-export-latex-hyperref-format \\ref{%s})
(setq org-e-latex-remove-logfiles nil)
(setq org-e-latex-toc-command \\tableofcontents\n\n)
(add-to-list 'org-e-latex-classes
 '(koma-article
   \\documentclass{scrartcl}
  [NO-DEFAULT-PACKAGES]
  [PACKAGES]
  [EXTRA]
  \\let\\itemize\\compactitem
  \\let\\description\\compactdesc
  \\let\\enumerate\\compactenum
  \\bibliography{local}
  \\newcolumntype{Y}{{\\RaggedRight\\arraybackslash}X}
   (\\section{%s} . \\section*{%s})
   (\\subsection{%s} . \\subsection*{%s})
   (\\subsubsection{%s} . \\subsubsection*{%s})
   (\\paragraph{%s} . \\paragraph*{%s})
   (\\subparagraph{%s} . \\subparagraph*{%s})))
ngz-nbsp
define-standard-biblatex-commands
define-style-specific-biblatex-commands
#+end_src

** Standard Biblatex citation commands

#+name: define-standard-biblatex-commands
#+begin_src emacs-lisp :noweb yes :results silent :exports none
  define-biblatex-cite-link
  define-biblatex-cap-cite-link
  define-biblatex-parencite-link
  define-biblatex-cap-parencite-link
  define-biblatex-footcite-link
  define-biblatex-footcitetext-link

#+end_src

#+name: define-biblatex-cite-link
#+begin_src emacs-lisp :results silent :exports none
  (org-add-link-type 
   cite 'ebib
   (lambda (path desc format)
 (cond
  ((eq format 'html)
   (format (cite%s/cite) path))
  ((eq format 'latex)
   (if (or (not desc) (equal 0 (search cite: desc)))
   (format \\cite{%s} path)
 (format \\cite[%s][%s]{%s}
 (cadr (split-string desc ;))
 (car (split-string desc ;))  path))
#+end_src

#+name: define-biblatex-cap-cite-link
#+begin_src emacs-lisp :results silent :exports none
  

Re: [O] LaTeX export problem

2012-09-20 Thread Alexander Vorobiev
Hi,

I am having similar problems with LaTeX export. I am exporting source
code snippets (XML) which has many variables with underscores in their
names. At some point in the process of switching to more recent Org
the export started producing incorrect LaTeX so the generation of PDF
fails, therefore the functionality is unusable for me.

Could you point us to any documentation on how to switch to the new
exporter? Is the tutorial
http://orgmode.org/worg/org-tutorials/org-latex-export.html still
relevant?

Thanks
Alex

On Wed, Sep 19, 2012 at 2:57 AM, Bastien b...@altern.org wrote:
 Hi Gary,

 Gary Oberbrunner ga...@oberbrunner.com writes:

 Using a recent git checkout of org-mode (f51c405), the following small
 org-mode file produces invalid LaTeX.  I'm pretty sure it used to
 work.  The \alpha and \beta seem to be what confuses it.

 ---snip
 * Scorecards
 ** Product Releases
 | *Product* | *\alpha* | *\beta* | *Release* | *Status* |
 |---+--+-+---+--|
 | test  | a| b   | c | d|
 ---snip

 Open this with emacs -Q (emacs 24), load org-mode, and C-c C-e C-d to
 export as LaTeX, you get the following error:

 The new LaTeX exporter does the right thing here.

 You can experiment with it or wait until it is part of core.

 Thanks,

 --
  Bastien




Re: [O] LaTeX export problem

2012-09-19 Thread Bastien
Hi Gary,

Gary Oberbrunner ga...@oberbrunner.com writes:

 Using a recent git checkout of org-mode (f51c405), the following small
 org-mode file produces invalid LaTeX.  I'm pretty sure it used to
 work.  The \alpha and \beta seem to be what confuses it.

 ---snip
 * Scorecards
 ** Product Releases
 | *Product* | *\alpha* | *\beta* | *Release* | *Status* |
 |---+--+-+---+--|
 | test  | a| b   | c | d|
 ---snip

 Open this with emacs -Q (emacs 24), load org-mode, and C-c C-e C-d to
 export as LaTeX, you get the following error:

The new LaTeX exporter does the right thing here.

You can experiment with it or wait until it is part of core.

Thanks,

-- 
 Bastien



[O] LaTeX export problem

2012-09-12 Thread Gary Oberbrunner
Using a recent git checkout of org-mode (f51c405), the following small
org-mode file produces invalid LaTeX.  I'm pretty sure it used to
work.  The \alpha and \beta seem to be what confuses it.

---snip
* Scorecards
** Product Releases
| *Product* | *\alpha* | *\beta* | *Release* | *Status* |
|---+--+-+---+--|
| test  | a| b   | c | d|
---snip

Open this with emacs -Q (emacs 24), load org-mode, and C-c C-e C-d to
export as LaTeX, you get the following error:

! Missing $ inserted.
inserted text
$
l.44  \textbf{Product}\textbf{\alpha}
  \textbf{\beta}\textbf{Re...


I'm no LaTeX guru, but here's the generated file:

% Created 2012-09-12 Wed 12:37
\documentclass[11pt]{article}
\usepackage[latin1]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\providecommand{\alert}[1]{\textbf{#1}}

\title{foo}
\author{}
\date{\today}
\hypersetup{
  pdfkeywords={},
  pdfsubject={},
  pdfcreator={Emacs Org-mode version 7.9.1}}

\begin{document}

\maketitle

\setcounter{tocdepth}{3}
\tableofcontents
\vspace*{1cm}
\section{Scorecards}
\label{sec-1}
\subsection{Product Releases}
\label{sec-1-1}


\begin{center}
\begin{tabular}{l}
 \textbf{Product}\textbf{\alpha}\textbf{\beta}  
\textbf{Release}\textbf{Status}  \\
\hline
 testa  b c
  d\\
\end{tabular}
\end{center}

\end{document}


-- 
Gary



Re: [O] LaTeX export problem

2012-01-17 Thread Piotr Kaźmierczak
Wiadomość napisana przez Nick Dokos w dniu 10 sty 2012, o godz. 01:13:

 Have you tried exporting a simple file to latex? Perhaps something as simple
 as:
 
 ---
 * Foo
 Bar
 ---
 
 
 Nick

Yes I have, it still produces a one-line TeX file. 


Re: [O] LaTeX export problem

2012-01-17 Thread Nick Dokos
Piotr Kaźmierczak p.h.kazmierc...@gmail.com wrote:

 Wiadomość napisana przez Nick Dokos w dniu 10 sty 2012, o godz. 01:13:
 
  Have you tried exporting a simple file to latex? Perhaps something as simple
  as:
  
  ---
  * Foo
  Bar
  ---
  
  
  Nick
 
 Yes I have, it still produces a one-line TeX file. 

In that case, it seems like your orgmode install is hosed - have you tried
reinstalling from scratch?

Nick



Re: [O] LaTeX export problem

2012-01-17 Thread Piotr Kaźmierczak
Wiadomość napisana przez Nick Dokos w dniu 17 sty 2012, o godz. 18:00:

 In that case, it seems like your orgmode install is hosed - have you tried
 reinstalling from scratch?

I did, but no luck. There must be something else I'm missing here, but I don't 
have time to investigate now. 

Thanks for your help, I'll post a solution here once I find one.

Piotr


Re: [O] LaTeX export problem

2012-01-17 Thread Eric S Fraga
Piotr Kaźmierczak p.h.kazmierc...@gmail.com writes:

 Wiadomość napisana przez Nick Dokos w dniu 10 sty 2012, o godz. 01:13:

 Have you tried exporting a simple file to latex? Perhaps something as simple
 as:
 
 ---
 * Foo
 Bar
 ---
 
 
 Nick

 Yes I have, it still produces a one-line TeX file. 

can you, just in case, post to the mailing list with both org and
resulting tex files attached?

Also, what do M-x find-library RET org RET and M-x org-version RET
say?

What operating system are you using?  I'm assuming a Mac from your
previous message.

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
: using Org-mode version 7.8.03 (release_7.8.03.144.g7233)



[O] LaTeX export problem

2012-01-09 Thread Piotr Kaźmierczak
Hi,   

I have a very strange problem: I can no longer process an org file with all my 
notes to LaTeX. I've been using org-mode this way for some time now, and I was 
always able to get a nice tex file I could later process to PDF. Now all I get 
is a TeX file with absolutely no new-line symbols (a huge one-line file), and 
pdflatex obviously can't process that. I haven't updated org for a while, and 
it doesn't seem to matter which Emacs version I try (GNU 23, GNU 24, Aquamacs 
2.4), I still can't get the correct output. The only difference from the last 
time I managed to get a correct tex output is that I added some more notes to 
the org file.  

I'm using Org 7.8.

Any ideas?

regards,
Piotr Kaźmierczak





Re: [O] LaTeX export problem

2012-01-09 Thread Nick Dokos

Piotr Kaźmierczak p.h.kazmierc...@gmail.com wrote:


 I have a very strange problem: I can no longer process an org file
 with all my notes to LaTeX. I've been using org-mode this way for some
 time now, and I was always able to get a nice tex file I could later
 process to PDF. Now all I get is a TeX file with absolutely no
 new-line symbols (a huge one-line file), and pdflatex obviously can't
 process that. I haven't updated org for a while, and it doesn't seem
 to matter which Emacs version I try (GNU 23, GNU 24, Aquamacs 2.4), I
 still can't get the correct output. The only difference from the last
 time I managed to get a correct tex output is that I added some more
 notes to the org file.
 

Have you tried exporting a simple file to latex? Perhaps something as simple
as:

---
* Foo
Bar
---


Nick



[O] LaTeX export: Problem with clipped tables

2011-07-09 Thread Frederik

Hi there!

I experience some problems when exporting clipped tables to LaTeX:
The text in the fields doesn't get properly expanded, the `=' is not 
removed.


Imagine the following table in org-mode:

| on the one hand | on the other = |
|-+-|
| 15| 15|
| some long tex= | Lorem ipsum d= |

Exporting to LaTeX gives me:

\begin{center}
  \begin{tabular}{ll}
on the one handon the other =nd  \\
\hline
some long tex=line in this fieldLorem ipsum d=or sit \\
  \end{tabular}
\end{center}

Strangely enough, when copying the LaTeX source from my emacs buffer 
into Thunderbird, the `=' disappear, and the text is correct...


I use version 7.6.

Any hints?

Regards.

--
Frederik




Re: [O] LaTeX export: Problem with clipped tables

2011-07-09 Thread Bastien
Hi Frederik,

Frederik freak.f...@gmail.com writes:

 I experience some problems when exporting clipped tables to LaTeX:
 The text in the fields doesn't get properly expanded, the `=' is not
 removed.

thanks for reporting this -- should be fixed now.

Best,

-- 
 Bastien