I think explanation to the problem is fact that Mac new line character (EOL)
is CR, Windows is CR+LF, and Unix is LF. For compatibility most Unix based
applications ported to Windows handles only LF from these two, so on Windows
options were seen as in separate lines, while on Mac until
On Wednesday 20 August 2008 07:45:18 Manveru wrote:
I think explanation to the problem is fact that Mac new line character
(EOL) is CR, Windows is CR+LF, and Unix is LF. For compatibility most Unix
based applications ported to Windows handles only LF from these two, so on
Windows options were
On 19.08.2008, at 21:21, Graham Smith wrote:
On 19 Aug 2008, at 19:57, Christian Ridderström wrote:
On Tue, 19 Aug 2008, Graham Smith wrote:
As you will see, from my other post, the issue was a leading comma
in the preamble, setting the Komascript options.
It seems that both the Mac and
So it isn't a Windows issue
Hi Graham,
I'm glad you solved the problem.
I want to add a word of encouragement here: In out group we have
been co-writing papers and documents using LyX on Windows/Linux/OSX
for years:
- There never, ever has been a problem with LyX itself.
- Only
I think explanation to the problem is fact that Mac new line character (EOL)
is CR, Windows is CR+LF, and Unix is LF. For compatibility most Unix based
applications ported to Windows handles only LF from these two, so on Windows
options were seen as in separate lines, while on Mac until
On Wednesday 20 August 2008 07:45:18 Manveru wrote:
I think explanation to the problem is fact that Mac new line character
(EOL) is CR, Windows is CR+LF, and Unix is LF. For compatibility most Unix
based applications ported to Windows handles only LF from these two, so on
Windows options were
On 19.08.2008, at 21:21, Graham Smith wrote:
On 19 Aug 2008, at 19:57, Christian Ridderström wrote:
On Tue, 19 Aug 2008, Graham Smith wrote:
As you will see, from my other post, the issue was a leading comma
in the preamble, setting the Komascript options.
It seems that both the Mac and
So it isn't a Windows issue
Hi Graham,
I'm glad you solved the problem.
I want to add a word of encouragement here: In out group we have
been co-writing papers and documents using LyX on Windows/Linux/OSX
for years:
- There never, ever has been a problem with LyX itself.
- Only
I think explanation to the problem is fact that Mac new line character (EOL)
is CR, Windows is CR+LF, and Unix is LF. For compatibility most Unix based
applications ported to Windows handles only LF from these two, so on Windows
options were seen as in separate lines, while on Mac until
On Wednesday 20 August 2008 07:45:18 Manveru wrote:
> I think explanation to the problem is fact that Mac new line character
> (EOL) is CR, Windows is CR+LF, and Unix is LF. For compatibility most Unix
> based applications ported to Windows handles only LF from these two, so on
> Windows options
On 19.08.2008, at 21:21, Graham Smith wrote:
On 19 Aug 2008, at 19:57, Christian Ridderström wrote:
On Tue, 19 Aug 2008, Graham Smith wrote:
As you will see, from my other post, the issue was a leading comma
in the preamble, setting the Komascript options.
It seems that both the Mac and
So it isn't a Windows issue
Hi Graham,
I'm glad you solved the problem.
I want to add a word of encouragement here: In out group we have
been co-writing papers and documents using LyX on Windows/Linux/OSX
for years:
- There never, ever has been a problem with LyX itself.
- Only
On Tue, 19 Aug 2008, Graham Smith wrote:
I have asked in another question (sa far without a solution) about
problems with getting a Lyx file created on a Mac to compile on Windows
(it compiles fine on Linux).
As I intend sharing files with a Windows user, is this a common problem,
and is
On Tuesday 19 August 2008 06:35:32 Graham Smith wrote:
I have asked in another question (sa far without a solution) about
problems with getting a Lyx file created on a Mac to compile on
Windows (it compiles fine on Linux).
As I intend sharing files with a Windows user, is this a common
On 19 Aug 2008, at 09:16, José Matos wrote:
On Tuesday 19 August 2008 06:35:32 Graham Smith wrote:
I have asked in another question (sa far without a solution) about
problems with getting a Lyx file created on a Mac to compile on
Windows (it compiles fine on Linux).
As I intend sharing files
On Tue, Aug 19, 2008 at 5:31 PM, Graham Smith [EMAIL PROTECTED] wrote:
On 19 Aug 2008, at 09:16, José Matos wrote:
The error message suggests that the culprit is a different version
installed of Koma between your different systems.
snip
Thanks, this could well be the case,
snip
I think
On 19 Aug 2008, at 10:59, John McCabe-Dansted wrote:
On Tue, Aug 19, 2008 at 5:31 PM, Graham Smith
[EMAIL PROTECTED] wrote:
On 19 Aug 2008, at 09:16, José Matos wrote:
The error message suggests that the culprit is a different version
installed of Koma between your different systems.
Christian,
As you will see, from my other post, the issue was a leading comma
in the preamble, setting the Komascript options.
It seems that both the Mac and Linux are forgiving of this syntax
error, but Windows is not.
So it isn't a Windows issue, but a sloppy syntax issue on my part.
On Tue, 19 Aug 2008, Graham Smith wrote:
As you will see, from my other post, the issue was a leading comma in
the preamble, setting the Komascript options.
It seems that both the Mac and Linux are forgiving of this syntax error,
but Windows is not.
So it isn't a Windows issue
Hi Graham,
On 19 Aug 2008, at 19:57, Christian Ridderström wrote:
On Tue, 19 Aug 2008, Graham Smith wrote:
As you will see, from my other post, the issue was a leading comma
in the preamble, setting the Komascript options.
It seems that both the Mac and Linux are forgiving of this syntax
error, but
On Tue, 19 Aug 2008, Graham Smith wrote:
I have asked in another question (sa far without a solution) about
problems with getting a Lyx file created on a Mac to compile on Windows
(it compiles fine on Linux).
As I intend sharing files with a Windows user, is this a common problem,
and is
On Tuesday 19 August 2008 06:35:32 Graham Smith wrote:
I have asked in another question (sa far without a solution) about
problems with getting a Lyx file created on a Mac to compile on
Windows (it compiles fine on Linux).
As I intend sharing files with a Windows user, is this a common
On 19 Aug 2008, at 09:16, José Matos wrote:
On Tuesday 19 August 2008 06:35:32 Graham Smith wrote:
I have asked in another question (sa far without a solution) about
problems with getting a Lyx file created on a Mac to compile on
Windows (it compiles fine on Linux).
As I intend sharing files
On Tue, Aug 19, 2008 at 5:31 PM, Graham Smith [EMAIL PROTECTED] wrote:
On 19 Aug 2008, at 09:16, José Matos wrote:
The error message suggests that the culprit is a different version
installed of Koma between your different systems.
snip
Thanks, this could well be the case,
snip
I think
On 19 Aug 2008, at 10:59, John McCabe-Dansted wrote:
On Tue, Aug 19, 2008 at 5:31 PM, Graham Smith
[EMAIL PROTECTED] wrote:
On 19 Aug 2008, at 09:16, José Matos wrote:
The error message suggests that the culprit is a different version
installed of Koma between your different systems.
Christian,
As you will see, from my other post, the issue was a leading comma
in the preamble, setting the Komascript options.
It seems that both the Mac and Linux are forgiving of this syntax
error, but Windows is not.
So it isn't a Windows issue, but a sloppy syntax issue on my part.
On Tue, 19 Aug 2008, Graham Smith wrote:
As you will see, from my other post, the issue was a leading comma in
the preamble, setting the Komascript options.
It seems that both the Mac and Linux are forgiving of this syntax error,
but Windows is not.
So it isn't a Windows issue
Hi Graham,
On 19 Aug 2008, at 19:57, Christian Ridderström wrote:
On Tue, 19 Aug 2008, Graham Smith wrote:
As you will see, from my other post, the issue was a leading comma
in the preamble, setting the Komascript options.
It seems that both the Mac and Linux are forgiving of this syntax
error, but
On Tue, 19 Aug 2008, Graham Smith wrote:
I have asked in another question (sa far without a solution) about
problems with getting a Lyx file created on a Mac to compile on Windows
(it compiles fine on Linux).
As I intend sharing files with a Windows user, is this a common problem,
and is
On Tuesday 19 August 2008 06:35:32 Graham Smith wrote:
> I have asked in another question (sa far without a solution) about
> problems with getting a Lyx file created on a Mac to compile on
> Windows (it compiles fine on Linux).
>
> As I intend sharing files with a Windows user, is this a common
>
On 19 Aug 2008, at 09:16, José Matos wrote:
On Tuesday 19 August 2008 06:35:32 Graham Smith wrote:
I have asked in another question (sa far without a solution) about
problems with getting a Lyx file created on a Mac to compile on
Windows (it compiles fine on Linux).
As I intend sharing files
On Tue, Aug 19, 2008 at 5:31 PM, Graham Smith <[EMAIL PROTECTED]> wrote:
> On 19 Aug 2008, at 09:16, José Matos wrote:
>> The error message suggests that the culprit is a different version
>> installed of Koma between your different systems.
> Thanks, this could well be the case,
I think
On 19 Aug 2008, at 10:59, John McCabe-Dansted wrote:
On Tue, Aug 19, 2008 at 5:31 PM, Graham Smith
<[EMAIL PROTECTED]> wrote:
On 19 Aug 2008, at 09:16, José Matos wrote:
The error message suggests that the culprit is a different version
installed of Koma between your different systems.
Christian,
As you will see, from my other post, the issue was a leading comma
in the preamble, setting the Komascript options.
It seems that both the Mac and Linux are forgiving of this syntax
error, but Windows is not.
So it isn't a Windows issue, but a sloppy syntax issue on my part.
On Tue, 19 Aug 2008, Graham Smith wrote:
As you will see, from my other post, the issue was a leading comma in
the preamble, setting the Komascript options.
It seems that both the Mac and Linux are forgiving of this syntax error,
but Windows is not.
So it isn't a Windows issue
Hi Graham,
On 19 Aug 2008, at 19:57, Christian Ridderström wrote:
On Tue, 19 Aug 2008, Graham Smith wrote:
As you will see, from my other post, the issue was a leading comma
in the preamble, setting the Komascript options.
It seems that both the Mac and Linux are forgiving of this syntax
error, but
I have asked in another question (sa far without a solution) about
problems with getting a Lyx file created on a Mac to compile on
Windows (it compiles fine on Linux).
As I intend sharing files with a Windows user, is this a common
problem, and is there any routine methods of avoiding it.
I have asked in another question (sa far without a solution) about
problems with getting a Lyx file created on a Mac to compile on
Windows (it compiles fine on Linux).
As I intend sharing files with a Windows user, is this a common
problem, and is there any routine methods of avoiding it.
I have asked in another question (sa far without a solution) about
problems with getting a Lyx file created on a Mac to compile on
Windows (it compiles fine on Linux).
As I intend sharing files with a Windows user, is this a common
problem, and is there any routine methods of avoiding it.
39 matches
Mail list logo
