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

file extension ODT can not be handled - odt can

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • None
    • None
    • Import/Export

      If a file has the file extension .ODT it can not be imported. If you rename the same file to .odt it can be imported.

      Is this a bconf problem?

          [TRANSLATE-2434] file extension ODT can not be handled - odt can

          Thomas Lauria made changes -
          Assignee Original: Thomas Lauria [ tlauria ] New: Marc Mittag [Administrator] [ marcmittag ]
          Marc Mittag [Administrator] made changes -
          Workflow Original: MittagQI Workflow [ 30808 ] New: MittagQI Workflow with Peer [ 37045 ]
          Marc Mittag [Administrator] made changes -
          Rank New: Ranked higher
          Marc Mittag [Administrator] made changes -
          Assignee Original: Marc Mittag [Administrator] [ marcmittag ] New: Thomas Lauria [ tlauria ]

          Marc Mittag [Administrator] added a comment - - edited

          tlauria it is definitely an okapi problem, that probably could be solved by mapping all file types that okapi supports in the bconf to all versions of upper case and lower case in the file extension.

          Yet this is a lot of effort and error prone.

          Much better is, to implement in translate5 (in core, independant from okapi) that we always convert the fileextension to lower case before sending it to okapi (it is ok, if it is lower case also in the translate5 export then).

          Since I think, this should also be a fast fix, I put this to the top of your pipeline

          Marc Mittag [Administrator] added a comment - - edited tlauria it is definitely an okapi problem, that probably could be solved by mapping all file types that okapi supports in the bconf to all versions of upper case and lower case in the file extension. Yet this is a lot of effort and error prone. Much better is, to implement in translate5 (in core, independant from okapi) that we always convert the fileextension to lower case before sending it to okapi (it is ok, if it is lower case also in the translate5 export then). Since I think, this should also be a fast fix, I put this to the top of your pipeline
          Thomas Lauria made changes -
          Status Original: Open [ 10002 ] New: Selected for Development [ 10100 ]
          Thomas Lauria made changes -
          Link New: This issue relates to TRANSLATE-2433 [ TRANSLATE-2433 ]
          Thomas Lauria made changes -
          Link Original: This issue clones TRANSLATE-2433 [ TRANSLATE-2433 ]
          Thomas Lauria made changes -
          Assignee Original: Thomas Lauria [ tlauria ] New: Marc Mittag [Administrator] [ marcmittag ]
          Thomas Lauria made changes -
          Description Original: If a file has the file extension .XLF it can not be imported. If you rename the same file to .xlf it can be imported.

          Please check also, that all other variations of upper and lower case file extensions are correctly supported.           		New: If a file has the file extension .ODT it can not be imported. If you rename the same file to .odt it can be imported.

          Is this a bconf problem?

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

              Created:
              Updated: