Why is my `incus info` partially translated?

Incus
1

Hi all,

I just created a basic container with incus launch images:ubuntu/24.04 dummy, I then have the following result for incus info dummy:

[me@mycomputer ~]$ incus info dummy
Nom : dummy
État : RUNNING
Type: container
Architecture : x86_64
PID: 17072
Créé : 2024/09/03 14:32 CEST
Last Used: 2024/09/03 14:32 CEST
Started: 2024/09/03 14:32 CEST

Ressources :
  Processus : 12
  CPU utilisé :
    CPU utilisé (en secondes): 0
  Mémoire utilisée :
    Mémoire (courante): 127.72MiB
  Réseau utilisé :
    eth0:
      Type: broadcast
      State: UP
      Host interface: veth4e8ff958
      MAC address: 00:16:3e:f3:fd:02
      MTU: 1500
      Octets reçus: 4.92kB
      Octets émis: 2.73kB
      Paquets reçus: 48
      Paquets émis: 29
      IP addresses:
        inet:  10.27.1.94/24 (global)
        inet6: fd42:ab2a:2225:e10c:216:3eff:fef3:fd02/64 (global)
        inet6: fe80::216:3eff:fef3:fd02/64 (link)
    lo:
      Type: loopback
      State: UP
      MTU: 65536
      Octets reçus: 0B
      Octets émis: 0B
      Paquets reçus: 0
      Paquets émis: 0
      IP addresses:
        inet:  127.0.0.1/8 (local)
        inet6: ::1/128 (local)

My default language is French (fr-ch) and, as you can see, some keys are translated and some are not. You may not notice it, but there are also NBSP at the end of French keys. For example, instead of Name, I have "Nom\u202F" (I discovered that thanks to shyaml). The NBSP only appears at the end of French names and can be explained because you are supposed to add a space before a colon in French, it’s probably part of the translation.

As it feels strange to have something half-translated, even more if it’s YAML keys, I would like to know if it’s normal, translation in progress or a bug.

NOTE: It doesn’t happen on my legacy LXC containers.

2

Welcome!

You are using the incus Command-Line Interface (CLI) client, which is translatable through this service.

Currently, the CLI client is translated at 31% for the French language (partial localisation).

If you can contribute and complete the translation, you can do so through the Incus Weblate translation site. This will then be picked up by the Incus project and the next release will have the new translations.
Note that it is suggested to translate first the Glossary package. By doing so, you will have proper translations for common repeating terminology.

If you really do not wish to view the (currently) partial French localisation, you may, for example, remove the file /opt/incus/share/locale/fr.mo, which is the file that has the French translation messages.

Doing translations is a way for a not-so-technical person to contribute back to a project they love. If you think you can fix those errors, you can do so and the fix will appear in the next release of the package.

3

incus info returns a user readable overview of the instance or server, it’s not YAML, so it’s correct for it to be translated, though as @simos pointed out, the Incus CLI isn’t currently fully translated to french which explains the mix in the output.

You can also do LC_ALL=C.UTF-8 incus info to have it skip any translation.

4

Thanks a lot for your answers!

I’ll help you translating if I have the time.