#991226 json2po: The message-context for a string occurring multiple times is always the same

Package:
translate-toolkit
Source:
translate-toolkit
Submitter:
Daniel Leidert
Date:
2021-10-18 06:09:05 UTC
Severity:
normal
Tags:
#991226#5
Date:
2021-07-17 23:59:26 UTC
From:
To:
I have a JSON file, in which so,e strings occur several times in different
keys. But the message context only contains one key multiple times. I think,
this is an error. Here an example:

#: .app.Active
msgctxt ".app.Active"
".app.Active"
".app.Active"
".app.Active"
".app.Active"
".app.Active"
".app.Active"
".app.Active"
".app.Active"
".app.Active"
msgid "Active"
msgstr ""

Instead of listing .app.Active multiple times I expect the other contexts to be
listed here.

This issue is the same both in unstable and experimental.

Regards, Daniel

- -- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages translate-toolkit depends on:
ii  python3                3.9.2-3
ii  python3-pkg-resources  52.0.0-4
ii  python3-translate      3.3.2-1

Versions of packages translate-toolkit recommends:
ii  translate-toolkit-doc  3.3.2-1

translate-toolkit suggests no packages.

- -- no debconf information

- -- debsums errors found:
debsums: changed file /usr/bin/json2po (from translate-toolkit package)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmDzbt4ACgkQS80FZ8KW
0F22/g/+J8nZUOV8L/UAG+rhKlB7HqfYXDsjUAQhrUHcDe7tROKpcypKyayBQj4r
4QlY3Q8lOe6GSt18dQVOsl58QQ9m0RCxaF8n6c3WRZlAVgKmoTClzHB30rtU6+z/
AytuXEhIACe5RXTscQ9O18wyVvuAJTOzI9zsvaixXB250jSl1huNBEl58v9Vn0e2
6VlDxQ92MI/1ShCCKbh3dgRJeRw8JkMk8WIRuSXcRbXVfwmvERbi2+00chNLaNnN
C6oMbLisAtCVu0B6fot52U+d+VDRR/8gjgObTrAW/fqEM79GWwyU5r03hoTKX1Eb
VFD49LT0hFuAmGPfcoKwoIaS2dZDWzp4j5pv7cJc9OOQjjKe8UOVMxE3+v0uxQNW
aSLPoXuV8rPnnSNzDLrFUH28zAiuAk9uzUXQbCTJbu7FUGSCVYEE38Xjf0LV6bCj
W8oi9bPPUnn43r7X06GN+kkIFK5bmMDzsKPgVlXJfNXFW3QK+ZkC1FHq03yQryXs
f3c3I9139RKZZa3MKbiRTiOUzgSAg+1HvYka1/wkEC+Q2fA7PAuVNiMmxDZ3hnL+
wtYDdYcavHyVh814M/Dnlih6P7LXtKaO2r/TAnqeEbiA1VhKJix43wCdVcd59bzm
SVprl2WsQUdVIFMKRBbQgGY+Q4WwVC8j3GjHxbtfg4I5AGwsUMY=
=Oias
-----END PGP SIGNATURE-----
#991226#10
Date:
2021-10-18 06:04:38 UTC
From:
To:
Hi Daniel,

I don't think I quite understand the situation that is described in this bug
report. Would you be able to point me at a specific json file and invocation of
json2po that fails? Or even better, provide a minimal (non-)working example?

thanks
Stuart