[Proposal]: Split or Remove GSettings Schema Strings in Translation POT Files

I am a coordinator of the Japanese Translation Team, and I have a suggestion for the developers from a translator’s perspective.
Currently, the POT files in each project include strings from the GSettings Schema. However, these strings are not shown to end users unless they use tools like dconf Editor. Therefore, translating them is unnecessary.
We would like to check translation percentages excluding these GSettings Schema strings.
To make this possible, I suggest either splitting the GSettings Schema (gschema) strings into a separate POT file or removing them from the main POT files altogether.

Please hear me about your idea for this topic.

There’s already such functionality. You can see the progress excluding GSettings under Japanese, under the ‘User Interface (red.)’ column, which is the one to the right of the graph.

It’s true that on the release group page (like GNOME 50), there’s no way to view non GSettings progress, but if you go through to a module’s page, you can see an option to use a ‘reduced translation file’, which excludes the settings. Use that file for translating instead. See the image below, it’s the button next to the blue question mark.

I understand setting up translation domains for every module would be a real pain, so this translation platform UI way seems best.

1 Like

Thank you for your post.
However, I feel “reduced translated file” doesn’t work.
This feature remove strings in files “gschema.xml.in”.
Many projects actually have files “gschema.xml”, not “gschema.xml.in”.
I will submit “issue” on repo of damned-lies in GNOME gitlab for improving filters.

Summary of Reduced Strings

  • “Current Reduced translated file (PO)” don’t include strings in “gschema.xml.in” or “gschema.xml.in”.
  • “Current Reduced translated file (PO)” include strings which have been already translated even strings of gschema.

( A issue I submitted. This is my mistake.)