images.Text: Add option for horizontal alignment

[jlskuz]

Please note that this is my first contribution to Hugo and also the first time I wrote something in Go. Please let me know if I missed anything and I will try my best to correct it.

Add an "alignx" option to the images.Text to control whether the value of the "x" option is the left border of the text (current behaviour), the center of each line or the right border.

Fixes #10849

Example with "alignx" "left":

Example with "alignx" "center":

Example with "alignx" "right":

[CLAassistant]

All committers have signed the CLA.

[jlskuz]

@bep Thanks for the review all your comments should be addressed now.

[jmooring]

This work fine, you just have to get the image before setting the options in order to calculate x offset...

{{ $fontPath := "https://github.com/google/fonts/raw/main/ofl/lato/Lato-Regular.ttf" }}
{{ $imagePath := "images/original.jpg" }}
{{ $text := "A kitten!" }}

{{ with try (resources.GetRemote $fontPath) }}
  {{ with .Err }}
    {{ errorf "%s" . }}
  {{ else with .Value }}
    {{ $font := . }}
    {{ with resources.Get $imagePath }}
      {{ $opts := dict
        "color" "#fbfaf5"
        "font" $font
        "linespacing" 8
        "size" 120
        "x" (div .Width 2 | int)
        "y" 50
        "alignx" "center"
      }}
      {{ $filter := images.Text $text $opts }}
      {{ with . | images.Filter $filter }}
        <img src="{{ .RelPermalink }}" width="{{ .Width }}" height="{{ .Height }}" alt="">
      {{ end }}
    {{ else }}
      {{ errorf "%s" "Unable to get resource %q" $imagePath }}
    {{ end }}
  {{ else }}
    {{ errorf "Unable to get resource %q" $fontPath }}
  {{ end }}
{{ end }}

[jlskuz]

Is there an easy way to re-trigger the tests myself? I fixed them.

Also I opened #13232 to add the ./check_gofmt.sh step to the development guide

[bep]

Is there an easy way to re-trigger the tests myself? I fixed them.

No.

There is a restriction in GitHub for first time contributors of a repository, it requires someone to Approve each PR build (which I guess makes sense, else spam bots would go bananas creating new CI builds).

Once this is merged, any new PR or push to a PR branch from you will trigger a build without any ceremony.