"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel Here is a patch that solves this problem (and others).
I'll apply it.
JMarc
"Jean-Marc" == Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel Here is a patch that solves this problem (and others).
Jean-Marc I'll apply it.
BTW, Dekel, there seem to be code (in filetool.C and the use of
QuitLyX) that seems interesting
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> Here is a patch that solves this problem (and others).
I'll apply it.
JMarc
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> Here is a patch that solves this problem (and others).
Jean-Marc> I'll apply it.
BTW, Dekel, there seem to be code (in filetool.C and the use of
QuitLyX) that
On Thu, Sep 07, 2000 at 12:26:45PM +0100, Jose Abilio Oliveira Matos wrote:
On Wed, Sep 06, 2000 at 12:45:29AM +0300, Dekel Tsur wrote:
On Tue, Sep 05, 2000 at 04:27:54PM +0100, Jose Abilio Oliveira Matos wrote:
Also is it possible to have different viewers for docbook and linuxdoc.
On Thu, Sep 07, 2000 at 12:26:45PM +0100, Jose Abilio Oliveira Matos wrote:
> On Wed, Sep 06, 2000 at 12:45:29AM +0300, Dekel Tsur wrote:
> > On Tue, Sep 05, 2000 at 04:27:54PM +0100, Jose Abilio Oliveira Matos wrote:
> > > Also is it possible to have different viewers for docbook and linuxdoc.
Jose Abilio Oliveira Matos [EMAIL PROTECTED] writes:
| I understand that every format should have a tag, what I find is that
| the file extension is too restrictive. Why not to associate with every format
| a label and an extension? That solves this case and future cases.
|
| Format
On Thu, Sep 07, 2000 at 04:24:21PM +0200, Lars Gullik Bjønnes wrote:
Jose Abilio Oliveira Matos [EMAIL PROTECTED] writes:
| I understand that every format should have a tag, what I find is that
| the file extension is too restrictive. Why not to associate with every format
| a label and
Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
| I understand that every format should have a tag, what I find is that
| the file extension is too restrictive. Why not to associate with every format
| a label and an extension? That solves this case and future cases.
|
| Format
On Thu, Sep 07, 2000 at 04:24:21PM +0200, Lars Gullik Bjønnes wrote:
> Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
>
>
> | I understand that every format should have a tag, what I find is that
> | the file extension is too restrictive. Why not to associate with every format
> | a
On Fri, Aug 25, 2000 at 01:45:56PM +0300, Dekel Tsur wrote:
Here is a patch that contains a complete rewrite of the export mechanism (by
'export' I also mean generating a preview DVI/Postscript).
The new code works by defining converters in lyxrc, and then chaining the
appropriate converters
On Tue, Sep 05, 2000 at 04:27:54PM +0100, Jose Abilio Oliveira Matos wrote:
One question Dekel, is the converter able to distinguish the linuxdoc and
the docbook cases, since both use the sgml extension?
File formats are distinguished by the extension, so we need to use .docbook
for
On Fri, Aug 25, 2000 at 01:45:56PM +0300, Dekel Tsur wrote:
> Here is a patch that contains a complete rewrite of the export mechanism (by
> 'export' I also mean generating a preview DVI/Postscript).
> The new code works by defining converters in lyxrc, and then chaining the
> appropriate
On Tue, Sep 05, 2000 at 04:27:54PM +0100, Jose Abilio Oliveira Matos wrote:
> One question Dekel, is the converter able to distinguish the linuxdoc and
> the docbook cases, since both use the sgml extension?
File formats are distinguished by the extension, so we need to use .docbook
for
Dekel Tsur [EMAIL PROTECTED] writes:
| On Mon, Sep 04, 2000 at 03:23:23PM +0200, Lars Gullik Bjønnes wrote:
|
| I have enabled the new export code in CVS, this will mean that some
| export targets will not work until fixed. We should try to do that
| quickly.
|
| I've already made several
On Mon, Sep 04, 2000 at 09:04:45PM +0200, Lars Gullik Bjnnes wrote:
Dekel Tsur [EMAIL PROTECTED] writes:
| I've already made several fixes (including fixing lib/configure so that
| lyxrc.defaults will contains the \converter commands).
Ok, only one thing?
Why implement copy in terms of
Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Mon, Sep 04, 2000 at 03:23:23PM +0200, Lars Gullik Bjønnes wrote:
| >
| > I have enabled the new export code in CVS, this will mean that some
| > export targets will not work until fixed. We should try to do that
| > quickly.
|
|
On Mon, Sep 04, 2000 at 09:04:45PM +0200, Lars Gullik Bjnnes wrote:
> Dekel Tsur <[EMAIL PROTECTED]> writes:
> | I've already made several fixes (including fixing lib/configure so that
> | lyxrc.defaults will contains the \converter commands).
>
> Ok, only one thing?
>
> Why implement copy in
On 30-Aug-2000 Lars Gullik Bjønnes wrote:
| Did you forgot tex has if/then clauses ?
| It is possible to use the same file with both latex/pdflatex:
|
| \newif \ifpdf
|\ifx \pdfoutput \undefined
| \pdffalse
|\else
| \pdftrue
| \fi
|
| \ifpdf
|
Juergen Vigna [EMAIL PROTECTED] writes:
| On 30-Aug-2000 Lars Gullik Bjønnes wrote:
| | Did you forgot tex has if/then clauses ?
| | It is possible to use the same file with both latex/pdflatex:
| |
| | \newif \ifpdf
| |\ifx \pdfoutput \undefined
| | \pdffalse
| |\else
| |
On 31-Aug-2000 Lars Gullik Bjønnes wrote:
also pdflatex will almost require parameters tt are different feom the
latex' ones for hyperref.
You're right about the parameters I've used:
\ifpdf
\usepackage[pdftex=true,pdftitle={The Open Development of LyX},pdfauthor={Allan
Rae[EMAIL
I strongly disagree. If you export to latex you are supposed to know
what you are doing.
Well. I usually export to LaTeX to hand out the result to people
without LyX. They hand it out to other people etc.
It will almost always be used on systems that I don't know.
Maybe some of them don't have
On Thu, Aug 31, 2000 at 04:45:14PM +0200, Juergen Vigna wrote:
P.S.: Thanks Dekel for this solution! :)
Actually, I got this code from lyx-users (it was posted by Matej Cepl).
On 30-Aug-2000 Lars Gullik Bjønnes wrote:
>| Did you forgot tex has if/then clauses ?
>| It is possible to use the same file with both latex/pdflatex:
>|
>| \newif \ifpdf
>|\ifx \pdfoutput \undefined
>| \pdffalse
>|\else
>| \pdftrue
>| \fi
>|
>| \ifpdf
>|
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 30-Aug-2000 Lars Gullik Bjønnes wrote:
| >| Did you forgot tex has if/then clauses ?
| >| It is possible to use the same file with both latex/pdflatex:
| >|
| >| \newif \ifpdf
| >|\ifx \pdfoutput \undefined
| >| \pdffalse
| >|\else
|
On 31-Aug-2000 Lars Gullik Bjønnes wrote:
> also pdflatex will almost require parameters tt are different feom the
> latex' ones for hyperref.
You're right about the parameters I've used:
\ifpdf
\usepackage[pdftex=true,pdftitle={The Open Development of LyX},pdfauthor={Allan
Rae<[EMAIL
> I strongly disagree. If you export to latex you are supposed to know
> what you are doing.
Well. I usually export to LaTeX to hand out the result to people
without LyX. They hand it out to other people etc.
It will almost always be used on systems that I don't know.
Maybe some of them don't
On Thu, Aug 31, 2000 at 04:45:14PM +0200, Juergen Vigna wrote:
>
> P.S.: Thanks Dekel for this solution! :)
Actually, I got this code from lyx-users (it was posted by Matej Cepl).
On Wed, Aug 30, 2000 at 12:28:38AM +0200, Lars Gullik Bjnnes wrote:
:-) I actually think the dirrerences might be enven larger, since when
using pdf you want to pass "pdflatex" as option to several latex
packages. And thus the whole latex file will be different.
Did you forgot tex has if/then
On Wed, Aug 30, 2000 at 12:28:38AM +0200, Lars Gullik Bjnnes wrote:
> :-) I actually think the dirrerences might be enven larger, since when
> using pdf you want to pass "pdflatex" as option to several latex
> packages. And thus the whole latex file will be different.
Did you forgot tex has
Dekel Tsur [EMAIL PROTECTED] writes:
| On Mon, Aug 28, 2000 at 07:42:26PM +0200, Lars Gullik Bjønnes wrote:
|
| + * src/LaTeX.C (run): If no file has been changed, check if the
| + output dvi/pdf file exists. If not, run (pdf)latex once.
|
| Why is this needed?
|
| The code
On Tue, Aug 29, 2000 at 10:00:56PM +0200, Lars Gullik Bjnnes wrote:
Dekel Tsur [EMAIL PROTECTED] writes:
| On Mon, Aug 28, 2000 at 07:42:26PM +0200, Lars Gullik Bj?nnes wrote:
| + * src/LaTeX.C (run): If no file has been changed, check if the
| + output dvi/pdf file exists. If
Dekel Tsur [EMAIL PROTECTED] writes:
| Yes, the dependency file of pdflatex can be different.
| So perhaps the correct solution is to use different dependency files for
| latex pdflatex:
:-) I actually think the dirrerences might be enven larger, since when
using pdf you want to pass
Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Mon, Aug 28, 2000 at 07:42:26PM +0200, Lars Gullik Bjønnes wrote:
| >
| > + * src/LaTeX.C (run): If no file has been changed, check if the
| > + output dvi/pdf file exists. If not, run (pdf)latex once.
| >
| > Why is this needed?
|
| The
On Tue, Aug 29, 2000 at 10:00:56PM +0200, Lars Gullik Bjnnes wrote:
> Dekel Tsur <[EMAIL PROTECTED]> writes:
> | On Mon, Aug 28, 2000 at 07:42:26PM +0200, Lars Gullik Bj?nnes wrote:
> | > + * src/LaTeX.C (run): If no file has been changed, check if the
> | > + output dvi/pdf file
Dekel Tsur <[EMAIL PROTECTED]> writes:
| Yes, the dependency file of pdflatex can be different.
| So perhaps the correct solution is to use different dependency files for
| latex & pdflatex:
:-) I actually think the dirrerences might be enven larger, since when
using pdf you want to pass
+ * src/LaTeX.C (run): If no file has been changed, check if the
+ output dvi/pdf file exists. If not, run (pdf)latex once.
Why is this needed? (You use it to get the dvi file generated even if
we are really setup to making pdf files, I'd like us to find a better
solution than this,
On Mon, Aug 28, 2000 at 07:42:26PM +0200, Lars Gullik Bjnnes wrote:
+ * src/LaTeX.C (run): If no file has been changed, check if the
+ output dvi/pdf file exists. If not, run (pdf)latex once.
Why is this needed?
The code is needed for the following case: Suppose I view the
+ * src/LaTeX.C (run): If no file has been changed, check if the
+ output dvi/pdf file exists. If not, run (pdf)latex once.
Why is this needed? (You use it to get the dvi file generated even if
we are really setup to making pdf files, I'd like us to find a better
solution than this,
On Mon, Aug 28, 2000 at 07:42:26PM +0200, Lars Gullik Bjnnes wrote:
>
> + * src/LaTeX.C (run): If no file has been changed, check if the
> + output dvi/pdf file exists. If not, run (pdf)latex once.
>
> Why is this needed?
The code is needed for the following case: Suppose I view
Here is a patch that contains a complete rewrite of the export mechanism (by
'export' I also mean generating a preview DVI/Postscript).
The new code works by defining converters in lyxrc, and then chaining the
appropriate converters to get the desired output format.
The code is still incomplete,
Dekel Tsur [EMAIL PROTECTED] writes:
| PS: Lars, can you give Baruch me CVS write access to exporter.[Ch] and
| converter.[Ch] ?
Let's see if you can get the access to cvs.lyx.org working first.
Lgb
Here is a patch that contains a complete rewrite of the export mechanism (by
'export' I also mean generating a preview DVI/Postscript).
The new code works by defining converters in lyxrc, and then chaining the
appropriate converters to get the desired output format.
The code is still incomplete,
Dekel Tsur <[EMAIL PROTECTED]> writes:
| PS: Lars, can you give Baruch & me CVS write access to exporter.[Ch] and
| converter.[Ch] ?
Let's see if you can get the access to cvs.lyx.org working first.
Lgb
44 matches
Mail list logo
