emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Flávio <flaviostz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Latex export error in tables
Date: Mon, 9 Feb 2009 12:40:29 +0000 (UTC)	[thread overview]
Message-ID: <loom.20090209T121047-366@post.gmane.org> (raw)
In-Reply-To: <e7cdbe30902080457m29fd0346i2d024174c54e8ea9@mail.gmail.com>

Manish <mailtomanish.sharma <at> gmail.com> writes:

> 
> 2009/2/8 Flávio de Souza
> [...]
> >
> > I tried with smaller files (only one dynamic block) but the problem
> > seems to disappear. I made some other attempts, but all useless. So I
> > think is something related with all those blocks I am using in this
> > particular org file.
> 
> Did those other files contain utf-8 characters?
> 
> >
> >
> > Problem happens 100% time when using my complete, that's the reason I
> > sent the whole file.
> >
> [snip: pdflatex compile log]
> > (/usr/share/texmf-texlive/tex/generic/babel/babel.def))) (./projeto.aux)
> > Runaway argument?
> > {\contentsline {subsection}{\numberline {4.1}Por qu\GenericError {(in\ETC.
> > ! File ended while scanning use of \@writefile.
> > <inserted text>
> >        \par
> > l.14 \begin{document}
> >
> > (/usr/share/texmf/tex/context/base/supp-pdf.tex
> > [Loading MPS to PDF converter (version 2006.09.02).]
> > ) (/usr/share/texmf-texlive/tex/latex/hyperref/nameref.sty
> > (/usr/share/texmf-texlive/tex/latex/oberdiek/refcount.sty)) (./projeto.out)
> > (./projeto.out)
> >
> > ! Package inputenc Error: Unicode char \u8:ávi not set up for use with LaTeX.
> 
> I think this is an issue at a more fundamental level than with export to Latex
> from Org.  Are you able to compile *any* utf-8 encoded tex file to PDF in your
> setup at all (whether generated by Org or something else?)  I am no unicode
> expert.  May be you would like to pursue this issue in parallel in some
> tex|latex|pdflatex group as well?
> 


Manish,

This is not a utf-8 encoding problem. When I generate a tex file with org, I
change manually from \usepackage[utf8]{inputenc} to
\usepackage[latin1]{inputenc}. All characters are recognized without any
problems. I tested it both in Linux and Windows XP. This works fine.

Now I will try to narrow down my problem and see if we can find a solution. I
really believe the problem is in tex code generated by org. I will show you the
reason I am pointing the problem to org.

If I have an org table in my file like this one:

#+BEGIN: columnview :hlines 1 :vlines t :id "09.0001-ESCH"  :skip-empty-rows t
|   | ITEM                 | Quotation | Sold | Required |
|---+----------------------+-----------+------+----------|
|   | * Escopo Horas       |       230 | 1640 |          |
|   | ** Gerência          |        10 |      |          |
|   | ** Definição         |        50 |      |          |
|   | ** Configuração      |       100 |      |          |
|   | ** Comis. & Start up |        50 |      |          |
|   | ** Documentação      |        20 |      |          |
| / | <>                   |        <> | <>   | <>       |
#+END:

Then I select the option to generate latex "[L] export as LaTeX to temporary
buffer" ( I only want the tex code, I am not going to do any further
transformation on it ). The raw code for that specific part of the file is:


\begin{tabular}{l|l|r|l}
 ITEM                    &  Quotation  &  Sold  &  Required  \\
\hline
 * Escopo Horas          &        230  &  1640  &            \\
 \textbf{* Gerência      &         10  &        &            \\
 *} Definição            &         50  &        &            \\
 \textbf{* Configuração  &        100  &        &            \\
 *} Comis. & Start up    &         50  &        &            \\
 ** Documentação         &         20  &        &            \\
\end{tabular}

The problems I can point to in this code are:

1) The code "\textbf{* Gerência" is wrong, it should be "\textbf{*} Gerência"
2) The code "*} Definição" is wrong, it should be "\textbf{*} Definição". The
same problem happens in other rows as you can see above. So all these open
command lines will be the source for the errors.
3) One minor problem is that the character "&" at "Comis. & Start up" should be
genrated as "\&". However this is a minor problem and I just dont use this
character anymore. 

Now I will describe my solution (workaround) I found today for it. Firstly I
changed my org table configuration to:

#+BEGIN: columnview :hlines 2 :vlines t :id "09.0001-ESCH"  :skip-empty-rows t
|   | ITEM                 | Quotation | Sold | Required |
|---+----------------------+-----------+------+----------|
|   | * Escopo Horas       |       230 | 1640 |          |
|---+----------------------+-----------+------+----------|
|   | ** Gerência          |        10 |      |          |
|---+----------------------+-----------+------+----------|
|   | ** Definição         |        50 |      |          |
|---+----------------------+-----------+------+----------|
|   | ** Configuração      |       100 |      |          |
|---+----------------------+-----------+------+----------|
|   | ** Comis.and Startup |        50 |      |          |
|---+----------------------+-----------+------+----------|
|   | ** Documentação      |        20 |      |          |
| / | <>                   |        <> | <>   | <>       |
#+END:

With the option :hlines 2 my table has horizontal lines in every row. When I
generate tex, it will look like this:

\begin{tabular}{l|l|r|l}
 ITEM                  &  Quotation  &  Sold  &  Required  \\
\hline
 * Escopo Horas        &        230  &  1640  &            \\
\hline
 ** Gerência           &         10  &        &            \\
\hline
 ** Definição          &         50  &        &            \\
\hline
 ** Configuração       &        100  &        &            \\
\hline
 ** Comis.and Start up  &         50  &        &            \\
\hline
 ** Documentação       &         20  &        &            \\
\end{tabular}

The above code is a perfect tex table and I get no errors, because now the code
is generated with \hline. I needed to "deviate" org tex generation code from
using \textbuf.... :)

I am not a specialist in Tex, I dont even know what \textbf means :) ...
... and I am still learning org, but in my opinion the problem is when org
generates the tex code.  

Maybe Carsten can give his opinion too. 

Thanks
Flávio.

  reply	other threads:[~2009-02-09 12:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-07 18:25 Flávio de Souza
2009-02-07 20:05 ` Manish
     [not found]   ` <87hc36ylr4.fsf@gmail.com>
2009-02-08 12:57     ` Manish
2009-02-09 12:40       ` Flávio [this message]
2009-02-09 12:51         ` R: " Giovanni Ridolfi
2009-02-09 14:22         ` Manish
2009-02-10 21:39           ` Flávio de Souza

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=loom.20090209T121047-366@post.gmane.org \
    --to=flaviostz@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: Latex export error in tables' \
    /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

Code repositories for project(s) associated with this 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).