Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-828

Refactor internal tag handling architecture

    XMLWordPrintable

Details

    • Task
    • Resolution: Duplicate
    • None
    • None
    • None

    Description

      Currently most of the tag related functions are fragmented over the whole application. Only for the internal content tags most code is centralized in the editor_Models_Segment_InternalTag class.
      Same concept should be used for all our internal tags (MQM, Term Tags).

      One goal is to provide the same interface for all tag types:
      mqm tags, term tags and content tags extend abstract tag.
      The abstract tag class defines the interface for commonly used methods: strip, replace etc.

      Another general class internal tag should provide a similar interface to malke bulk operations, example:
      generalTag->strip(string, MQM|term) → this leaves content tags

      Attachments

        Issue Links

          Activity

            People

              axelbecher Axel Becher
              tlauria Thomas Lauria
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: