From kde-i18n-doc  Mon May 23 21:50:32 2022
From: Frederik Schwarzer <schwarzer () kde ! org>
Date: Mon, 23 May 2022 21:50:32 +0000
To: kde-i18n-doc
Subject: Re: svn up might break translations
Message-Id: <8067045.T7Z3S40VBb () fedora>
X-MARC-Message: https://marc.info/?l=kde-i18n-doc&m=165334257724546

On Monday, May 23, 2022 11:08:37 PM CEST Freek de Kruijf wrote:
> Op maandag 23 mei 2022 22:29:55 CEST schreef Frederik Schwarzer:
> > On Saturday, May 21, 2022 10:41:15 AM CEST Freek de Kruijf wrote:
> > > Op zaterdag 21 mei 2022 10:08:01 CEST schreef Antoni Bella=20
P=E9rez:
> > Hi,
> >=20
> > > >   I prefer make svn up before copy new translations and go
> > > >   on...
> > > >   Possible>
> > > >=20
> > > > cross translations? See the local diff. Toni
> > > >=20
> > > > Sent from Yahoo Mail on Android
> > > >=20
> > > >   On dv., de maig 20, 2022 at 23:57, Frederik
> > > >   Schwarzer<schwarzer@kde.org>>
> > > >=20
> > > > wrote:   Hi,
> > > >=20
> > > > we currently have a problem with our workflow.
> > > >=20
> > > > For some time now Lokalize formats even short strings as:
> > > >=20
> > > > msgstr ""
> > > > "Foo"
> > > >=20
> > > >=20
> > > > Our server-side scripts then update the files to make them
> > > > look
> > > > like:
> > > >=20
> > > > msgstr "Foo"
> > > >=20
> > > >=20
> > > > If now the translator wants to commit the changes a few days
> > > > later,
> > > > svn complains that we need to run "svn up" first.
> > > >=20
> > > > SVN performs a merge then and creates messages like:
> > > >=20
> > > > msgstr "Foo"
> > > > "Foo"
> > > >=20
> > > > ... resulting in strings like "FooFoo" in the GUI.
> > > >=20
> > > >=20
> > > > Has enyone else seen this?
> > >=20
> > > In my workflow, before doing any work on translations, I do an
> > > "svn
> > > up". After finishing translating on that day, I do a commit
> > > before
> > > midnight.
> >=20
> > The problem with this is that "midnight" does not have any meaning
> > wrt skripty. It runs for ... I don't know ... 15 hours or so? So
> > it might throw sticks between your legs during the day. :D
> >=20
> > > When I get new versions of .po files from other translators, I
> > > also
> > > first do an "svn up", put the received .po file in its location,
> > > replacing the newest one from the svn server.
> > >=20
> > > I also have the .pot files available, also renewed with "svn up"
> > > and I do a merge of the .pot file with the new .po file, which
> > > is what happens on the svn server during the night. So it is
> > > not really necessary, but after the merge I can check whether
> > > new elements need some work. Again a commit before midnight.
> >=20
> > For this I use Lokalize. That way I do not have to wait for the
> > next skripty run or merge with the .pot file to see if there are
> > translations missing.
>=20
> Midnight for me is -1:00 UTC or -2:00 UTC (DST)
>=20
> I am not aware of a sync action in Lokalize.
>=20
> > See:
> > Sync -> Open file for sync/merge
> > Sync -> Copy all new translations
>=20
> Is this using kdesvn? I only use the command line.

The Sync action is from Lokalize. You can find it in the menu, if you=20
have a PO file open for editing.

Cheers,
=46rederik