Hi,
i\'ve translates (not 100% complete) the qt_de.qm.
i\'ve copy the file in the i18n-folder of avidemux 2.5, started avidemux2_qt4.exe, but no effect. the inferface is in english.
the gtk-version is in german, no problem.
how can i try the german file?
and: Who is the bugtracker???
Thanks
Since Avidemux translations are working again I post here the german translation files for the Qt interface:
Thanks to Mean the actual german translation is included within the AVIdemux v2.5.4 (r6714) package. This version you can download e.g. here (http://sourceforge.net/projects/avidemux/).
Translation for newer beta builds (http://avidemux.razorbyte.com.au/#avidemux2.5):
* r6796 (http://www.mediafire.com/file/7b2ok2kprzeortw/Avidemux_r6796_german.zip)
Usage:You need to copy/replace only both
qm files to the
i18n folder. Restart Avidemux and you should see the (updated) german GUI, if you use a german windows version. Please note this works first since Avidemux 2.5.3 (r6303).
Also I\'ve added both
ts files for further or individual editing of the language files.
However, the translation is definitely not 100% complete neither 100% correct, but it\'s a beginning after times without any translation. Btw. at this time some items can\'t translated yet, because they seem to be hardcoded or I don\'t found them within the ts files. Therefore I would need some help/advice for the
following unsolved issues found in
r6796:
[list=*]
- some items in the job list are still untranslateable, means the four column labels (at this time 1,2,3,4) and the different status labels in column 2, e.g. \"Ready\"[/*]
- the word \"Dummy\" in Tools --> Preferences... --> Audio --> AudioDevice can\'t translated[/*]
- the window title \"avidemux2\" of the indexing window can\'t translated[/*]
- the whole crash window can\'t translated, e.g. \"Press OK to build crash info\"[/*]
- under the video filter window: the description under each activated filter (right area) is not translateable, e.g. \"Rotate x degrees\" or \"V-Flip\"[/*]
- One phrase with several meanings:
[list=1]
- at the left side in the Avidemux main GUI --> the two buttons with the word \"Filters\" --> seems to be the same variable. For example it isn\'t possible to translate the upper button to \"Video Filter\" and the lower one to \"Audio Filter\". Thank you for the hint to LoRd_MuldeR.[/*]
- x264 encoder settings: the word \"disabled\" in three different pulldown menus: tab \"frame\" --> \"Adaptive B-frame Decision:\" and \"B-frames as References:\" and tab \"Motion\" --> \"Weighted Prediction for P-frames:\"[/*]
- Xvid encoder settings: The word \"Custom\" within the first tab \"General\" in the frame \"Multithreading\" and in the frame \"Pixel Aspect Ratio\" seems to be the same variable.[/*]
- the word \"none\" is used several times, e.g. in the encoding window next to the audio and video codec when the copy mode is chosen, in the audio filters in the pull down menu \"frame rate change\" and in the audio menu when you chose \"none\" audio track[/*]
Translation status: 92% (1.935 of 2.088 non-obsolete phrases)[/*]
- Main GUI including preferences and the \"encoding...\" window: done[/*]
- Decoder options (F3 key), postprocessing (F4 key) and video calculator (F7 key): done[/*]
- Auto scripts: done[/*]
- Shortcuts and keystrokes: done[/*]
- Plugin-Manager: done[/*]
- encoder configuration dialog boxes: almost done, except some special technical phrases, x264 settings have additional CLI switches[/*]
- Filters: Transform, Color, Sharpness, Subtitles, Misc done, the rest is partially completed[/*]
I don\'t know if it\'s a good idea to translate whole encoder settings. At some points I think it leads to more confusion than it helps, e.g. x264 encoder settings, last two tabs
\"Output\". I would be glad for some suggestions or opinions at all.
Quote from: Lanceat this time some items can\'t translated yet, because they seem to be hardcoded or I don\'t found them within the ts files
try and download this
http://svn.berlios.de/viewvc/*checkout*/avidemux/branches/avidemux_2.5_branch_gruntster/po/qt_filter_context.xsltand replace the one from my tools (you should do this from time to time)
this
should fix some problems like \"Configure\" and \"Filters\" buttons, or \"Preferences\" window
as for x264 and xvid configuration windows, I have the same problem.
Quote from: zoppoas for x264 and xvid configuration windows, I have the same problem.
Do you still have this problem if you use the latest TS file from SVN? These were generated using Qt 4.5.3.
@zoppo: You are right the updated xslt file solved that small GUI problem and the most Xvid issues. Thank you for your hint. I didn\'t know that I have to update that file from time to time.
@gruntster: I\'m sorry but my knowledge seems very limited to that things :(. But I downloaded the \"avidemux_de.ts\" file from here (http://svn.berlios.de/viewvc/avidemux/branches/avidemux_2.5_branch_gruntster/po/), hope that\'s the right one. But when I try to open that file with \"Qt Linguist\" it says \"Unexpected tag at avidemux_de.ts:3:67\", besides the doctype of that file is \"XHTML 1.0\" but the working ts file has a \"TS\" doctype. Maybe I\'ve done something wrong, please advice.
Btw. does this mean, if that new ts file will work at some time, I have to translate the whole ts file again? Pleeeaaase say no:o.
I\'ve updated the translation file and the open issues in my original post.
Sounds like the TS file wasn\'t saved properly. To download from SVN, right-click the download link on this page (http://svn.berlios.de/viewvc/avidemux/branches/avidemux_2.5_branch_gruntster/po/avidemux_de.ts?view=log) and select \"Save Target As\". Otherwise my next SDK build will contain the new TS file.
You don\'t need to translate the whole file again. The current version in SVN is the one you originally supplied but I\'ve updated it using Qt 4.5.3 to include the tags that were dropped by Qt 4.6.2. The Decoder Options, Postprocessing and Preferences windows all translate fine for me using this file. If you\'ve since made further updates it\'s no problem, I can do the update again.
Quote from: Lancedoes this mean, if that new ts file will work at some time, I have to translate the whole ts file again? Pleeeaaase say no:o.
here\'s a trick:
you can save the translated ts file as \"QT Linguist Phrase Book (*.qph)\".
then open the untranslated ts file, select \"Phrase\" menu, \"Open phrase book\".
then \"Edit\" menu, \"Batch translation\" -> \"Run\".
(I would not tick \"Set tranlsated entries to finished\", it\'s better to check them)
@zoppo and @gruntster: Thank you very mutch for your help, without you I couldn\'t have done this. I have updated the translation files again, but there are lot things undone.
@Lance - committed your version 6. Thanks again.
I made some additions especially to the x264 encoder settings including some new x264 settings introduced in r6288.
Further translations to all encoder settings have been done and some more untranslateable phrases were found. See again my first post in this thread.
Quote from: LanceFurther translations to all encoder settings have been done and some more untranslateable phrases were found. See again my first post in this thread.
Most of those should already be fixed in SVN except for the encoding window and Auto wizards.
What do you advice? Should I download again the latest \"qt_filter_context.xsl\" or should I wait for the next release for windows here (http://avidemux.razorbyte.com.au)? Or do you mean it should work already with r6288?
Probably best to wait for the next build. I\'ll try to squeeze in a fix for the encoding window too.
Very nice. Thank you.
r6303 checked but there are still some untranslateable phrases. Very strange is the tab name \"Settings\", I can translate that word for the \"M-JPEG Encoder\", \"M-PEG1 Encoder\" and the \"M-PEG2 Encoder\" within the ts file, but within AviDemux nothing happens :/.
Update: Shortcuts adapted to german language, video properties window completed (besides the untranslateable word \"frames\"), some bugs eliminated and some error windows translated
Translation file adapted to r6340...
Are most issues now resolved?
I\'m sorry I edited my first post after that message. Please have a look at post #2 and see for your own ;).
I have to state: Great work, thank you gruntster.
Cool, I\'ll investigate the outstanding issues. Auto scripts should be translatable now though. Does it not work?
You\'re right. All Auto scripts are translated, beside one phrase in the menu called \"Optical Disc\" because it\'s simultaneously a file name. I don\'t know how you wanne solve this. A solution could be renaming it to a trade name like the other items, e.g. \"CD/DVD\", but in file system conventions a slash isn\'t allowed.
* Video Filters window -> the button \"Partial\" (below right)
It should work. It hasn\'t been translated in your file (P&artial).
* Video properties windows -> 3 times the word \"No\" in the frame \"Extra Video Properties\"
Fixed r6342.
* Some shortcut keys can\'t translated: means \"Del\" to \"Entf\", \"End\" to \"Ende\", \"Home\" to \"Pos 1\" and \"Left, Right, Down, Up\" to \"nach links, nach rechts, nach unten, nach oben\".
Fixed r6343.
* Auto scripts: the item \"Optical Disc\" because it\'s the file name of the folder containig those scripts
Fixed r6348.
Your r6340 v2 translation is now committed. Thanks :)
You are incredible :o.
* Thank you for the hint regarding the \"Partial\" button in the filter window. It seems I was blind :/.
* Please note I\'ve found another strange connection in the x264 encoder settings. I translated the word \"Custom\" on the first tab \"General\" in the frame \"Multithreading\". After days I noticed now this translation took place on the last tab \"Output\", frame \"Pixel Aspect Ratio\", word \"Custom\", too. I suppose a custom \"Pixel Aspect Ratio\" has nothing to do with a custom \"Multithreading\" and vice versa :D?
Finally I have to state you fix the issues faster than I can find more of them :). I look forward to test the new revisions.
Update: ca. 60 new phrases translated (x264 settings, some translation errors corrected, word \"partial\" in filter window ;), etc.)
Quote from: Lance* Please note I\'ve found another strange connection in the x264 encoder settings. I translated the word \"Custom\" on the first tab \"General\" in the frame \"Multithreading\". After days I noticed now this translation took place on the last tab \"Output\", frame \"Pixel Aspect Ratio\", word \"Custom\", too. I suppose a custom \"Pixel Aspect Ratio\" has nothing to do with a custom \"Multithreading\" and vice versa :D?
Fixed r6351.
Update: 160 new phrases translated, e.g. Filters Transform and Subtitle done
Update:
Shortcuts: \"inside menu\" letter fine tuning done
some Xvid tanslations fixed
x264 translation completed and tuned
It would be very courteous when this files could committed to the Avidemux package, so I haven\'t to sync that whole bunch again with a newer revision. Besides in the next days no further upate will occur. Thank you very mutch in advance.
Quote from: LanceIt would be very courteous when this files could committed to the Avidemux package, so I haven\'t to sync that whole bunch again with a newer revision.
Unfortunately your upload link no longer works.
Update: synced for r6370, tried to include LoRd_MuldeR\'s hints (german) (http://avidemux.org/admForum/viewtopic.php?pid=44350#p44350)
Could you check please, very strange: From r6340 till r6370 some translations (692 phrases) seems to be gone?: In r6340 were 2096 phrases to translate in r6370 only 1404 phrases, still. E.g. almost the whole \"preferences\" window and name and settings of the \"MPEG-2 requant\" video encoder are gone.
Looks like I accidentally ran lupdate from Qt 4.6 which made a lot of the strings obsolete. I\'ve committed your latest version to SVN with the obsolete strings corrected.
Quote from: LanceUpdate: synced for r6370, tried to include LoRd_MuldeR\'s hints (german)
Nice :)
Update: I took the newest avidemux_de.ts (r6371) file from svn and synced it again with my latest translations. Please have a look at post #2 (http://avidemux.org/admForum/viewtopic.php?pid=44117#p44117) in this thread, because there are still some small issues.
It would be very courteous when this files could committed to the Avidemux package, so I haven\'t to sync that whole bunch again with a newer revision.
Thanks to a two years old post (http://avidemux.org/admForum/viewtopic.php?pid=27001#p27001) of user \"zoppo\" I\'ve found out how to translate special keys on localized keyboards, means e.g. cursor keys, \"Del\", \"End\" and \"Home\". In the file avidemux_xx.ts you can redefine the keys which are to press for a certain function. But there you have to use the original english keyboard layout labels, means e.g. \"Del\", \"End\", \"Home\" and for the cursor keys \"down\", \"up\", \"left\" and \"right\". But if you want to translate the displayed key for a certain function in the menu of Avidemux, e.g. menu \"Go\" --> \"previous frame\" -> \"left\", then you have to translate this case in the qt_xx.ts file.
translation files synced for r6442 and Plugin-Manager translated
Some new x264 settings translated.
I have troubles getting the file
Got it, thanks
Some new items translated:
* windows title \"Jobs\"
* the new x264 settings for weightp introduced from Alex Wright at Wed 24.10.2010:
\"Make --weightp 1 a better speed tradeoff
Since fade analysis is now so fast, weightp 1 now does fade analysis but no reference duplication.
This is the opposite of what it used to do (reference duplication but no fade analysis).
This also gives weightp\'s better fade quality to faster presets (up to superfast).\"
download (http://www.mediafire.com/file/7b2ok2kprzeortw/Avidemux_r6796_german.zip)
Here is the update gtk+ translation for german (usefull for 2.5.5 and 2.5.6).
Hi
I used Avidemux 2.5.6 in german.
Now I switched to 2.6.1 and I want to have it in german too.
Is there a way to have it (maybe partially with the existing translation) ?
You must have one of the last builds, the translations have been re-enabled on February 24th.
If you use the windows version, just copy the folder "i18n" from avidemux 2.5.6 and you should have a partial translation.
thanks for reply.
I just now redownloaded the windows binaries 2.6.1 from berlios and from the sourceforge mirror as well. the binaries are identical, sourceforge tells me that it was last modified at 2012-12-20.
I copied the i18n folder from 2.5.4 but now, Avidemux does not start anymore and there is no error message at all :-(
do I need to get newer binaries somehow? thanks.
yes, use latest. Download, unpack with 7zip, replace installed with this content. win 32/64-bit: http://avidemux.org/nightly/
cool, thanks!
I hope there isn't a problem when I wake up this thread. I wanne refresh my help in translating avidemux into the german language because the new nightly (http://www.avidemux.org/nightly/win64/) is working fine (for me). But at first I need some technical help to contribute. Where can I get always the latest ts-file for the translation? My progress I will post as usually here. I hope thats still the right way to do it? Otherwise please advice.
You can find the language files in latest git
I had a look into the files especially avidemux_de.ts and de.po. In my opinion most of the strings are already translated. But I cant see an effect by most of the strings within avidemux after applying the new translation file e.g. the first menu item File:
<message>
<location filename="../avidemux/ADM_userInterfaces/ADM_GTK/ADM_gui2/GUI_main2.cpp" line="291"/>
<source>_File</source>
<translation>_Datei</translation>
</message>
or within de.po:
#: avidemux/ADM_libraries/ADM_utilities/ADM_gettext.cpp:37
#: avidemux/ADM_userInterfaces/ADM_GTK/ADM_gui2/GUI_main2.cpp:291
msgid "_File"
msgstr "_Datei"
On the other hand the following string applies to avidemux, e.g.:
<message>
<location filename="../avidemux/ADM_userInterfaces/ADM_commonUI/DIA_prefs.cpp" line="420"/>
<source>Preferences</source>
<translation type="unfinished">Einstellungen</translation>
</message>
So why does the translation for the string Preferences work and for File it does not?
Furthermore I couldn't find e.g. the string Save as Image within the avidemux_de.ts and/or de.po. So it seems there is currently no way to translate this string, right?
Maybe someone could shed some light into this.
You can find the language files qt_de.ts avidemux_de.ts in latest git https://github.com/mean00/avidemux2/tree/master/avidemux/qt4/i18n
I don't have answers to your questions, I never used translation files.
Here is an incremental update for the German translation. The attached patch adds 47 neu translations and modifies 7 existing ones. It doesn't address any deeper issues like duplicated Ctrl+T shortcuts etc.
I didn't dare to remove type="unfinished" entries. What are they exactly for? What is going to happen with 1925 "obsolete" translations in avidemux_de.ts?
Just one caveat: usually the list of recently opened files lives in a submenu of the File menu. The current Avidemux Qt GUI departs from the canon and places "Recent" at the top level of the menu bar where the space is already populated by four more items which normally are put into a submenus. As german words are often quite long, this design decision doesn't work out well in the german locale.
The correct and already shortend translation for "Recent" would be "Zuletzt verwendet" ââ,¬â€œ 17 characters instead of 6! No way one could accomodate 11 additional characters in the menu bar, so I resorted to "Verlauf" ("History") instead. This is not really strictly correct, but this is as good as it gets and it still allows to use Alt+R shortcut to access the item via keyboard.
@@ -5672,11 +5672,11 @@ Drop timing informations ?</source>
</message>
<message>
<source>&Recent</source>
- <translation type="unfinished"></translation>
+ <translation type="unfinished">Ve&rlauf</translation>
</message>
First patch committed
Thx
Here comes the next iteration. The "translation-update-de-20160731" patch removes the conflicting Ctrl+T shortcut, adds somewhat 26 new, modifies 8 existing translations and deletes an arbitrarily picked duplicate. I did dare to delete a bunch of type="unfinished" entries for translations where I was really sure this time.
This patch requires the attached patch for avidemux/common/ADM_commonUI/DIA_prefs.cpp to make more strings translatable.
More iterations to come, starting with keyboard navigation in menus.
The time is ripe for the third iteration. The "translation-update-and-cleanup-de-20160811" patch removes 10 strings which should not be translated, adds 16 new translated strings, fixes a couple of old capitalisation and grammar issues and reworks a whole lot of my own translations from the first patch, adding accelerators in the main menu whenever practicable (I wish they were present in the English version) and resolving conflicts whenever possible.
Some translations do not work: http://avidemux.org/smif/index.php/topic,16909.msg76132.html#msg76132 (http://avidemux.org/smif/index.php/topic,16909.msg76132.html#msg76132)
The second patch, "make-adm-composer-strings-translations-work" makes already existing translations (and one new) in the ADM_Composer context work, replacing three incidences of QT_TR_NOOP in avidemux/common/ADM_editor/src with QT_TRANSLATE_NOOP in ADM_Composer context. If the idea of this patch is based on my error, please ignore it.
Here comes the next iteration as i18n-de-update-2016-09-04-and-remove-period-in-filter-names.patch merged with a partial fix for http://avidemux.org/smif/index.php/topic,17067.0.html (http://avidemux.org/smif/index.php/topic,17067.0.html) and a patch to accomodate the newly added "addBorder" context from [i18n] Make more strings translatable (Daniel Amm) (https://github.com/mean00/avidemux2/commit/4d7dc5d475706e20e650c37bf2618f445757e391) as many .ts files already contained suitable translations for this plugin in "addBorders" context.
My apologies for the massive all-in-one patch, I tried to operate with stacked, isolated patches and finally messed up the stack at some point :-[
Mean, if you are unhappy with an all-in-one patch, I'll carefully separate German translation update, the periods-after-filter-names cosmetics (maybe extended to include all offenders) and the new-context-for-existing-translations patch for the remainder of .ts files. This work wasn't doable yesterday. But prior to putting more time and effort into it, some communication would be helpful.
Committed as [i18n] German translation update by eumagga0x2a (https://github.com/mean00/avidemux2/commit/ae50ac0f15f34f2f85ff575b21fd33186bd082ec), thanks a lot!
It's been a while since I last updated the German translation ;)
The new iteration almost finalizes the translation of the top level of the main window, finally including tooltips, and adds translations for the "Black" and "Change FPS" plugins (total of 41 added or modified strings). A solution for numerus in translations is being sorely missed...
Translations for strings from avidemux_plugins/ADM_videoFilters6/changeFps/changeFps.cpp:38
const PredefinedFps_t predefinedFps[]=
{
{QT_TRANSLATE_NOOP("changeFps","Custom"), 10000,1000},
{QT_TRANSLATE_NOOP("changeFps","25 (PAL)"), 25000,1000},
{QT_TRANSLATE_NOOP("changeFps","23.976 (Film)"), 24000,1001},
{QT_TRANSLATE_NOOP("changeFps","29.97 (NTSC)"), 30000,1001},
{QT_TRANSLATE_NOOP("changeFps","50 (Pal)"), 50000,1000},
{QT_TRANSLATE_NOOP("changeFps","59.93 (NTSC)"), 60000,1001}
};
have no effect; any ideas why, please?
Not sure it is valid, i.e. the original code
I wish I would understand your hint. Is the problem related to QT_TRANSLATE_NOOP not being located inside a function?? The code as such works (though there is not much use of this plugin as it doesn't simultaneously operate on audio) and the *.ts file entries are correct.
A screenshot is attached.
That one was a bit of a puzzle.
The problem was actually 2 problems :
1- The pro file was outdated and the update script was broken. This is fixed
2- Two filters have about the same translation strings, but only one appeared in the pro file due to the above
So you were changing another filter
Both are hopefully fixed now
English show for [Copy] now [&Copy] in both Video and Audio Output (GUI)
It is probably being alisased to another menu entry
Quote from: Jan Gruuthuse on September 07, 2016, 08:05:25 AM
English show for [Copy] now [&Copy] in both Video and Audio Output (GUI)
Is Accelerators in the titles of diaElemTimeStamp shown as "&", don't work (http://avidemux.org/smif/index.php/topic,17128.0.html) actually the same?
Quote from: mean on September 07, 2016, 07:34:52 AM
That one was a bit of a puzzle.
The problem was actually 2 problems :
1- The pro file was outdated and the update script was broken. This is fixed
Is this how all my carefully crafted <location filename="path/to/source/file" line="uint16_t" /> entries were eradicated?
Quote2- Two filters have about the same translation strings, but only one appeared in the pro file due to the above
So you were changing another filter
I was editing the right context (changeFps). The context resampleFps has similar strings, this is true, and I can confirm that the configuration dialog of the "Change FPS" filter shows translations (or lack thereof) from the "Resample FPS" plugin. Is it another Qt bug, that Qt is not able to keep different contexts apart?
QuoteBoth are hopefully fixed now
No, but the issue is locally not visible due to new translations I added to the resampleFps context (it will be in the next i18n-de update).
The thing is the qt_update.sh script rescans the source file(s) and collects them for translatable string and adds entry to the ts files
It's better not to do it manually , else it will be erased at next update
I can revert the avidemux_de.ts file, but it will come back at a later point
Quote from: mean on September 07, 2016, 05:27:40 PM
I can revert the avidemux_de.ts file, but it will come back at a later point
No, please don't (if necessary I can always checkout an earlier revision of the file), as I've been warned now... However, if the script could add the references to the code on its own it would be really handy. They are extraordinary helpful for verifying the validity of translations in code. Otherwise I find myself grepping the source all the time.
That should be the case, but something does not work
Should be better now, sorry for the merges
Quote from: Jan Gruuthuse on September 07, 2016, 08:05:25 AM
English show for [Copy] now [&Copy] in both Video and Audio Output (GUI)
This is normal again.
Quote from: mean on September 07, 2016, 06:37:22 PM
Should be better now, sorry for the merges
Awesome (https://github.com/mean00/avidemux2/commit/265779eb266909c4cb7e24ec29390085f1deb8f4), thanks!
The next update for the German translation is attached.
This time an update almost (except of the description for the ssa filter) finalises the German translation for video filters and touches a couple of other areas (muxers, quota dialog etc.). The patch "i18n-de-update-2016-09-15.patch" adds 149 new and modifies 82 pre-existing translations.
Unfortunately, all Qt provided translations for "Cancel", "Open" etc. labels on buttons are MIA. No idea why, the qt_de.ts file seems to contain all necessary translations.
thanks
My apologies, I realized that I forgot to translate the update notification in the last i18n-de update. If the ship has sailed, then yeah, I'm too late. Otherwise the mini-patch
diff --git a/avidemux/qt4/i18n/avidemux_de.ts b/avidemux/qt4/i18n/avidemux_de.ts
index 3b08ac5..6f543fc 100644
--- a/avidemux/qt4/i18n/avidemux_de.ts
+++ b/avidemux/qt4/i18n/avidemux_de.ts
@@ -14078,7 +14078,7 @@ Please delete the idx2 file and reopen.</source>
<message>
<location line="-1301"/>
<source><b>New version available</b><br> Version %1<br>Released on %2.<br>You can download it here<br> <a href='%3'>%3</a><br><br><small> You can disable autoupdate in preferences.</small></source>
- <translation type="unfinished"></translation>
+ <translation><b>Neue Version verfügbar</b><br>Version %1<br>Freigegeben am %2.<br>Das Update kann hier heruntergeladen werden:<br><a href='%3'>%3</a><br><br><small>Sie können automatische ÃÅ"berprüfung auf Updates in Einstellungen deaktivieren.</small></translation>
</message>
<message>
<location line="+788"/>
is attached (tested with a local "update server").
By the way, due to the string for the date coming directly from the content of "update_for_(Linux|Win(32|64)).html" file it is not localized, and the US date format (is it meant to be the US date format?) is very confusing for Germans who write month and day in the opposite order. It is twice as confusing if such date string is embedded into a German text. Maybe using the ISO date format like 2016-02-09 instead?
(Of course, serving an unsigned file over unencrypted connection suggesting user to click on a link can never go wrong...)
I sense a bit of irony
The only way it could be dangerous is :
1- Taking control of avidemux.org
2- Overriding local DNS
Both are more of a problem by themselves, unless i'm missing something
Yes, sure. Any MITM could be an issue too, but really, to have a way to let user know about a new release is a big improvement on its own, even if it doesn't meet standards of players like Mozilla etc.
Agreed, it is a first version
The following rather small update modifies 18 translations:
diff --git a/avidemux/qt4/i18n/avidemux_de.ts b/avidemux/qt4/i18n/avidemux_de.ts
index 3b08ac5..26b5303 100644
--- a/avidemux/qt4/i18n/avidemux_de.ts
+++ b/avidemux/qt4/i18n/avidemux_de.ts
@@ -7812,22 +7812,22 @@ Drop timing informations ?</source>
<message>
<location filename="../../common/ADM_commonUI/DIA_builtin.cpp" line="-16"/>
<source>Fontconfig</source>
- <translation type="unfinished">Schriftkonfiguration</translation>
+ <translation type="unfinished"></translation>
</message>
<message>
<location line="+2"/>
<source>Gettext</source>
- <translation type="unfinished">Gettext</translation>
+ <translation type="unfinished"></translation>
</message>
<message>
<location line="+5"/>
<source>x86</source>
- <translation type="unfinished">Kodierer {86?}</translation>
+ <translation type="unfinished"></translation>
</message>
<message>
<location line="+1"/>
<source>x86-64</source>
- <translation type="unfinished">Kodierer</translation>
+ <translation type="unfinished"></translation>
</message>
<message>
<location line="+7"/>
@@ -8100,7 +8100,7 @@ Läuft es trotzdem?</translation>
<message>
<location line="+8"/>
<source>Select File to Save Audio</source>
- <translation type="unfinished">Wähle eine Datei um den Ton zu speichern</translation>
+ <translation type="unfinished">Audio-Datei zum Speichern wählen</translation>
</message>
<message>
<location line="+5"/>
@@ -8110,17 +8110,17 @@ Läuft es trotzdem?</translation>
<message>
<location line="+5"/>
<source>Select BMP to Save</source>
- <translation type="unfinished">Wähle einen BMP-Dateinamen um zu speichern</translation>
+ <translation>BMP-Datei zum Speichern wählen</translation>
</message>
<message>
<location line="+6"/>
<source>Select JPEG to Save</source>
- <translation type="unfinished">Wähle einen JPEG-Dateinamen um zu speichern</translation>
+ <translation>JPEG-Datei zum Speichern wählen</translation>
</message>
<message>
<location line="+8"/>
<source>Select File to Save</source>
- <translation type="unfinished">Wähle einen Dateinamen um zu speichern</translation>
+ <translation>Datei zum Speichern wählen</translation>
</message>
<message>
<location line="+62"/>
@@ -8946,7 +8946,9 @@ Warning, the settings must be close.</source>
<source>The video is in copy mode but the cut points are not on keyframes.
The video will be saved but there will be corruption at cut point(s).
Do you want to continue anyway ?</source>
- <translation type="unfinished"></translation>
+ <translation>Für Video ist der Kopiermodus ausgewählt, aber Schittpunkte befinden sich nicht auf Keyframes.
+Das Video wird gespeichert, aber es wird Bildstörungen an Schnittpunkten geben.
+Trotzdem fortsetzen?</translation>
</message>
<message>
<location line="+11"/>
@@ -9648,13 +9650,14 @@ This message will not be displayed again.</source>
<message>
<location filename="../../../avidemux_plugins/ADM_muxers/muxerAvi/muxerAvi.cpp" line="+74"/>
<source>Bad Idea</source>
- <translation type="unfinished"></translation>
+ <translation type="unfinished">Tun Sie dies nicht!</translation>
</message>
<message>
<location line="+0"/>
<source>Using H264/H265 in AVI is a bad idea, MKV is better for that.
Do you want to continue anyway ?</source>
- <translation type="unfinished"></translation>
+ <translation>Es ist eine schlechte Idee, AVI für H264/H265 zu verwenden, MKV ist dafür besser geeignet.
+Trotzdem fortsetzen?</translation>
</message>
<message>
<location line="+10"/>
@@ -9664,7 +9667,7 @@ This message will not be displayed again.</source>
<message>
<location line="+0"/>
<source>Cannot create AVI file</source>
- <translation type="unfinished"></translation>
+ <translation>Kann AVI-Datei nicht erstellen</translation>
</message>
<message>
<location filename="../../../avidemux_plugins/ADM_muxers/muxerAvi/muxerAviConfig.cpp" line="+25"/>
@@ -9674,7 +9677,7 @@ This message will not be displayed again.</source>
<message>
<location line="+3"/>
<source>Avi Muxer</source>
- <translation type="unfinished"></translation>
+ <translation>AVI Muxer</translation>
</message>
</context>
<context>
@@ -9687,7 +9690,7 @@ This message will not be displayed again.</source>
<message>
<location line="+1"/>
<source>Select avs filename[*.avs]</source>
- <translation type="unfinished">Wähle den avs Dateiname [*.avs]</translation>
+ <translation type="unfinished">Wähle Dateinamen [*.avs]</translation>
</message>
<message>
<location line="-7"/>
@@ -13596,17 +13599,17 @@ der Halbbilder (deinterlaceing)</translation>
<message>
<location filename="../../common/gui_navigate.cpp" line="+227"/>
<source>Cannot go to next keyframe</source>
- <translation type="unfinished"></translation>
+ <translation>Kann nicht zum nächsten Keyframe wechseln</translation>
</message>
<message>
<location line="+69"/>
<source>Cannot go to previous keyframe</source>
- <translation type="unfinished"></translation>
+ <translation>Kann nicht zum vorhergehenden Keyframe wechseln</translation>
</message>
<message>
<location line="+176"/>
<source>Seek</source>
- <translation type="unfinished"></translation>
+ <translation type="unfinished">Navigation</translation>
</message>
<message>
<location line="+15"/>
@@ -14078,7 +14081,7 @@ Please delete the idx2 file and reopen.</source>
<message>
<location line="-1301"/>
<source><b>New version available</b><br> Version %1<br>Released on %2.<br>You can download it here<br> <a href='%3'>%3</a><br><br><small> You can disable autoupdate in preferences.</small></source>
- <translation type="unfinished"></translation>
+ <translation><b>Neue Version verfügbar</b><br>Version %1<br>Freigegeben am %2.<br>Das Update kann hier heruntergeladen werden:<br><a href='%3'>%3</a><br><br><small>Sie können automatische ÃÅ"berprüfung auf Updates in Einstellungen deaktivieren.</small></translation>
</message>
<message>
<location line="+788"/>Once it has been committed, I'd request to apply the second patch, which adds 5 translatable strings to the file dialog and to regenerate .ts files then:
diff --git a/avidemux/qt4/ADM_userInterfaces/ADM_gui/file_qt4.cpp b/avidemux/qt4/ADM_userInterfaces/ADM_gui/file_qt4.cpp
index 7466b2a..944e500 100644
--- a/avidemux/qt4/ADM_userInterfaces/ADM_gui/file_qt4.cpp
+++ b/avidemux/qt4/ADM_userInterfaces/ADM_gui/file_qt4.cpp
@@ -37,7 +37,7 @@ static void GUI_FileSelSelectWriteInternal(const char *label, const char *ext, c
*name = NULL;
QString str ;
QString fileName,dot=QString(".");
- QString filterFile=QString("All files (*.*)");
+ QString filterFile=QString(QT_TRANSLATE_NOOP("qfile","All files (*.*)"));
bool doFilter = !!(ext && strlen(ext));
QFileDialog::Options opts;
int extSize=1;
@@ -77,7 +77,7 @@ static void GUI_FileSelSelectWriteInternal(const char *label, const char *ext, c
if(doFilter)
{
- filterFile=QString(ext)+QString(" files (*.")+QString(ext)+QString(")");
+ filterFile=QString(ext)+QString(QT_TRANSLATE_NOOP("qfile"," files (*."))+QString(ext)+QString(")");
}
fileName = QFileDialog::getSaveFileName(NULL,
label, // caption
@@ -105,7 +105,7 @@ static void GUI_FileSelSelectWriteInternal(const char *label, const char *ext, c
if(newFile.exists())
{
QFileInfo fileInfo(newFile);
- QString q=QString("Overwrite file ")+fileInfo.fileName()+QString("?");
+ QString q=QString(QT_TRANSLATE_NOOP("qfile","Overwrite file "))+fileInfo.fileName()+QString("?");
if(!GUI_Question(q.toUtf8().constData()))
{
ADM_dezalloc(*name);
@@ -126,7 +126,7 @@ static void GUI_FileSelSelectReadInternal(const char *label, const char *ext, ch
*name = NULL;
QString str ;
QString fileName,dot=QString(".");
- QString filterFile=QString("All files (*.*)");
+ QString filterFile=QString(QT_TRANSLATE_NOOP("qfile","All files (*.*)"));
bool doFilter = !!(ext && strlen(ext));
QFileDialog::Options opts;
@@ -144,7 +144,7 @@ static void GUI_FileSelSelectReadInternal(const char *label, const char *ext, ch
if(doFilter)
{
- filterFile=QString(ext)+QString(" files (*.")+QString(ext)+QString(")");
+ filterFile=QString(ext)+QString(QT_TRANSLATE_NOOP("qfile"," files (*."))+QString(ext)+QString(")");
}
fileName = QFileDialog::getOpenFileName(NULL,
label, // captionI'll fix the Russian translation which is going to be probably broken again by lupdate immediately afterwards.
Attachments:
- i18n-de-update-2016-10-04.patch
- i18n-file-dialog-make-more-strings-translatable.patch
Forgot to clarify that the latest translation update includes the single string update from Sept. 16 (http://avidemux.org/smif/index.php/topic,7437.msg77074.html#msg77074 (http://avidemux.org/smif/index.php/topic,7437.msg77074.html#msg77074)), so the latter is obsolete.
I'm sorry for changing course once again.
Once your time permits, could you please have a look at the patch always-allow-all-files-in-qfiledialog+translatable-strings.patch in Re: 2.6.10 output dropdown missing valid options (http://avidemux.org/smif/index.php/topic,16507.msg77451.html#msg77451) instead of the second patch (i18n-file-dialog-make-more-strings-translatable.patch) in the post above? The former includes and thus obsoletes the latter and adds an optional "All files" filter to the filepicker.
However, the first patch (i18n-de-update-2016-10-04.patch) should be applied first, when possible.
TIA
Here comes a small out-of-order update fixing translations of some video filters which turned out to be misleading and adding translations for the encoding dialog.
diff --git a/avidemux/qt4/i18n/avidemux_de.ts b/avidemux/qt4/i18n/avidemux_de.ts
index 26b5303..9628ec5 100644
--- a/avidemux/qt4/i18n/avidemux_de.ts
+++ b/avidemux/qt4/i18n/avidemux_de.ts
@@ -9887,12 +9887,12 @@ Trotzdem fortsetzen?</translation>
<message>
<location filename="../../../avidemux_plugins/ADM_videoFilters6/changeFps/changeFps.cpp" line="+76"/>
<source>Change FPS</source>
- <translation type="unfinished">Zeitraffer / Zeitlupe</translation>
+ <translation>Bildfrequenz ändern</translation>
</message>
<message>
<location line="+1"/>
<source>Speed up/slow down the video as if altering fps. This filter changes duration.</source>
- <translation type="unfinished">Beschleunige oder verlangsame das Video als würde sich die Bildfrequenz ändern. Dieser Filter beeinflusst die Abspieldauer.</translation>
+ <translation>Beschleunige oder verlangsame Video durch Änderung der Bildfrequenz. Dieser Filter beeinflusst die Abspieldauer.</translation>
</message>
<message>
<location line="-37"/>
@@ -10590,7 +10590,7 @@ Soll dieses jetzt geladen werden ?
<message>
<location line="-350"/>
<source>Shut down computer when finished</source>
- <translation type="unfinished">nach Beendigung den Computer herunterfahren</translation>
+ <translation>Nach Beendigung den Computer herunterfahren</translation>
</message>
<message>
<location line="+20"/>
@@ -10630,12 +10630,12 @@ Soll dieses jetzt geladen werden ?
<message>
<location line="+13"/>
<source>Advanced</source>
- <translation type="unfinished">Fortgeschritten</translation>
+ <translation>Details</translation>
</message>
<message>
<location line="-164"/>
<source>Main</source>
- <translation type="unfinished"></translation>
+ <translation>Allgemein</translation>
</message>
<message>
<location line="+48"/>
@@ -10643,7 +10643,10 @@ Soll dieses jetzt geladen werden ?
p, li { white-space: pre-wrap; }
</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Time Remaining:</span></p></body></html></source>
- <translation type="unfinished"></translation>
+ <translation><html><head><meta name="qrichtext" content="1" /><style type="text/css">
+p, li { white-space: pre-wrap; }
+</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
+<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Verbleibende Zeit:</span></p></body></html></translation>
</message>
<message>
<location line="+169"/>
@@ -10667,7 +10670,10 @@ p, li { white-space: pre-wrap; }
p, li { white-space: pre-wrap; }
</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Audio Size:</span></p></body></html></source>
- <translation type="unfinished"></translation>
+ <translation><html><head><meta name="qrichtext" content="1" /><style type="text/css">
+p, li { white-space: pre-wrap; }
+</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
+<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Größe Audio:</span></p></body></html></translation>
</message>
<message>
<location line="+10"/>
@@ -10675,7 +10681,10 @@ p, li { white-space: pre-wrap; }
p, li { white-space: pre-wrap; }
</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Total Size:</span></p></body></html></source>
- <translation type="unfinished"></translation>
+ <translation><html><head><meta name="qrichtext" content="1" /><style type="text/css">
+p, li { white-space: pre-wrap; }
+</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
+<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Gesamtgröße:</span></p></body></html></translation>
</message>
<message>
<location line="+24"/>
@@ -10683,7 +10692,10 @@ p, li { white-space: pre-wrap; }
p, li { white-space: pre-wrap; }
</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Video Size:</span></p></body></html></source>
- <translation type="unfinished"></translation>
+ <translation><html><head><meta name="qrichtext" content="1" /><style type="text/css">
+p, li { white-space: pre-wrap; }
+</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
+<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Größe Video:</span></p></body></html></translation>
</message>
<message>
<location line="+47"/>
@@ -10692,6 +10704,10 @@ p, li { white-space: pre-wrap; }
</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Average Bitrate:</span></p></body></html></source>
<translation type="unfinished"></translation>
+ <translation><html><head><meta name="qrichtext" content="1" /><style type="text/css">
+p, li { white-space: pre-wrap; }
+</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
+<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Durchschnittliche Bitrate:</span></p></body></html></translation>
</message>
<message>
<location line="+10"/>
@@ -10706,7 +10722,10 @@ p, li { white-space: pre-wrap; }
p, li { white-space: pre-wrap; }
</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Processed Frames:</span></p></body></html></source>
- <translation type="unfinished"></translation>
+ <translation><html><head><meta name="qrichtext" content="1" /><style type="text/css">
+p, li { white-space: pre-wrap; }
+</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
+<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Bilder verarbeitet:</span></p></body></html></translation>
</message>
<message>
<location line="+10"/>
@@ -10722,7 +10741,10 @@ p, li { white-space: pre-wrap; }
p, li { white-space: pre-wrap; }
</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Elapsed:</span></p></body></html></source>
- <translation type="unfinished"></translation>
+ <translation><html><head><meta name="qrichtext" content="1" /><style type="text/css">
+p, li { white-space: pre-wrap; }
+</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
+<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Zeit vergangen:</span></p></body></html></translation>
</message>
<message>
<location line="+10"/>
@@ -10735,7 +10757,10 @@ p, li { white-space: pre-wrap; }
p, li { white-space: pre-wrap; }
</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Frames/sec:</span></p></body></html></source>
- <translation type="unfinished"></translation>
+ <translation><html><head><meta name="qrichtext" content="1" /><style type="text/css">
+p, li { white-space: pre-wrap; }
+</style></head><body style=" font-weight:400; font-style:normal; text-decoration:none;">
+<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-size:8pt; font-weight:600;">Bilder pro Sekunde:</span></p></body></html></translation>
</message>
</context>
<context>
@@ -14522,7 +14547,7 @@ Ready.
<message>
<location line="+35"/>
<source>Resample FPS</source>
- <translation>Bildfrequenz ändern</translation>
+ <translation>Resample</translation>
</message>
<message>
<location line="+1"/>
I'll start translating "All files" in the filepicker once the .ts files get regenerated :)
Do we expect any new strings for translation prior to the release?
I have a few translations locally which are not pushed yet. If there won't be any are more strings to come, I'll push my i18n-de-update, open a pull request just for these few bits and wait for the .ts files to be regenerated some day.
If there are no more string updates till the release, I won't push my update now, but instead regenerate all the .ts files myself, add translations for the strings introduced since the previous refresh of the .ts files, fix the expectedly broken Russian translation, push everything and then open a pull request.
By the way, are there any news about qt_*.ts files capable to fix issue with Qt strings like "Cancel" remaining untranslated?
I'd like to finish the dxva2 part
It should not produce much translatable string
It is all fine, and it is great to watch the ability to use hwaccel on Windows, where probably the vast majority of users come from, taking shape. Please just let me know when the time is ripe to regenerate the .ts files (I ended up recently adding one new translatable string myself...) and whether you prefer to do it yourself. Thanks!
Quote from: eumagga0x2a on October 31, 2016, 10:09:36 PM
By the way, are there any news about qt_*.ts files capable to fix issue with Qt strings like "Cancel" remaining untranslated?
Fixed in a way which does not break Qt4 by Daniel Amm and mean in 90520e4ddd30c8a7b6150d93ce56422f5fc49d0e, da18ab61720a9e07c3b622fc9be529c909226b33, bea3c4817cc3a013840802ef83cea872ca2ef158 and 505fad84cb2161881ece577ea83086a96eb7a20a.
Thanks a lot!