[Gimp-developer] Asking for help/collaboration in nonprofit mini-project around covid-19

Thank you Ofnuts, Ken and Pat for your quick responses.
I can take advantage of something from each of your contributions.
I don't know about ImageMagic, but the shell scripting is one of my best. I
have reading and work for a few days.
If I get everything to work I will notify in this forum, in case someone
wants to use or share it.

Till then kind regards

Un cordial saludo,


*Pedro Cáliz*


El sáb., 2 may. 2020 a las 4:45, <[email protected]>
escribió:

> ------------------------------
> Message: 2
> Date: Fri, 1 May 2020 23:21:18 +0200
> From: Ofnuts <[email protected]>
> Subject: Re: [Gimp-developer] Asking for help/collaboration in
>         nonprofit mini-project around covid-19
> Message-ID: <[email protected]>
>
> Typically done with ImageMagick: https://imagemagick.org/index.php
>
> Some features:
>
> https://imagemagick.org/Usage/resize/
>
> https://imagemagick.org/Usage/text/
>
> ------------------------------
> Message: 4
> Date: Sat, 2 May 2020 02:24:11 +0100
> From: Ken Moffat <[email protected]>
> Subject: Re: [Gimp-developer] Asking for help/collaboration in
>         nonprofit mini-project around covid-19
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=utf-8
>
> On Fri, May 01, 2020 at 11:21:18PM +0200, Ofnuts wrote:

Probably getting a bit OT for gimp-dev, but I'll reply here anyway
> this time.
>
> For the rest, typically done with shell script(s) from bash since
> all you are doing is invoking programs with some options, e.g. 'cp'
> to move files from 'A' to 'C' IFF (if and only if) the modifications
> to create the file in B did not end in failure.
>
> Obviously, set aside some work space to play around with a *copy*
> of a file and then when the modifications seem to work on that file,
> try a copy of a different file.
>
> I've done the resizing in the past but I've never tried adding text
> on top, or borders.
>
> But the fun part will be downloading everything from the original
> directory, and then wiping out everything that is there, without
> losing anything that comes in after you have started the download.
>
> Perhaps list everything currently at the directory, wget each item
> in turn checking for no errors (e.g. full disk, non-responsive
> external server) make a backup (did I mention the aggravation caused
> by losing something someone sent you?) and only then rm the file
> from the original.
>
> Or do the rm at the end, but perhaps keeping a separate file of those
> jpegs you have successfully downloaded and adding the details to that
> file after tou have successfully downloaded a file.
>
> For IM there are lots of posts online.
>
> I've in the past used it to resize a batch of photos, the salient
> points were (from a bash script which was modifying the original
> in-place):
>
> for F in $*; do
>         echo "Processing $F" # I like scripts to keep me informed
>
>         # confirm it really is a jpeg, and find its dimensions
>         DIMENSIONS=$(identify $F | grep JPEG | awk '{ print $3}')
>         if [ -z "$DIMENSIONS" ]; then
>                 echo "ERROR: $F seems not to be a jpeg"
>                 exit 1
>         fi
>         WIDTH=$(echo $DIMENSIONS | cut -d 'x' -f1)
>         DEPTH=$(echo $DIMENSIONS | cut -d 'x' -f2)
>
>         if [ $WIDTH -gt 2048 ] || [ $DEPTH -gt 2048 ]; then
>                 mogrify -resize 2048x2048 $F
>         else
>                 echo "$F not resized, is only $WIDTH x $DEPTH"
>         fi
> done
>
> As with all old scripts, or hunks you find online, replace active
> commands by a comment of what will happen when doing it the first
> time, so in this case comment out the mogrify and add e.g.
>                 echo "will resize usign mogrify"
> or alternatively for a simple command like that just try the command
> on a copied jpeg to confirm it, and any other options you add, do
> the right think (then use 'identify' and 'display' afterwards).
>
> You might also need to consider how much upload space you have, and
> bandwidth for people viewing, if this becomes popular.  I'm guessing
> a jpeg of max dimension 2048 will typically be less than 2 MB, but
> YMMV.
>
> Also, you'll want to review the results at full size, even if most
> people have screens which are smaller than 2048x2048.
>
> ?en
> --
>                  See You Later, Holy Poppadom!
>                     -- Red Dwarf, The Promised Land
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 1 May 2020 21:45:17 -0500
> From: Pat David <[email protected]>
> To: Ken Moffat <[email protected]>
> Subject: Re: [Gimp-developer] Asking for help/collaboration in
>         nonprofit mini-project around covid-19
> Message-ID:
>         <CAPC+-knVHpiUDg6ZmC-5wTxKBmrCEY=
> [email protected]>
> Content-Type: text/plain; charset="UTF-8"
>
> Also, not sure if it?s helpful but we wrote a simple imagemagick command
> for something similar to what you?re asking for:
>
>
> https://discuss.pixls.us/t/annotation-with-imagemagick-watermark-ish/1813?u=patdavid
>
> Might have some luck with other ideas there for what you?re trying to do
> (or the gimp-user list).
>
> hth
>
> On Fri, May 1, 2020 at 8:31 PM Ken Moffat via gimp-developer-list <
> [email protected]> wrote:
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> End of gimp-developer-list Digest, Vol 104, Issue 3
> ***************************************************
>
_______________________________________________
gimp-developer-list mailing list
List address:    [email protected]
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list