Am 03.10.2017 um 22:06 schrieb Kornel Benko :
>
> Am Dienstag, 3. Oktober 2017 um 19:59:38, schrieb Stephan Witt
>
>> Am 02.10.2017 um 02:04 schrieb Kornel Benko :
>>>
>>> Am Sonntag, 1. Oktober 2017 um 22:16:43, schrieb Stephan Witt
>>>
Am Dienstag, 3. Oktober 2017 um 19:59:38, schrieb Stephan Witt
> Am 02.10.2017 um 02:04 schrieb Kornel Benko :
> >
> > Am Sonntag, 1. Oktober 2017 um 22:16:43, schrieb Stephan Witt
> >
> >> Am 01.10.2017 um 10:20 schrieb Kornel Benko
On Tue, Oct 03, 2017 at 06:36:03PM +, Stephan Witt wrote:
>
> > Am 01.10.2017 um 06:59 schrieb Stephan Witt :
> >
> > Am 30.09.2017 um 20:15 schrieb Scott Kostyshak :
> >>
> >> On Wed, Sep 20, 2017 at 09:11:53PM +, Scott Kostyshak wrote:
> >>
>
> Am 01.10.2017 um 06:59 schrieb Stephan Witt :
>
> Am 30.09.2017 um 20:15 schrieb Scott Kostyshak :
>>
>> On Wed, Sep 20, 2017 at 09:11:53PM +, Scott Kostyshak wrote:
>>
But this is too complex for 2.3.0, IMO. So I’d put my patch in and
let
Am 02.10.2017 um 02:04 schrieb Kornel Benko :
>
> Am Sonntag, 1. Oktober 2017 um 22:16:43, schrieb Stephan Witt
>
>> Am 01.10.2017 um 10:20 schrieb Kornel Benko :
>>>
>>> Am Sonntag, 1. Oktober 2017 um 06:59:51, schrieb Stephan Witt
>>>
Am Sonntag, 1. Oktober 2017 um 22:16:43, schrieb Stephan Witt
> Am 01.10.2017 um 10:20 schrieb Kornel Benko :
> >
> > Am Sonntag, 1. Oktober 2017 um 06:59:51, schrieb Stephan Witt
> >
> >> Am 30.09.2017 um 20:15 schrieb Scott Kostyshak
Am 01.10.2017 um 10:20 schrieb Kornel Benko :
>
> Am Sonntag, 1. Oktober 2017 um 06:59:51, schrieb Stephan Witt
>
>> Am 30.09.2017 um 20:15 schrieb Scott Kostyshak :
>>>
>>> On Wed, Sep 20, 2017 at 09:11:53PM +, Scott Kostyshak wrote:
>>>
Am Sonntag, 1. Oktober 2017 um 06:59:51, schrieb Stephan Witt
> Am 30.09.2017 um 20:15 schrieb Scott Kostyshak :
> >
> > On Wed, Sep 20, 2017 at 09:11:53PM +, Scott Kostyshak wrote:
> >
> >>> But this is too complex for 2.3.0, IMO. So I’d put my patch in
Am 30.09.2017 um 20:15 schrieb Scott Kostyshak :
>
> On Wed, Sep 20, 2017 at 09:11:53PM +, Scott Kostyshak wrote:
>
>>> But this is too complex for 2.3.0, IMO. So I’d put my patch in and
>>> let some nice guys change the splash files.
>
> From what I understand, after your
On Wed, Sep 20, 2017 at 09:11:53PM +, Scott Kostyshak wrote:
> > But this is too complex for 2.3.0, IMO. So I’d put my patch in and
> > let some nice guys change the splash files.
From what I understand, after your most recent patch is put in 2.3.x, we
no longer need a patch for the splash
On Sun, Sep 24, 2017 at 12:24:26PM +0200, Stephan Witt wrote:
>
> This is the solution I’d like to propose. It’s not tested on Linux and
> Windows.
>
> The idea is to add imgconvert as fallback-converter for SVG to PDF and PNG to
> PDF.
> At the moment it uses the Qt library routines for image
Am 24.09.2017 um 12:24 schrieb Stephan Witt :
>
> Am 21.09.2017 um 15:08 schrieb Stephan Witt :
>>
>> Am 21.09.2017 um 14:54 schrieb Enrico Forestieri :
>>>
>>> On Thu, Sep 21, 2017 at 11:43:29AM +0200, Stephan Witt wrote:
My question
Am 21.09.2017 um 15:08 schrieb Stephan Witt :
>
> Am 21.09.2017 um 14:54 schrieb Enrico Forestieri :
>>
>> On Thu, Sep 21, 2017 at 11:43:29AM +0200, Stephan Witt wrote:
>>>
>>> My question (again): how can I circumvent this and configure „my“ converter
>>> so
On 2017-09-21, Stephan Witt wrote:
> Am 21.09.2017 um 09:50 schrieb Jürgen Spitzmüller :
>> 2017-09-20 22:20 GMT+02:00 Stephan Witt :
...
> ... the mentioned fallback means LyX is able to show the document with
> SVG on screen using internal Qt when converters are
On Fri, Sep 22, 2017 at 11:26:47AM +0200, Enrico Forestieri wrote:
>
> If you want to preserve the vector format, you could also try to
> statically link the following:
> https://github.com/openclipart-dev/svg2pdf
In which case, the following may also be of interest to you:
On Thu, Sep 21, 2017 at 03:08:45PM +0200, Stephan Witt wrote:
> Am 21.09.2017 um 14:54 schrieb Enrico Forestieri :
> > On Thu, Sep 21, 2017 at 11:43:29AM +0200, Stephan Witt wrote:
> >>
> >> My question (again): how can I circumvent this and configure „my“ converter
> >> so it’s
Am 21.09.2017 um 14:54 schrieb Enrico Forestieri :
>
> On Thu, Sep 21, 2017 at 11:43:29AM +0200, Stephan Witt wrote:
>>
>> My question (again): how can I circumvent this and configure „my“ converter
>> so it’s used to convert the SVG to PNG and run pdflatex with the PNG instead
On Thu, Sep 21, 2017 at 11:43:29AM +0200, Stephan Witt wrote:
>
> My question (again): how can I circumvent this and configure „my“ converter
> so it’s used to convert the SVG to PNG and run pdflatex with the PNG instead
> of the PDF (which would be rasterized anyway, when ImageMagick is used for
Am 21.09.2017 um 11:31 schrieb Guenter Milde :
>
> On 2017-09-20, Scott Kostyshak wrote:
>> On Wed, Sep 20, 2017 at 10:20:04PM +0200, Stephan Witt wrote:
>
>>> Shouldn’t the Linux packagers
>>> made aware of the dependency of LyX on Inkscape?
>
> On Linux, we have working
Am 21.09.2017 um 09:50 schrieb Jürgen Spitzmüller :
>
> 2017-09-20 22:20 GMT+02:00 Stephan Witt :
> > The current situation is not worse than 2.2.x, right? In other words,
> > there is no regression with regards to 2.2.x, but an argument could be
> > made that
On 2017-09-20, Scott Kostyshak wrote:
> On Wed, Sep 20, 2017 at 10:20:04PM +0200, Stephan Witt wrote:
>> Shouldn’t the Linux packagers
>> made aware of the dependency of LyX on Inkscape?
On Linux, we have working alternatives to Inkscape (rsvgbased).
> I don't know. Currently, the "lyx" package
2017-09-20 22:20 GMT+02:00 Stephan Witt :
> > The current situation is not worse than 2.2.x, right? In other words,
> > there is no regression with regards to 2.2.x, but an argument could be
> > made that there is a regression (from the user perspective) with respect
> > to
On Wed, Sep 20, 2017 at 10:20:04PM +0200, Stephan Witt wrote:
> I’m in favor of a working SVG to PNG conversion for systems without a
> SVG to PDF or EPS converter.
> Ideally for inset-info only and for SVG
> graphic insets presenting an error message.
Interesting idea to consider. I wonder if
Am 20.09.2017 um 20:22 schrieb Scott Kostyshak :
>
> On Mon, Sep 18, 2017 at 10:21:46AM +0200, Stephan Witt wrote:
>> Am 18.09.2017 um 05:55 schrieb Scott Kostyshak :
>>>
>>> On Sun, Sep 17, 2017 at 06:24:46PM +0200, Stephan Witt wrote:
>>>
> Den 13. sep.
On Mon, Sep 18, 2017 at 10:21:46AM +0200, Stephan Witt wrote:
> Am 18.09.2017 um 05:55 schrieb Scott Kostyshak :
> >
> > On Sun, Sep 17, 2017 at 06:24:46PM +0200, Stephan Witt wrote:
> >
> >>> Den 13. sep. 2017 03:29, skrev Scott Kostyshak:
> It actually amazes me how few
Am 18.09.2017 um 05:55 schrieb Scott Kostyshak :
>
> On Sun, Sep 17, 2017 at 06:24:46PM +0200, Stephan Witt wrote:
>
>>> Den 13. sep. 2017 03:29, skrev Scott Kostyshak:
It actually amazes me how few people care about including bitmaps
>>
>> I certainly care too.
>
>
Am 18.09.2017 um 08:36 schrieb Jürgen Spitzmüller :
>
> Am Sonntag, den 17.09.2017, 22:51 +0200 schrieb Stephan Witt:
>> I’ve just learned that the converter calls for on-screen display in
>> build_script in GraphicsConverter.cpp and for export to pdf seem to
>> have different
Am 17.09.2017 um 22:51 schrieb Stephan Witt :
>
> Am 17.09.2017 um 21:07 schrieb Stephan Witt :
>>
>> Am 17.09.2017 um 19:48 schrieb Jürgen Spitzmüller :
>>>
>>> Am Sonntag, den 17.09.2017, 15:26 +0200 schrieb Stephan Witt:
Because of the
Am Sonntag, den 17.09.2017, 22:51 +0200 schrieb Stephan Witt:
> I’ve just learned that the converter calls for on-screen display in
> build_script in GraphicsConverter.cpp and for export to pdf seem to
> have different interpretation of $$i ???
>
> SVG to PNG works with $$i resp. $$o and not with
On Sun, Sep 17, 2017 at 06:24:46PM +0200, Stephan Witt wrote:
> > Den 13. sep. 2017 03:29, skrev Scott Kostyshak:
> >> It actually amazes me how few people care about including bitmaps
>
> I certainly care too.
Rereading the email I sent, it could easily be interpreted as though I
was implying
Am 17.09.2017 um 21:07 schrieb Stephan Witt :
>
> Am 17.09.2017 um 19:48 schrieb Jürgen Spitzmüller :
>>
>> Am Sonntag, den 17.09.2017, 15:26 +0200 schrieb Stephan Witt:
>>> Because of the change directory coded in inkscape starter the $$i for
>>> the
>>> input
Am 17.09.2017 um 19:48 schrieb Jürgen Spitzmüller :
>
> Am Sonntag, den 17.09.2017, 15:26 +0200 schrieb Stephan Witt:
>> Because of the change directory coded in inkscape starter the $$i for
>> the
>> input file name leads to a „file not found“ error. With a change to
>> inkscape
Am Sonntag, den 17.09.2017, 15:26 +0200 schrieb Stephan Witt:
> Because of the change directory coded in inkscape starter the $$i for
> the
> input file name leads to a „file not found“ error. With a change to
> inkscape —file=$$p/$$i --export-area-drawing --without-gui --export-
> pdf=$$p/$$o
Am Sonntag, den 17.09.2017, 19:15 +0200 schrieb Stephan Witt:
> But I need to change configure.py to call inkscape with full path
> names
> for the input image and the conversion result to get it work.
>
> Do you think this is a problem?
No. But remember to do that also for the svg2*tex scripts
> Am 17.09.2017 um 18:41 schrieb Jürgen Spitzmüller :
>
> Am Sonntag, den 17.09.2017, 18:01 +0200 schrieb Stephan Witt:
>>> It does. See how we deal with inkscape on windows.
>>
>> Yes, and I don’t like it. How do you deal with it on Linux?
>
> Linux doesn't need the full path,
Am Sonntag, den 17.09.2017, 18:01 +0200 schrieb Stephan Witt:
> > It does. See how we deal with inkscape on windows.
>
> Yes, and I don’t like it. How do you deal with it on Linux?
Linux doesn't need the full path, unless you are using some customized
build. But then, I would set the full path
Am 15.09.2017 um 15:13 schrieb Helge Hafting :
>
>
>
> Den 13. sep. 2017 03:29, skrev Scott Kostyshak:
>> It actually amazes me how few people care about including bitmaps
>> graphics in their final meant-for-publication drafts. I wonder if I am
>> the only one that is
Am 17.09.2017 um 17:44 schrieb Jürgen Spitzmüller :
>
> Am Sonntag, den 17.09.2017, 15:26 +0200 schrieb Stephan Witt:
>> I’ve made a test. The cost for 200 calls of the pure shell script
>> /Applications/Inkscape.app/Contents/Resources/bin/inkscape
>> is 0m52.436s real. The cost
Am Sonntag, den 17.09.2017, 15:26 +0200 schrieb Stephan Witt:
> I’ve made a test. The cost for 200 calls of the pure shell script
> /Applications/Inkscape.app/Contents/Resources/bin/inkscape
> is 0m52.436s real. The cost for 200 calls of the lyx-provided
> wrapper lyx/development/MacOSX/inkscape
Am 17.09.2017 um 08:03 schrieb Jürgen Spitzmüller :
>
> Am Samstag, den 16.09.2017, 20:46 +0200 schrieb Stephan Witt:
>> No, it doesn’t work.
>
> Why?
Because it doesn’t find the binary.
> 1) inkscape-bin is in
>> /Applications/Inkscape.app/Contents/Resources/bin
>
> And then
> Can't we make it pass the full pathname rather than just the
> filename?
And that's exactly what my approach is trying to do.
Jürgen
>
> Richard
>
signature.asc
Description: This is a digitally signed message part
Am Samstag, den 16.09.2017, 20:46 +0200 schrieb Stephan Witt:
> No, it doesn’t work.
Why?
> 1) inkscape-bin is in
> /Applications/Inkscape.app/Contents/Resources/bin
And then type does not find it, or what is the problem exactly
> 2) additional arguments have to be passed to avoid X-Server
On 09/16/2017 04:33 PM, Stephan Witt wrote:
> Am 16.09.2017 um 22:15 schrieb mn :
>> On 16.09.17 20:46, Stephan Witt wrote:
>>> Am 16.09.2017 um 11:58 schrieb Jürgen Spitzmüller :
> Then we should fix the checkInkscape() routine in configure.py.
> What do you
Am 16.09.2017 um 22:15 schrieb mn :
>
> On 16.09.17 20:46, Stephan Witt wrote:
>> Am 16.09.2017 um 11:58 schrieb Jürgen Spitzmüller :
>
Then we should fix the checkInkscape() routine in configure.py.
What do you need specifically? Full path? How is it
Am 16.09.2017 um 11:58 schrieb Jürgen Spitzmüller :
>
> Am Mittwoch, den 13.09.2017, 11:22 +0200 schrieb Jürgen Spitzmüller:
>> Am Mittwoch, den 13.09.2017, 09:59 +0200 schrieb Stephan Witt:
>>> I fear the detection of Inkscape on Mac is not correct. The python
>>> scripts assume
Am Mittwoch, den 13.09.2017, 11:22 +0200 schrieb Jürgen Spitzmüller:
> Am Mittwoch, den 13.09.2017, 09:59 +0200 schrieb Stephan Witt:
> > I fear the detection of Inkscape on Mac is not correct. The python
> > scripts assume the binary is inkscape if not on windows.
>
> Then we should fix the
On Wed, Sep 13, 2017 at 10:06:04AM +0200, Pavel Sanda wrote:
> So they might even
> see that the image in output pdf is somewhat blurry but the link between that
> and tiff format submitted is not there.
I can see that. I never know whether to give a comment explaining the
issue when I read PDF
Den 13. sep. 2017 03:29, skrev Scott Kostyshak:
It actually amazes me how few people care about including bitmaps
graphics in their final meant-for-publication drafts. I wonder if I am
the only one that is annoyed when I am reading a PDF and see a bitmap
that should be a vector graphic.
I
On 2017-09-13, Pavel Sanda wrote:
> Stephan Witt wrote:
>> BTW, I didn???t say the installation of ImageMagick is useless. My
>> point is: LyX shouldn???t present error messages on preview of the
>> documentation as a PDF-document. That???s why I???m trying to
>> establish a conversion path from
Am Mittwoch, den 13.09.2017, 11:53 +0200 schrieb Stephan Witt:
> Am 13.09.2017 um 11:22 schrieb Jürgen Spitzmüller :
> >
> > Am Mittwoch, den 13.09.2017, 09:59 +0200 schrieb Stephan Witt:
> > > I fear the detection of Inkscape on Mac is not correct. The
> > > python
> > > scripts
Am 13.09.2017 um 11:22 schrieb Jürgen Spitzmüller :
>
> Am Mittwoch, den 13.09.2017, 09:59 +0200 schrieb Stephan Witt:
>> I fear the detection of Inkscape on Mac is not correct. The python
>> scripts assume the binary is inkscape if not on windows.
>
> Then we should fix the
Am Mittwoch, den 13.09.2017, 09:59 +0200 schrieb Stephan Witt:
> I fear the detection of Inkscape on Mac is not correct. The python
> scripts assume the binary is inkscape if not on windows.
Then we should fix the checkInkscape() routine in configure.py. What do
you need specifically? Full path?
Am 13.09.2017 um 03:29 schrieb Scott Kostyshak :
>
> On Wed, Sep 13, 2017 at 01:59:55AM +0200, Stephan Witt wrote:
>
>> That’s why I’m trying to establish a conversion path from LyX+SVG-icons to
>> PDF-output via PNG.
>
> If this is implemented and the .lyx files contains an
Stephan Witt wrote:
> >> BTW, I didn???t say the installation of ImageMagick is useless. My point
> >> is: LyX shouldn???t present error messages on preview of the documentation
> >> as a PDF-document. That???s why I???m trying to establish a conversion
> >> path from LyX+SVG-icons to
Scott Kostyshak wrote:
> It actually amazes me how few people care about including bitmaps
> graphics in their final meant-for-publication drafts. I wonder if I am
> the only one that is annoyed when I am reading a PDF and see a bitmap
> that should be a vector graphic.
My experience is that
Am 13.09.2017 um 09:13 schrieb Pavel Sanda :
>
> Stephan Witt wrote:
>> BTW, I didn???t say the installation of ImageMagick is useless. My point is:
>> LyX shouldn???t present error messages on preview of the documentation as a
>> PDF-document. That???s why I???m trying to
Stephan Witt wrote:
> BTW, I didn???t say the installation of ImageMagick is useless. My point is:
> LyX shouldn???t present error messages on preview of the documentation as a
> PDF-document. That???s why I???m trying to establish a conversion path from
> LyX+SVG-icons to PDF-output via PNG. I
On Wed, Sep 13, 2017 at 01:59:55AM +0200, Stephan Witt wrote:
> That’s why I’m trying to establish a conversion path from LyX+SVG-icons to
> PDF-output via PNG.
If this is implemented and the .lyx files contains an included .svg as a
graphic, then it would also be converted to a bitmap for the
Am 11.09.2017 um 20:55 schrieb Pavel Sanda :
>
> Stephan Witt wrote:
>>> If it's not easily possible we should at least make clear to newcomers that
>>> lyx without tex & imagemagick will have lot of problems.
>>
>> LyX without TeX is a problem. This can be solved by a newcomer
Stephan Witt wrote:
> > If it's not easily possible we should at least make clear to newcomers that
> > lyx without tex & imagemagick will have lot of problems.
>
> LyX without TeX is a problem. This can be solved by a newcomer by installing
> MacTeX. Easy.
> LyX without ImageMagick shouldn???t
Le 11/09/2017 à 16:50, mn a écrit :
On 11.09.17 16:18, Stephan Witt wrote:
Am 11.09.2017 um 14:12 schrieb Pavel Sanda :
Stephan Witt wrote:
What can I do to convert the LyX documents containing inset-info
instances without ImageMagick?
ATM, LyX seems to have a hard dependency
On 11.09.17 16:18, Stephan Witt wrote:
> Am 11.09.2017 um 14:12 schrieb Pavel Sanda :
>>
>> Stephan Witt wrote:
>>> What can I do to convert the LyX documents containing inset-info
>>> instances without ImageMagick?
>>>
>>> ATM, LyX seems to have a hard dependency on the
Am 11.09.2017 um 14:12 schrieb Pavel Sanda :
>
> Stephan Witt wrote:
>> What can I do to convert the LyX documents containing inset-info instances
>> without ImageMagick?
>>
>> ATM, LyX seems to have a hard dependency on the ImageMagick tools. On a Mac
>> this implies the
Stephan Witt wrote:
> What can I do to convert the LyX documents containing inset-info instances
> without ImageMagick?
>
> ATM, LyX seems to have a hard dependency on the ImageMagick tools. On a Mac
> this implies the installation of MacPorts of HomeBrew to get it. To do so one
> has to
> Am 10.09.2017 um 20:53 schrieb Scott Kostyshak :
>
> On Sun, Sep 10, 2017 at 11:05:42AM +0200, Stephan Witt wrote:
>> Dear all,
>>
>> I tried to solve the issue with SVG conversion on Mac and now I’m a little
>> bit lost.
>>
>> The facts first:
>>
>> Until MacTeX 2014
On Sun, Sep 10, 2017 at 11:05:42AM +0200, Stephan Witt wrote:
> Dear all,
>
> I tried to solve the issue with SVG conversion on Mac and now I’m a little
> bit lost.
>
> The facts first:
>
> Until MacTeX 2014 there was ImageMagick included in the TeX distribution for
> Mac. Later releases
66 matches
Mail list logo