Of course you don't have to rotate original files. Also, the correct POV is that you don't move/rotate/scale images or any other graphic objects. It's coordinate system that's being transformed, and changes are cumulative. Instead of keeping track of transforms applied so far, use push/pop stack frame, returning each time to unscaled/unrotated LL page corner as 0,0.

In fact, the "image" method does save/transform(translate to X,Y and scale to WxH)/restore, because image is 1x1 box "filled" with all its pixels. So there are now several transforms and stack frames for each image. That may seem wasteful but it isn't. Be generous with "save"/"restore" calls if required. (What's wasteful is importing the same image 16 times, but it's done only for sake of illustration.)

The "translate" and "image" calls could be combined in obvious way, and you can omit centering images inside A4 boxes altogether, if they are A4 as you say.

use strict;
use warnings;
use LWP::Simple;
use PDF::API2;

use constant {
    JPG => 'jpg.jpg',
    PDF => 'pdf.pdf',
    URL => 'https://jpeg.org/images/jpeg-home.jpg',
    A4W => 595,
    A4H => 842,
    RES => 72,  # image above is at 72 dpi
};

-f JPG 
    or is_success getstore URL, JPG
    or die;

my $pdf = PDF::API2-> new;
my $page = $pdf-> page;
$page-> mediabox( 'A0' );
my $content = $page-> gfx;

for my $row ( 0 .. 3 ) {
    for my $col ( 0 .. 3 ) {
        $content-> save;
        $content-> transform(
            -translate => [ A4W + $row * A4W, $col * A4H ],
            -rotate    => 90,
        );
        my $jpeg = $pdf-> image_jpeg( JPG );
        my $w = 72 / RES * $jpeg-> width; 
        my $h = 72 / RES * $jpeg-> height;
        
        $content-> translate(( A4H - $w )/2, ( A4W - $h )/2 );
        $content-> image( $jpeg, 0, 0, 72 / RES );
        $content-> restore;
    }
}
$pdf-> saveas( 'pdf.pdf' );

[download]

In reply to Re: Making a 4 x 4 of rotated images (PDF::API2) by vr
in thread Making a 4 x 4 of rotated images (PDF::API2) by cristofayre

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.