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

(In reply to Gabriel Gazzán from comment #0)
> SUMMARY
> There are many compositions/effects names that are not currently translated
> in the UI.

Hi Gabriel, what is left to do in this ticket ?

Hi @luzpaz@protonmail.com !
As of the latest nightly (11891):

- Compositions names are all translated.
- The effects names still untranslated are listed below:

Alpha, Mask, and Keying
------------------------
Lumakey
Premultiply or Unpremultiply
Spillsupress


Color and Image Correction
-------------------------------
Bw0r
Grayworld
Invert0r
Swapuv


Misc
-----
Alphaextract
Backgroundkey
Colordetect
Colorspace & Transfer Characteristics
Libswscale Color Transform
Scale
Scale_d3d11
Set Qt Blend Mode
Sr_amf
Vpp_amf
Xine Deinterlacer


Stylize
-------
NDVI filter


Deprecated
-------------
Basic Image Converter
Blockdetect
Blurdetect
Ccrepack
FFmpeg Image Converter (appears 2 times?)
FFmpeg Image Scaler
Fsync
Grad Fun
Latency
Legacy FFmpeg Deinterlacer
Scdet
Siti
Subtitle (appears 2 times?)
Tiltandshift

Thanks a lot for this last list. So in fact these are the effects that don't have an xml description. Instead of writing xml files just to have translation, I will try to write a small script that will extract the necessary strings and input them in our translation pipeline.

Created attachment 188802 [details]
attachment-3390021-0.html

It’s probably easier to quickly whip up the XML files than writing the script. I can get on it tomorrow. 


Sent from Yahoo Mail for iPhone


On Thursday, January 22, 2026, 9:40 PM, Jean-Baptiste Mardelle <bugzilla_noreply@kde.org> wrote:

https://bugs.kde.org/show_bug.cgi?id=473086

--- Comment #18 from Jean-Baptiste Mardelle <jb@kdenlive.org> ---
Thanks a lot for this last list. So in fact these are the effects that don't
have an xml description. Instead of writing xml files just to have translation,
I will try to write a small script that will extract the necessary strings and
input them in our translation pipeline.

After looking more closely, quite o lot of these effects are also not directly usable in Kdenlive and should not be displayed in the list, I will work on it.
Also, Bernd, creating xml files should have an added value, since it makes the Kdenlive sources larger and startup slower as we have to read each of them on startup. 

Having a way to simply gather translations in case nothing else is needed for an effect/composition seems like a better approach to me.

I agree it seems a good/fast solution.

I've just realized that I unintentionally left out the Audio effects in the previous list. 😅

Here they are:

Audio
------------------------------------------------
· Adecorrelate
· Adenorm
· Adrc
· Adynamicequalizer
· Adynamicsmooth
· Aexciter
· Afreqshift
· Afwtdn
· Alatency
· Ambisonic Decoder
· Ambisonic Encoder
· Aphaseshift
· Apsyclip
· Arnndn
· Aspectralstats
· Asubboost
· Asubcut
· Asupercut
· Asuperpass
· Asuperstop
· Atilt
· Audio Levels
· Audio Sample Format Converter
· Audio Seam
· Auto Fade
· Convert Audio Channel Count
· Dialoguenhance
· FFmpeg Audio Resampler
· Speechnorm
· Tiltshelf
· Virtualbass


Channels
------------------------------------------------
· Audio Pan


Modulators
------------------------------------------------
· Treble


Tools
------------------------------------------------
· Aderivative
· Aintegral


Volume and Dynamics
------------------------------------------------
· Asoftclip


Finally, there are also the default template effects (that I don't know if they could technically be translated or not), but in any case, here they are too:

Templates
------------------------------------------------
· Secondary color correction
· secondary-color-correction-v2
· Shut-off

I agree, too, with the approach of not showing effects that are not really useful to users, as they only generate confusion and ultimately complaints.

Git commit d794ad1888b224617c6683feb8eb70c1abf6e439 by Jean-Baptiste Mardelle.
Committed on 23/01/2026 at 09:30.
Pushed by mardelle into branch 'release/25.12'.

Hide some irrelevant effects from UI using hidden_effects.txt / hidden_transitions.txt files. Allow copy from effects list description

M  +12   -0    data/excluded_effects.txt
A  +10   -0    data/hidden_effects.txt
A  +2    -0    data/hidden_transitions.txt
M  +5    -0    src/assets/abstractassetsrepository.hpp
M  +7    -0    src/assets/abstractassetsrepository.ipp
M  +17   -7    src/assets/assetlist/view/assetlistwidget.cpp
M  +4    -0    src/assets/assetlist/view/assetlistwidget.hpp
M  +8    -1    src/effects/effectsrepository.cpp
M  +3    -0    src/effects/effectsrepository.hpp
M  +6    -0    src/mainwindow.cpp
M  +8    -0    src/transitions/transitionsrepository.cpp
M  +3    -0    src/transitions/transitionsrepository.hpp
M  +2    -0    src/uiresources.qrc

https://invent.kde.org/multimedia/kdenlive/-/commit/d794ad1888b224617c6683feb8eb70c1abf6e439

A possibly relevant merge request was started @ https://invent.kde.org/multimedia/kdenlive/-/merge_requests/795

(In reply to Jean-Baptiste Mardelle from comment #20)
> After looking more closely, quite o lot of these effects are also not
> directly usable in Kdenlive and should not be displayed in the list, I will
> work on it.
> Also, Bernd, creating xml files should have an added value, since it makes
> the Kdenlive sources larger and startup slower as we have to read each of
> them on startup. 
> 
> Having a way to simply gather translations in case nothing else is needed
> for an effect/composition seems like a better approach to me.

frei0r.ndvi is missing crucial parameters, so IMO a XML is needed. If I create one, does that negate/supercede your script? Or is it overwritten/ignored by your script?

Perhaps we discuss this first, decide which effects are not suitable for the user, and then work on the remaining ones with or without XML.

Created attachment 188830 [details]
Current list of available effects and their testing status

I have started this list to continue the excellent work Massimo has started. Note avfilter audio effects are still pending as most audio effects are WIP. I worked extensively on LADSPA effects due to some community requests.

Created attachment 188831 [details]
Current list of available effects and their testing status (V2)

Update to allow filtering by audio filters/effects

(In reply to Bernd from comment #25)
> frei0r.ndvi is missing crucial parameters, so IMO a XML is needed. 

I remember spending quite some time trying to obtain something useful from this effect, unfortunately without any success.
So, I believe there must be something missing in its current implementation in Kdenlive. 👍

(In reply to Gabriel Gazzán from comment #28)
> (In reply to Bernd from comment #25)
> > frei0r.ndvi is missing crucial parameters, so IMO a XML is needed. 
> 
> I remember spending quite some time trying to obtain something useful from
> this effect, unfortunately without any success.
> So, I believe there must be something missing in its current implementation
> in Kdenlive. 👍

The new XML is here: https://invent.kde.org/multimedia/kdenlive/-/merge_requests/797

You can already put it into the effects folder of your Kdenlive installation and it works (any update of Kdenlive before it's merged and part of the next build overwrites that, of course).

(In reply to Bernd from comment #29)
> (In reply to Gabriel Gazzán from comment #28)
> > (In reply to Bernd from comment #25)
> > > frei0r.ndvi is missing crucial parameters, so IMO a XML is needed. 
> > 
> > I remember spending quite some time trying to obtain something useful from
> > this effect, unfortunately without any success.
> > So, I believe there must be something missing in its current implementation
> > in Kdenlive. 👍
> 
> The new XML is here:
> https://invent.kde.org/multimedia/kdenlive/-/merge_requests/797
> 
> You can already put it into the effects folder of your Kdenlive installation
> and it works (any update of Kdenlive before it's merged and part of the next
> build overwrites that, of course).

Great! Thx.
I'll give it a try...

(In reply to Bernd from comment #29)
Oh, yes... it totally changed into a useful effect! 😎
Thanks for that!

Now, I can visualize people being able to use Kdenlive to work with this kind of footage. 💪

Git commit 3335721fffd79895b3ffe09110efe53ade92f496 by Jean-Baptiste Mardelle, on behalf of Bernd Jordan.
Committed on 12/02/2026 at 17:07.
Pushed by mardelle into branch 'master'.

Update/Add some effects XML

Adding XML files for
* NDVI

Updating XML files for
* 3-point balance
* avfilter.colorize (fixed hue setting)
* avfilter.scroll (fixed initial positions, see bug 510325)

M  +1    -1    data/effects/avfilter/avfilter_colorize.xml
M  +2    -2    data/effects/avfilter/avfilter_scroll.xml
M  +1    -0    data/effects/frei0r/CMakeLists.txt
A  +53   -0    data/effects/frei0r/frei0r_ndvi.xml
M  +10   -10   data/effects/frei0r/frei0r_three_point_balance.xml

https://invent.kde.org/multimedia/kdenlive/-/commit/3335721fffd79895b3ffe09110efe53ade92f496