Untranslatable strings

[Oleh]

Hello!
Please update language file but sometimes there are untranslated strigs.

[eumagga0x2a]

Your screenshot looks like you don't use the latest Avidemux build. If you have translated a string in a particular context, but the translation is not shown, this usually means that the .ts file is not in sync with the Avidemux build you are testing with.

Translation files in https://github.com/mean00/avidemux2_i18n are indeed not fully up to date, but this doesn't affect the strings you have pointed out. I can refresh them if this helps, but please be aware that some translatable strings will likely change before the 2.7.7 release and the files will be refreshed again closer to the release date.

[Oleh]

OK. Let's wait until the release of 2.7.7. but please update ts for ukrainian.

[eumagga0x2a]

Please don't wait until the release happens, just please be aware that some changes are expected to come before 2.7.7 is out.

[Oleh]

In the updated ts, I've updated the Ukrainian localization, but not all lines are localized.
Please see the images.

[eumagga0x2a]

The only location which actually should be translatable is the label in the progress dialog ("Залишилося часу: 12 seconds") where the strings originate from avidemux/common/ADM_osSupport/ADM_misc.cpp and are not collected by lrelease for not immediately clear reason (apart from the bad idea to hardcode plural form which is specific for English but wrong for many other languages). The code needs to be fixed to properly support plural.

The rest are strings which cannot be made translatable.

[Oleh]

Ok. I understand.
Thanks.

[Oleh]

Hi!
I've problem with post in branch Translation.

CleanTalk: *** Forbidden. Please enable JavaScript. ***

My version Qt Linguist 4.8 for Windows.
Type the "unfinished" disappears because I mark the translated strings as completed.
Why did they disappear obsolete|vanished? I do not know.
However, I was looking for obsolete|vanished in
en.ts = 0
fr.ts - obsolete = 0, vanished = 2
ru.ts - obsolete = 11, vanished = 0

An interesting case when compared!

ru.ts

        <source>&amp;Calculator...</source>
        <translation type="obsolete">&amp;Калькулятор...</translation>
   
fr.ts

        <source>&amp;Calculator...</source>
        <translation type="vanished">&amp;Calculette...</translation>

I downloaded the distribution from the link you sent me
https://github.com/mean00/avidemux2_i18n/commit/4391aa58cafd16c67952a2fa17a7bcbddca41f0b

[eumagga0x2a]

I've problem with post in branch Translation.

CleanTalk: *** Forbidden. Please enable JavaScript. ***

CleanTalk false-positives, again. Please try posting from a private browser window, this was reported to help sometimes.

My version Qt Linguist 4.8 for Windows.

Hoppla, it should be 5.x, preferably the latest available. Qt4 and all related tools are deprecated and mostly unsupported in Avidemux (even if effort is done not to break compilation with Qt4). 

Type the "unfinished" disappears because I mark the translated strings as completed.

Right, just please don't mark empty translations as finished if they are not meant to be empty (I know, I advised somewhere to do the opposite, my bad).

Why did they disappear obsolete|vanished? I do not know.

"vanished" was introduced by Qt5, your Linguist version cannot understand it. I am still unsure whether you provide the full source to Linguist.

However, I was looking for obsolete|vanished in
en.ts = 0
fr.ts - obsolete = 0, vanished = 2
ru.ts - obsolete = 11, vanished = 0

An interesting case when compared!

ru.ts

        <source>&amp;Calculator...</source>
        <translation type="obsolete">&amp;Калькулятор...</translation>
 
fr.ts

        <source>&amp;Calculator...</source>
        <translation type="vanished">&amp;Calculette...</translation>

I must have been wrong about the way lrelease sets these hints. It definitely doesn't overwrite the type value if a translation already has been marked as obsolete.

I downloaded the distribution from the link you sent me
https://github.com/mean00/avidemux2_i18n/commit/4391aa58cafd16c67952a2fa17a7bcbddca41f0b

You need the C++ source you translate (how do you know the semantics of what you translate then??), not just the translation files, i.e. you need to clone both repositories – the main one AND the i18n submodule as outlined in https://avidemux.org/smif/index.php/topic,19122.msg88990.html#msg88990 even if you don't use GitHub.

[Oleh]

Right, just please don't mark empty translations as finished if they are not meant to be empty (I know, I advised somewhere to do the opposite, my bad).

********************************************

I updated empty translations as unfinished.

[eumagga0x2a]

Thank you, I'll check it tomorrow.

[eumagga0x2a]

Update applied. Thank you for fixing a lot of cases of destroyed format specifications, my apologies for the delay.

I've regenerated translation files as there have been some changes in the x265 video encoder plugin GUI including the RDO (rate-distortion optimisation) part, notoriously difficult to translate (e.g. it is horribly wrong in the Russian translation but pretty close in the German one, albeit also not optimal).

[Oleh]

Which are synonyms to the rate and distortion.

[eumagga0x2a]

Just pointing to the Wikipedia article might be better than me trying to explain it:

https://en.wikipedia.org/wiki/Rate%E2%80%93distortion_theory

[xyzzy]

I don't think "Abweichung bewerten" is really right for a German translation of "Rate distortion".  It seems like a translation if "rate" were a verb, as if one were saying "evaluate distortion" or "measure distortion."

But that is not what is being said.  "Rate Distortion Optimization:" could be written in a longer form as "Parameters to control the optimization of Rate and Distortion:".  Rate and Distortion are two nouns.

Deutsche wikipedia translates it as "Rate-Verzerrungs".  I found a patent text that uses "Steuerung der Ratenverzerrung" for exactly this concept.  But I wonder "Ratenverzerrung" really is more like "distortion of rate", akin to "Zeitverzerrung" as "warping of time", which isn't the correct concept.