Closed 1sixth closed 3 years ago
Thanks for reaching out!
I will have a look what we can do. Docker has the same issue. The underlying problem is that we're counting characters which are not equally wide in this case.
The � issue looks like a terminal issue rather than a Podman issue.
Regarding the correct alignment of the table, I fear that this will be hard. Even the tabwriter package [1] assumes that all characters have the same width.
The � issue looks like a terminal issue rather than a Podman issue.
You are right. I just tried kitty/0.20.3
and no �
gets printed.
Thanks for checking, @1sixth!
I fear that there's nothing much Podman can do for the table formatting. It's based on the assumption that all characters have an equal width (same for the Go standard library).
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman search
sometimes prints�
if the image description contains CJK characters.Columns after DESCRIPTION don't line up properly if the image description contains CJK characters.
Steps to reproduce the issue:
Run
podman search docker.io/qbittorrent
orpodman search docker.io/qbittorrent --no-trunc
.Describe the results you received:
podman search docker.io/qbittorrent
:podman search docker.io/qbittorrent --no-trunc
:podman search docker.io/debian
:You can see that everything works as expected if the image description is ASCII-only.
Describe the results you expected:
I expect no
�
printed (unless some image author delibrately puts it in the description), and columns after DESCRIPTION should line up properly.Additional information you deem important (e.g. issue happens only occasionally):
I use
alacritty/0.8.0
as my terminal emulator. Everything mentioned above happens even when I pass--config-file /dev/null
toalacritty
.If you want to test Japanese characters, try
podman search docker.io/japanese-nlp
.Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes.
Additional environment details (AWS, VirtualBox, physical, etc.):