Re: export to odt and HTML (Word)
On 07/18/2012 11:22 PM, Jack Tanner wrote: On my LyX 2.0.4, Windows, export to odt and HTML (Word) is very broken. For example, at times I get this in messages: 23:14:21.748: C:\Users\lunacy\AppData\Local\Temp\lyx_tmpdir.Hp8096\lyx_tmpbuf3t4ht my-doc.tex -cooxtpipes -coo -ewin32/tex4ht.env 23:14:21.751: --- error --- Illegal storage address but then I also get: 23:14:21.772: Successful export to format: odt 23:18:42.401: Automatic save done. Naturally, the export fails, i.e., neither the temp dir nor the actual doc dir contain an exported file. These look like bugs in the tex4ht package you're using to do the export. tex4ht is known to be problematic on Windows. (It's a bit flaky sometimes on other platforms, too.) LyX must think the export worked because tex4ht is returning the code for success. That's the only way we know what's happened. Richard
Re: Undo.cpp reports an error on trunk
On 07/18/2012 03:08 PM, Jean-Marc Lasgouttes wrote: Le 18/07/12 17:43, Richard Heck a écrit : Looks like you never backported this particular fix. If you decide to do it, I'll backport my patch too. Which thing didn't I backport? This one, I think. I guess that should go in, so I've done it. Richard
Re: export to odt and HTML (Word)
On Saturday, July 21, 2012 9:57:22 AM, Richard Heck wrote: These look like bugs in the tex4ht package you're using to do the export. tex4ht is known to be problematic on Windows. (It's a bit flaky sometimes on other platforms, too.) I've now spent about 12 hours trying to get tex4ht to work. I've tried it in MiKTeX 2.9, in TexLive under Cygwin, and under CentOS. My verdict is that tex4ht is awfully, awfully broken. For one, the file tex4ht.env comes with at least two sets of hard-coded paths that cannot possibly work on any system other than the developer's. Then there's the piece of the xtpipes infrastructure that generates invalid XML that it later tries to parse and fails... I got better results with pandoc for conversion from LyX-exported TeX to docx. It's fast and robust. However, pandoc has poor support for input from TeX tables. It seems like if LyX could export either to pandoc-enhanced markdown or to pandoc's native format, we'd have pretty good support for conversion from LyX to a bunch of useful formats. See http://johnmacfarlane.net/pandoc/
Re: export to odt and HTML (Word)
On 07/21/2012 12:50 PM, Jack Tanner wrote: On Saturday, July 21, 2012 9:57:22 AM, Richard Heck wrote: These look like bugs in the tex4ht package you're using to do the export. tex4ht is known to be problematic on Windows. (It's a bit flaky sometimes on other platforms, too.) I've now spent about 12 hours trying to get tex4ht to work. I've tried it in MiKTeX 2.9, in TexLive under Cygwin, and under CentOS. My verdict is that tex4ht is awfully, awfully broken. For one, the file tex4ht.env comes with at least two sets of hard-coded paths that cannot possibly work on any system other than the developer's. Then there's the piece of the xtpipes infrastructure that generates invalid XML that it later tries to parse and fails... I got better results with pandoc for conversion from LyX-exported TeX to docx. It's fast and robust. However, pandoc has poor support for input from TeX tables. It seems like if LyX could export either to pandoc-enhanced markdown or to pandoc's native format, we'd have pretty good support for conversion from LyX to a bunch of useful formats. See http://johnmacfarlane.net/pandoc/ Have you talked to John (another philosopher!) about the LaTeX issues? I'm sure he'd be interested in fixing them. Richard
Re: LyX, XeTeX, bidi and Hebrew
On 2012-07-19, Ronen Abravanel wrote: XeTexX get in in the modern (unicode) sense of right. LyX, by default, input it wrong, but LyX output is good for pdfLaTeX. LyX fixes it's output in the plain-text output, and my patch apply the same correction for Hebrew-XeTeX output... I still consider it better to fix the output to pdflatex, so that the input can be modern. Günter
demande une aide
Bonjour, J'ai un grand probleme avec le LYX qui m'a casse la tete pendant deux semaines Quand je convertis le fichier lyx a pdf il me donne une message d'erruer: impossible de l'excutaion epstopdf, le fichier n'existe pas J'ai essaie toutes les solutions donnees dans plusieurs forumes sans resultats est-ceque vous pouvez s.v.p m'aider Laila TATAIE
Demande une aide
Bonjour, Je presise le type d'erruer: Package pdftex.def error : then the name of the figure Merci d'avance Laila TATAIE
Left-click problems with split views
This is in LyX 2.0.4 on Windows Vista. Open a document with a float: Figure or wrap: Figure inset (or table wrap float). Split the view -- left/right or upper/lower doesn't matter. In the new view the inset will open or close with a left click (the cursor turns from the text I-shape to a little hand). In the original view the cursor remains in the text I-shape and the inset cannot be opened or closed with a left click. However, a right click, then left-clicking on Open inset, does still work. Most of the sizable LyX documents on my computer that contain figures show this behaviour, but one doesn't. I can't see any obvious difference. Creating a test document containing only a float: Figure and splitting the view does *not* produce the problem -- although it does show, by clicking back and forth irregularly in left and right views on the inset, that the inset sometimes opens or closes together in both views and sometimes not. A related problem with a split view occurs with equations, although this occurs irregularly and generally seems to require a certain amount of clicking beforehand. In the new view the cursor can be placed anywhere in the equation with a left click. In the original view the cursor sits at the start of the equation and doesn't respond to left clicks. It can still be moved with the arrow keys. Closing the split view cures the problems. Andrew
Re: export to odt and HTML (Word)
On Saturday, July 21, 2012 2:28:06 PM, Richard Heck wrote: Have you talked to John (another philosopher!) about the LaTeX issues? I'm sure he'd be interested in fixing them. I didn't, but only because I found this message, which makes it look like he knows about the issues already: https://groups.google.com/d/topic/pandoc-discuss/_NrHzZoDRd4/discussion
Re: export to odt and HTML (Word)
On 07/18/2012 11:22 PM, Jack Tanner wrote: On my LyX 2.0.4, Windows, export to odt and HTML (Word) is very broken. For example, at times I get this in messages: 23:14:21.748: C:\Users\lunacy\AppData\Local\Temp\lyx_tmpdir.Hp8096\lyx_tmpbuf3>t4ht my-doc.tex "-cooxtpipes -coo" -ewin32/tex4ht.env 23:14:21.751: --- error --- Illegal storage address but then I also get: 23:14:21.772: Successful export to format: odt 23:18:42.401: Automatic save done. Naturally, the export fails, i.e., neither the temp dir nor the actual doc dir contain an exported file. These look like bugs in the tex4ht package you're using to do the export. tex4ht is known to be problematic on Windows. (It's a bit flaky sometimes on other platforms, too.) LyX must think the export worked because tex4ht is returning the code for "success". That's the only way we know what's happened. Richard
Re: Undo.cpp reports an error on trunk
On 07/18/2012 03:08 PM, Jean-Marc Lasgouttes wrote: Le 18/07/12 17:43, Richard Heck a écrit : Looks like you never backported this particular fix. If you decide to do it, I'll backport my patch too. Which thing didn't I backport? This one, I think. I guess that should go in, so I've done it. Richard
Re: export to odt and HTML (Word)
On Saturday, July 21, 2012 9:57:22 AM, Richard Heck wrote: These look like bugs in the tex4ht package you're using to do the export. tex4ht is known to be problematic on Windows. (It's a bit flaky sometimes on other platforms, too.) I've now spent about 12 hours trying to get tex4ht to work. I've tried it in MiKTeX 2.9, in TexLive under Cygwin, and under CentOS. My verdict is that tex4ht is awfully, awfully broken. For one, the file tex4ht.env comes with at least two sets of hard-coded paths that cannot possibly work on any system other than the developer's. Then there's the piece of the xtpipes infrastructure that generates invalid XML that it later tries to parse and fails... I got better results with pandoc for conversion from LyX-exported TeX to docx. It's fast and robust. However, pandoc has poor support for input from TeX tables. It seems like if LyX could export either to pandoc-enhanced markdown or to pandoc's native format, we'd have pretty good support for conversion from LyX to a bunch of useful formats. See http://johnmacfarlane.net/pandoc/
Re: export to odt and HTML (Word)
On 07/21/2012 12:50 PM, Jack Tanner wrote: On Saturday, July 21, 2012 9:57:22 AM, Richard Heck wrote: These look like bugs in the tex4ht package you're using to do the export. tex4ht is known to be problematic on Windows. (It's a bit flaky sometimes on other platforms, too.) I've now spent about 12 hours trying to get tex4ht to work. I've tried it in MiKTeX 2.9, in TexLive under Cygwin, and under CentOS. My verdict is that tex4ht is awfully, awfully broken. For one, the file tex4ht.env comes with at least two sets of hard-coded paths that cannot possibly work on any system other than the developer's. Then there's the piece of the xtpipes infrastructure that generates invalid XML that it later tries to parse and fails... I got better results with pandoc for conversion from LyX-exported TeX to docx. It's fast and robust. However, pandoc has poor support for input from TeX tables. It seems like if LyX could export either to pandoc-enhanced markdown or to pandoc's native format, we'd have pretty good support for conversion from LyX to a bunch of useful formats. See http://johnmacfarlane.net/pandoc/ Have you talked to John (another philosopher!) about the LaTeX issues? I'm sure he'd be interested in fixing them. Richard
Re: LyX, XeTeX, bidi and Hebrew
On 2012-07-19, Ronen Abravanel wrote: > XeTexX get in in the modern (unicode) sense of right. > LyX, by default, input it "wrong", but LyX output is good for pdfLaTeX. > LyX fixes it's output in the plain-text output, and my patch apply the same > correction for Hebrew-XeTeX output... I still consider it better to fix the output to pdflatex, so that the input can be "modern". Günter
demande une aide
Bonjour, J'ai un grand probleme avec le LYX qui m'a casse la tete pendant deux semaines Quand je convertis le fichier lyx a pdf il me donne une message d'erruer: "impossible de l'excutaion epstopdf, le fichier n'existe pas" J'ai essaie toutes les solutions donnees dans plusieurs forumes sans resultats est-ceque vous pouvez s.v.p m'aider Laila TATAIE
Demande une aide
Bonjour, Je presise le type d'erruer: Package pdftex.def error : then the name of the figure Merci d'avance Laila TATAIE
Left-click problems with split views
This is in LyX 2.0.4 on Windows Vista. Open a document with a float: Figure or wrap: Figure inset (or table wrap float). Split the view -- left/right or upper/lower doesn't matter. In the new view the inset will open or close with a left click (the cursor turns from the text I-shape to a little hand). In the original view the cursor remains in the text I-shape and the inset cannot be opened or closed with a left click. However, a right click, then left-clicking on Open inset, does still work. Most of the sizable LyX documents on my computer that contain figures show this behaviour, but one doesn't. I can't see any obvious difference. Creating a test document containing only a float: Figure and splitting the view does *not* produce the problem -- although it does show, by clicking back and forth irregularly in left and right views on the inset, that the inset sometimes opens or closes together in both views and sometimes not. A related problem with a split view occurs with equations, although this occurs irregularly and generally seems to require a certain amount of clicking beforehand. In the new view the cursor can be placed anywhere in the equation with a left click. In the original view the cursor sits at the start of the equation and doesn't respond to left clicks. It can still be moved with the arrow keys. Closing the split view cures the problems. Andrew
Re: export to odt and HTML (Word)
On Saturday, July 21, 2012 2:28:06 PM, Richard Heck wrote: Have you talked to John (another philosopher!) about the LaTeX issues? I'm sure he'd be interested in fixing them. I didn't, but only because I found this message, which makes it look like he knows about the issues already: https://groups.google.com/d/topic/pandoc-discuss/_NrHzZoDRd4/discussion
