Skip to content
← General

Enter your feature ideas or any bug you found

General

Categories

(thinking…)

OBSOLETE TERMS

The interface provides the ability to delete a single term. For our workflow, the translator usually does not know that a single term should be deleted because the files are all generated. We generate new POT files that contain all the active terms. It would be nice to have the ability to upload a POT file which has the with the option 'delete all terms marked obsolete'. Or add a classification to terms to be marked 'Obsolete' in the user interface and based on import similar to how terms can be marked fuzzy. Obsolete terms would be excluded from export.

http://www.gnu.org/software/gettext/manual/html_node/Obsolete-Entries.html Note that it would be good if the translation of the deleted term remained in a translation memory.

4 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Jonathan Marston shared this idea  ·   ·  Report…  ·  Admin →

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Luigi commented  ·   ·  Report

    I agree with you:
    this point is similar to mine here:
    http://poeditor.uservoice.com/forums/171919-general/suggestions/3480103-rest-api-option-to-keep-as-obsolete-unused-terms

    As you say, "obsolete" term should not be exported.

    Also I would mark sentences available in poeditor but not anymore in the POT file as "obsolete":
    - translation will stay there (so that they can be reenabled if reinserted again in the pot file)
    - translation of obsolete term will NOT be shown to translator (to avoid them loosing time)

    Bottom line:
    we can keep work done in the past (as maybe useful again) but don't add unuseful work to the translators

  • Luigi commented  ·   ·  Report

    The workflow could be:

    1- Admin creates an updated POT file
    2- Admin upload it on poeditor
    3- Unused sentences will be shown (like today) but with also the list of translation languages already available for that sentence
    4- Admin can decide to
    - keep
    - delete
    - store
    all OR each of those sentences (maybe a default action can be defined on a per project base, or maybe "store" -being the safest option- could be the std option)
    5- "stored" items will NOT be shown on the list to be translated and WILL NOT be exported
    6- The next time admin upload a file, if the "stored" item is again in place, it will appear automatically with all linked translations previously made.
    7- During normal administration, Admin will have the chance to look for the "stored" sentences and delete them or make them standard
    8- Stored sentences will be part of the translation memory for all admin's projects

  • Luigi commented  ·   ·  Report

    Me too, I would like to keep the UNUSED (=obsolete) translation in poeditor but:
    - not making them available for further translation
    - not exported

    Sometime I change my mind about original sentence and revert back to a previous version.

    What I would like is:
    1- to avoid that translator wastes time for obsolete sentences
    2- to avoid that translator who already made a sentence (which I made then obsolete) waste time to do it again, if for any reason I reinstate it

    In this sense there should be an option in the import page, to mark as OBSOLETE the terms not found in the new import

    Obsolete item would then be available to ADMIN only (and he could eventually delete those).

    If, they are reinstated in the new POT file, they will become already available, together with already made translations.

    In this case we would eventually not even need to delete obsolete terms as they might become part of the translation memory.