Installer texts language translations

[M.T]

German:

LangString Start_License_Lang ${AvsLang} "Lizenz in deutsch"

Polish:

LangString Start_License_Lang ${AvsLang} "Licencja po polsku"

M.T

[IanB]

Please check why the polish licence is missing under the URL:
http://avisynth2.cvs.sourceforge.net/*checkout*/avisynth2/avisynth/distrib/gpl-pl.txtOops :o it should be gpl-pl.txt (I have fixed the post above)

[IanB]

@gzarkadas, Fizick, niiyan,

Prompted by your comments and suggestions I have had another go at improving the feel of the Installer with translated GPL-*.txt's.

This time round the Installer always starts on the "Licence Agreement" page loaded with the official English GPL.txt. Clicking the "I Agree" button takes you to the "Choose Components" page as usual.

If there is a translated GPL-*.txt for the current language the "Back" button is enabled, but re-labelled as "Translate". Clicking this takes you to a 2nd copy of the "Licence Agreement" page loaded with the translated GPL-*.txt and with the "I Agree" button re-labelled as "Next". This gives the illusion of being on the License page and flipping the text box contents between the translated License text and the Official License text.

If this model is satisfactory we will need translations for the "Translate" button text i.e.LangString AVS_TranslateBtn ${AvsLang} "&Translate"As usual for windows Button Labels you can optionally use the "&" character to mark Alt-T as a quick select keystroke.

If elements are still confusing or unacceptable please keep in mind we are constrained by what can be coded with standard NSIS scripting. Anyway this is what development is about, ideas and discussion, thanks again.

