[ATTENTION] Please, update your localizations

[quendimax]

What about "&Dictionaries... F3" in the MainWindow context? Why does it need to add F3 here.
In Windows that views correct. But in Unity the F3 mark is offset to "Dictionaries".

[Tvangeste]

What about "&Dictionaries... F3" in the MainWindow context? Why does it need to add F3 here.
In Windows that views correct. But in Unity the F3 mark is offset to "Dictionaries".

This is because the shortuct F3 is overloaded, unfortunately. By default, F3 opens up that dictionaries UI, but when the search within article is activated via Ctrl+F then F3 is a shortcut for the "search next" action.

But I agree that the way it is done is not ideal. Would you mind opening an issue in our issue tracker?

[Tvangeste]

@quendimax, could you post a screenshot of the buggy menu from your system?

[chulai]

Yes, the solution is not ideal but works if you translate the "&Dictionaries...{TABSPACE}F3" in a text editor and don't update it never again. I think Qt Linguistic doesn't play well with the {TABSPACE} trick.

Code: Select all

       <source>&amp;Dictionaries...{TABSPACE}F3</source>
       <translation>&amp;Diccionarios...{TABSPACE}F3</translation>


Ideally we shouldn't have to fall into this trick and at the same time be able to use F3 to open Dictionaries dialog in all scenarios except when the inline search dialog is open (Ctrl + F). In which case F3 is the shortcut for the Next result button.

[Tvangeste]

Ok, I've filed a couple of issues for the F3 and Shift-F3 handling:

Issue #184: F3 and Shift-F3 shortcuts don't work in a scan popup window when Search is activated
Issue #185: Dictionaries menu uses hardcoded shortcut value in its text

Will fix.

P.S. Fixed!

[quendimax]

Perfectly!
I think a screenshot doesn't already need.

[jennie]

Is it ok if I upload the updated Greek translation here?

[Tvangeste]

Is it ok if I upload the updated Greek translation here?

Thank you for the updates! I've just committed them to the master repository. Sure, it is OK to post them here. Whatever is the most suitable for you.

An alternative approach is to submit pull requests against the GoldenDict repository, but that requires some knowledge of git and github and some find it a bit too complicated.

It is easier for us, maintaniers, though, since in order to apply the pull request I just need press a single button.

But a ZIP archive with the *.ts file is not a big problem too, just a couple of additional steps for me (to download, extract and commit with some message).

In short, if you don't know git/github, posting a ZIP file here is the right thing to do.

[dg333]

Not sure if this deserves a separate thread, thus, I’ll ask it here. Is there any option to test a localization file before committing? In other words, can I do something like this:

Code: Select all

goldendict localizationfile=/home/me/somelanguage_SOMECOUNTRY.ts

to try it?

[Tvangeste]

I don't think that GD can handle such command line.

But you can always "release" your *.ts file from within the Linguist UI (File -> Release), it will create the appropriate *.qm file which you could copy to GoldienDict's locale directory and test it.