GNOME Bugzilla – Bug 342727
XML Import Druid is way way way too technical
Last modified: 2018-06-29 21:05:13 UTC
Naive users who encounter the XML Import Druid upon upgrade to 1.9.* will be flabbergasted. The title is obscure in the extreme, as is the explanation given in the druid. Some suggestions about improvement are in the Debian BTS entry.
This bug is in the Debian BTS as http://bugs.debian.org/368139.
quoting Daniel Burrows: "[...] I may not be the best person to design better text, though." This holds for me even more :D First of all, it is rather late for a change of a translatable string, as we are in definite string freeze. CC'ing cstim. Any comments on what to do about this bug? My opinion: The issue itself is technical, so I see no way to make the decision page significantly easier. And I like the strings. The longer I think about it, the more I dislike changing it ;-)
I'm not so sure about this and the string freeze. We've got eight translations that have been updated since the string freeze (Spanish, Greek, French, Russian, Slovak, Swedish, German, Norwegian), so changing strings here would mean to require additional work from all of these. Also, some translators may already have changed the wording here so that the dialog talks about "the gnucash data file" instead of "the gnucash XML file" in the translated form. In any case I'd like to hear exact proposals about how the strings should be changed before we decide whether we accept this string freeze break. The Debian bug only has some ideas, but not the exact strings. If the proposed changes are convincingly more understandable than the existing strings, they will be accepted for 2.0.0; otherwise, they will have to wait for a later release. Clearly, the following strings are concerned at most. Exact proposals, anyone? #: ../src/gnome-utils/glade/druid-gnc-xml-import.glade msgid "GnuCash XML Import Druid" #: ../src/gnome-utils/glade/druid-gnc-xml-import.glade msgid "Finish GnuCash XML Import" #: ../src/gnome-utils/druid-gnc-xml-import.c:188 msgid "" "The file you tried to load does not specify an encoding, so GnuCash is " "unable to unambiguously interpret it. This is typical for files created with " "GnuCash prior to 2.0.\n" "\n" "On the next page you will be asked to select the best looking decoded string " "for every ambiguous word GnuCash found while trying to open your file. " "Therefore GnuCash has guessed what encodings you might have used. So " "probably everything will look just fine and you can simply click 'Forward'.\n" "\n" "If it does not work for you, try to change the default encoding at the top. " "Maybe you even have to edit the list of encodings by clicking on the button " "in the top right corner.\n" "\n" "The page is not overly complicated, just take the time until you feel " "comfortable with it. You can always come back and read this message again." #: ../src/gnome-utils/druid-gnc-xml-import.c:202 msgid "Missing file encoding" #: ../src/gnome-utils/druid-gnc-xml-import.c:205 msgid "" "The file has been loaded successfully. If you click 'Apply' it will be saved " "and reloaded into the main application. That way you will have a working " "file as backup in the same directory.\n" "\n" "You can also go back and verify your selections by clicking on 'Back'."
String freeze is now lifted again; we're free to change the strings to any better proposals. Proposals for these five strings, anyone?
Applied to SVN, r14604.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=342727. Please update any external references or bookmarks.