Menu

#925 Commit target files doesn't work if target is mapped in another repo

4.1
closed-duplicate
None
5
2020-12-02
2018-09-26
No

I have a team project where the source folder and the target folder are mapped to a second repository different than the one where the OmegaT project is.
The target files are correctly created with Create target files.
However, if I click on "Commit target" nothing happens. The target files are not pushed to the second repository.
See [#1341]

Related

Feature Requests: #1341

Discussion

  • Didier Briel

    Didier Briel - 2018-09-27
    • assigned_to: Alex Buloichik
     
  • Didier Briel

    Didier Briel - 2018-09-27

    I can reproduce it.
    I tested with a folder mapping, and with a file mapping (one specific target file mapped). It doesn't work in both cases.

    Didier

     
    • Kos Ivantsov

      Kos Ivantsov - 2018-09-27

      Does it work as expected for source files when they are napped to a non-main repository?

       
      • Didier Briel

        Didier Briel - 2018-09-27

        There's no change for source files so, yes, it works as expected (as you can see in OmegaT localisation projects).

        Didier

         
        • Kos Ivantsov

          Kos Ivantsov - 2018-09-27

          I meant when trying to commit source files mapped to non-main repository

           
          • Didier Briel

            Didier Briel - 2018-09-27

            I haven't tried it, but it's quite possible there is the same issue.

            Didier

             
  • Kos Ivantsov

    Kos Ivantsov - 2019-05-06
     

    Related

    Feature Requests: #1341


    Last edit: Kos Ivantsov 2019-05-06
  • Kos Ivantsov

    Kos Ivantsov - 2019-05-06
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,3 +1,4 @@
     I have a team project where the source folder and the target folder are mapped to a second repository different than the one where the OmegaT project is.
     The target files are correctly created with Create target files.
     However, if I click on "Commit target" nothing happens. The target files are not pushed to the second repository. 
    +See [#1341]
    
     

    Related

    Feature Requests: #1341

  • Marco Cevoli

    Marco Cevoli - 2020-11-25

    Any news about this bug? Has anyone tried to fix it? Who can I talk to to sponsor the fixing?

     
  • Kos Ivantsov

    Kos Ivantsov - 2020-11-25

    The fix has been developed by Briac in June or July, it's currently in the branch https://sourceforge.net/p/omegat/code/ci/topic/briacp/commit-single-target/~/tree/
    (it addresses not only the current file despite the branch name, but all target files, plus updates remote segmentation.conf and filters.xml after they have been altered using OmegaT GUI respecting their possible mappings)

     
  • Kos Ivantsov

    Kos Ivantsov - 2020-11-25

    Meanwhile there have been some changes in the master, and now that branch needs some additional work in order to be merged into master. It doesn't answer the who question, of course.

     
  • Martin Fleurke

    Martin Fleurke - 2020-12-01
    • status: open --> closed-duplicate
     
  • Martin Fleurke

    Martin Fleurke - 2020-12-01

    This is a duplicate of [#1019], which I thought I had fixed 2 months ago, but I made a small mistake. It should be fixed now.

     

    Related

    Bugs: #1019


    Last edit: Aaron Madlon-Kay 2020-12-02
    • Kos Ivantsov

      Kos Ivantsov - 2020-12-01

      It still commits target files to the main repo, not to the one where they are are supposed to end up in according to the mappings.

       
  • Marco Cevoli

    Marco Cevoli - 2020-12-01

    Is the fix in the nightly build or in the latest version or is it still to be merged?

     
  • Aaron Madlon-Kay

    Yeah I'm not sure this is really a duplicate of [#1019].

     

    Related

    Bugs: #1019

  • Martin Fleurke

    Martin Fleurke - 2020-12-02

    It's in todays nightly build. Given the timestamps of your comments, I think you were just a tiny bit too early.
    If you still think the problem persists, then please share your mapping as well, and I'll have a look.

     

Log in to post a comment.

MongoDB Logo MongoDB