Publication authors' second names are generated with lowercase letters (randomly)

[andrew-test1]

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/HugoBlox/hugo-blox-builder/issues?q=is%3Aissue
• This issue is not a question, feature request, or anything other than a bug report directly related to Hugo Blox Builder. Please post those things on Discord: https://discord.gg/z8wNYzb

Description

Bug in site generation.
The second names of the publication's authors may randomly appear with lowercase letters.

Example

content/ru/publication/journal-article/index.md:

title: "An example journal article"
authors:
- admin
- Robert Ford
- Ivan I. Ivanov
- John V. Meme
- Serge A Tankian
- Pavel A. Escobarov
...

Result:

As a result, the second name sometimes starts with a lowercase letter and sometimes with an uppercase letter.
There is no author's pages in content/authors folder.

Reproduction Link

n/a

Steps to Reproduce

1. Use HugoBlox/theme-research-group
2. Update index.md in the publication folder
3. Deploy on github
   ...

Expected Result

Names are displayed as in index.md: Ivan I. Ivanov, John V. Meme, Serge A Tankian, Pavel A. Escobarov.

Actual Result

Names are not displayed as in index.md: Ivan I. Ivanov, John v. Meme, Serge a Tankian, Pavel A. Escobarov.

What Hugo Module versions does your site use?

github.com/wowchemy/starter-hugo-research-group
go 1.15

What operating system(s) are you seeing the problem on?

Windows

What browser(s) are you seeing the problem on?

No response

Which Hugo Blox template are you using?

theme-research-group

What version of Hugo are you using?

0.135.0

[github-actions]

This issue is stale because it has not had any recent activity. The resources of the project maintainers are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the main branch, consider contributing a Pull Request with a fix.

If this is a feature request, and you feel that it is still relevant and valuable, consider contributing a Pull Request for review.

This issue will automatically close soon if no further activity occurs. Thank you for your contributions.