https://bugs.kde.org/show_bug.cgi?id=526624

            Bug ID: 526624
           Summary: Previous/next menu options are inconsistent and
                    confusing (for both users and translators)
    Classification: Applications
           Product: lokalize
      Version First unspecified
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: editor
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected], [email protected]
  Target Milestone: ---

DESCRIPTION
In the Go menu, we have the following previous/next options:

Previous Not Ready
Next Not Ready
Previous non-empty but not ready
Next non-empty but not ready
Previous Untranslated
Next Untranslated

These are confusingly named and have inconsistent capitalisation:

In Lokalize ‘Not Ready’ means ‘fuzzy’ (for gettext PO files), i.e., there *is*
a suggested translation, but it’s marked as ‘fuzzy’. And the msgctxt for the
‘Previous/Next Not Ready’ strings even says:
@action:inmenu\n 'not ready' means 'fuzzy' in gettext terminology

But if you choose the menu option, you do *not* go to the previous/next fuzzy
string, but instead to (what Lokalize calls) an ‘Incomplete’ string, i.e. a
string which is either fuzzy *or* completely untranslated.

If you choose the ‘Previous/Next non-empty but not ready’, you actually go the
previous/next *fuzzy* string.

Besides this, the capitalisation is inconsistent (‘Previous non-empty but not
ready’ is mostly in lowercase, while the other strings are in Title Case).

Only the names need changes. (Do *not* change what the options do, for the
translators have been using the existing keyboard shortcuts for years!)

I’m not sure what the best names are, but if we want to be consistent with the
rest of Lokalize, it would be:

Previous Incomplete
Next Incomplete
Previous Not ready
Next Not ready
Previous Untranslated
Next Untranslated

Personally, I like the ‘fuzzy’ terminology, but it seems Lokalize tries to
avoid it (to be consistent the XLIFF and the Qt Linguist file formats?).



STEPS TO REPRODUCE
1. Open a PO file
2. Open the ‘Go’ menu

OBSERVED RESULT
See discussion above.

EXPECTED RESULT
See discussion above for a suggestion.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20260929
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Kernel Version: 7.2.8-1-default (64-bit)
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to