Web Translation tool

[Łukasz Wojniłowicz]

ad 1. The project feature of Lokalize has the "Branch folder" option. If
you open your KF5 project then you can point "Branch folder" to your
KF6. If the structure and translation units match between them then you
can translate one project and have translations automatically copied to
the other.

Cheers,
Łukasz

On Fri, 5 Apr 2024 23:15:11 +0300
Yaron Shahrabani <sh.yaron at gmail.com> wrote:

> Great, that makes a lot of sense, thank you!
> Now I have 2 other problems:
> 1. I don't know how to combine KF5 with KF6 in the same project.
> 2. The plural form for Hebrew is the old one.
> 
> Thanks :)
> Yaron Shahrabani
> 
> <DevOps - Hebrew translator>
> 
> 
> 
> On Fri, Apr 5, 2024 at 10:54 PM Karl Ove Hufthammer <karl at huftis.org>
> wrote:
> 
> > Karl Ove Hufthammer skreiv 05.04.2024 21:44:  
> > > I recommend using Lokalize (and its ‘project’ feature). Then
> > > there’s basically no difference between PO files and
> > > POT-files-without-PO files. They both appear in the project view.
> > > The PO files have a green icon (fully translated) or blue icon
> > > (partially translated), while the POT files have a black icon.
> > > Then you click on the POT file, a PO file is *automatically*
> > > created in the correct folder. So you never have to go manually
> > > hunting for new files to translate.  
> >
> > To clarify, here’s a screenshot (attached) showing what the feature
> > looks like in Lokalize. Note that the ‘klock._json_.pot’ file is
> > shown with a black icon and has the file extension ‘.pot’, which
> > indicates that it doesn’t yet have a corresponding ‘.po’ file. When
> > you click on it, it’s opened as a normal translation file, which
> > you can translate, and it automatically gets a ‘.po’ extension when
> > you save it (using ‘Ctrl + S’).
> >
> >
> > --
> > Karl Ove Hufthammer
> >