https://bugs.kde.org/show_bug.cgi?id=473086
--- Comment #4 from Gabriel Gazzán <gabcor...@gmail.com> --- (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. -- You are receiving this mail because: You are watching all bug changes.
