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

Select correct okapi file filter for txt-files by default

Details

    • High
    • Hide
      By default the file format conversion used for txt-files the okapi-filter "moses-text". In this filter xml-special characters like & < > where kept in encoded version when the file was reconverted back to txt after export from translate5. This was wrong. Now the default was changed to the okapi plain-text filter, what handles the xml-special chars correctly.
      Show
      By default the file format conversion used for txt-files the okapi-filter "moses-text". In this filter xml-special characters like & < > where kept in encoded version when the file was reconverted back to txt after export from translate5. This was wrong. Now the default was changed to the okapi plain-text filter, what handles the xml-special chars correctly.

    Description

      By default the wrong file filter for txt files had been selected in translate5s okapi setup.

      Therefore xml special chars had been encoded in the reexport from translate5 to txt.

      Attachments

        Activity

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

          Select correct okapi file filter for txt-files by default

          Details

            • High
            • Hide
              By default the file format conversion used for txt-files the okapi-filter "moses-text". In this filter xml-special characters like & < > where kept in encoded version when the file was reconverted back to txt after export from translate5. This was wrong. Now the default was changed to the okapi plain-text filter, what handles the xml-special chars correctly.
              Show
              By default the file format conversion used for txt-files the okapi-filter "moses-text". In this filter xml-special characters like & < > where kept in encoded version when the file was reconverted back to txt after export from translate5. This was wrong. Now the default was changed to the okapi plain-text filter, what handles the xml-special chars correctly.

            Description

              By default the wrong file filter for txt files had been selected in translate5s okapi setup.

              Therefore xml special chars had been encoded in the reexport from translate5 to txt.

              Attachments

                Activity

                  People

                    marcmittag Marc Mittag [Administrator]
                    marcmittag Marc Mittag [Administrator]
                    Votes:
                    0 Vote for this issue
                    Watchers:
                    1 Start watching this issue

                    Dates

                      Created:
                      Updated:
                      Resolved:

                      People

                        marcmittag Marc Mittag [Administrator]
                        marcmittag Marc Mittag [Administrator]
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                        Dates

                          Created:
                          Updated:
                          Resolved: