What language is missing?

You seem to have good command of the English language so perhaps you could help by providing the translation of said effects to whatever language you want to see them translated to.

The current state of the translation of the Kdenlive documentation is listed here (https://l10n.kde.org/stats/gui/trunk-kf5/package/documentation-docs-kdenlive-org/) where you can also find how to contribute to and help with the translation.

(In reply to Bernd from comment #1)
> What language is missing?
> 
> You seem to have good command of the English language so perhaps you could
> help by providing the translation of said effects to whatever language you
> want to see them translated to.
> 
> The current state of the translation of the Kdenlive documentation is listed
> here
> (https://l10n.kde.org/stats/gui/trunk-kf5/package/documentation-docs-
> kdenlive-org/) where you can also find how to contribute to and help with
> the translation.

(In reply to Bernd from comment #1)
> What language is missing?
> 
> You seem to have good command of the English language so perhaps you could
> help by providing the translation of said effects to whatever language you
> want to see them translated to.
> 
> The current state of the translation of the Kdenlive documentation is listed
> here
> (https://l10n.kde.org/stats/gui/trunk-kf5/package/documentation-docs-
> kdenlive-org/) where you can also find how to contribute to and help with
> the translation.

Hi Bernd,
Thanks for answering so quickly.
I am, in fact, the translator for Spanish, since 2011. :)
Last month I've also taken the translation of the documentation in charge, and I'm doing it at a good pace. That has had the side effect of me really looking much deeper into every feature/option in the UI, so I started filing several issues here, in case they are of help. I have several others that I haven't managed to post yet, but they will come...

Specifically, the problem I'm reporting here is that the vast majority of those compositions/effects names don't even appear in the PO file to be translated, so they should be in English in all locales, I guess.
There's one honorable mention that I remember, that does appear in the PO (and is translated there), but still remains untranslated in the UI, and that is the "Wipe" transition.

Cheers,
g

(In reply to Gabriel Gazzán from comment #2)
> (In reply to Bernd from comment #1)
> > What language is missing?
> > 
> > You seem to have good command of the English language so perhaps you could
> > help by providing the translation of said effects to whatever language you
> > want to see them translated to.
> > 
> > The current state of the translation of the Kdenlive documentation is listed
> > here
> > (https://l10n.kde.org/stats/gui/trunk-kf5/package/documentation-docs-
> > kdenlive-org/) where you can also find how to contribute to and help with
> > the translation.
> 
> (In reply to Bernd from comment #1)
> > What language is missing?
> > 
> > You seem to have good command of the English language so perhaps you could
> > help by providing the translation of said effects to whatever language you
> > want to see them translated to.
> > 
> > The current state of the translation of the Kdenlive documentation is listed
> > here
> > (https://l10n.kde.org/stats/gui/trunk-kf5/package/documentation-docs-
> > kdenlive-org/) where you can also find how to contribute to and help with
> > the translation.
> 
> Hi Bernd,
> Thanks for answering so quickly.
> I am, in fact, the translator for Spanish, since 2011. :)
> Last month I've also taken the translation of the documentation in charge,
> and I'm doing it at a good pace. That has had the side effect of me really
> looking much deeper into every feature/option in the UI, so I started filing
> several issues here, in case they are of help. I have several others that I
> haven't managed to post yet, but they will come...
> 
> Specifically, the problem I'm reporting here is that the vast majority of
> those compositions/effects names don't even appear in the PO file to be
> translated, so they should be in English in all locales, I guess.
> There's one honorable mention that I remember, that does appear in the PO
> (and is translated there), but still remains untranslated in the UI, and
> that is the "Wipe" transition.
> 
> Cheers,
> g

Very nice to meet you, Gabriel!

I am currently working on the documentation updating old stuff, adding missing stuff and bringing screenshots up to date. There are a few new things Eugen and I are putting in to make it an even more useful documentation.

I don't know how i18n works and who or what creates the PO files you mentioned. But in terms of translating effect names I am wondering whether it would be better to focus on the effect descriptions than on the names.

(In reply to Bernd from comment #3)
> (In reply to Gabriel Gazzán from comment #2)
> > (In reply to Bernd from comment #1)
> > > What language is missing?
> > > 
> > > You seem to have good command of the English language so perhaps you could
> > > help by providing the translation of said effects to whatever language you
> > > want to see them translated to.
> > > 
> > > The current state of the translation of the Kdenlive documentation is listed
> > > here
> > > (https://l10n.kde.org/stats/gui/trunk-kf5/package/documentation-docs-
> > > kdenlive-org/) where you can also find how to contribute to and help with
> > > the translation.
> > 
> > (In reply to Bernd from comment #1)
> > > What language is missing?
> > > 
> > > You seem to have good command of the English language so perhaps you could
> > > help by providing the translation of said effects to whatever language you
> > > want to see them translated to.
> > > 
> > > The current state of the translation of the Kdenlive documentation is listed
> > > here
> > > (https://l10n.kde.org/stats/gui/trunk-kf5/package/documentation-docs-
> > > kdenlive-org/) where you can also find how to contribute to and help with
> > > the translation.
> > 
> > Hi Bernd,
> > Thanks for answering so quickly.
> > I am, in fact, the translator for Spanish, since 2011. :)
> > Last month I've also taken the translation of the documentation in charge,
> > and I'm doing it at a good pace. That has had the side effect of me really
> > looking much deeper into every feature/option in the UI, so I started filing
> > several issues here, in case they are of help. I have several others that I
> > haven't managed to post yet, but they will come...
> > 
> > Specifically, the problem I'm reporting here is that the vast majority of
> > those compositions/effects names don't even appear in the PO file to be
> > translated, so they should be in English in all locales, I guess.
> > There's one honorable mention that I remember, that does appear in the PO
> > (and is translated there), but still remains untranslated in the UI, and
> > that is the "Wipe" transition.
> > 
> > Cheers,
> > g
> 
> Very nice to meet you, Gabriel!
> 
> I am currently working on the documentation updating old stuff, adding
> missing stuff and bringing screenshots up to date. There are a few new
> things Eugen and I are putting in to make it an even more useful
> documentation.
> 
> I don't know how i18n works and who or what creates the PO files you
> mentioned. But in terms of translating effect names I am wondering whether
> it would be better to focus on the effect descriptions than on the names.

Same to me, Bernd! :)
I see the work you're doing daily, when I update my SVN. It's much appreciated, there are various sections of the manual that are really out of date.

Just for the record, I'm referring in this issue to the UI, not the documentation.
Of course there are several effects with such strange names that I wouldn't dare to translate them (nor it'd make any sense), but at the same time, there are several other ones with much more common names, that users often see translated in other programs as well. So the idea would be to have as much effects with localized names as it makes sense. The same applies to compositions, which names are pretty standard in every comp app out there, and users are used to see them translated.
Then, of course the effects' parameters (that's a whole other issue), and descriptions / "tooltips" are really useful to have localized too.

Hi there,
After a long while, I'd like to check if there's any intention to make the compositions and effects names translatable in the UI ?
I think it would greatly improve the sense of completeness of the translation of the program.
Or is there any technical obstacles for achieving this goal, that I'm missing?

Thanks for listening!

Git commit 3a495be063de5eb334e87fbacd623f0b5de623ef by Jean-Baptiste Mardelle.
Committed on 14/03/2025 at 06:00.
Pushed by mardelle into branch 'release/25.04'.

Add missing subfolders for translations

M  +1    -1    Messages.sh

https://invent.kde.org/multimedia/kdenlive/-/commit/3a495be063de5eb334e87fbacd623f0b5de623ef

Thanks for your report. Turns out lots of our effects / transitions xml info files where in subfolders that were not included by the extract message script. I now just fixed that and most of the missing stuff now seems to appear.
KDE's CI job extracting and updating script seems to run around 5am CET time, so tomorrow the new strings should show up in the translation system.

Oh... great!
That's excellent news! :)
Thank you
g

I've noticed that a handful of composite methods still remain untranslated,
all of them were already translated in the PO file since long ago (but never shown translated in the UI) 
and are also labeled in the PO file as "Transition Name":

- Composite
- Dissolve
- Slide
- Transform
- Wipe

and maybe (since their names in English and Spanish are the same, I can't confirm. but they meet the pattern...)
- Luma
- Regionalize (don't know what is that, but appears as a transition name)

3 more effect names that don't show translated in the UI, even though they are translated in the PO file since long ago:

Audio Pan
Mask Apply
3-way Rotate

(most probably there's also a few more...)

Thanks for your report. I don't find anything in the code that could explain the missing translations. However all transitions you mention have a context attribute for their name, like:
https://invent.kde.org/multimedia/kdenlive/-/blob/master/data/transitions/composite.xml#L4

Could you check if editing the xml to remove the context="..." attribute in the name fixes the translation ?
For example edit /usr/share/kdenlive/transitions/composite.xml and change the name tag in line 4 to be:

<name>Composite</name>

Then restart Kdenlive and check if the translation appears..
Thanks in advance.

Removing the context from the "context.xml" didn't change the end result...
BUT
Removing the string context from the PO file (and compiling it again into a MO) did work!

I've later undone the first step (the change in the context.xml), and the translation kept showing as expected.

I don't know what all this really means! haha :D

Yes!! Good catch. The translation context was the key. I will work on a fix in the next days.

niiice
thanks!!  :)

Git commit 9a08c67ee2aea88e735750a02d40679c6dc756d2 by Jean-Baptiste Mardelle.
Committed on 21/03/2025 at 05:40.
Pushed by mardelle into branch 'release/25.04'.

Fix some effects/composition names appear untranslated - caused by i18n context

M  +7    -3    src/assets/abstractassetsrepository.ipp
M  +16   -1    src/xml/xml.cpp
M  +3    -0    src/xml/xml.hpp

https://invent.kde.org/multimedia/kdenlive/-/commit/9a08c67ee2aea88e735750a02d40679c6dc756d2