Bug 305598 - File in BranchDir does not get updated
Summary: File in BranchDir does not get updated
Status: REPORTED
Alias: None
Product: lokalize
Classification: Applications
Component: project management (show other bugs)
Version: 1.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Nick Shaforostoff
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-22 13:14 UTC by Freek de Kruijf
Modified: 2019-09-17 09:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
first screenshot (85.92 KB, image/png)
2019-09-17 09:01 UTC, Freek de Kruijf
Details
second screenshot (230.82 KB, image/png)
2019-09-17 09:02 UTC, Freek de Kruijf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Freek de Kruijf 2012-08-22 13:14:36 UTC
I use the same project file with lokalize 1.2 as with lokalize 1.4. I have a BranchDir definition in that file. I have the subwindow secondary synchronization open when working on a po file. When I copy the English text I see this text also appear in that subwindow in 1.2. However not in 1.4. After translation in 1.2 and inspecting the file in the BranchDir, also the file there is updated. Both similar files are the same. However this does not happen when using 1.4. I have to open that file using another project file, where PoBaseDir is the same as BranchDir in the above mentioned file, and I use TM to get it updated to the same level as the first file.
This looks like a regression from 1.2 to 1.4.

Reproducible: Always

Steps to Reproduce:
1. see above
2.
3.
Comment 1 Adrián Chaves (Gallaecio) 2019-09-01 19:52:26 UTC
Can you reproduce this issue with the latest version of Lokalize? I’ve just tested with a new project, with the same fiel copied in two different branch folders. The translation unit of the alternative branch shows up in the Secondary Sync subwindow, updates accordingly, and upon saving the secondary file reflects the changes as well.
Comment 2 Bug Janitor Service 2019-09-16 04:33:07 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Freek de Kruijf 2019-09-16 13:04:32 UTC
Apparently I don't understand how this works. The way I have configured the .lokalize (project) file has changed from version 1.2 to 1.4. I still use the configuration of 1.2 which synchronized the branch with trunk. Now it does not anymore.
In the test setup the project file is:
[General]
AltDir=./
BranchDir=/home/user/vertalingen/svn/testbranch/nl/
GlossaryTbx=/home/user/vertalingen/svn/trunkkf5/nl/woordenlijst.tbx
LangCode=nl
MailingList=kde-i18n-nl@kde.org
PoBaseDir=/home/user/vertalingen/svn/testtrunk/nl
PotBaseDir=/home/user/vertalingen/svn/testtrunk/templates
ProjectID=test-nl
TargetLangCode=nl

I have .pot files in both 
$HOME/vertalingen/testtrunk/templates/messages/applications/ and $HOME/vertalingen/testbranch/templates/messages/applications/
I have a partly translated .po file in 
/home/user/vertalingen/testtrunk/nl/messages/applications/ 
and started with a .po file without any translations in
/home/user/vertalingen/testbranch/nl/messages/applications/
It is my expectation that working on the .po file in testtrunk the .po file in testbranch gets updated also if the English text matches.
Comment 4 Adrián Chaves (Gallaecio) 2019-09-17 04:25:51 UTC
I believe that should work. Could you try upgrading your version of Lokalize to 19.08.1?
Comment 5 Freek de Kruijf 2019-09-17 07:43:20 UTC
(In reply to Adrián Chaves (Gallaecio) from comment #4)
> I believe that should work. Could you try upgrading your version of Lokalize
> to 19.08.1?

My distribution, openSUSE Tumbleweed, provides 19.08.0.

Should that work also?
Comment 6 Adrián Chaves (Gallaecio) 2019-09-17 07:52:42 UTC
I think it should.

If you create a project from scratch, the way I did, does it work for you, or does it also fail?
Comment 7 Freek de Kruijf 2019-09-17 09:01:39 UTC
Created attachment 122688 [details]
first screenshot
Comment 8 Freek de Kruijf 2019-09-17 09:02:57 UTC
Created attachment 122689 [details]
second screenshot
Comment 9 Freek de Kruijf 2019-09-17 09:15:15 UTC
(In reply to Adrián Chaves (Gallaecio) from comment #6)
> I think it should.
> 
> If you create a project from scratch, the way I did, does it work for you,
> or does it also fail?

I invoked lokalize using the given project file (created for testing). The expanded Project View is shown in the first screenshot.
I selected dolpnin.po in this tab, to edit this file. I did drag the corresponding branch file in the Secondary Synchronization, although I would expect this to be a standard action, given the BranchDir= in the project file. I updated a few items in the trunk file using <Ctrl>+U on an item. With the mouse on the sub window Secondary Synchronization, I get a popup showing what are the details. See the second screenshot, but did not notice any change in these details while editing some items in the trunk file, also not after pressing <Ctrl>+S.