From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: heic to jpg conversion
Date: Thu, 13 Aug 2020 13:56:44 +0200 [thread overview]
Message-ID: <2817e5ee-efba-5eed-e9cc-d6b11feb9bde@towo.net> (raw)
In-Reply-To: <f5f4d234-2439-a117-8f1a-1c90b9c55108@gmail.com>
Am 13.08.2020 um 12:13 schrieb Marco Atzeri via Cygwin:
> On 13.08.2020 10:18, Thomas Wolff wrote:
>> Am 13.08.2020 um 09:54 schrieb Fergus Daly via Cygwin:
>>> Does Cygwin include the capability to convert heic to jpg (or png or
>>> anything else Windows-readable)?
>>> I tried "convert" (previously all-powerful) but that does not work
>>> (in any obvious way, anyway).
>> Works for me. What does `type convert` say?
>> --
>
> Thomas,
> are you sure ?
Well, no, I just ran a simple test case which seems to have misled me.
`convert x.jpg x.heic` did produce an image file with suffix .heic,
without any complaint. However, `file x.heic` would identify it as JPEG
format. Weird.
>
> looking at the documentation
> https://imagemagick.org/script/formats.php
>
> we need libheif to support that format and
> we have not yet it.
>
> As expected
> identify -list format | grep -i heic
>
> output is empty.
>
> I will look on it.
>
> Regards
> Marco
>
>
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2020-08-13 11:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 7:54 Fergus Daly
2020-08-13 8:18 ` Thomas Wolff
2020-08-13 10:13 ` Marco Atzeri
2020-08-13 11:56 ` Thomas Wolff [this message]
2020-08-13 10:13 ` Fergus Daly
2020-08-13 15:15 ` Brian Inglis
2020-08-13 18:58 ` Marco Atzeri
2020-08-14 19:12 ` Marco Atzeri
2020-08-16 7:10 Fergus Daly
2022-10-01 13:57 ambrose huang
2022-10-01 16:07 ` Andrey Repin
2022-10-02 10:56 Fergus Daly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2817e5ee-efba-5eed-e9cc-d6b11feb9bde@towo.net \
--to=towo@towo.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).