Re: Problems with Org Mode which doesn't properly manage linebreaks in LaTeX export

From: Carsten Dominik <carsten.dominik@gmail.com>
To: Pierfranco Minsenti <pierfranco.minsenti@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problems with Org Mode which doesn't properly manage linebreaks in LaTeX export
Date: Sun, 3 Jan 2010 20:14:07 +0100	[thread overview]
Message-ID: <9E561110-AAE8-46AA-A15D-657FE8AAB6A9@gmail.com> (raw)
In-Reply-To: <4bec4eb31001031110l58b8913fh26b787482b25bf13@mail.gmail.com>

On Jan 3, 2010, at 8:10 PM, Pierfranco Minsenti wrote:

> You are right Carsten: in my .emacs file I have put, since long, the  
> following lines of command about longlines (following a  
> recommendation found on the Internet and so far I have been  
> perfectly happy with this):
>
> ;;LONGLINES:
> (autoload 'longlines-mode
>     "longlines.el"
>      "Minor mode for automatically wrapping long lines." t)
>
>
> Now, just 2 questions:
>
> 1) should I disable the setting about longlines mode in my .emacs  
> file in order to solve the problem with the export from .org to  
> latex? Would it be enough?

Why don't you try?  I think it should solve the problem.

>
> AND about your recommendation to switch to Emacs 23
>
> 2) I use an old version  of CarbonEmacs for MAC OS X 10.3 Panther  
> 2007 and for using the new 2009 version of CarbonEmacs (which  
> requires Leopard) I should say farewell to my G4 Ibook and buy  
> another computer. So: is there another way to switch to Emacs 23?

I guess you could compile Emacs 23 yourself.

- Carsten

