On Thu, Apr 09, 2015 at 05:22:07PM +0200, Markus Mohrhard wrote:
>Hey,
>
>As you are discussing this on the developer list and not in bugzilla I
>have to assume that you plan to work on resolving that issue. You
>already got a few interesting code pointers pointing to libxml2 in th
Hey,
On Thu, Apr 9, 2015 at 5:13 PM, Jens Tröger
wrote:
> On Thu, Apr 09, 2015 at 11:42:07AM +0300, Tor Lillqvist wrote:
> >> release builds should not print red herrings on stdout/stderr;
> >
> >But running soffice from the command line on OS X is not the right
> >thing to do anyw
On Thu, Apr 09, 2015 at 11:42:07AM +0300, Tor Lillqvist wrote:
>> release builds should not print red herrings on stdout/stderr;
>
>But running soffice from the command line on OS X is not the right
>thing to do anyway (unless you are a developer debugging something), so
>debatin
Tor,
On Thu, Apr 09, 2015 at 11:28:46AM +0300, Tor Lillqvist wrote:
>Note that you are running the soffice binary from the command-line,
>which obviously is not at all a normal way to run LibreOffice on OS
>X.
What is "normal" is not the question. I run most of my stuff out of a
term
On Thu, Apr 09, 2015 at 10:43:16AM +0200, David Tardon wrote:
> Hi,
>
> Also, we do not know which version of libreoffice this is. The message
> could come from libetonyek, for example. Early versions did not handle
> non-XML input correctly.
>
> D.
This is with LO 4.3.5.2, whichever build you c
On Thu, Apr 09, 2015 at 06:54:11AM -0400, Andrew Pitonyak wrote:
> What happens of you rename the file to have a .txt file extension?
Then it works fine without any output.
Jens
--
Jens Tröger
http://savage.light-speed.de/
___
LibreOffice mailing lis
What happens of you rename the file to have a .txt file extension?
On Apr 9, 2015 3:44 AM, =?ISO-8859-1?Q?Jens_Tr=F6ger?=
wrote:
>
> Hi,
>
> I'm not sure if this is the right place to post this. After running LO
> I loaded a LaTeX file:
>
> http://www.math.duke.edu/computing/tex/templates/
Hi,
On Thu, Apr 09, 2015 at 11:27:16AM +0300, Tor Lillqvist wrote:
> Note that you are running the soffice binary from the command-line, which
> obviously is not at all a normal way to run LibreOffice on OS X. Any
> messages printed to standard output or standard error are easy to
> misinterpret,
> release builds should not print red herrings on stdout/stderr;
But running soffice from the command line on OS X is not the right thing to
do anyway (unless you are a developer debugging something), so debating
what it should or should not do in such a case is a bit pointless. And thus
also pas
On 09.04.2015 10:27, Tor Lillqvist wrote:
> Note that you are running the soffice binary from the command-line,
> which obviously is not at all a normal way to run LibreOffice on OS X.
> Any messages printed to standard output or standard error are easy to
> misinterpret, and unless you plan to inv
> Note that you are running the soffice binary from the command-line,
>
One could even say that by doing so, you by definition are asking for "odd
output"...
--tml
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.o
Note that you are running the soffice binary from the command-line, which
obviously is not at all a normal way to run LibreOffice on OS X. Any
messages printed to standard output or standard error are easy to
misinterpret, and unless you plan to investigate yourself what is going on,
you should ign
On 09.04.2015 09:56, Jens Tröger wrote:
> That it's loading the file as a normal text document. Instead, the
> 'parser' tells me that the document I'm loading is empty
>
> :1: parser error : Document is empty
>
> which it is not, and then it flags a LaTeX command. How am I supposed
> to inter
> The minimum expectation I have on any application that can edit text
But LibreOffice Writer is not really intended to edit "text". It is
intended to edit word processing documents in various formats. That one
can, barely, use it to edit "plain text" is actually a misfeature in my
opinion.
Anywa
On Thu, Apr 09, 2015 at 11:05:05AM +0300, Tor Lillqvist wrote:
> That it's loading the file as a normal text document.
>
>But LibreOffice is not a text editor.
>
> Instead, the 'parser' tells me that the document I'm loading is empty
>
>Most likely some filter misrecognises th
> That it's loading the file as a normal text document.
But LibreOffice is not a text editor.
Instead, the
> 'parser' tells me that the document I'm loading is empty
>
Most likely some filter misrecognises the LaTeX source as its own format,
but then when it actually tries to load it, it (of
That it's loading the file as a normal text document. Instead, the
'parser' tells me that the document I'm loading is empty
:1: parser error : Document is empty
which it is not, and then it flags a LaTeX command. How am I supposed
to interpret this output? If it has no significance, then why
What did you expect to happen?
--tml
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Hi,
I'm not sure if this is the right place to post this. After running LO
I loaded a LaTeX file:
http://www.math.duke.edu/computing/tex/templates/samplefile.tex
which gave me the following terminal output:
savage@pooh ~ > /Applications/LibreOffice64.app/Contents/MacOS/soffice
:1: parse
19 matches
Mail list logo
