From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierfranco Minsenti Subject: Re: Problems with Org Mode which doesn't properly manage linebreaks in LaTeX export Date: Sun, 3 Jan 2010 19:30:35 +0100 Message-ID: <4bec4eb31001031030m70cdd49ci833dd0fa40c0fa0e@mail.gmail.com> References: <4bec4eb31001030851j1595fa0fm37e9cf661abc0529@mail.gmail.com> <5F9FB5CE-DB51-4AA0-A650-655A718E1040@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0359382133==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NRVDw-0002Qs-EZ for emacs-orgmode@gnu.org; Sun, 03 Jan 2010 13:30:44 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NRVDr-0002HS-3t for emacs-orgmode@gnu.org; Sun, 03 Jan 2010 13:30:43 -0500 Received: from [199.232.76.173] (port=39767 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NRVDq-0002H7-Us for emacs-orgmode@gnu.org; Sun, 03 Jan 2010 13:30:39 -0500 Received: from mail-bw0-f215.google.com ([209.85.218.215]:62558) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NRVDp-0004Aj-SU for emacs-orgmode@gnu.org; Sun, 03 Jan 2010 13:30:38 -0500 Received: by bwz7 with SMTP id 7so9978353bwz.26 for ; Sun, 03 Jan 2010 10:30:35 -0800 (PST) In-Reply-To: <5F9FB5CE-DB51-4AA0-A650-655A718E1040@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org --===============0359382133== Content-Type: multipart/alternative; boundary=000325557726ff00c0047c46cc5d --000325557726ff00c0047c46cc5d Content-Type: text/plain; charset=ISO-8859-1 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 > > 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 > > > > --000325557726ff00c0047c46cc5d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 th= e =3D=3D=3D=3D rows):

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
* ML built-in transaction monitoring facility


** Features
MetaLib has a built-in transaction monitoring facility (a transaction logg= ing 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 t= he following:
=A0- date/time stamp of transactions
=A0- resource name= (i.e. resources as targets for the metasearch engine: databases, catalogue= s, directories, search engines, full-text electronic collections etc.) avai= lable in the systems (the so called local KnowledgeBase)
=A0- resource type (i.e. subject gateway; library catalogues, etc.) and dis= cipline
=A0- resource access method code: (i.e. the type of connector re= quired to comunicate with the external resource: e.g. Z39.50; HTML protocol= ; XML protocol)
=A0- users demographic data: Affiliation: Undergraduate; Graduate; Staff; G= uest) and Academic status: Undergraduate; Graduate; Post Graduate; Faculty = Member; Other)
=A0- users type related to: authenticated use of the syst= em and use of personalization features: Registered Users; Users with Person= al Lists; Users with Saved Items
=A0- number of searches per resource
=A0- number of search sessions per = day, user groups
=A0- patron's entry (i.e. the search query)
=A0-= the number of hits
=A0- search type code (i.e. the type of fields used)=
=A0- search status code (DONE; ERROR; SUSPEND; FIND; FETCH; CANCEL)
=A0- 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 sy= stem made available. These consist in the fact that relevant data are filte= red out:
=A0- IP of users (which would make it possible to identify their provenance= from the local network of from the outside internet)
=A0- data about fu= ll-text resources found and actual file the downloaded are not available. Infact the Links to Native Interface section warns that: "This statist= ical report counts the number of times users link to the native interface o= f a resource. This report includes links to the native interface of any res= ource presented in the user interface, including Link Only resources (i.e.,= not searchable in MetaLib); links to the native interface to view the sear= ch results of a Search and Link resource; as well as links to the native in= terface to view full-text documents, etc. that may be included as external = links in the full records of search results. The display includes the datab= ase name and number of times linked."

Besides, the convention used for counting queries:
=A0- the system = counts queries per target resources, so that single queries submitted in th= e user interface are multiplied by the number of target resouces they have = actually been sent.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Here are the sam= e lines as they appear in the exported LaTeX file (the lines between the &l= t;<<< rows):

<<<<<<<<<<<&l= t;<<<<<<<<<<<<<<<<<<&= lt;<<<<<<<<<<<<<<<<<<= <<<<<<<<

% Created 2010-01-03 Sun 19:20 \documentclass[11pt]{article} \usepackag= e[latin1]{inputenc}=A0=A0=A0 %[utf8]{inputenc} \usepackage[T1]{fontenc} \us= epackage{graphicx} \usepackage{longtable} \usepackage{hyperref}=A0=A0 \titl= e{ML-TLA} \author{Pierfranco Minsenti} \date{03 January 2010}=A0 \begin{doc= ument}=A0 \maketitle=A0 \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
tran= saction log data and analyze them at their convenience.



The = data elements stored by the transaction logging component are the
follow= ing:
\begin{itemize} \item date/time stamp of transactions \item resource name (= i.e. resources as targets for the metasearch engine: \end{itemize} database= s, catalogues, directories, search engines, full-text electronic
collect= ions etc.) available in the systems (the so called local KnowledgeBase)
\begin{itemize} \item resource type (i.e. subject gateway; library catalogu= es, etc.) and \end{itemize} discipline
\begin{itemize} \item resource ac= cess method code: (i.e. the type of connector required to \end{itemize} com= unicate with the external resource: e.g. Z39.50; HTML protocol; XML
protocol)
\begin{itemize} \item users demographic data: Affiliation: Und= ergraduate; Graduate; Staff; Guest) \end{itemize} and Academic status: Unde= rgraduate; Graduate; Post Graduate; Faculty Member;
Other)
\begin{ite= mize} \item users type related to: authenticated use of the system and use = of \end{itemize} personalization features: Registered Users; Users with Per= sonal 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 entr= y (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; SUSPEN= D; FIND; FETCH; CANCEL) \item system modules used (Quick Search; Find Datab= ase; MetaSearch; History; \end{itemize} Alerts)



\subsection{Limitations} \label{sec-1.2}

The pre-define= d 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 r= esource
presented in the user interface, including Link Only resources (i.e., notsearchable in MetaLib); links to the native interface to view the search<= br>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 externa= l
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 th= at single queries \end{itemize} submitted in the user interface are multipl= ied by the number of target
reosurces they have actually been sent


=A0\end{document}

<<<<<<<<<<&l= t;<<<<<<<<<<<<<<<<<<&= lt;<<<<<<<<<<<<<<<<<<= <<<<<<<<<<<<<<

Pierfranco




2010/1/3 Carst= en 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 V= ersion 1.6.0).

The problem is the folllowing: in the header lines of the LaTeX file export= ed from an original Org file, the different commands which are automaticall= y addedd by the system and which should begin each of them on a new paragra= ph, appear all in a single multiline paragraph. The problem is that this pa= ragraph 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 long= er 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 noth= ing has changed.

I have also checked the specific LaTeX export variables of Org but all seem= s 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 wor= ks 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@gn= u.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten




--000325557726ff00c0047c46cc5d-- --===============0359382133== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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 --===============0359382133==--