Re: M$ Word - LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-05 Thread miyata

"Arnd Hanses" [EMAIL PROTECTED] wrote:

 #ifndef strcasecmp
 #define strcasecmp stricmp  // emx uses M$ fn name instead of posix
 name??!
 #define _strcasecmp stricmp
 #endif

Better to use AC_CHECK_FUNCS(strcasecmp strncasecmp stricmp strnicmp) and

#if !defined(HAVE_STRCASECMP)  defined(HAVE_STRICMP)
#define strcasecmp stricmp
#endif
#if !defined(HAVE_STRNCASECMP)  defined(HAVE_STRNICMP)
#define strncasecmp strnicmp
#endif

, that is, in case you have to use autoconf...

FYI non of strcasecmp, strncasecmp, stricmp nor strnicmp is in ANSI nor
in POSIX.  GNU libc is not always comforming to ANSI/POSIX standard.
In quite a few aspects, EMX is much more comforming to ANSI/POSIX.
However, strcasecmp and strncasecmp are in UNIX95 and UNIX98.

Regards,
SMiyata
^



Re: M$ Word -> LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-05 Thread miyata

"Arnd Hanses" <[EMAIL PROTECTED]> wrote:

> #ifndef strcasecmp
> #define strcasecmp stricmp  // emx uses M$ fn name instead of posix
> name??!
> #define _strcasecmp stricmp
> #endif

Better to use AC_CHECK_FUNCS(strcasecmp strncasecmp stricmp strnicmp) and

#if !defined(HAVE_STRCASECMP) && defined(HAVE_STRICMP)
#define strcasecmp stricmp
#endif
#if !defined(HAVE_STRNCASECMP) && defined(HAVE_STRNICMP)
#define strncasecmp strnicmp
#endif

, that is, in case you have to use autoconf...

FYI non of strcasecmp, strncasecmp, stricmp nor strnicmp is in ANSI nor
in POSIX.  GNU libc is not always comforming to ANSI/POSIX standard.
In quite a few aspects, EMX is much more comforming to ANSI/POSIX.
However, strcasecmp and strncasecmp are in UNIX95 and UNIX98.

Regards,
SMiyata
^



Re: M$ Word - LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-03 Thread Duncan Simpson


RTF is an excellent solution to the word to something else, inclyding LyX, 
problem. Not only does it support practically everything bar macro virii but 
it is also documented and reasonably sensible (quite a contrast with Word 
binary format, which is subject to NDAs and baroque to put it mildly).

One would imagine the purpose of word binary format is to defeat reverse 
engineering, even if it induces masses of bugs in word and trebles the code 
size. Given the only way to fix bugs in word is to upgrade, which costs money, 
conspiracy theorists would say I was right :-) IMHO they might not be entirely 
wrong. Word 98 is avuabale without a NDA but the file format itself is just as 
dire (not worse than word 6, primarly because doing wose is virtually 
impossible).

Unofrtunately 99% of the time people need to do this the only avialable format 
is word binary junk. Hence word2x, catdoc and MSWordview---you do not imagine 
the authors of these beasts actually like word format, do you? I can only 
speak for word2x's author myself, of course.
-- 
Duncan (-:
"software industry, the: unique industry where selling substandard goods is
legal and you can charge extra for fixing the problems."




Re: M$ Word - LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-03 Thread Richard E. Hawkins

duncan delivered,
 
 RTF is an excellent solution to the word to something else, inclyding LyX, 
 problem. Not only does it support practically everything bar macro virii but 
 it is also documented and reasonably sensible (quite a contrast with Word 
 binary format, which is subject to NDAs and baroque to put it mildly).

But isn't Word's implementation of RTF nonstandard and incompatible with real RTF 
(nah, not from them . . .)


-- 




Re: M$ Word - LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-03 Thread Arnd Hanses

On Thu, 02 Sep 1999 18:58:46 +0100, Duncan Simpson wrote:

 Given the only way to fix bugs in word is to upgrade, which costs money, 
conspiracy theorists would say I was right :-) IMHO they might not be entirely 
wrong. Word 98 is avuabale without a NDA but the file format itself is just as 
dire (not worse than word 6, primarly because doing wose is virtually 
impossible).


