Uploaded image for project: 'XWiki Infrastructure'
  1. XWiki Infrastructure
  2. XINFRA-66

Batch reviews and updates enhancement

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Duplicate
    • Minor
    • l10n.xwiki.org
    • None
    • L10N, batch, update, search
    • N/A
    • N/A

    Description

      Trigger
      Currently it's hard to make massive searches and updates.

      Example.
      Let's assume that we have created some initial translation of some term which is encountered in 100 places which originally was pretty close and acceptable. But then after a while a better synonym was found (e.g. due to language evolution or language expert digging out a better variant or original English word has changed etc.)
      Now we need to search and replace old term translation with a new one.
      This can be easily achieved in more or less advanced text editor like Notepad++ or Open Source IntelliJ IDEA. But in current implementation of L10N application it's much more difficult to do. One should first search for all old terms, then going one-by-one translation the translator should repeat open-edit-save cycle for each item. In total it takes 5-15 extra seconds for each record:

      • 4-10 seconds to return search results (depending on the amount of records found)
      • 1-2 seconds to open translation
      • 1-2 seconds to save translation

      Solution
      So there might be a good way for the L10N application to utilize the power of independent text editor if it provided means to do the following:

      1. Download non-encoded localization file for particular language in the *.properties format
      2. Update the document (translate, update previous translations)
      3. Upload that translated part back into L10N application
        • Items that did not change are ignored
        • Keys that are present in the uploaded file but not present application are ignored.
      4. Instantly see changes as a list of "to be reviewed" items
      5. If there were conflicts during upload (e.g. some uploaded translation message already existed) the review row is highlighted showing all available translation versions.

      Addition to this would be the ability to

      1. Download ONLY non-localized messages (empty ones) in the *.properties format but with current English translation.

      Advantages

      • Faster translation/review
      • Ability to translate bundles without access to the Internet
      • It's easier reference back to translations already made when having all of them in one document (helps in bringing consistency to translations where it has been broken for some reasons)

      Disadvantages

      • <put here if any>

      Attachments

        Activity

          People

            vmassol Vincent Massol
            coldserenity Roman Arkadijovych Muntyanu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: