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 59418 - Message state menu should only contain message states
Message state menu should only contain message states
Status: VERIFIED FIXED
Product: gtranslator
Classification: Other
Component: Interface
0.x
Other Windows
: Normal enhancement
: 1.0
Assigned To: Fatih Demir
Fatih Demir
Depends on:
Blocks: 59417
 
 
Reported: 2001-08-23 08:59 UTC by Emese Kovacs
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Emese Kovacs 2001-08-23 08:59:40 UTC
The message state menu currently has:
Translated
Fuzzy
Sticky

This is misleading.
In the menu, you are able to check both translated and fuzzy, which does 
not seem to make sense.
Sticky is not a message state but an edit option (that is: paste original).

Valid states for strings are:
untranslated
translated
fuzzy
obsoleted

The first 3 are mutually exclusive.
The last is in addition of the first 3 (untranslated/translated and fuzzy 
messages can all be obsolete or not).

The sticky menu item would rather belong to the edit menu (it could be 
named "Paste original".
Comment 1 Fatih Demir 2001-08-23 10:52:18 UTC
Well, the situation with "Sticky" is that it's handled internally
currently (is more then just a paste, the status bit for Stickiness
get's set), but isn't made "persistent" yet (via something like a
special gtranslator-specific extension-comment "#> Sticky" or
something like that. If we do this once, you can then distinct between
normally translated and sticky messages -- sticky messages are also
translated per se.

Fuzzy <-> Translated situation: hmm, this should be really exclusive.

Obsolete status: this is quite different from our current view of
source: obsolete messages are stored as a single gchar and appended to
the file on write (like msgmerge does, too) so that an "Obsolete"
message status isn't currently offered.

If we want to enable per-message ability to toggle obsolete entries,
this would involve many source changes, but would be possible... Hmm
Comment 2 Fatih Demir 2002-02-15 13:18:36 UTC
Well, this was solved by just putting "Translated" and "Fuzzy" into
the status menu.

These two should be the only logical choices indeed.