As usual get it here, AviSynth_080601.zip (http://avisynth2.sourceforge.net/AviSynth_080601.zip) (AviSynth_080711.exe).

Please check carefully that the Start Menu shortcut translations and the ANSI encoded 8 bit contents of the gpl-*.txt files are correct?

[Underground78]

Suggestions for the French language file :

LangString Start_License_Lang ${AvsLang} "Licence en français"

LangString AVS_TranslateBtn ${AvsLang} "&Traduire"or
LangString AVS_TranslateBtn ${AvsLang} "Afficher la licence en français" but it's propably to long ...

[niiyan]

@IanB,

If there is a translated GPL-*.txt for the current language the "Back" button is enabled, but re-labelled as "Translate". Clicking this takes you to a 2nd copy of the "Licence Agreement" page loaded with the translated GPL-*.txt and with the "I Agree" button re-labelled as "Next". This gives the illusion of being on the License page and flipping the text box contents between the translated License text and the Official License text.

AviSynth_080711.exe looks better than the previous version.
In my opinion, 2nd "I Agree" button should be re-labelled as "Back", not "Next", because we go back to the 1st Agreement page when we click it.

If you need translation for "Translate" button text, I'll update AVS_Japanese.nsh soon.

[IanB]

@Underground78,

I can move and size the buttons within the area at the bottom with Windows SendMessage.(HWND, ...) calls.
Turns out I can't express the required RECT structure in NSIS script. :(


Maybe you can screen grab the installer page and attack the image with paint to show how you might like your "Afficher la licence en français" to appear. e.g Align it left and make the button 50% of the frame wide.

If you like I can try to parameterise it so it can be overridden on a per language file basis.


@niiyan,

Yes we can re-label the "I Agree" button. I am already doing so to make it the NSIS standard "Next >" text.

I didn't hack into the AVS_*.nsh files this time, I figured I should wait for some feedback because I guessed there would be good ideas and it's a pain doing these artistic changes in little bits and pieces. I'll collect all the ideas and do a single change to include all the new translated texts that will be required. At this point I wanted to get a functional infrastructure that can be tweaked.

[Underground78]

Maybe you can screen grab the installer page and attack the image with paint to show how you might like your "Afficher la licence en français" to appear. e.g Align it left and make the button 50% of the frame wide.

I can't find a good way to do this, I think it's really to long ... My first proposal was probably better.

[M.T]

@ niiyan

AviSynth_080711.exe looks better than the previous version.
In my opinion, 2nd "I Agree" button should be re-labelled as "Back", not "Next", because we go back to the 1st Agreement page when we click it.


I'm have a suggestion for the 2nd button in the translation: A button called "Original" should switch back to the english license.
Please have a look on my attached BMP file.

M.T

[M.T]

Maybe you will need a new entry like: "LangString AVS_OriginalBtn"


LangString AVS_TranslateBtn ${AvsLang} "Überse&tzung"

LangString AVS_OriginalBtn ${AvsLang} "&Original"

...

LangString Start_Online ${AvsLang} "AviSynth Homepage"

And here are the polish one:

LangString AVS_TranslateBtn ${AvsLang} "&Tłumaczenie"

LangString AVS_OriginalBtn ${AvsLang} "&Oryginał"

...

LangString Start_Online ${AvsLang} "Strona Domowa AviSynth"


@ IanB:
Could you correct this bug in the german license please:

http://img172.imageshack.us/img172/1216/11lc1.th.png (http://img172.imageshack.us/my.php?image=11lc1.png)

[M.T]

If you have more docs installed it's more difficult to find the right doc in the start menu! Please make a separate folder for the docs in the start menu. And add English (red marked) to the english installer code. Have a look on the Attachment :

[M.T]

And finally make also a separate folder for the licenses and translations in the program folder.
Or better : Install only the translated TXT license files for the language that is selected at the beginning of the instalation.
Have look on the file:

[IanB]

@M.T,

For the gpl-de.txt, I shaved 1 space off the left indent and removed the 3 "." from within the line, hopefully that will be enough pixels to stop the damn auto-wrapping. Diese Übersetzung wurde ursprünglich erstellt von Katja Lachmann Übersetzungen
im Auftrag der S.u.S.E. GmbH - http://www.suse.de. Sie wurde überarbeitet von
Peter Gerwinski, G-N-U GmbH - http://www.g-n-u.de (31 Oktober 1996, 4 Juni 2000)
it was
Peter Gerwinski, G-N-U GmbH - http://www.g-n-u.de (31. Oktober 1996, 4. Juni 2000).

I'll comment on your 1.bmp when the mod approves it.
Okay I see. You want to move the "Return" button to the same location as the "Translation" button was. Good in theory but I haven't worked out how to feed structs (i.e a RECT) to system calls in NSIS.



@All,

I am currently proposing to make the 2 buttons concerned available in the AVS_*.nsh language files. Thus individual translators can choose the texts to be culturally most appropriate.

Here is the change I am thinking of checking into CVS :-...
; Translation and matching Return license buttons

LangString AVS_TranslateBtn ${AvsLang} "&Translation"
LangString AVS_ReturnBtn ${AvsLang} $(^NextBtn) ; or maybe use $(^BackBtn)

; Optional Licence file translation

; !define AvsLicenceFile "gpl.txt"Any further thought?

M.T, My AVS_ReturnBtn is equivalent to your AVS_OriginalBtn

[IanB]

@M.T,

Yes I can easily install the licence files into a subdirectory.

As for the documention shortcuts in a separate folder, I had considered this in the past, I too generally have all the docs installed for test purposes, but I had considered myself a very unusual case, so I didn't do it.

The normal case I have expected was for people to install only 1 or maybe 2 language documentation sets and I think for that case what currently happens looks better.

Do others have any thoughts on the matter?

:Edit: Sorry I missed the $(Start_Doc_English)="English Avisynth Documentation" suggestion first time through. With the latest installer script these strings are all definable per language, so we allow freedom as to the actual texts of each for each language. I might suggest for the documentation shortcut name the current "Language Name" is somewhat redundant, so I would not be upset, if for example in the Polish version the "Polska dokumentacja" was to become just "Avisynth dokumentacja" and the "Angielska dokumentacja" stayed as is.

What do people think?

[M.T]

And what about this solution:

[M.T]

I see that your gpl-pl.txt has errors. Wrong Code page. Please replace it with my correction.

[krieger2005]

Just saw in the pic of M.T. the Translation "Click on Accept" ("Klicken Sie auf Annahmen", where to accept the german license) but the name of the button is "next" ("Weiter").

[IanB]

@krieger2005,

Yes, this is exactly what the above discussions are about, how best to label the buttons within the NSIS framework.

Current thoughts are standard "Next", standard "Back", translation of "Original" or something else entirely.

Feel free to brainstorm ideas here.

[niiyan]

@M.T

I'm have a suggestion for the 2nd button in the translation: A button called "Original" should switch back to the english license.

I prefer "Back" rather than "Original".
If it is "Original", it is more difficult for users to understand what they should do next.

@IanB

The 2nd localized License Agreement page has the same message as in the 1st page: "If you accept the term of the agreement, click ...".
But it looks a little strange because the 2nd page doesn't have [I Agree] button.

I noticed some texts were corrupted and not readable in the Language selection page.
I can't read French, Portuguese and Portuguese (Brasil).

[WarpEnterprises]

Why exactly should the English version of the license be visible,too if there is a translated version included?
It makes the user's way quite strange.

Another proposal would be to write in the text field that AviSynth is under license xyz (this can be translated easily) and to present the license text (original and translated) as separate buttons or links in the above text (mysql-administrator does it this way).

[Underground78]

Why exactly should the English version of the license be visible,too if there is a translated version included?

I think it's because the translations are not official ...

[IanB]

@niiyan,

Yes I think the standard "Back" button text is better, or perhaps "Return" is a choice, but I will leave it up to each translator to choose for their language.

I currently have MUI_LANGDLL_ALLLANGUAGES turned on. This forces the Installer to display all the Language options, even if the current code page does not have the all the characters required to display the strings. The default behaviour is to only show those Language options for which the current code page has characters available. I will probably turn this option off for the production release.


@WarpEnterprises,

Yes Underground78 is correct, it's because the translations are not official.

And as Wilbert has pointed out the user must click the "I Agree" button only from the English GPL.txt page.



Any and all brainstorm ideas welcome ;)