As it seems, Word 8 is now de facto the international standard for
document exchange, even in the internet and within specialized academic
contexts. LaTeX 'market share' is rapidly decreasing. Even Linux people
seem to adhere more and more (see the new xyzOffice suite efforts for
Linux). So LyX has to change gears and gain speed...

Unfortunately 99% of the time people need to do this the only avialable format 
is word binary junk. Hence word2x, catdoc and MSWordview---you do not imagine 
the authors of these beasts actually like word format, do you? I can only 
speak for word2x's author myself, of course.

Do you plan Word 8 support?

Some time ago I compiled an old version of word2x on emx. Compiling was
relatively easy, only minor quirks. Adding something like this; I think
not all were necessary:

#ifdef __cplusplus
extern "C" {
#endif

#ifdef __EMX__

/* Compare S1 and S2, ignoring case.  */
int stricmp(__const__ char *, __const__ char *);

#ifndef strcasecmp
#define strcasecmp stricmp  // emx uses M$ fn name instead of posix
name??!
#define _strcasecmp stricmp 
#endif 

/* Compare S1 and S2, ignoring case.  */
int memicmp(__const__ void *, __const__ char *, size_t);

#ifndef memcasecmp 
#define memcasecmp memicmp  // emx uses M$ fn name
#endif

#if !defined(__STRICT_ANSI__)  !defined(_POSIX_SOURCE)

/* Compare no more than N chars of S1 and S2, ignoring case. */
int strnicmp(__const__ char *, __const__ char *, size_t);

#ifndef strncasecmp 
#define strncasecmp strnicmp  // emx uses M$ fn name
#define _strncasecmp strnicmp
#endif 

#endif /* !defined(__STRICT_ANSI__) */
#endif // __EMX__

#ifdef __cplusplus
}
#endif

Those funny fn names - despite emx' aim to facilitate Unix ports - is
always a reason for headache. 

BTW: Porting LyX we have the very same nuisance, recompiling the emx
Lib C with new aliases would help, but is non-standard.

Could you add this (as far as it is still necessary) to your code base
(to config.h or so?)?

I would like to release an updated emx version, perhaps a bit
synchronized with a LyX release for OS/2, if this hasn't already been
done (there was an old release from Russia, IIRC a bit idiosyncratic).
Would you agree?

A usability problem: Non ASCII-character handling was a major problem
for me; do you plan to add some support for the different M$-code pages
and LaTeX encodings (as used with Babel)?

Greets,

Arnd



Re: M$ Word - LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-03 Thread Garst R. Reese

Arnd Hanses wrote:
 
 As it seems, Word 8 is now de facto the international standard for
 document exchange, even in the internet and within specialized academic
 contexts. LaTeX 'market share' is rapidly decreasing. Even Linux people
 seem to adhere more and more (see the new xyzOffice suite efforts for
 Linux). So LyX has to change gears and gain speed...
 
Hmm, why are all those folks with Word 8 asking me to publish their
books using LyX/LaTeX?
Yes, I also have to deal those lazy nits in "specialized academic
contexts," but I sure won't encourage them.
Garst



Re: M$ Word - LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-03 Thread Alejandro Aguilar Sierra

On Sat, 4 Sep 1999, Arnd Hanses wrote:

 As it seems, Word 8 is now de facto the international standard for
 document exchange, even in the internet and within specialized academic
 contexts. LaTeX 'market share' is rapidly decreasing. Even Linux people
 seem to adhere more and more (see the new xyzOffice suite efforts for
 Linux). So LyX has to change gears and gain speed...

I don't think that people used to the wysiwym comfort of LyX will be happy
with a boring wysiwyg word processor. The only reason support for import/
export is suitable is precisely to be able to interchange documents with
those unfortunates that doesn't know the joy of LyX.

