After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 563442 - Don't split strings marked for translation
Don't split strings marked for translation
Status: RESOLVED FIXED
Product: gnome-lirc-properties
Classification: Other
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: gnome-lirc-properties-maint
gnome-lirc-properties-maint
Depends on:
Blocks:
 
 
Reported: 2008-12-06 13:44 UTC by Leonardo Ferreira Fontenelle
Modified: 2010-04-21 07:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Remove bad string concatenation (6.24 KB, patch)
2009-10-18 22:49 UTC, Leonardo Ferreira Fontenelle
none Details | Review

Description Leonardo Ferreira Fontenelle 2008-12-06 13:44:02 UTC
Does that seem a good sentence for you? :)

#: ../gnome_lirc_properties/backend.py:385
msgid "Make sure you keep pressing the <b>same</b> button and that you "

That's what I see when the code looks like this:

        if line.startswith(self._token_wait_toggle_mask):
            self.RequestAction(
                _('Press a button repeatedly as fast as possible.'),
                _('Make sure you keep pressing the <b>same</b> button and that you ' +
                  '<b>do not hold</b> the button down.\nWait a little between button ' +
                  'presses if you cannot see any progress.'))

Please fix this and other similar messages.

http://live.gnome.org/TranslationProject/DevGuidelines/Never%20split%20sentences
Comment 1 Leonardo Ferreira Fontenelle 2009-01-03 20:29:19 UTC
Ping
Comment 2 Murray Cumming 2009-01-03 22:09:50 UTC
A patch would be welcome.
Comment 3 Leonardo Ferreira Fontenelle 2009-10-18 22:49:36 UTC
Created attachment 145754 [details] [review]
Remove bad string concatenation

I'm not really a programmer, so please check if this doesn't break anything.
Comment 4 Murray Cumming 2010-04-21 07:07:28 UTC
I'm very sorry for ignoring your patch until now.

This seems to have been fixed in the meantime, by putting the whole string on one line.