Hello everybody! Reviewing translations of the “dconf-editor” module I maintain, I’ve discovered that I had a string generation problem: in the gschema file, four strings contains line breaks, but these line breaks doesn’t finish in the po files, and so the translations made by translators do not finish in the application. So sad. :·( That has been reported in the Bugzilla instance by Piotr Drąg[1] against GLib using another module as example. So. I’m not sure if I’m in a “string freeze break request” case or not (I don’t find my exact case in the Wiki[2]), but I have two proposition for fixing these bug-ly untranslated strings: – Proposition 1: fix the string generation using “

” in the gschema file, and let translators redo the translations; – Proposition 2: replace the two line breaks by one space, so that all translations already done work, but without any line break (and I’d change the strings next cycle for what is wanted). I had also planned a 1bis proposition, where I fix the gschema file and all the translations in one patch, avoiding work from translators, but following previous discussion, that’s probably not a path I can follow. ;) Anyway, should I do something, or not, and if yes what? That’s not an important change, but for now translators are working on strings that doesn’t appear, and that lost time makes me sad. :·( Waiting for your suggestions, Arnaud [1] https://bugzilla.gnome.org/show_bug.cgi?id=793931 [2] https://wiki.gnome.org/TranslationProject/HandlingStringFreezes -- Arnaud Bonatti ________________________________ courriel : arnaud bonatti gmail com
Attachment:
0001-Proposition-1.patch
Description: Text Data
Attachment:
0001-Proposition-2.patch
Description: Text Data