On 1/27/24 12:37, Pavel Sanda wrote:
On Sat, Jan 27, 2024 at 05:30:19PM +0100, didiergab...@free.fr wrote:
With this second version the pdf preview is also perfect !
Good, committed as 7eb5003a81ab. Will be part of RC2,
for your convenience you can leave the new configure.py
within your local
On Sat, Jan 27, 2024 at 05:30:19PM +0100, didiergab...@free.fr wrote:
> With this second version the pdf preview is also perfect !
Good, committed as 7eb5003a81ab. Will be part of RC2,
for your convenience you can leave the new configure.py
within your local RC1 installation...
Pavel
--
On Sat, Jan 27, 2024 at 06:05:02PM +0100, didiergab...@free.fr wrote:
> After setting up this version of the ???configure.py??? script I no longer
> find any trace of the file converter:
> PDF (graphic) ???> PNG with the command:
> ???pdftoppm -r 72 -png -singlefile $$i > $$o???
>
> Can you
After setting up this version of the “configure.py” script I no longer find any
trace of the file converter:
PDF (graphic) —> PNG with the command:
“pdftoppm -r 72 -png -singlefile $$i > $$o”
Can you confirm that this is normal? (I tell myself that I may have clicked on
the “remove” button
With this second version the pdf preview is also perfect !
- Mail original -
| On Sat, Jan 27, 2024 at 02:29:15PM +0100, Pavel Sanda wrote:
| > On Sat, Jan 27, 2024 at 01:43:02PM +0100, didiergab...@free.fr
| > wrote:
| > > It's perfect ! See for yourself???
| >
| > Good. I will need to
On Sat, Jan 27, 2024 at 02:29:15PM +0100, Pavel Sanda wrote:
> On Sat, Jan 27, 2024 at 01:43:02PM +0100, didiergab...@free.fr wrote:
> > It's perfect ! See for yourself???
>
> Good. I will need to prepare more generic patch for you to test.
Didier, please test the generic version of
On Sat, Jan 27, 2024 at 01:43:02PM +0100, didiergab...@free.fr wrote:
> It's perfect ! See for yourself???
Good. I will need to prepare more generic patch for you to test.
Stay tuned,
Pavel
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
ps :
But be careful, I'll come back with another question in a few minutes... On the
list of simple users... For a story about the background color of an svg
graphic... ;o)
- Mail original -
| It's perfect ! See for yourself…
| Thank’s
| Thank you so much !
| ps:
| - Mail
On Sat, Jan 27, 2024 at 01:16:39PM +0100, didiergab...@free.fr wrote:
> I see where the ???cache??? folder is located in my user directory here :
>
> C:\Users\Didier\AppData\Roaming\LyX2.4\cache
>
> And I just spotted the configure.py file here:
>
> C:\Users\Didier\AppData\Local\Programs\LyX
I see where the “cache” folder is located in my user directory here :
C:\Users\Didier\AppData\Roaming\LyX2.4\cache
And I just spotted the configure.py file here:
C:\Users\Didier\AppData\Local\Programs\LyX 2.4\Resources
So ok ?
- Mail original -
| On Sat, Jan 27, 2024 at
On Sat, Jan 27, 2024 at 12:48:40PM +0100, didiergab...@free.fr wrote:
> I'm a little lost, because I managed the discussion threads very poorly and I
> didn't always place my comments in the right places...
Do not worry, we will manage.
> You would like the screenshot showing the preview of the
On Tue, Jan 23, 2024 at 09:22:23PM +0100, Thibaut Cuvelier wrote:
> On Tue, 23 Jan 2024 at 18:35, Pavel Sanda wrote:
>
> > On Tue, Jan 23, 2024 at 11:58:54AM -0500, Richard Kimberly Heck wrote:
> > > pdftoppm -r 72 -png -singlefile $$i > $$o
> >
> > This is new route in 2.4 which can be
On Tue, 23 Jan 2024 at 18:35, Pavel Sanda wrote:
> On Tue, Jan 23, 2024 at 11:58:54AM -0500, Richard Kimberly Heck wrote:
> > pdftoppm -r 72 -png -singlefile $$i > $$o
>
> This is new route in 2.4 which can be used to avoid IM problems in linux.
> We perhaps triggerred unnecessary problems
On 1/23/24 12:33, Pavel Sanda wrote:
On Tue, Jan 23, 2024 at 11:58:54AM -0500, Richard Kimberly Heck wrote:
pdftoppm -r 72 -png -singlefile $$i > $$o
This is new route in 2.4 which can be used to avoid IM problems in linux.
We perhaps triggerred unnecessary problems on Windows.
This
On Tue, Jan 23, 2024 at 11:58:54AM -0500, Richard Kimberly Heck wrote:
> pdftoppm -r 72 -png -singlefile $$i > $$o
This is new route in 2.4 which can be used to avoid IM problems in linux.
We perhaps triggerred unnecessary problems on Windows.
This could be sovled by making pdftoppm addition
Here it is.
Here is the command I can see under Tools> Preferences> File Handling>
Converters, at the PDF to PNG converter: « pdftoppm -r 72 -png -singlefile $$i
> $$o » as you said... I’ll try to increase the dpi
ps : On these computer svg from inkscape preview is ok so good point.
-
On 1/23/24 04:06, didiergab...@free.fr wrote:
I am currently in front of my Windows 10 PC at my workplace with which
I am experiencing exactly the same symptoms.
I followed your instructions, and you will find the requested file
attached.
I will do the same thing again this evening at home,
On Friday, January 8, 2021 4:05:39 PM WET Jean-Marc Lasgouttes wrote:
> I have no idea about that, but I am the kind of guy who thinks that we
> do not care about dvi file...
IIRC the preview mechanism used the dvi output.
I am quite happy to use the preview even although I do not know how this
Le 08/01/2021 à 16:50, José Abílio Matos a écrit :
On Tuesday, January 5, 2021 5:10:13 PM WET Jean-Marc Lasgouttes wrote:
> José, what is the status on this?
Honestly? Since I am not masochist I do not play with hornets nests. :-)
So as far I remember the issue is: is there any reason in
On Tuesday, January 5, 2021 5:10:13 PM WET Jean-Marc Lasgouttes wrote:
> Le 13/06/2019 à 17:41, José Abílio Matos a écrit :
> > Last week while working with python2/python3 differences I found clues
> > that
> > the legacy graphics conversion has problems.
> >
>
Le 13/06/2019 à 17:41, José Abílio Matos a écrit :
Last week while working with python2/python3 differences I found clues that
the legacy graphics conversion has problems.
Like I said in bugs #11457 and #11282:
"This also means that the legacy conversion has some issues but I think that
b
Le 13/06/2019 à 17:41, José Abílio Matos a écrit :
Last week while working with python2/python3 differences I found clues that
the legacy graphics conversion has problems.
Like I said in bugs #11457 and #11282:
"This also means that the legacy conversion has some issues but I think that
b
Le 13/06/2019 à 17:41, José Abílio Matos a écrit :
Last week while working with python2/python3 differences I found clues that
the legacy graphics conversion has problems.
Like I said in bugs #11457 and #11282:
"This also means that the legacy conversion has some issues but I think that
b
On Friday, 14 June 2019 07.33.33 WEST Enrico Forestieri wrote:
> s/rsvg-convert/pdftocairo/
I have. But I want to test all the available scenarios to understand what is
going on.
The purpose of this thread is to understand what are the minimum requirements
for instant preview and to fix the
On Fri, Jun 14, 2019 at 08:28:09AM +0200, Enrico Forestieri wrote:
> On Fri, Jun 14, 2019 at 07:09:27AM +0100, José Abílio Matos wrote:
> >
> > In terms of speed, the conversion is slow.
>
> Do you have rsvg-convert installed?
s/rsvg-convert/pdftocairo/
--
Enrico
nces I found clues
> > > that
> > > the legacy graphics conversion has problems.
> >
> > Which kind of problems?
>
> In terms of speed, the conversion is slow.
Do you have rsvg-convert installed?
> > > Like I said in bugs #11457 and #11282:
> > >
On Friday, 14 June 2019 06.59.16 WEST Enrico Forestieri wrote:
> On Thu, Jun 13, 2019 at 04:41:44PM +0100, José Abílio Matos wrote:
> > Last week while working with python2/python3 differences I found clues
> > that
> > the legacy graphics conversion has problems.
>
On Thu, Jun 13, 2019 at 04:41:44PM +0100, José Abílio Matos wrote:
> Last week while working with python2/python3 differences I found clues that
> the legacy graphics conversion has problems.
Which kind of problems?
> Like I said in bugs #11457 and #11282:
> "This also mean
Last week while working with python2/python3 differences I found clues that
the legacy graphics conversion has problems.
Like I said in bugs #11457 and #11282:
"This also means that the legacy conversion has some issues but I think that
by now everyone should be using dvipng to that
On 04/06/2017 03:40, Enrico Forestieri wrote:
On Fri, Jun 02, 2017 at 12:55:47AM +0200, Enrico Forestieri wrote:
So, output_file is always empty, whatever op.dryrun. I think that
the following change was instead meant:
- string const output_file = prepareHTMLFile(op);
+ string
On Sat, Jun 03, 2017 at 03:22:32PM -0400, Scott Kostyshak wrote:
> On Fri, Jun 02, 2017 at 12:55:47AM +0200, Enrico Forestieri wrote:
>
> > So, output_file is always empty, whatever op.dryrun. I think that
> > the following change was instead meant:
> >
> > - string const output_file =
On Fri, Jun 02, 2017 at 12:55:47AM +0200, Enrico Forestieri wrote:
> So, output_file is always empty, whatever op.dryrun. I think that
> the following change was instead meant:
>
> - string const output_file = prepareHTMLFile(op);
> + string const output_file = op.dryrun ? string() :
017 +0200
> >
> > skip graphics conversion when runparams.dryrun is true
>
> After this commit, if I copy a selection that has an image in it, I get
> the following message:
>
> insets/InsetGraphics.cpp (956): InsetGraphics::xhtml: Unable to prepare file
>
On Fri, May 05, 2017 at 08:30:51AM +0200, Tommaso Cucinotta wrote:
> commit 0cf394dd79337b14adb2930a617c2027e0d6f2d8
> Author: Tommaso Cucinotta <tomm...@lyx.org>
> Date: Thu May 4 07:49:07 2017 +0200
>
> skip graphics conversion when runparams.dryrun is true
After t
messages. I have activated Graphics
Conversion messages in the GUI, and I see lots of messages regarding python
scripts, etc. I even see will guess format from file extension: plantuml
- PlantUML
I know the PlantUML script is working for the PNG and EPS, but even there I
don't see a call to the .bat
called properly, but I
can't see any trace of it in the Debug messages. I have activated Graphics
Conversion messages in the GUI, and I see lots of messages regarding
python scripts, etc. I even see will guess format from file extension:
plantuml - PlantUML
I know the PlantUML script
messages. I have activated Graphics
Conversion messages in the GUI, and I see lots of messages regarding python
scripts, etc. I even see " will guess format from file extension: plantuml
-> PlantUML"
I know the PlantUML script is working for the PNG and EPS, but even there I
don't see a cal
t try
PPM, but SVG.
> Anyway, I want to make sure my .bat file is being called properly, but I
> can't see any trace of it in the Debug messages. I have activated Graphics
> Conversion messages in the GUI, and I see lots of messages regarding
> python scripts, etc. I even see "
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Something similar is needed by convertDefault.sh too. See
Angus attached. I won't apply this to the 1.3.x branch till you say
Angus Ok.
Ok.
JMarc
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Something similar is needed by convertDefault.sh too. See
Angus> attached. I won't apply this to the 1.3.x branch till you say
Angus> Ok.
Ok.
JMarc
Two patches attached, for 1.3.x and 1.4.x. Rationale below.
Ok to apply to 1.3.x, Jean-Marc?
Angus
You'd think that building a shell script, so, would be safe:
script infile= QuoteName(infile) '\n'
infile_base= QuoteName(infile_base) '\n'
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus Two patches attached, for 1.3.x and 1.4.x. Rationale below. Ok
Angus to apply to 1.3.x, Jean-Marc? Angus
Angus All variables must be wrapped in double quotes: [...]
Provided this has been correctly tested, this is fine.
Thanks.
JMarc
Jean-Marc Lasgouttes wrote:
Angus == Angus Leeming [EMAIL PROTECTED]
writes:
Angus Two patches attached, for 1.3.x and 1.4.x. Rationale below. Ok
Angus to apply to 1.3.x, Jean-Marc? Angus
Angus All variables must be wrapped in double quotes: [...]
Provided this has been correctly
Angus Leeming wrote:
If testing means it works for me, then it's been tested. This leads to
an image displayed by LyX:
[ ...snip... ]
I'll apply it.
Something similar is needed by convertDefault.sh too. See attached. I won't
apply this to the 1.3.x branch till you say Ok.
--
AngusIndex:
Two patches attached, for 1.3.x and 1.4.x. Rationale below.
Ok to apply to 1.3.x, Jean-Marc?
Angus
You'd think that building a shell script, so, would be safe:
script << "infile=" << QuoteName(infile) << '\n'
<< "infile_base=" << QuoteName(infile_base) << '\n'
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Two patches attached, for 1.3.x and 1.4.x. Rationale below. Ok
Angus> to apply to 1.3.x, Jean-Marc? Angus
Angus> All variables must be wrapped in double quotes: [...]
Provided this has been correctly tested, this is fine.
Jean-Marc Lasgouttes wrote:
>> "Angus" == Angus Leeming <[EMAIL PROTECTED]>
>> writes:
>
> Angus> Two patches attached, for 1.3.x and 1.4.x. Rationale below. Ok
> Angus> to apply to 1.3.x, Jean-Marc? Angus
>
> Angus> All variables must be wrapped in double quotes: [...]
>
> Provided
Angus Leeming wrote:
> If testing means "it works for me", then it's been tested. This leads to
> an image displayed by LyX:
[ ...snip... ]
> I'll apply it.
Something similar is needed by convertDefault.sh too. See attached. I won't
apply this to the 1.3.x branch till you say Ok.
--
AngusIndex:
status.13x says it all: Enable graphics conversion using the default
convertDefault.sh converter when exporting, even if convertDefault.sh is not
executable.
The patch has been in the 1.4 tree since 28 August. It was created in response
to this thread:
http://article.gmane.org
Angus == Angus Leeming [EMAIL PROTECTED] writes:
Angus status.13x says it all: Enable graphics conversion using the
Angus default convertDefault.sh converter when exporting, even if
Angus convertDefault.sh is not executable.
Go for it.
JMarc
status.13x says it all: Enable graphics conversion using the default
convertDefault.sh converter when exporting, even if convertDefault.sh is not
executable.
The patch has been in the 1.4 tree since 28 August. It was created in response
to this thread:
http://article.gmane.org
>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> status.13x says it all: Enable graphics conversion using the
Angus> default convertDefault.sh converter when exporting, even if
Angus> convertDefault.sh is not executable.
Go for it.
JMarc
Hi,
I'm using current CVS and I am experiencing problems when loading Grace files
into graphics. Although the GRACE format is explicitly defined in the
preferences (by default) as well as the conversions from GRACE to EPS/JPG/PNG,
when I load a grace file (.agr extension), I get an error
Hi,
I'm using current CVS and I am experiencing problems when loading Grace files
into graphics. Although the GRACE format is explicitly defined in the
preferences (by default) as well as the conversions from GRACE to EPS/JPG/PNG,
when I load a grace file (.agr extension), I get an error
Hi,
A former thread at this list has guided me through how
to use Grace files (2D-graphics package) as input files
for the Graphics/figure inset Works great in LyX!!!
However, when I export my LyX file as LaTeX, the Grace
files are exported as figure files When I then run latex
on this newly
On Friday 01 March 2002 12:27 pm, R. Lahaye wrote:
Hi,
A former thread at this list has guided me through how
to use Grace files (2D-graphics package) as input files
for the Graphics/figure inset. Works great in LyX!!!
However, when I export my LyX file as LaTeX, the Grace
files are
Angus Leeming wrote:
On Friday 01 March 2002 12:27 pm, R Lahaye wrote:
I suppose this is a general problem with the conversion mechanism
and exporting latex, isn't it?
As it is now, the latex file is unusable
Maybe Maybe the fault is with you
You need to define also a converter
On Fri, 1 Mar 2002, R Lahaye wrote:
With that -dbg option I get, when I export to LaTeX:
[]
filetools(getExtFromContents)
Couldn't find a known Type!
will use ext or a user defined format
don't unzip file or export latex/home/lahaye/figures/newfigagr
[]
Any idea what's
On Friday 01 March 2002 12:48 pm, R. Lahaye wrote:
Angus Leeming wrote:
On Friday 01 March 2002 12:27 pm, R. Lahaye wrote:
I suppose this is a general problem with the conversion mechanism
and exporting latex, isn't it?
As it is now, the latex file is unusable.
Maybe.
On Fri, 1 Mar 2002, Angus Leeming wrote:
In my lyxrcdefaults I have
\Format graceagr GRACE
\converter agr eps xmgrace -hardcopy -hdevice EPS $$i
If you don't, then you should
cvs update
autogensh
configure
You shouldn't need to make anything
the last
Hi,
A former thread at this list has guided me through how
to use Grace files (2D-graphics package) as input files
for the Graphics/figure inset. Works great in LyX!!!
However, when I export my LyX file as LaTeX, the Grace
files are exported as figure files. When I then run latex
on this newly
On Friday 01 March 2002 12:27 pm, R. Lahaye wrote:
> Hi,
>
> A former thread at this list has guided me through how
> to use Grace files (2D-graphics package) as input files
> for the Graphics/figure inset. Works great in LyX!!!
>
> However, when I export my LyX file as LaTeX, the Grace
> files
Angus Leeming wrote:
>
> On Friday 01 March 2002 12:27 pm, R. Lahaye wrote:
> >
> > I suppose this is a general problem with the conversion mechanism
> > and exporting latex, isn't it?
> >
> > As it is now, the latex file is unusable.
>
> Maybe. Maybe the fault is with you.
>
> You need to
On Fri, 1 Mar 2002, R. Lahaye wrote:
> With that -dbg option I get, when I export to LaTeX:
>
> [...]
> filetools(getExtFromContents)
> Couldn't find a known Type!
> will use ext or a "user" defined format
> don't unzip file or export latex/home/lahaye/figures/newfig.agr
> [...]
On Friday 01 March 2002 12:48 pm, R. Lahaye wrote:
> Angus Leeming wrote:
> >
> > On Friday 01 March 2002 12:27 pm, R. Lahaye wrote:
> > >
> > > I suppose this is a general problem with the conversion mechanism
> > > and exporting latex, isn't it?
> > >
> > > As it is now, the latex file is
On Fri, 1 Mar 2002, Angus Leeming wrote:
> In my lyxrc.defaults I have
>
> \Format graceagr GRACE ""
> \converter agr eps "xmgrace -hardcopy -hdevice EPS $$i" ""
>
> If you don't, then you should
> cvs update
> autogen.sh
> configure
> You shouldn't need to
66 matches
Mail list logo