[IanB]

@All,

This is just to assemble the changes and fixes provided so far. I have defaulted the "return" button to the standard "BackBtn" text, translators hopefully will provide better texts in there next submissions.

If people are happy, we will need translations for the "Translate" and "Return" button text i.e.; Translation and matching Return license buttons

LangString AVS_TranslateBtn ${AvsLang} "&Translation"
LangString AVS_ReturnBtn ${AvsLang} "Re&turn" ; $(^BackBtn) $(^NextBtn)I will leave it to the individual translators to choose culturally appropriate texts for these button. As usual for windows Button Labels you can optionally use the "&" character to mark Alt-T as a quick select keystroke.

If elements are still confusing or unacceptable please keep in mind we are constrained by what can be coded with standard NSIS scripting. Anyway this is what development is about, ideas and discussion, thanks again.

As usual get it here, AviSynth_080601.zip (http://avisynth2.sourceforge.net/AviSynth_080601.zip) (AviSynth_080715.exe).

Source is my RC3 tree, includes fixes for AviSource with RGB24, and guard bytes for Huffyuv/XviD reading past the end of the input buffer. Also corrects testing for NULL malloc returns on VFB's i.e I now check the big buffer as well as the small struct.

Please check carefully that the Start Menu shortcut translations and the ANSI encoded 8 bit contents of the gpl-*.txt files are correct?

[niiyan]

@IanB,

I tried AviSynth_080715.exe.
It looks better now.
There is no need for some other translations in AVS_Japanese.nsh.

I will probably turn this option off for the production release.

I understand.

[M.T]

@IanB,

I found 2 bugs in the polish file. I uploaded the corrected one!
The Polish Start Menu shortcuts and the gpl-pl.txt are OK so far!

Could you change the german gpl and put two dots back?
I think that deleting one dot is enough to pass the auto-wrapping.
If not I will let you know. The date looks much better with a dot!

Peter Gerwinski, G-N-U GmbH - http://www.g-n-u.de (31. Oktober 1996, 4. Juni 2000)

M.T

PS:
I think that that fits better, you also use it on the Homepage in the polish section:

LangString Start_Online ${AvsLang} "Strona główna AviSynth"

http://www.alice-dsl.net/m_t/AVS_Polish.nsh (updated)

[talen9]

Italian:

LangString AVS_TranslateBtn ${AvsLang} "&Traduzione"
LangString AVS_ReturnBtn ${AvsLang} $(^BackBtn) ; "&Indietro" ; $(^NextBtn) ;

I literally translated "Back" ... btw, it was *already* translated in the installer, when i tried executing the installation, even if your prototype presented it as "Re&turn" :confused:

Complete and updated italian language file:

[M.T]

@IanB,

I see on the Homepage that you have different language versions on it.
I think it would be nicer if every language installation gets its own Start Menu link to this section on the Homepage:

English -> http://avisynth.org/mediawiki/Main_Page
German -> http://avisynth.org/mediawiki/Main_Page/de
Spanish -> http://avisynth.org/mediawiki/Main Page/es
French -> http://avisynth.org/mediawiki/Main Page/fr
Japanese -> http://avisynth.org/mediawiki/Main Page/ja
Polish -> http://avisynth.org/mediawiki/Main_Page/pl
Russian -> http://avisynth.org/mediawiki/Main Page/ru

What do you think?

[M.T]

@ All,

In the translation of the license there is also this text saying to press the button (I agree) to continue.
I think my new suggestion can solve this. Just put the button there and disable it.
Look on the GIF and tell me what do you think about it.

M.T

[IanB]

@niyan, M.T, talen9,

Thanks for the updates guys. :D

@niyan,

I suppose I should put up a version soon with the default MUI_LANGDLL_ALLLANGUAGES option to make sure there are no hidden pitfalls. ;)

