Depending on capitalization of --loader argument, --unicode fails

[GBember01]

If I run efibootmgr -c -d /dev/nvme0n1 -p 1 -L "Gentoo via Shim" -l '\EFI\gentoo\shimx64.efi' -u '\EFI\gentoo\bzImage.efi'
It tries to add \EFI\gentoo\bzImage.efi as another file to boot resulting in
Boot0003* Gentoo via Shim HD(1,GPT,c12a7328-f81f-11d2-ba4b-00a0c93ec93b,0x800,0x200000)/File(\EFI\gentoo\shimx64.efi) File(.\EFI\gentoo\bzImage.efi)

But if I instead run efibootmgr -c -d /dev/nvme0n1 -p 1 -L "Gentoo via Shim" -l '\efi\gentoo\shimx64.efi' -u '\EFI\gentoo\bzImage.efi'
Notice the "\efi" instead of "\EFI"
It generates a proper entry
Boot0003* Gentoo via Shim HD(1,GPT,c12a7328-f81f-11d2-ba4b-00a0c93ec93b,0x800,0x200000)/File(\efi\gentoo\shimx64.efi)\EFI\gentoo\bzImage.efi with "\EFI\gentoo\bzImage.efi" as an argument

I'm running efibootmgr 18-r1

[GBember01]

It seems to work properly on 17-r1

[GBember01]

After updating back to 18-r1, I'm not sure what's happening here, the entry still is Boot0003* Gentoo via Shim HD(1,GPT,c12a7328-f81f-11d2-ba4b-00a0c93ec93b,0x800,0x200000)/File(\EFI\gentoo\shimx64.efi) File(.\EFI\gentoo\bzImage.efi),
so it might just be an error when printing the boot entry, and not when writing it