Re: How to setup image converters on Mac?

[Stephan Witt]

> 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 there was ImageMagick included in the TeX distribution for 
>> Mac. Later releases don’t have it anymore.
> 
> Do you happen to know why? (don't search if you don't, I'm just
> curious).

It’s explained here:

https://www.tug.org/mactex/TeXLive2017+Changes.pdf

"… because tex4ht, the only program supplied by TEX live that used convert, no 
longer requires that program.“

Stephan

Re: Any rc1 blockers?

[Scott Kostyshak]

On Fri, Sep 08, 2017 at 07:54:02AM +0200, Stephan Witt wrote:
> Am 08.09.2017 um 04:30 schrieb Scott Kostyshak :
> > 
> > Dear all,
> > 
> > I think most would agree that the 2.3.x branch is quite stable, and I'm
> > satisfied that 2.3.0beta1 has received a significant amount of testing.
> > I think we should start thinking about rc1. If anyone disagrees and
> > prefers to release a beta2 first instead, please let me know now.
> > 
> > Assuming everyone is fine with moving towards rc1, are there any issues
> > that you view as rc1 blockers?
> 
> Yes, the missing SVG resp. SVGZ converter for the inset-icon instances
> in splash.lyx and other help documents on Mac is not solved yet.

Thanks, Stephan. I agree we should fix that.

Scott


signature.asc
Description: PGP signature

Re: Any rc1 blockers?

[Scott Kostyshak]

On Sun, Sep 10, 2017 at 01:38:26AM +0200, Uwe Stöhr wrote:
> El 08.09.2017 a las 04:30, Scott Kostyshak escribió:
> 
> > I think we should start thinking about rc1.
> 
> Fine with me. Just the patch for
> http://www.lyx.org/trac/ticket/10679
> should go in before. Then the new 2.3.0 feature of supporting SVG+text files
> will also work under Windows.

Sounds good. Thanks to you and Jürgen for making progress on that.

Scott


signature.asc
Description: PGP signature

Re: How to setup image converters on Mac?

[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 there was ImageMagick included in the TeX distribution for 
> Mac. Later releases don’t have it anymore.

Do you happen to know why? (don't search if you don't, I'm just
curious).

Scott


signature.asc
Description: PGP signature

Re: upgrading to libiconv 1.15 for LyX 2.3

[Scott Kostyshak]

On Sun, Sep 10, 2017 at 02:51:36PM +0200, Uwe Stöhr wrote:
> While reporting compiler warnings in libiconv 1.14 I noticed that version
> 1.15 was released in February this year. So I grabbed the sources from
> https://ftp.gnu.org/pub/gnu/libiconv/
> and updated them in our git master.
> 
> It compiles fine and works fine here.
> I don't know about Linux. If it is uncritical I opt to upgrade libiconv also
> for LyX 2.3.0 before we release it. What do you think?

Looks like the first release in 5 years. Seems like the same maintainer,
and since there hasn't been any emergency release in the past few
months, I would guess it's safe. Does anyone else have an opinion?

By the way, I wonder if it would be nice to collect all of our
dependencies and to check for new versions e.g. before beta1 and update
everything all at once. Do we have such a list?

Scott


signature.asc
Description: PGP signature

Re: iconv warnings

[Uwe Stöhr]

El 10.09.2017 a las 14:18, Uwe Stöhr escribió:

I just compiled the current 2.3.x branch to perform some final tests. I 
noted some avoidable compiler warnings in libiconv, see below


I reported the warnings to the email address and got already a reply. 
They will analyze the signed/unsigned mismatch warnings for future 
releases meanwhile I can ignore them. the other 2 sorts of warnings are 
not explainable in their opinion and I should ignore them too.


regards Uwe

upgrading to libiconv 1.15 for LyX 2.3

[Uwe Stöhr]

While reporting compiler warnings in libiconv 1.14 I noticed that 
version 1.15 was released in February this year. So I grabbed the 
sources from

https://ftp.gnu.org/pub/gnu/libiconv/
and updated them in our git master.

It compiles fine and works fine here.
I don't know about Linux. If it is uncritical I opt to upgrade libiconv 
also for LyX 2.3.0 before we release it. What do you think?


regards Uwe

iconv warnings

[Uwe Stöhr]

I just compiled the current 2.3.x branch to perform some final tests. I 
noted some avoidable compiler warnings in libiconv, see below. The 
question is if we should or could fix this? If we don't do this, does 
anybody know where I can or should report this?

There is a github page:
https://github.com/win-iconv/win-iconv/issues
which seems to be inactive
but also
https://www.gnu.org/software/libiconv/ that suggest a mail address to 
report bugs.


thanks and regards
Uwe

  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\utf7.h(162): warning 
C4018: '<': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\utf7.h(331): warning 
C4018: '<': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\hz.h(39): warning C4018: 
'<': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\hz.h(51): warning C4018: 
'<': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\hz.h(57): warning C4018: 
'<': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\hz.h(65): warning C4018: 
'<': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\hz.h(80): warning C4018: 
'<': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\loop_unicode.h(47): 
warning C4018: '<=': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\loop_unicode.h(91): 
warning C4018: '<=': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\loop_unicode.h(142): 
warning C4018: '<=': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\loop_unicode.h(258): 
warning C4018: '<=': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\loop_unicode.h(418): 
warning C4018: '<=': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\loop_unicode.h(422): 
warning C4018: '<=': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\loop_unicode.h(503): 
warning C4018: '<=': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\loop_unicode.h(519): 
warning C4018: '<=': signed/unsigned mismatch (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
  d:\lyxgit\2.3.x\3rdparty\libiconv\1.14\lib\loop_wchar.h(40): warning 
C4273: 'mbrtowc': inconsistent dll linkage (compiling source file 
D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c) 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]
 D:\LyXGit\2.3.x\3rdparty\libiconv\1.14\lib\iconv.c(427): warning 
C4090: 'function': different 'const' qualifiers 
[D:\LyXGit\2.3.x\compile-2015\3rdparty\libiconv\iconv.vcxproj]

How to setup image converters on Mac?

[Stephan Witt]

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 don’t have it anymore.

I added the home-made SVG2PNG conversion utility from Enrico to my LyX bundle 
and configured it for SVG to PNG conversion. For PNG to PDF I configured a 
converter with the „sips“ command line utility.

LyX seems to assume the presence of the command „convert“ or „magick“. If I 
hide both commands on my system there are converters configured e.g. from SVG 
to PDFTEX using LyX’s python scripts. These scripts obviously are failing 
without these tools.

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 install Xcode from Apple. That’s a big hurdle and I’d like to avoid it 
and stick to the available command line tools.

Regards,
Stephan