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 520974 - Some script names are not marked for translation
Some script names are not marked for translation
Status: RESOLVED FIXED
Product: orca
Classification: Applications
Component: i18n
2.21.x
Other Linux
: Normal minor
: 2.24.0
Assigned To: Rich Burridge
Depends on:
Blocks:
 
 
Reported: 2008-03-07 12:35 UTC by Gabor Kelemen
Modified: 2009-03-10 00:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Attachments
Mark script names for translation (3.16 KB, patch)
2008-03-07 12:36 UTC, Gabor Kelemen
accepted-commit_after_freeze Details | Review
Revision #1. (6.27 KB, patch)
2008-03-27 16:56 UTC, Rich Burridge
committed Details | Review

Description Gabor Kelemen 2008-03-07 12:35:33 UTC
In src/orca/default.py, there are some script names that are visible on the UI, but are not marked for translation. Trivial patch attached, but probably needs translator comment from developers.
Comment 1 Gabor Kelemen 2008-03-07 12:36:14 UTC
Created attachment 106772 [details] [review]
Mark script names for translation
Comment 2 Willie Walker 2008-03-07 13:47:15 UTC
Hi Gabor:

This particular text really is for debug/developer purposes only, so it's something we didn't want to burden the translators with.  Do you think we should still mark it for translation?

Will
Comment 3 Gabor Kelemen 2008-03-07 14:34:39 UTC
Hi

I think the question is wrong. If it's visible for users, you need to mark it for translation. I saw these on the UI, so they are definitely visible :). 

If you don't want them bless as feature-complete stable features, because they are unfinished, buggy, etc., then hide them behind some configure option, which is set to false by default, like --enable-unstable-features or so. 

In the current feature/string/hard code frozen situation, I'd suggest to commit this into the stable branch after 2.22 is out.
Comment 4 Willie Walker 2008-03-07 15:05:12 UTC
OK.  Thanks!  Marking this for 2.22.1, with the understanding that we need to first add translator comments.  Note also that this should be committed to trunk for the 2.23.x releases.
Comment 5 Willie Walker 2008-03-25 14:07:10 UTC
Since this will represent adding new strings, I'm going to mark this for 2.23.1.  The strings are really for debugging purposes only, so I don't think there is a significant user impact needed to justify string changes for 2.22.x.
Comment 6 Rich Burridge 2008-03-27 16:56:10 UTC
Created attachment 108121 [details] [review]
Revision #1.

Thanks Gabor. I've added in some translators comments 
for each string and checked the patch into SVN trunk.
Moving the bug to '[pending]'. If any of the translator
comments need tweaking, please let me know.