Bug#1109154: gpg-key2ps can't display UTF-8 in key uid name

2025-07-13 Thread Guilhem Moulin
Control: tag -1 = pending

On Sat, 12 Jul 2025 at 17:43:27 +0200, Guilhem Moulin wrote:
> AFAIK not and that tool is no longer maintained, I should probably add a
> deprecation warning in the manual page.

Done in 0b206df5e92fd1e2d35e930c3da8053db6319480.

-- 
Guilhem.


signature.asc
Description: PGP signature


Bug#1109154: gpg-key2ps can't display UTF-8 in key uid name

2025-07-12 Thread xiao sheng wen
Hi,

Thanks for your quick reply!

在 2025/7/12 23:43, Guilhem Moulin 写道:
> Hi,
> 
> On Sat, 12 Jul 2025 at 23:27:49 +0800, xiao sheng wen wrote:
>> gpg-key2ps -1 -p a4 [email protected] | gs -sDEVICE=pdfwrite 
>> -sOutputFile=out.pdf
>>
>> My Chinese name in uid display question mark.
>>
>> I tested use only "gpg-key2 [email protected]", I also find it's question 
>> mark
>> in it's output.
>>
>> Is gpg-key2ps support UTF-8 well?
> 
> AFAIK not and that tool is no longer maintained, I should probably add a
> deprecation warning in the manual page.
> 
> I'd suggest to use gpg-key2latex(1) instead (also from signing-party)
> and use XeLaTeX to convert LaTeX output to PDF.  I'm not familiar enough
> with Postscript and wrote gpg-key2latex(1) to workaround that particular
> issue with gpg-key2ps(1), plus other issues such as as feature requests
> for photo IDs and QR codes.  gpg-key2latex(1) is still supported :-)
Yes, use gpg-key2latex(1) is better for CJK word.

After I installed package texlive-lang-cjk, I can get my Chinese name 
correctly. 

I use the following command:

gpg-key2latex -p a4 [email protected]|xelatex

The output pdf filename is texput.pdf.

Perhaps we need to update the wiki:
https://wiki.debian.org/Keysigning#Step_3:_Print_your_key 

in "Use gpg-key2ps to generate a PDF" section. 

Nice to meet you in Brest!

-- 
肖盛文 xiao sheng wen -- Debian Developer(atzlinux)
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40debian.org
Debian salsa: https://salsa.debian.org/atzlinux-guest
GnuPG Public Key: 0x00186602339240CB


OpenPGP_0x00186602339240CB.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1109154: gpg-key2ps can't display UTF-8 in key uid name

2025-07-12 Thread Guilhem Moulin
Hi,

On Sat, 12 Jul 2025 at 23:27:49 +0800, xiao sheng wen wrote:
> gpg-key2ps -1 -p a4 [email protected] | gs -sDEVICE=pdfwrite 
> -sOutputFile=out.pdf
>
> My Chinese name in uid display question mark.
>
> I tested use only "gpg-key2 [email protected]", I also find it's question 
> mark
> in it's output.
>
> Is gpg-key2ps support UTF-8 well?

AFAIK not and that tool is no longer maintained, I should probably add a
deprecation warning in the manual page.

I'd suggest to use gpg-key2latex(1) instead (also from signing-party)
and use XeLaTeX to convert LaTeX output to PDF.  I'm not familiar enough
with Postscript and wrote gpg-key2latex(1) to workaround that particular
issue with gpg-key2ps(1), plus other issues such as as feature requests
for photo IDs and QR codes.  gpg-key2latex(1) is still supported :-)

-- 
Guilhem.


signature.asc
Description: PGP signature


Bug#1109154: gpg-key2ps can't display UTF-8 in key uid name

2025-07-12 Thread xiao sheng wen
Package: signing-party
Version: 2.12-1
Tags: l10n
X-Debbugs-Cc: [email protected],[email protected]

Hi,

When I use:

gpg-key2ps -1 -p a4 [email protected] | gs -sDEVICE=pdfwrite 
-sOutputFile=out.pdf

My Chinese name in uid display question mark.

I tested use only "gpg-key2 [email protected]", I also find it's question mark
in it's output.

Is gpg-key2ps support UTF-8 well?


Thanks!

Report from DebConf25 in Brest!

xiao sheng wen

-- System Information:
Release:12.11.0
Codename:   bookworm
Architecture: x86_64

Kernel: Linux 6.12.32+bpo-rt-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_CN:zh
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages signing-party depends on:
ii  gnupg  2.2.40-1.1+deb12u1
ii  libc6  2.36-9+deb12u12
ii  libclass-methodmaker-perl  2.24-2+b3
ii  libgnupg-interface-perl1.02-3
ii  libmailtools-perl  2.21-2
ii  libmd0 1.0.4-2
ii  libmime-tools-perl 5.510-1
ii  libnet-idn-encode-perl 2.500-3+b1
ii  libterm-readkey-perl   2.38-2+b1
ii  libtext-template-perl  1.61-1
ii  perl   5.36.0-7+deb12u2
ii  python33.11.2-1+b1
ii  qprint 1.1.dfsg.2-2.1

Versions of packages signing-party recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.96-15+deb12u7
ii  libgd-perl [libgd-gd2-perl]2.76-4+b1
ii  libpaper-utils 1.1.29
ii  whiptail   0.52.23-1+b1

Versions of packages signing-party suggests:
ii  fonts-noto-cjk   1:20220127+repack1-1
ii  fonts-noto-mono  20201225-1
ii  imagemagick  8:6.9.11.60+dfsg-1.6+deb12u3
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.6+deb12u3
pn  mutt | neomutt   
ii  qrencode 4.1.1-1
ii  texlive-font-utils   2022.20230122-4
ii  texlive-latex-extra  2022.20230122-4
ii  texlive-latex-recommended2022.20230122-3
ii  texlive-xetex2022.20230122-3
pn  wipe 

-- no debconf information