That’s because you are trying to call a single field in the nested builder when you have to get the snippets for the nested builder snippets/fieldsets in your historyimagethinby snippet first.
You can translate file meta data just like you can translate page content, that’s not the issue. But whether or not that is the most elegant solution or not, that depends on what you want to achieve.
I haven’t used a nested builder field yet, so I can’t really give you advice from the top of my head without testing it first.
Does “metadata” in this case mean the EXIF/IPTC data from the jpg or is my head working in the wrong direction? Could you give me a hint for the meta data thing and how to call it? I am kind of clueless, even where to start searching.
I thought this nested field was rather a standard operation… so now I absolutely understand you!
This is what your historyimagepair.php snippet would probably have to look like (for your original nested builder)
<div>
<?php foreach($block->imagelist()->toBuilderBlocks() as $subBlock): ?>
<!-- this is the snippet for the _img block -->
<?php if($file = $subBlock->images()->toFile()): ?>
<figure>
<img src="<?= $file->url() ?>" alt="">
<figcaption><?= $subBlock->caption()->kt() ?></figcaption>
</figure>
<?php endif ?>
<!-- end of images block snippet -->
<?php endforeach ?>
</div>
Note that I use $block instead of $data (you would have to change that to fit your variable)
This will work without additional snippets, because inside the nested fieldset, there is only a single fieldset. If you were to use different fieldsets, you would have to call the corresponding snippets again.