Update avidemux_fr.ts

[Need74]

Hi
I have done the update of one line of the Avidemux_fr.ts file.

For the rest I am in the process of finishing the complete translation of the "avidemux_fr.ts" file on the missing terms and the errors of interpretation or poorly adapted wording.

I searched everywhere on my PC where the "avidemux_fr.xml" or .ts file could be found without finding anything. I am therefore having difficulty validating all my proposals because I cannot reproduce the action of my changes.

It may indeed happen that my proposals are too long depending on the available space or are not adapted to the correct screen or dialog box. I am therefore interested in a way to test my work without necessarily going through the source code, the implementation of which I do not understand.

Thank you for your feedback and thank you to the developers of Avidemux who offer free software that is very useful for anyone who wants to adapt videos to their hardware environment.

best regard

[eumagga0x2a]

I apologize for disappearing for so long. I would strongly recommend to install a modern user-friendly Linux distribution (e.g. Fedora or Ubuntu) which should give you a working local build environment for Avidemux with minimal effort within a fraction of an hour, please see README. Translation files (*.ts) will be in avidemux2/avidemux/qt4/i18n directory.

As font sizes vary a lot across platforms, something that works great in one environment may look strange in another. This is normal and is hard to avoid.

Regarding the payload of this PR, are you sure that the French translation of "B-frames" needs a hyphen? I hardly ever saw "trames B" written as "trames-B".

[Need74]

Hi and also sorry for my lack of responsiveness.

I note with interest that my translation work is listened to and I am very happy to share a little passion for this wonderful Avidemux software that I discovered a good ten years ago when I started wanting to put videos on my phone at the time and normal formats were very large.

I have almost finished the work of translating the entire software, including the dialog boxes as well as all the plugins and other muxer-demuxers.

Not being comfortable with compiling software and working on source files, I contented myself with working on the interface adaptation file for my French language which is "linguist_fr.qm" and its version .xml linguist_fr.ts.

I used Qt-linguist which allows you to compile ".ts" files on which it is possible to make modifications with a simple text editor.

Thanks to Qt-linguist I was able to extract the German, Turkish, and Slovak translation files which are very complete and I was thus able to find all or almost all the references to the lines to be able to write the lines in my French language.

For this purpose I also created an empty English translation file linguist_en.ts and also its compiled version linguist_en.qm in which I arranged all the section "names" in alphabetical order so that the file comparison of a language to another is facilitated. To carry out this sorting I developed a small macro on Excel to create an .xml file with entries sorted by and empty at the translation level.

Then to make the comparisons I use the excellent Winmerge and they were very useful for me to adjust my translation as best as possible because I am only an amateur in video and I do not master all the technical English vocabulary.

I have tried to the best of my ability to translate all the terms into French even if for some the English term is so popularized that it is sometimes useful to keep it, at least between (). I'm thinking of Suround or Loudness.... Knowing that for many people, knowing the translation into their language allows them to better understand what the software does.

Concerning the dash for B-frame I don't think it's very important to put it or not but indeed it seems to me that it would be good to be able to have two translation files for the same language, a very technical file at the same time. use by people who know the world of audio and video with the classic English terms "Frames, Bitrate....." and another for those who are discovering and being closer to the person's native language with " Image, Flow...." but that's another debate.

So thank you for telling me how I can share my work on the Github platform because I noticed that the language files (.ts) present are somewhat different from the base file, notably with lines of which I suppose indicates the history of modifications but which I do not know how to master with Qt-linguist.

I'm going to stop my long message here which shows that I have really become passionate about video editing for several years and that Avidemux with its free distribution has greatly supported me.

Very cordially and with the pleasure of sharing in a free world.

PS: I can make available as an attachment the ".ts" files for French and the blank English file with the choice of classification by or as it is in the Turkish version (the most complete) or the original French version of which I almost doubled the number of lines.
I still have plenty of questions and comments regarding the software but that will be for another discussion.