>
> Thank you for your kind help.
>
> best wishes
>
> pierfranco
>
> 2010/1/3 Carsten Dominik <carsten.dominik@gmail.com>
> Hi Pierfranco,
>
> are you using longlines.el or something similar with hard and soft  
> new lines?
> Bad Idea.  Your best option is to switch to Emacs 23 and use is  
> built-in facilities (visual-line-mode and word-wrap) to display long  
> lines.
>
> - Carsten
>
>
> On Jan 3, 2010, at 7:30 PM, Pierfranco Minsenti wrote:
>
> Hi Carsten,
>
> thank you yor your early reply.
> Here is an example as you requested: some lines from my  
> original .org file (the lines between the ==== rows):
>
> =========================================================
> * ML built-in transaction monitoring facility
>
>
> ** Features
>
> MetaLib has a built-in transaction monitoring facility (a  
> transaction logging component).
> This component enables system administrators to retrieve the stored  
> transaction log data and analyze them at their convenience.
>
>
> The data elements stored by the transaction logging component are  
> the following:
>  - date/time stamp of transactions
>  - resource name (i.e. resources as targets for the metasearch  
> engine: databases, catalogues, directories, search engines, full- 
> text electronic collections etc.) available in the systems (the so  
> called local KnowledgeBase)
>  - resource type (i.e. subject gateway; library catalogues, etc.)  
> and discipline
>  - resource access method code: (i.e. the type of connector required  
> to comunicate with the external resource: e.g. Z39.50; HTML  
> protocol; XML protocol)
>  - users demographic data: Affiliation: Undergraduate; Graduate;  
> Staff; Guest) and Academic status: Undergraduate; Graduate; Post  
> Graduate; Faculty Member; Other)
>  - users type related to: authenticated use of the system and use of  
> personalization features: Registered Users; Users with Personal  
> Lists; Users with Saved Items
>  - number of searches per resource
>  - number of search sessions per day, user groups
>  - patron's entry (i.e. the search query)
>  - the number of hits
>  - search type code (i.e. the type of fields used)
>  - search status code (DONE; ERROR; SUSPEND; FIND; FETCH; CANCEL)
>  - system modules used (Quick Search; Find Database; MetaSearch;  
> History; Alerts)
>
>
> ** Limitations
>
> The pre-defined reports available suffers severals limitations, some  
> peculiar drawbaks of the web logging system made available. These  
> consist in the fact that relevant data are filtered out:
>  - IP of users (which would make it possible to identify their  
> provenance from the local network of from the outside internet)
>  - data about full-text resources found and actual file the  
> downloaded are not available.
> Infact the Links to Native Interface section warns that: "This  
> statistical report counts the number of times users link to the  
> native interface of a resource. This report includes links to the  
> native interface of any resource presented in the user interface,  
> including Link Only resources (i.e., not searchable in MetaLib);  
> links to the native interface to view the search results of a Search  
> and Link resource; as well as links to the native interface to view  
> full-text documents, etc. that may be included as external links in  
> the full records of search results. The display includes the  
> database name and number of times linked."
>
> Besides, the convention used for counting queries:
>  - the system counts queries per target resources, so that single  
> queries submitted in the user interface are multiplied by the number  
> of target resouces they have actually been sent.
>
> =================================================================
>
> Here are the same lines as they appear in the exported LaTeX file  
> (the lines between the <<<< rows):
>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
> % Created 2010-01-03 Sun 19:20 \documentclass[11pt]{article}  
> \usepackage[latin1]{inputenc}    %[utf8]{inputenc} \usepackage[T1] 
> {fontenc} \usepackage{graphicx} \usepackage{longtable}  
> \usepackage{hyperref}   \title{ML-TLA} \author{Pierfranco Minsenti}  
> \date{03 January 2010}  \begin{document}  \maketitle   
> \setcounter{tocdepth}{3} \tableofcontents \vspace*{1cm}
>
> \section{ML built-in transaction monitoring facility} \label{sec-1}
>
>
> \subsection{Features} \label{sec-1.1}
>
> MetaLib has a built-in transaction monitoring facility (a  
> transaction logging
> component).
> This component enables system administrators to retrieve the stored
> transaction log data and analyze them at their convenience.
>
>
>
> The data elements stored by the transaction logging component are the
> following:
> \begin{itemize} \item date/time stamp of transactions \item resource  
> name (i.e. resources as targets for the metasearch engine:  
> \end{itemize} databases, catalogues, directories, search engines,  
> full-text electronic
> collections etc.) available in the systems (the so called local  
> KnowledgeBase)
> \begin{itemize} \item resource type (i.e. subject gateway; library  
> catalogues, etc.) and \end{itemize} discipline
> \begin{itemize} \item resource access method code: (i.e. the type of  
> connector required to \end{itemize} comunicate with the external  
> resource: e.g. Z39.50; HTML protocol; XML
> protocol)
> \begin{itemize} \item users demographic data: Affiliation:  
> Undergraduate; Graduate; Staff; Guest) \end{itemize} and Academic  
> status: Undergraduate; Graduate; Post Graduate; Faculty Member;
> Other)
> \begin{itemize} \item users type related to: authenticated use of  
> the system and use of \end{itemize} personalization features:  
> Registered Users; Users with Personal Lists; Users
> with Saved Items
> \begin{itemize} \item number of searches per resource \item number  
> of search sessions per day, user groups \item patron's entry (i.e.  
> the search query) \item the number of hits \item search type code  
> (i.e. the type of fields used) \item search status code (DONE;  
> ERROR; SUSPEND; FIND; FETCH; CANCEL) \item system modules used  
> (Quick Search; Find Database; MetaSearch; History; \end{itemize}  
> Alerts)
>
>
>
> \subsection{Limitations} \label{sec-1.2}
>
> The pre-defined reports available suffers severals limitations, some  
> peculiar
> drawbaks of the web logging system made available. These consist in  
> the fact
> that relevant data are filtered out:
> \begin{itemize} \item IP of users (which would make it possible to  
> identify their provenance from \end{itemize} the local network of  
> from the outside internet)
> \begin{itemize} \item data about full-text resources found and  
> actual file the downloaded are not \end{itemize} available.
> Infact the Links to Native Interface section warns that: ``This  
> statistical
> report counts the number of times users link to the native interface  
> of a
> resource. This report includes links to the native interface of any  
> resource
> presented in the user interface, including Link Only resources  
> (i.e., not
> searchable in MetaLib); links to the native interface to view the  
> search
> results of a Search and Link resource; as well as links to the native
> interface to view full-text documents, etc. that may be included as  
> external
> links in the full records of search results. The display includes  
> the database
> name and number of times linked.''
>
> Besides, the convention used for counting queries:
> \begin{itemize} \item the system counts queries per target  
> resources, so that single queries \end{itemize} submitted in the  
> user interface are multiplied by the number of target
> reosurces they have actually been sent
>
>
>  \end{document}
>
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>
> Pierfranco
>
>
>
>
> 2010/1/3 Carsten Dominik <carsten.dominik@gmail.com>
>
> Hi Pierfranco,
>
> please augment your report with example input (.org file) and
> output (.tex file).
>
> Thanks.
>
> - Carsten
>
>
> On Jan 3, 2010, at 5:51 PM, Pierfranco Minsenti wrote:
>
> Hi all,
>
> this is my 1st message to the list and I am writing to ask for help.
> I have a problem with the LaTeX export features of Org Mode, version  
> 6.27a. installed on a GNU Emacs Emacs 22.1.1 (powerpc-apple- 
> darwin7.9.0, Carbon Version 1.6.0).
>
> The problem is the folllowing: in the header lines of the LaTeX file  
> exported from an original Org file, the different commands which are  
> automatically addedd by the system and which should begin each of  
> them on a new paragraph, appear all in a single multiline paragraph.  
> The problem is that this paragraph is commented, because it begins  
> with the % Created 2010-01-03 etc. also added by the system.
> Perhaps this is also why the the PDF export doen't work.
>
> Another problem, caused by a line break not properly managed, is  
> related to bulleted lists when they are exported to a LaTeX file:  
> when items are longer that a single line, the lines after the first  
> are broken down (that is: the second line etc. begin a new, not- 
> bulleted paragraph, and they are not the second line of the item).
>
> I have set the variable Org Export Preserve Breaks to on (non-nil)  
> but nothing has changed.
>
> I have also checked the specific LaTeX export variables of Org but  
> all seems properly setted.
> By the way, when I make a very similar export from another Emacs  
> mode, that is Muse Mode, to LaTeX, I don't have these problems and  
> everything works just fine.
>
> Has anybody experienced this problem with Org Mode and could help me?
>
> Thank you very much in advance.
>
> pierfranco
>
> _______________________________________________
> 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
>
> - Carsten
>
>
>
>
>
> - Carsten
>
>
>

- Carsten