Neal Becker wrote:
> I'd like to try this patch. Do I need to rebuild lyx?
It's included in latest trunk.
> Is this version 1.5.4, or 1.6?
1.6. I had a patch for 1.5 (and I also use it), but it's a file format
change, so it can't go into branch.
Jürgen
Jürgen Spitzmüller wrote:
> Jürgen Spitzmüller wrote:
>> There was a typo in the patch. Corrected one attached.
>
> Grmpf. I reattached the ols one. Try this.
>
> Jürgen
I'd like to try this patch. Do I need to rebuild lyx?
Is this version 1.5.4, or 1.6?
José Matos wrote:
>> Would it be really more difficult to support that through the include
>> inset? Will it be easy later on to go from your solution to a 'proper'
>> solution (whatever it may be?)
>
> I think this is in line with the figure and external insets merge that has
> been discussed so
José Matos wrote:
> I agree with you. This is not a "hard" but a "soft" file format change.
> What I mean here is that there is no syntax change, the new file will be
> read by any 1.5.x version, but it will fail because we are adding a new
> term (word) unknown to previous versions. You are the l
José Matos <[EMAIL PROTECTED]> writes:
> On Wednesday 09 April 2008 09:18:35 Jean-Marc Lasgouttes wrote:
>> Would it be really more difficult to support that through the include
>> inset? Will it be easy later on to go from your solution to a 'proper'
>> solution (whatever it may be?)
>
> I thin
On Wednesday 09 April 2008 09:18:35 Jean-Marc Lasgouttes wrote:
> Would it be really more difficult to support that through the include
> inset? Will it be easy later on to go from your solution to a 'proper'
> solution (whatever it may be?)
I think this is in line with the figure and external i
Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
> The attached patch adds rudimental support via the external inset.
Would it be really more difficult to support that through the include
inset? Will it be easy later on to go from your solution to a 'proper'
solution (whatever it may be?)
JMarc
On Wednesday 09 April 2008 08:32:43 Juergen Spitzmueller wrote:
> Actually, after rethinking I think that a file format change is needed.
> José?
I agree with you. This is not a "hard" but a "soft" file format change. What
I mean here is that there is no syntax change, the new file will be read
Jürgen Spitzmüller wrote:
> This is one of the "can be always added" category. I'm even thinking about
> implementing it in 1.5.5 (no file format change).
Actually, after rethinking I think that a file format change is needed.
José?
Jürgen
Uwe Stöhr wrote:
> Why this? Isn't it just a check if pdftops exists and not the final calling
> command?
It's the command that gets inserted to the prefs by default.
The -f and -l flags are needed, else the conversion fails with multi-page PDF
files. See man pdftops:
-eps
Gener
> --- lib/configure.py (Revision 24162)
> +++ lib/configure.py (Arbeitskopie)
> @@ -409,7 +409,7 @@
> checkProg('a PDF to PS converter', ['pdf2ps $$i $$o', 'pdftops $$i $$o'],
> rc_entry = [ r'\converter pdf ps"%%"""' ])
> #
> -checkProg('a PD
Jürgen Spitzmüller wrote:
> There was a typo in the patch. Corrected one attached.
Grmpf. I reattached the ols one. Try this.
Jürgen
Index: lib/external_templates
===
--- lib/external_templates (Revision 24162)
+++ lib/external_templ
Jürgen Spitzmüller wrote:
> The attached patch adds rudimental support via the external inset.
There was a typo in the patch. Corrected one attached.
Jürgen
Index: lib/external_templates
===
--- lib/external_templates (Revision 24162
> This is one of the "can be always added" category. I'm even thinking about
> implementing it in 1.5.5 (no file format change).
OK, I see.
> And I've done enough bugfixing lately.
I wouldn't criticize or force you to do anything. I appreciate your bugfixes.
regards Uwe
Uwe Stöhr wrote:
> > The attached patch adds rudimental support via the external inset.
>
> How can I test that this works?
apply the patch, insert->File->External Material, chose PDFPages.
> > Objections?
>
> Hmm, I think this is a useful feature as this topic appears from time to
> time on th
> The attached patch adds rudimental support via the external inset.
How can I test that this works?
> Objections?
Hmm, I think this is a useful feature as this topic appears from time to time on the lyx-users list,
but we should really come to an end now with new features for LyX 1.6. But of
16 matches
Mail list logo