@talen9,

Sorry for any confusion.

";" is the NSIS comment character.

$(^BackBtn) is the NSIS standard text for the "Back Button". $(^name) is how you access any of the NSIS standard strings.

So the Magenta part is active script, the green part is comment.LangString AVS_ReturnBtn ${AvsLang} $(^BackBtn) ; "&Indietro" ; $(^NextBtn) ;
@M.T,

Okay, I will put 2 of the dots back in the gpl-de.txt.

Yes I could make the home page URL language specific. But "http://www.avisynth.org" is pretty maintenance free, the wiki tends to mutate unexpectedly occasionally (okay once or twice). Perhaps the homepage should be more generic with the translations easier to find. I will wait to see if we get more comments on this proposal before I act.

And yes your "Suggestion 3" is almost exactly what I have been trying to make happen. I just cannot sufficiently control the button activity or placement. NSIS script currently lacks the syntax needed to poke system calls that need pointers to binary structures. I originally had something similar to this but with the buttons reversed. It was basically why the 1st cut used the "Next" button text, I thought it looked very confusing having the "I Accept" button swap places, so I took it back out.

[IanB]

@M.T,

I resurrected one of my original attempts with the left "Back" button labelled "I Agree" and greyed out.

I have removed the install section and all the files so it is non functional but only 140Kb. AviSynth_NoFiles.zip (http://avisynth2.sourceforge.net/AviSynth_NoFiles.zip) (AviSynth_080716.exe 140Kb)

Thoughts? :confused:

:Edit: Quick update, This now also has the default MUI_LANGDLL_ALLLANGUAGES

I can only select Deutsch, English, Francais, Italiano, Japanese, Portugues and Portugues (Brazil).

Cesky, Greek, Polski and Russian are all hidden.

[talen9]

@talen9,

Sorry for any confusion.

";" is the NSIS comment character.

$(^BackBtn) is the NSIS standard text for the "Back Button". $(^name) is how you access any of the NSIS standard strings.

So the Magenta part is active script, the green part is comment.LangString AVS_ReturnBtn ${AvsLang} $(^BackBtn) ; "&Indietro" ; $(^NextBtn) ;


To tell the truth, I suspected some pitfall there :p

Anyway, as I said before, the default "^BackBtn" string already sounds OK to me ... here the revised translation:

[niiyan]

@IanB,

I tried AviSynth_080716.exe.

I prefer grayed-out "I Agree" button.
But "Next" button is used instead of "Back" button, though AVS_Japanese.nsh hasn't been changed.
"I Agree" button is placed in the left side of "Next" button.
In my opinion, grayed "I Agree" button should be the same place as in the first License page.

Now I can only select English and Japanese in the Language selection menu.

[IanB]

In my opinion, grayed "I Agree" button should be the same place as in the first License page.And this is what M.T has suggested, and what I very originally wanted to do. Problem is I cannot find a way to move the buttons or reassign their NSIS purpose. Hence all the stuffing around trying work around this look and feel deficiency. If only I could easily swap the 2 buttons Grrr!

[M.T]

I updated the AviSynth Homepage a little bit. Manly translated some polish and german missing pages!

@IanB,

The Installer looks good now. The german license (with two dots) and the polish one are ok now. And the polish Translate button is ok now. Sorry that it isn't so easy to turn the I Agree button - it would looks much better on the other side. But it's also ok as it is now.

I think the Installer is finished now. Or is still something missing?

M.T

[IanB]

@M.T,

Yes, I am just waiting for the remaining translations for the "&Translation" button. I have Babelfished the Czech and Portuguese, but they need confirmation. And the Greek and Russian, which use a different alphabet.

For the moment I will stick with the single button, AviSynth_080715.exe, style using the standard $(^BackBtn). If I get an epiphany I will add in a greyed out "I Agree" button as the middle button.

Any comments on the effects of the default MUI_LANGDLL_ALLLANGUAGES setting with the AviSynth_080716.exe test harness?

[gzarkadas]

Here are the button texts for the Greek installer.

The text of the return button is same as the nsis default except the ampersand. It could as well be the nsis default, pick whatever you like.


; Translation and matching Return license buttons

LangString AVS_TranslateBtn ${AvsLang} "&Μετάφραση"
LangString AVS_ReturnBtn ${AvsLang} "&Πίσω" ; $(^BackBtn) $(^NextBtn)


Regarding the 080716 installer, I can see only English, Greek and Japanese languages in the drop-down list. I have to admit that Japanese is a bit unexpected, since we cannot display those characters in our codepage :). In any case, I would opt for having all options available if the initial automatic language selection does not suit the user; IMO the benefit of having less lines at the drop-down list is less important from the restriction that is imposed (restrictions are ugly).

