GNOME Bugzilla – Bug 73295
Please remove markup from messages marked for translation
Last modified: 2004-12-22 21:47:04 UTC
#: capplets/keyboard/gnome-keyboard-properties.glade.h:1 msgid "<i>fast</i>" msgstr "" #: capplets/keyboard/gnome-keyboard-properties.glade.h:2 msgid "<i>loud</i>" msgstr "" #: capplets/keyboard/gnome-keyboard-properties.glade.h:3 msgid "<i>quiet</i>" msgstr "" #: capplets/keyboard/gnome-keyboard-properties.glade.h:4 msgid "<i>slow</i>" msgstr "" There are lots of reasons why marking markup for translation is a bad idea. Some of the reasons are the danger of accidental "mistranslations" of markup, and another reason is that the markup clutters the messages and makes translation of what really should be translated harder. It disguises what really should be translated, makes changes in what really should be translated harder to find, unnecessarily warns for changes when only markup was changed, and makes use of translation databases (translation memories) harder since there never will be a clean apply when words are obfuscated with irrelevant markup. Please remove the markup from the parts that are marked for translation above, so that what is marked for translation is only the words "fast", "loud", "quiet", and "slow".
This also applies to #: capplets/mouse/gnome-mouse-properties.glade.h:3 msgid "<i>Fast</i>" msgstr "" #: capplets/mouse/gnome-mouse-properties.glade.h:4 msgid "<i>High</i>" msgstr "" #: capplets/mouse/gnome-mouse-properties.glade.h:5 msgid "<i>Large</i>" msgstr "" #: capplets/mouse/gnome-mouse-properties.glade.h:6 msgid "<i>Low</i>" msgstr "" #: capplets/mouse/gnome-mouse-properties.glade.h:7 msgid "<i>Slow</i>" msgstr "" #: capplets/mouse/gnome-mouse-properties.glade.h:8 msgid "<i>Small</i>" msgstr ""
And #: capplets/mouse/gnome-mouse-properties.glade.h:1 msgid "" "<b>Note:</b>\n" "\t\t\t You will need to logout and log back in for this setting to take " "effect." msgstr ""
This markup really needs to be translated, as the only alternative to markup is to mark offsets (which is totally broken for i18n), or to do something like: str = g_strdup_printf ("<b>", _("some string"), "</b>", _("some other string")); which gives a disconnect to the translator too, and can't be done from glade (which is really important). (It's also really tedious, and not worth the effort imho).
> This markup really needs to be translated, as the only alternative > to markup is to mark offsets (which is totally broken for i18n), Agreed, that's certainly not a viable solution. > or to do something like: > str = g_strdup_printf ("<b>", _("some string"), "</b>", _("some > other string")); > which gives a disconnect to the translator too, I don't understand what you're talking about here (the "disconnect"). This solution is used quite often. > and can't be done from glade (which is really important). Yes, maybe this should be made a bug report against glade, but wouldn't a better solution be to refrain from using markup in these messages in the mean time? > (It's also really tedious, and not worth the effort imho). "Translating" markup is tedious, pointless, and makes translation and translation maintenance more difficult than it has to be for all the reasons mentioned above. Really, this has to be solved.
I added a glade bug report, bug 73339.
Updating all cc bugs that have the GNOME2 keyword set to the GNOME2.0 milestone, to help jrb triage/prioritize cc bugs. Filter on 'luis doing GNOME2 work' to ignore this spam.
This was fixed in intltool.