On Thu, Jul 26, 2001 at 08:26:21PM +0300, Dekel Tsur wrote:
On Wed, Jul 25, 2001 at 10:34:05PM +0100, Jose Abilio Oliveira Matos wrote:
On Wed, Jul 25, 2001 at 03:03:40PM +0200, Jean-Marc Lasgouttes wrote:
3. The \L and \R commands for Hebrew files.
- \L{text} is a shortcut to
Yes, I'm still alive.
Jose, it's great to see that you made progress on the reLyX stuff. I took a
brief look at it and it looked fine, although I might have done a couple
things differently. Unfortunately, I don't have much free time, or I could
try to help with the uninstalled reLyX problem
On Wed, Jul 25, 2001 at 10:34:05PM +0100, Jose Abilio Oliveira Matos wrote:
> On Wed, Jul 25, 2001 at 03:03:40PM +0200, Jean-Marc Lasgouttes wrote:
> >
> > You have to know the current language at this point of the document.
>
> Now I know the language of the document
> How many ways
On Thu, Jul 26, 2001 at 08:26:21PM +0300, Dekel Tsur wrote:
> On Wed, Jul 25, 2001 at 10:34:05PM +0100, Jose Abilio Oliveira Matos wrote:
> > On Wed, Jul 25, 2001 at 03:03:40PM +0200, Jean-Marc Lasgouttes wrote:
> > >
>
> 3. The \L and \R commands for Hebrew files.
> - \L{text} is a shortcut
Yes, I'm still alive.
Jose, it's great to see that you made progress on the reLyX stuff. I took a
brief look at it and it looked fine, although I might have done a couple
things differently. Unfortunately, I don't have much free time, or I could
try to help with the uninstalled reLyX problem
.
:-)
Jose On a more serious note, this is good news since it will close
Jose one section of bugs in the reLyX man page, and simplify the
Jose import of latex documents.
Remember to suppress the corresponding bugs from the man page.
That's the easy part. :-)
Jose I have used the UserGuide
gt;
> As I have already said to José, this is major good news.
:-)
> Jose> On a more serious note, this is good news since it will close
> Jose> one section of bugs in the reLyX man page, and simplify the
> Jose> import of latex documents.
>
> Remember to suppress
On Wed, Apr 04, 2001 at 12:31:29PM +0200, j.heidemeier wrote:
I'd like to ask for a short status concerning the
the possible import of MS created texts into lyx.
So I'm curious if reLyX now handles longtables or if there are other
promising routes from MS-apps to lyx.
reLyX hasn't changed
list [EMAIL PROTECTED]
Date: Wed, 4 Apr 2001 17:03:26 -0400
From: Amir Karger [EMAIL PROTECTED]
To: "J. Heidemeier" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: reLyX and import of MS-Word resp. RFT documents
Mail-Followup-To: Amir Karger [EMAIL PROTECTED],
"J. Hei
On Wed, Apr 04, 2001 at 12:31:29PM +0200, j.heidemeier wrote:
> I'd like to ask for a short status concerning the
> the possible import of MS created texts into lyx.
> So I'm curious if reLyX now handles longtables or if there are other
> promising routes from MS-apps to lyx.
to:[EMAIL PROTECTED]>
> Delivered-To: mailing list [EMAIL PROTECTED]
> Date: Wed, 4 Apr 2001 17:03:26 -0400
> From: Amir Karger <[EMAIL PROTECTED]>
> To: "J. Heidemeier" <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: reLyX and import of M
it.
When relyx tries the conversion, I see this in the console:
$ lyx
Converting from latex to lyx
[...]
Math parse error: unexpected '_'
lyx: SIGSEGV signal caught
I have fixed the math parser code, so LyX will longer crash when trying to
read such a corrupt file.
We still need to fix
ex to export it.
>
> When relyx tries the conversion, I see this in the console:
>
> $ lyx
> Converting from latex to lyx
[...]
> Math parse error: unexpected '_'
> lyx: SIGSEGV signal caught
I have fixed the math parser code, so LyX will longer crash when trying to
read s
it.
I do believe you've found a bug in reLyX!
It's pretty bizzarre. It turns out that reLyX thinks \)* is a starred
version of the \) command, rather than realizing that it's supposed to be \)
followed by an asterisk in plain text. (In case you're wondering, the $'s in
the .tex file get turned
ex to export it.
I do believe you've found a bug in reLyX!
It's pretty bizzarre. It turns out that reLyX thinks \)* is a starred
version of the \) command, rather than realizing that it's supposed to be \)
followed by an asterisk in plain text. (In case you're wondering, the $'s in
the .tex fil
attachments, so
I put the tex file here for you to see:
http://lark.cc.ukans.edu/~pauljohn/software/apsa9704.tex
I can edit that file in Emacs and generate the dvi, which looks OK.
When relyx tries the conversion, I see this in the console:
$ lyx
Converting from latex to lyx
Calling reLyX -f 'mid97005
attachments, so
I put the tex file here for you to see:
http://lark.cc.ukans.edu/~pauljohn/software/apsa9704.tex
I can edit that file in Emacs and generate the dvi, which looks OK.
When relyx tries the conversion, I see this in the console:
$ lyx
Converting from latex to lyx
Calling reLyX -f 'mid97005
On Wed, Nov 01, 2000 at 03:35:07PM +0100, Yves Bastide wrote:
reLyX cannot handle document class names with non `word' characters
(not in [A-Za-z_]), such as article-hermes. This patch therefore replaces
\w by \S (non blank) in the regular expression.
Good point.
Note
"Amir" == Amir Karger [EMAIL PROTECTED] writes:
Amir Sure, I suppose. New patch below. Jean-Marc, could you apply?
Done.
JMarc
On Wed, Nov 01, 2000 at 03:35:07PM +0100, Yves Bastide wrote:
>
> reLyX cannot handle document class names with non `word' characters
> (not in [A-Za-z_]), such as article-hermes. This patch therefore replaces
> \w by \S (non blank) in the regular expression.
Good po
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:
Amir> Sure, I suppose. New patch below. Jean-Marc, could you apply?
Done.
JMarc
My last patch for today (-:
reLyX cannot handle document class names with non `word' characters
(not in [A-Za-z_]), such as article-hermes. This patch therefore replaces
\w by \S (non blank) in the regular expression.
Note this is not foolproof, either: perhaps better would be \s*(\S+)\s
My last patch for today (-:
reLyX cannot handle document class names with non `word' characters
(not in [A-Za-z_]), such as article-hermes. This patch therefore replaces
\w by \S (non blank) in the regular expression.
Note this is not foolproof, either: perhaps better would be \s*(\S+)\s
le.
Bund"=Länder"=Gruppe
should become
Bund-Länder-Gruppe
reLyX just uses "=
Could reLyx not recognize that this is a German text? I can't read perl, so I
am lost about implementation details.
WISHLIST:
Also not translated is \frqq{} and \flqq{} which form the (traditio
le.
Bund"=Länder"=Gruppe
should become
Bund-Länder-Gruppe
reLyX just uses "=
Could reLyx not recognize that this is a German text? I can't read perl, so I
am lost about implementation details.
WISHLIST:
Also not translated is \frqq{} and \flqq{} which form the (traditiona
On Sat, Oct 07, 2000 at 11:27:05PM +0200, Charles de Miramon wrote:
Hello,
While trying to understand who to translate unicode characters in Lyx, I've
found these LateX codes that are not correctly translated by RelyX :
1) Latex code \i (dotless i ) is translated in \i when it should
On Sat, Oct 07, 2000 at 11:27:05PM +0200, Charles de Miramon wrote:
> Hello,
>
> While trying to understand who to translate unicode characters in Lyx, I've
> found these LateX codes that are not correctly translated by RelyX :
>
> 1) Latex code \i (dotless i ) is tra
Hello,
While trying to understand who to translate unicode characters in Lyx, I've
found these LateX codes that are not correctly translated by RelyX :
1) Latex code \i (dotless i ) is translated in \i when it should be \i \i
--
Charles de Miramon
Centre de Recherches Historiques
Hello,
While trying to understand who to translate unicode characters in Lyx, I've
found these LateX codes that are not correctly translated by RelyX :
1) Latex code \i (dotless i ) is translated in \i when it should be \i \i
--
Charles de Miramon
Centre de Recherches Historiques
On Fri, Aug 11, 2000 at 02:29:05PM +0200, Jos van den Oever wrote:
Hi,
When I import a latex file with floating figures, the figure is place outside of the
float. Below I give the latex input file, then the resulting lyx file and then what
the lyx file should be.
Hey Kayvan! I took a look
On Fri, Aug 11, 2000 at 02:29:05PM +0200, Jos van den Oever wrote:
> Hi,
>
> When I import a latex file with floating figures, the figure is place outside of the
>float. Below I give the latex input file, then the resulting lyx file and then what
>the lyx file should be.
Hey Kayvan! I took a
Hi,
When I import a latex file with floating figures, the figure is place outside of the
float. Below I give the latex input file, then the resulting lyx file and then what
the lyx file should be.
test2.tex
#LyX 1.1 created this file. For more info see http://www.lyx.org/
\lyxformat 2.16
Hi,
When I import a latex file with floating figures, the figure is place outside of the
float. Below I give the latex input file, then the resulting lyx file and then what
the lyx file should be.
test2.tex
#LyX 1.1 created this file. For more info see http://www.lyx.org/
\lyxformat 2.16
On Mon, Jul 24, 2000 at 10:30:12AM +0900, R. Lahaye wrote:
Amir Karger wrote:
On Sat, Jul 22, 2000 at 02:45:29AM +0900, R. Lahaye wrote:
/my/dir/my_file.tex: import failed. (buffer-import latex: [M-fil])
Is this a bug?
Maybe.
How can I more directly find out where reLyX
a bug?
> >
> > Maybe.
>
> How can I more directly find out where reLyX is struggling when the
> import fails?
I guess the problem with Asger's writing Import->LaTeX functionality into
LyX is that people no longer realize that reLyX is its own program.
Run 're
])
Is this a bug?
Maybe.
Is this a known bug? If not, I'll try to find out
what is actually going wrong.
(It's a straight forward article, that uses tables,
math-matrices and a bibtex file).
Please do try to figure out what's going on. In theory, relyx should be able
to import most things that LyX
-import latex: [M-fil])
Is this a bug?
Maybe.
Please do try to figure out what's going on. In theory, relyx should be able
to import most things that LyX outputs. There will be exceptions, but we
should find out if your case is an exception we know about.
How can I debug a "import failed&q
port latex: [M-fil])
>
> Is this a bug?
Maybe.
> Is this a known bug? If not, I'll try to find out
> what is actually going wrong.
>
> (It's a straight forward article, that uses tables,
> math-matrices and a bibtex file).
Please do try to figure out what's going on. In theo
t; > /my/dir/my_file.tex: import failed. (buffer-import latex: [M-fil])
> >
> > Is this a bug?
>
> Maybe.
> Please do try to figure out what's going on. In theory, relyx should be able
> to import most things that LyX outputs. There will be exceptions, but we
> should
Hi,
[1.1.6cvs]
I would like to check this list first before
digging deeper:
I've exported my paper as LaTeX and then tried to
import this LaTeX output into LyX; just for fun.
(I've renamed the LaTeX file, to avoid name overlaps!).
It didn't work to my surprise and I get in the bottom
status
Hi,
[1.1.6cvs]
I would like to check this list first before
digging deeper:
I've exported my paper as LaTeX and then tried to
import this LaTeX output into LyX; just for fun.
(I've renamed the LaTeX file, to avoid name overlaps!).
It didn't work to my surprise and I get in the bottom
status
- extra environments text input (-r)
Maybe this could even choose a layout and the extra environments could
be read from the corresponding .layout file?
Anyway, it would be nice if an unknown environment would be translated
to \begin{env} and \end{env} in LaTeX and the content would be
> - extra environments text input (-r)
Maybe this could even choose a layout and the extra environments could
be read from the corresponding .layout file?
Anyway, it would be nice if an unknown environment would be translated
to \begin{env} and \end{env} in LaTeX and the content would be
Speaking of menu-fixing, I'm remembering that several people suggested a
"Paste as LaTeX" command -- probably a couple of years ago by now. The thing
is, we have the technology. All you have to do is:
(1) copy the text you're pasting into /tmp/foo.tex
(2) reLyX -p -c Class /t
Speaking of menu-fixing, I'm remembering that several people suggested a
"Paste as LaTeX" command -- probably a couple of years ago by now. The thing
is, we have the technology. All you have to do is:
(1) copy the text you're pasting into /tmp/foo.tex
(2) reLyX -p -c Class /t
epair what?
For 1.1.5: remove lib/reLyX/reLyX, re-run configure, and then install
should work (remember to remove the file before re-running configure).
This will be fixed in 1.1.5fix1.
For 1.1.4: this problem has been fixed in 1.1.4fix1.
JMarc
chment Where should I look to
Danie> repair what?
For 1.1.5: remove lib/reLyX/reLyX, re-run configure, and then install
should work (remember to remove the file before re-running configure).
This will be fixed in 1.1.5fix1.
For 1.1.4: this problem has been fixed in 1.1.4fix1.
JMarc
I am using RedHet6.0 linux on a pentium with xforms 089
Also 114 has a problem - see attachment
Where should I look to repair what?
TIA
--
Danie Wessels (D.A.); Radiation and Reactor Theory (RRT)
Nuclear Energy Corporation of South Africa (NECSA)
Email: dwessels @aec.co.za; Cell: 082 432
I am using RedHet6.0 linux on a pentium with xforms 089
Also 114 has a problem - see attachment
Where should I look to repair what?
TIA
--
Danie Wessels (D.A.); Radiation and Reactor Theory (RRT)
Nuclear Energy Corporation of South Africa (NECSA)
Email: dwessels @aec.co.za; Cell: 082 432
"nbecker" == nbecker [EMAIL PROTECTED] writes:
nbecker ./../../config/mkinstalldirs .//reLyX/bin
OK, some questions:
- did you run configure several times before getting this error?
- do you have "." explicitely in your path?
- does the problem vanish if you de
"Jean-Marc" == Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
"nbecker" == nbecker [EMAIL PROTECTED] writes:
nbecker ./../../config/mkinstalldirs .//reLyX/bin
Jean-Marc OK, some questions:
Jean-Marc - did you run configure several times before getting
>>>>> "nbecker" == nbecker <[EMAIL PROTECTED]> writes:
nbecker> ./../../config/mkinstalldirs .//reLyX/bin
OK, some questions:
- did you run configure several times before getting this error?
- do you have "." explicitely in your path?
- does the
>>>>> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>>>>> "nbecker" == nbecker <[EMAIL PROTECTED]> writes:
nbecker> ./../../config/mkinstalldirs .//reLyX/bin
Jean-Marc> OK, some questions:
On Mon, Jun 05, 2000 at 11:52:38PM +0200, Tomasz Motylewski wrote:
On Mon, 5 Jun 2000, Amir Karger wrote:
$newfile = "$basename.lyx";
} else { # keep relative path, e.g. Just change suffix
- ($newfile = $fil) =~ s/$suffix/.lyx/;
+
"Kayvan" == Kayvan A Sylvan [EMAIL PROTECTED] writes:
Kayvan Tomasz's version looks right to me and I don't think it breaks
Kayvan anything.
So shall I commit it?
JMarc
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| "Kayvan" == Kayvan A Sylvan [EMAIL PROTECTED] writes:
|
| Kayvan Tomasz's version looks right to me and I don't think it breaks
| Kayvan anything.
|
| So shall I commit it?
Be quick if you are going to..
Lgb
`/usr/local/src/lyx-1.1.5/src'
make[2]: Leaving directory `/usr/local/src/lyx-1.1.5/src'
make[1]: Leaving directory `/usr/local/src/lyx-1.1.5/src'
Making install in lib
make[1]: Entering directory `/usr/local/src/lyx-1.1.5/lib'
Making install in reLyX
make[2]: Entering directory `/usr/local/src/lyx
On Mon, Jun 05, 2000 at 11:52:38PM +0200, Tomasz Motylewski wrote:
> On Mon, 5 Jun 2000, Amir Karger wrote:
>
> > $newfile = "$basename.lyx";
> > } else { # keep relative path, e.g. Just change suffix
> > - ($newfile = $fil) =~ s/$suffix/.lyx/;
> > +
> "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes:
Kayvan> Tomasz's version looks right to me and I don't think it breaks
Kayvan> anything.
So shall I commit it?
JMarc
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes:
|
| Kayvan> Tomasz's version looks right to me and I don't think it breaks
| Kayvan> anything.
|
| So shall I commit it?
Be quick if you are going to..
Lgb
`/usr/local/src/lyx-1.1.5/src'
make[2]: Leaving directory `/usr/local/src/lyx-1.1.5/src'
make[1]: Leaving directory `/usr/local/src/lyx-1.1.5/src'
Making install in lib
make[1]: Entering directory `/usr/local/src/lyx-1.1.5/lib'
Making install in reLyX
make[2]: Entering directory `/usr/local/src/lyx
OK. I haven't touched reLyX in months, and I haven't been latexing either.
And I don't have the energy to look through the reLyX source. So I'm not
entirely sure whether there this is the right thing to do. However, I've
fixed what might be a bug.
--- ../CVS/lyx-devel/lib/reLyX/LastLyX.pm
file d3.tex.tex.") and still gets
translated to "\begin_inset Include \include{d3.tex}"
I have checked that value of $suffix at that place is "".
BTW. Both \input{d2} and \input{d2.tex} are recognized by Latex.
Here goes my version of patch:
diff -Nur reLyX/LastLyX.pm /tmp/reLy
OK. I haven't touched reLyX in months, and I haven't been latexing either.
And I don't have the energy to look through the reLyX source. So I'm not
entirely sure whether there this is the right thing to do. However, I've
fixed what might be a bug.
--- ../CVS/lyx-devel/lib/reLyX/LastLyX.pm
X: "No file d3.tex.tex.") and still gets
translated to "\begin_inset Include \include{d3.tex}"
I have checked that value of $suffix at that place is "".
BTW. Both \input{d2} and \input{d2.tex} are recognized by Latex.
Here goes my version of patch:
diff -Nur reLyX/L
e makefile does not use libinstalldirs or
Angus install-data-local).
I did not remove those targets because I don't know what they do and
feared they might be called by the lib/ makefile, for example.
Angus I submitted this patch because LyX wasn't installing reLyX
Angus correctly. Its rejecti
My bad.
I made the changes to get reLyX to install because it used not to.
I started again with the Makefile.am in CVS and everything works perfectly.
Sorry for wasting bandwidth :(
All I can say in my defence is that install-data-local, libinstalldirs used not
to called. Now
h should still be
Angus> applied because the makefile does not use libinstalldirs or
Angus> install-data-local).
I did not remove those targets because I don't know what they do and
feared they might be called by the lib/ makefile, for example.
Angus> I submitted this patch because
My bad.
I made the changes to get reLyX to install because it used not to.
I started again with the Makefile.am in CVS and everything works perfectly.
Sorry for wasting bandwidth :(
All I can say in my defence is that install-data-local, libinstalldirs used not
to called. Now
Hello,
reLyx can not handle the following simple LaTeX document:
- ---
\documentclass{article}
\title{Bug report about reLyx crashing on item}
\author{Alain Le Guennec}
\date{April 28, 2000}
\begin{document}
The following list
\item [{[1]}] Apparently, reLyx does not like this item.
This is a known problem. From the reLyX BUGS file:
- In optional arguments, reLyX doesn't recognize a braced bracket
"{]}" as being different from a regular bracket. You'll notice this
problem if you've got a d
"Kayvan A. Sylvan" [EMAIL PROTECTED] writes:
\item [{[1]}] Apparently, reLyx does not like this item.
This is a known problem. From the reLyX BUGS file:
- In optional arguments, reLyX doesn't recognize a braced bracket
"{]}" as being different from a reg
On Fri, Apr 28, 2000 at 07:18:11PM +0200, Alain Le Guennec wrote:
"Kayvan A. Sylvan" [EMAIL PROTECTED] writes:
\item [{[1]}] Apparently, reLyx does not like this item.
This is a known problem. From the reLyX BUGS file:
- In optional arguments, reLyX doesn't recogniz
Hello,
reLyx can not handle the following simple LaTeX document:
- ---
\documentclass{article}
\title{Bug report about reLyx crashing on item}
\author{Alain Le Guennec}
\date{April 28, 2000}
\begin{document}
The following list
> \item [{[1]}] Apparently, reLyx does not like this item.
This is a known problem. From the reLyX BUGS file:
- In optional arguments, reLyX doesn't recognize a braced bracket
"{]}" as being different from a regular bracket. You'll notice this
problem if you've got
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
> > \item [{[1]}] Apparently, reLyx does not like this item.
>
> This is a known problem. From the reLyX BUGS file:
>
> - In optional arguments, reLyX doesn't recognize a braced bracket
> "{]}&
On Fri, Apr 28, 2000 at 07:18:11PM +0200, Alain Le Guennec wrote:
> "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
>
> > > \item [{[1]}] Apparently, reLyx does not like this item.
> >
> > This is a known problem. From the reLyX BUGS file:
> >
f\layout#1{\string\layout #1^^J^^J}
should work, although I did not test it]
* currently, the name-layout conversion is hardcoded, and this is no
good. What you should do (like reLyX does) is to parse the textclass
file and discover which layout goes with which command/environment
(Itemiz
ne feed with ^^J
[for example, something like
\def\layout#1{\string\layout #1^^J^^J}
should work, although I did not test it]
* currently, the name<->layout conversion is hardcoded, and this is no
good. What you should do (like reLyX does) is to parse the textclass
file and discover which l
"Amir" == Amir Karger [EMAIL PROTECTED] writes:
Andre Put \def\lyxprotect{\protect} in the preamble and use
Andre '\lyxprotect' for the 'helpers'. reLyX could then ignore
Andre \lyxprotect and copy \protect...
Amir This should be able to work. The problem is that you have to
A
>>>>> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:
Andre> Put \def\lyxprotect{\protect} in the preamble and use
Andre> '\lyxprotect' for the 'helpers'. reLyX could then ignore
Andre> \lyxprotect and copy \protect...
Amir> This should be able to
I think that more important than where the information goes, for the moment,
is who will collect it. I'm no expert in TeX, LyX or reLyX, but I am willing
to compile suggestions into a document and make it available in whatever
form. However, I personally know very little about these tricks, so
"Amir" == Amir Karger [EMAIL PROTECTED] writes:
Amir No kidding! (BTW, I think there are a couple very minor fixes
Amir sitting around that I never checked in.) I wouldn't hold my
Amir breath, Jean-Marc. I've been asking for help on reLyX for about
Amir two years now, but - while I
Yes, that's really a problem, I know about it. However, it is not bad
from time to time to ask again :) It seems that Kayvan somehow
volunteered to work a bit on reLyX. Even if it is a tiny bit, this
will certainly be welcome.
Yes. I did volunteer to take over reLyX for Amir. An hour
On Wed, Mar 01, 2000 at 11:59:12AM +0100, Jean-Marc Lasgouttes wrote:
"Andre" == Andre Poenitz [EMAIL PROTECTED] writes:
Or decide that \protect should disappear in constructs like \protect\[
and \protect\], since LyX should add them back. Can reLyX do it, or is
it out of reach
On Wed, Mar 01, 2000 at 11:59:12AM +0100, Jean-Marc Lasgouttes wrote:
"Andre" == Andre Poenitz [EMAIL PROTECTED] writes:
I don't know. How can reLyX tell that it's a \protect that LyX put
in, and not one that the coder put in?
Andre Urmh... would the following work?
Andr
I think that more important than where the information goes, for the moment,
is who will collect it. I'm no expert in TeX, LyX or reLyX, but I am willing
to compile suggestions into a document and make it available in whatever
form. However, I personally know very little about these tricks, so
>>>>> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes:
Amir> No kidding! (BTW, I think there are a couple very minor fixes
Amir> sitting around that I never checked in.) I wouldn't hold my
Amir> breath, Jean-Marc. I've been asking for help on reLyX fo
>
> Yes, that's really a problem, I know about it. However, it is not bad
> from time to time to ask again :) It seems that Kayvan somehow
> volunteered to work a bit on reLyX. Even if it is a tiny bit, this
> will certainly be welcome.
>
Yes. I did volunteer to take o
On Wed, Mar 01, 2000 at 11:59:12AM +0100, Jean-Marc Lasgouttes wrote:
> >>>>> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> Or decide that \protect should disappear in constructs like \protect\[
> and \protect\], since LyX should add them bac
On Wed, Mar 01, 2000 at 11:59:12AM +0100, Jean-Marc Lasgouttes wrote:
> >>>>> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> >> I don't know. How can reLyX tell that it's a \protect that LyX put
> >> in, and not one that the cod
On Tue, Feb 29, 2000 at 04:39:08PM +0100, Michael Creel wrote:
Rather than modify reLyX, maybe the best solution would to create a
document that explains this sort thing so that people would know how to
modify their TeX documents before applying reLyX. I only found my
solution
"Amir" == Amir Karger [EMAIL PROTECTED] writes:
Amir On Tue, Feb 29, 2000 at 04:39:08PM +0100, Michael Creel wrote:
Rather than modify reLyX, maybe the best solution would to create
a document that explains this sort thing so that people would know
how to modify their TeX docume
reLyX man page, the current reLyX BUGS page, or the reLyX section of the
User's Guide (which is currently very small). The last seems like the place
most likely to be read by people who have a problem. The bad news, as I
I think, the man page is a better place. That's the place where I'd
as talking about
rewriting the docs for importing - I suppose the reLyX stuff could go
wherever that does.
But of course, you do not
have time for that (no, do not insist, you do not).
You folks are being so supportive! Although it seems like I spend all my
time these days writing emails a
On Tue, Feb 29, 2000 at 05:16:26PM +0100, Jean-Marc Lasgouttes wrote:
"Amir" == Amir Karger [EMAIL PROTECTED] writes:
Amir That's a great idea. It could also include some of the more
Amir popular reLyX bugs and lacking features, like:
Amir - macros like "\newcommand{\
I'm not really working on reLyX at all. Unfortunately, noone else is either,
even though there are a number of bugs to be fixed and new features that
could be added. (In fact, I think this Scientific Workplace bug or a similar
one has been mentioned before.) I'm forwarding this to the lyx
for importing - I suppose the reLyX stuff could go
wherever that does.
Actually I was going to start on _Exporting_, but you are right -
importing should be added too. Maybe as a first whack I'll hand convert
the man page into LyX and patch it into Extended. We'll see where it goes
from there.
Mike
[EMAIL
I don't know. How can reLyX tell that it's a \protect that LyX put in, and
not one that the coder put in?
Urmh... would the following work?
Put \def\lyxprotect{\protect} in the preamble and use '\lyxprotect' for
the 'helpers'. reLyX could then ignore \lyxprotect and copy \protect...
Andre
On Tue, Feb 29, 2000 at 04:39:08PM +0100, Michael Creel wrote:
>
>Rather than modify reLyX, maybe the best solution would to create a
>document that explains this sort thing so that people would know how to
>modify their TeX documents before applying reLyX. I o
701 - 800 of 986 matches
Mail list logo
