Lars Gullik Bjønnes wrote:
> Luis Rivera writes:
> | Hello,
> |
> | I tried to run tex2lyx on win95/98, without success. The programs
> | crashed crying as follows:
> |
> | On win95
> |
> | The TEX2LYX.EXE file is linked to missing export
> | KERNEL32.DLL:GetFileAttributesExA
> Can't we just decl
Luis Rivera <[EMAIL PROTECTED]> writes:
| Hello,
|
| I tried to run tex2lyx on win95/98, without success. The programs
| crashed crying as follows:
|
| On win95
|
| The TEX2LYX.EXE file is linked to missing export
| KERNEL32.DLL:GetFileAttributesExA
Can't we just declare that we do not suppor
Hello,
I tried to run tex2lyx on win95/98, without success. The programs
crashed crying as follows:
On win95
The TEX2LYX.EXE file is linked to missing export
KERNEL32.DLL:GetFileAttributesExA
On win98
The TEX2LYX.EXE file is linked to missing export
SHELL32.DLL:SHGetFolderPathA
This bug seem
Am Montag, 11. Juli 2005 20:28 schrieb Andre Poenitz:
> On Mon, Jul 11, 2005 at 10:14:20AM -0300, João Luis Meloni Assirati
wrote:
> > That would be
> >
> > ERT(\begin{unknown}) ERT(\large some text) ERT(\end{unknown})
> >
> > or even better
> >
> > ERT(
> > \begin{unknown}
> > \large some tex
Am Montag, 11. Juli 2005 20:26 schrieb João Luis Meloni Assirati:
> Your patch misses a } at the end of the function parse_box at text.C
(do you
> really test your patches or you just know they are going to work???:)
I have one "dirty" tree with lots of changes and one "clean" tree for
applyi
On Mon, Jul 11, 2005 at 10:14:20AM -0300, João Luis Meloni Assirati wrote:
> Em Seg 11 Jul 2005 10:09, João Luis Meloni Assirati escreveu:
>
> > IMHO, the only way to solve this problem is to parse the entire contents
> > between \begin{unknown} and \end{unknown} as ERT.
>
> That would be
>
> E
Em Seg 11 Jul 2005 13:01, Georg Baum escreveu:
> João Luis Meloni Assirati wrote:
> > I still think that this is impossible since unless the lyx format had a
> > special syntax for unknown environments.
>
> I still don't think that it is impossible. Proof attached ;-)
Yes, I'm convinced that it is
João Luis Meloni Assirati wrote:
> I still think that this is impossible since unless the lyx format had a
> special syntax for unknown environments.
I still don't think that it is impossible. Proof attached ;-)
> Think of this possibility:
>
> \large some text
> \begin{unknown}
> \huge some o
Jean-Marc Lasgouttes wrote:
> BTW Georg, do we honor the reLyXre stuff defined in syntax.default to
> know which environment contents should be translated?
No, but I have a patch that adds that. It is waiting for some spare minutes
to test it.
Georg
Georg,
Em Seg 11 Jul 2005 10:37, Georg Baum escreveu:
> > Em Seg 11 Jul 2005 10:09, João Luis Meloni Assirati escreveu:
> >> IMHO, the only way to solve this problem is to parse the entire contents
> >> between \begin{unknown} and \end{unknown} as ERT.
>
> No. Jean-Marc invented the context class
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> No. Jean-Marc invented the context class to handle things like
Georg> that. The correct way would be to make parse_environment
Georg> restrict font changes to the environment contents also for
Georg> unknown environments. I don't know
João Luis Meloni Assirati wrote:
> Em Seg 11 Jul 2005 10:09, João Luis Meloni Assirati escreveu:
>
>> IMHO, the only way to solve this problem is to parse the entire contents
>> between \begin{unknown} and \end{unknown} as ERT.
No. Jean-Marc invented the context class to handle things like that.
Em Seg 11 Jul 2005 10:09, João Luis Meloni Assirati escreveu:
> IMHO, the only way to solve this problem is to parse the entire contents
> between \begin{unknown} and \end{unknown} as ERT.
That would be
ERT(\begin{unknown}) ERT(\large some text) ERT(\end{unknown})
or even better
ERT(
\begin{u
Hello,
The following latex fragment:
\begin{titlepage}
\large some text
\end{titlepage}
will produce a bad lyx file (it can be any other unknown environment, not
necessarily titlepage). The corresponding lyx file will be interpreted by lyx
(1.3 as well as 1.4) as:
ERT(\begin{titlepage}) ( \l
Am Freitag, 23. Juli 2004 17:35 schrieb Angus Leeming:
> Apply the fix but print a warning to stderr. That should satisfy
everybody.
Good idea, I did it like that.
Georg
On Friday 23 July 2004 16:35, Angus Leeming wrote:
>
> Apply the fix but print a warning to stderr. That should satisfy
> everybody.
I agree with Angus.
--
José Abílio
Georg Baum wrote:
>> tex2lyx bug.tex > tmp.lyx
>> lyx2lyx -t221 tmp.lyx > bug.lyx
>> unix2dos bug.lyx
>
> I believe that the last step is not needed.
>
>> The bug can be avoided by replacing \cr with \\ throughout.
>
> And that is what you should do anyway. \cr is a tex construct, not latex.
> I
[EMAIL PROTECTED] wrote:
> tex2lyx bug.tex > tmp.lyx
> lyx2lyx -t221 tmp.lyx > bug.lyx
> unix2dos bug.lyx
I believe that the last step is not needed.
> The bug can be avoided by replacing \cr with \\ throughout.
And that is what you should do anyway. \cr is a tex construct, not latex. If
you lo
Hi,
The attached .lyx file causes the Windows native port (Qt version) of LyX
1.3.2 to crash. It was produced from the attached .tex file using the
following commands on a Linux box
tex2lyx bug.tex > tmp.lyx
lyx2lyx -t221 tmp.lyx > bug.lyx
unix2dos bug.lyx
The bug can be avoided by replacing \cr
19 matches
Mail list logo