Greets,

Alejandro



Re: M$ Word -> LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-03 Thread Duncan Simpson


RTF is an excellent solution to the word to something else, inclyding LyX, 
problem. Not only does it support practically everything bar macro virii but 
it is also documented and reasonably sensible (quite a contrast with Word 
binary format, which is subject to NDAs and baroque to put it mildly).

One would imagine the purpose of word binary format is to defeat reverse 
engineering, even if it induces masses of bugs in word and trebles the code 
size. Given the only way to fix bugs in word is to upgrade, which costs money, 
conspiracy theorists would say I was right :-) IMHO they might not be entirely 
wrong. Word 98 is avuabale without a NDA but the file format itself is just as 
dire (not worse than word 6, primarly because doing wose is virtually 
impossible).

Unofrtunately 99% of the time people need to do this the only avialable format 
is word binary junk. Hence word2x, catdoc and MSWordview---you do not imagine 
the authors of these beasts actually like word format, do you? I can only 
speak for word2x's author myself, of course.
-- 
Duncan (-:
"software industry, the: unique industry where selling substandard goods is
legal and you can charge extra for fixing the problems."




Re: M$ Word -> LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-03 Thread Richard E. Hawkins

duncan delivered,
 
> RTF is an excellent solution to the word to something else, inclyding LyX, 
> problem. Not only does it support practically everything bar macro virii but 
> it is also documented and reasonably sensible (quite a contrast with Word 
> binary format, which is subject to NDAs and baroque to put it mildly).

But isn't Word's implementation of RTF nonstandard and incompatible with real RTF 
(nah, not from them . . .)


-- 




Re: M$ Word -> LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-03 Thread Arnd Hanses

On Thu, 02 Sep 1999 18:58:46 +0100, Duncan Simpson wrote:

> Given the only way to fix bugs in word is to upgrade, which costs money, 
>conspiracy theorists would say I was right :-) IMHO they might not be entirely 
>wrong. Word 98 is avuabale without a NDA but the file format itself is just as 
>dire (not worse than word 6, primarly because doing wose is virtually 
>impossible).
>

As it seems, Word 8 is now de facto the international standard for
document exchange, even in the internet and within specialized academic
contexts. LaTeX 'market share' is rapidly decreasing. Even Linux people
seem to adhere more and more (see the new xyzOffice suite efforts for
Linux). So LyX has to change gears and gain speed...

>Unfortunately 99% of the time people need to do this the only avialable format 
>is word binary junk. Hence word2x, catdoc and MSWordview---you do not imagine 
>the authors of these beasts actually like word format, do you? I can only 
>speak for word2x's author myself, of course.

Do you plan Word 8 support?

Some time ago I compiled an old version of word2x on emx. Compiling was
relatively easy, only minor quirks. Adding something like this; I think
not all were necessary:

#ifdef __cplusplus
extern "C" {
#endif

#ifdef __EMX__

/* Compare S1 and S2, ignoring case.  */
int stricmp(__const__ char *, __const__ char *);

#ifndef strcasecmp
#define strcasecmp stricmp  // emx uses M$ fn name instead of posix
name??!
#define _strcasecmp stricmp 
#endif 

/* Compare S1 and S2, ignoring case.  */
int memicmp(__const__ void *, __const__ char *, size_t);

#ifndef memcasecmp 
#define memcasecmp memicmp  // emx uses M$ fn name
#endif

#if !defined(__STRICT_ANSI__) && !defined(_POSIX_SOURCE)

/* Compare no more than N chars of S1 and S2, ignoring case. */
int strnicmp(__const__ char *, __const__ char *, size_t);

#ifndef strncasecmp 
#define strncasecmp strnicmp  // emx uses M$ fn name
#define _strncasecmp strnicmp
#endif 

#endif /* !defined(__STRICT_ANSI__) */
#endif // __EMX__

#ifdef __cplusplus
}
#endif

Those funny fn names - despite emx' aim to facilitate Unix ports - is
always a reason for headache. 