[IanB]

@gzarkadas,

Thanks! :D

Yes, I feel a little uneasy with options suppressed, you arr never quit sure that what you intend is actually present.

[IanB]

@All,

Another quick 140Kb version with the install section and all the files removed so people can do a quick check on their texts. AviSynth_NoFiles2.zip (http://avisynth2.sourceforge.net/AviSynth_NoFiles2.zip) (AviSynth_080718.exe 140Kb)

Also I turned the MUI_LANGDLL_ALLLANGUAGES option back on, I think the restricted list sucked.

Thoughts?

[Fizick]

Can software installers ask people to click to agree to the GPL? If I get some software under the GPL, do I have to agree to anything?

Some software packaging systems have a place which requires you to click through or otherwise indicate assent to the terms of the GPL. This is neither required nor forbidden. With or without a click through, the GPL's rules remain the same.

Merely agreeing to the GPL doesn't place any obligations on you. You are not required to agree to anything to merely use software which is licensed under the GPL. You only have obligations if you modify or distribute the software. If it really bothers you to click through the GPL, nothing stops you from hacking the GPLed software to bypass this.
http://www.gnu.org/licenses/gpl-faq.html#ClickThrough

[Leak]

http://www.gnu.org/licenses/gpl-faq.html#ClickThrough
Heh. :D

Gotta bookmark that; the uncontrolled growth of installers using the GPL as an EULA is really getting out of hand...

[niiyan]

@IanB,

Also I turned the MUI_LANGDLL_ALLLANGUAGES option back on, I think the restricted list sucked.

I agree with you.
I don't like the restricted list, too.

But Francais, Portugues and Portugues (Brazil) are still corrupted in the full list.
Could you force language name to be only ASCII characters (alphabet)?

[IanB]

Could you force language name to be only ASCII characters?Possibly, the strings are defined during the parsing of the MUI_LANGUAGE macro which in turn loads the various NSIS resource for each required language. For the most part the NSIS macros are fairly well written to allow overriding for various things. So some research might turn up how to override the display name for the language.

However to a French native "Français" is their language name not "Francais", similarly "Português" is not "Portugues". I do not know how such restrictions are tolerated, but I fear in some case it could be regarded as offensive.

[niiyan]

@IanB,

However to a French native "Français" is their language name not "Francais", similarly "Português" is not "Portugues". I do not know how such restrictions are tolerated, but I fear in some case it could be regarded as offensive.

I didn't mean that "Français" should be displayed as "Francais", and so on.
But the current installer replaces "ç" and "ê" with another meaningless characters.
I think it should be modified by the time 2.5.8 Final is released.

So, what do you think of using English name, i.e. "French"?
"Japanese" has been already restricted and displayed by using English name.

[IanB]

@niiyan,

Isn't using the English translation of a language name a little English centric. I guess it's about 7/3 with the NSIS development people, Czech, German, French, Italian, Polish & Portuguese(2) use the native name. Greek, Japanese & Russian use the English name.

So this is the drawback of using Codepage technology, you only see the correct glyphs when your codepage matches the codepage of the author.

French.nlf # Language ID : 1036 # Codepage : 1252
Portuguese.nlf # Language ID : 2070 # Codepage : 1252
Japanese.nlf # Language ID : 1041 # Codepage : 932

The byte values of the 2 characters in codepage 1252 are ord("ç")=231 and ord("ê")=234. These will display as different glyphs with different code pages.

The 2 choices NSIS currently offers are MUI_LANGDLL_ALLLANGUAGES=ON or MUI_LANGDLL_ALLLANGUAGES=OFF and I really do not like the MUI_LANGDLL_ALLLANGUAGES=OFF option.

So far we have come up with two other choice, vandalising the glyphs to the nearest ascii equivalent, or using the English name for the languages.

I guess if this was a French cored project and I saw "Anglais" on the list of languages I might be a little confused if I didn't have a small amount of experience with French.

Thoughts from other non-english speaking natives :confused:

[IanB]

@All,

Okay here a full 3.8Mb installer package. If we are happy with the current look and feel compromises I would like to put his up as the RC3.

Summary :- The Czech and Portuguese are still my ham fisted Babelfished translations, so they need confirmation from a native speaker.
MUI_LANGDLL_ALLLANGUAGES is turned on.
For translated GPL-*.txt page I am using the NSIS standard Back button text, $(^BackBtn) on the centre button. The left button is hidden.
I am sticking with the low maintenance "http://avisynth.org/" homepage link.
I am using the codepage mismatched NSIS standard Language names texts.

As usual get it here, AviSynth_080601.zip (http://avisynth2.sourceforge.net/AviSynth_080601.zip) (AviSynth_080719.exe).

Source is my RC3 tree, includes Latest Japanese docs, minor Russian docs updates, fixes for AviSource with RGB24, and guard bytes for Huffyuv/XviD reading past the end of the input buffer. Also corrects testing for NULL malloc returns on VFB's i.e I now check the big buffer as well as the small struct.

Please check carefully that the Start Menu shortcut translations and the ANSI encoded 8 bit contents of the gpl-*.txt files are correct?

[niiyan]

@IanB,

The 2 choices NSIS currently offers are MUI_LANGDLL_ALLLANGUAGES=ON or MUI_LANGDLL_ALLLANGUAGES=OFF and I really do not like the MUI_LANGDLL_ALLLANGUAGES=OFF option.

So far we have come up with two other choice, vandalising the glyphs to the nearest ascii equivalent, or using the English name for the languages.

Thanks for your reply.
I understand why English name isn't used and why some texts are corrupted.
But I still don't know which is better...

Anyway, AviSynth_080719.exe works correctly for start menu and gpl-*.txt.

[gzarkadas]

...Please check carefully that the Start Menu shortcut translations and the ANSI encoded 8 bit contents of the gpl-*.txt files are correct?

Regarding the Greek installer, everything is ok except for the 1st word of the shortcut for the localised licence text. It currently says:
Greek Άδεια χρήσης
while it should be (to be fully localised):
Ελληνική άδεια χρήσης
Note that I have changed the case of the second word, but if this raises difficulties keeping it as-is is also acceptable.

Ansi text attached.

[M.T]

@IanB,

I asked a czech translator, if he can check the installer. This is his email to me:

Hello Michal,

I checked the installer. Everything is OK, except of GNU GPL License in Czech language. It contains some "diacritic"-mistakes. I copied also the text of GPL into Notepad (codepage ANSI) and corrected it. I send the text to you, if you can, please add it into Czech installer. I can´t make this, because at this moment I work on other translations and the NSIS is not installed on my computer.

Thank you for your help. Best regards,

--
Marián H.

So i included his corrected version of the czech license....

[IanB]

@All,

If there are no more issues or comments, I will add niiyan, gzarkadas and M.T's contributions and make an official RC3 release this weekend.

[Wilbert]

@All,

We need your help again. We would like to have the translation of the strings (words between the quotes)

LangString Czech_Text ${AvsLang} "Czech Documentation"
LangString Czech_Bubble ${AvsLang} "Install Czech help"
LangString Start_Doc_Czech ${AvsLang} "Czech AviSynth Documentation"

in the following languages:

Czech
French
German
Greek
Italian
Japanese
Polish
Portuguese
Portuguese (Brazil)
Russian

[Leak]

We need your help again. We would like to have the translation of the strings (words between the quotes)
German, going by what's in the German language file already:

LangString Czech_Text ${AvsLang} "Tschechische Dokumentation"
LangString Czech_Bubble ${AvsLang} "Tschechische Hilfe installieren"
LangString Start_Doc_Czech ${AvsLang} "Tschechische Avisynth Dokumentation"
np: Rhythm & Sound with Tikiman - What A Mistry (Showcase)