BTW: Porting LyX we have the very same nuisance, recompiling the emx
Lib C with new aliases would help, but is non-standard.

Could you add this (as far as it is still necessary) to your code base
(to config.h or so?)?

I would like to release an updated emx version, perhaps a bit
synchronized with a LyX release for OS/2, if this hasn't already been
done (there was an old release from Russia, IIRC a bit idiosyncratic).
Would you agree?

A usability problem: Non ASCII-character handling was a major problem
for me; do you plan to add some support for the different M$-code pages
and LaTeX encodings (as used with Babel)?

Greets,

Arnd



Re: M$ Word -> LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-03 Thread Garst R. Reese

Arnd Hanses wrote:
> 
> As it seems, Word 8 is now de facto the international standard for
> document exchange, even in the internet and within specialized academic
> contexts. LaTeX 'market share' is rapidly decreasing. Even Linux people
> seem to adhere more and more (see the new xyzOffice suite efforts for
> Linux). So LyX has to change gears and gain speed...
> 
Hmm, why are all those folks with Word 8 asking me to publish their
books using LyX/LaTeX?
Yes, I also have to deal those lazy nits in "specialized academic
contexts," but I sure won't encourage them.
Garst



Re: M$ Word -> LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-03 Thread Alejandro Aguilar Sierra

On Sat, 4 Sep 1999, Arnd Hanses wrote:

> As it seems, Word 8 is now de facto the international standard for
> document exchange, even in the internet and within specialized academic
> contexts. LaTeX 'market share' is rapidly decreasing. Even Linux people
> seem to adhere more and more (see the new xyzOffice suite efforts for
> Linux). So LyX has to change gears and gain speed...

I don't think that people used to the wysiwym comfort of LyX will be happy
with a boring wysiwyg word processor. The only reason support for import/
export is suitable is precisely to be able to interchange documents with
those unfortunates that doesn't know the joy of LyX.

Greets,

Alejandro



M$ Word - LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-02 Thread Alejandro Aguilar Sierra

-- Forwarded message --
Date: Tue, 24 Aug 1999 13:48:30 -0700
From: Levente NOVÁK [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: M$ Word - LyX (was Re: Hi and small scroll wheel patch

Hello Alejandro,

There is a very good RTF to LaTeX converter, namely rtf2latex2e which
can not only convert text from RTF documents to LaTeX but tables also
and is furthermore able to extract figures and equations (these are then
in WMF format, so you have to convert them to EPS yourself). Word can
export in RTF format, and reLyX does the job of converting LaTeX to LyX.
I think it would only need to put a "hook" in LyX like it is the case
for reLyX, but unfortunately I can not do it myself as I do not speak C
nor C++.
When I tried catdoc and word2x some time ago, they did not have the
flexibility and power of rtf2latex2e. It changed maybe since then.

Levente

PS: I wrote you because I am not subscribed to the lyx lists. Could you
forward this mail to lyx-devel please?




M$ Word -> LyX (was Re: Hi and small scroll wheel patch (fwd)

1999-09-02 Thread Alejandro Aguilar Sierra

-- Forwarded message --
Date: Tue, 24 Aug 1999 13:48:30 -0700
From: Levente NOVÁK <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: M$ Word -> LyX (was Re: Hi and small scroll wheel patch

Hello Alejandro,

There is a very good RTF to LaTeX converter, namely rtf2latex2e which
can not only convert text from RTF documents to LaTeX but tables also
and is furthermore able to extract figures and equations (these are then
in WMF format, so you have to convert them to EPS yourself). Word can
export in RTF format, and reLyX does the job of converting LaTeX to LyX.
I think it would only need to put a "hook" in LyX like it is the case
for reLyX, but unfortunately I can not do it myself as I do not speak C
nor C++.
When I tried catdoc and word2x some time ago, they did not have the
flexibility and power of rtf2latex2e. It changed maybe since then.

Levente

PS: I wrote you because I am not subscribed to the lyx lists. Could you
forward this mail to lyx-devel please?