Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GoogleTranslate Package (refresh) bug? #157

Closed
zzynx opened this issue Feb 7, 2017 · 1 comment
Closed

GoogleTranslate Package (refresh) bug? #157

zzynx opened this issue Feb 7, 2017 · 1 comment

Comments

@zzynx
Copy link

zzynx commented Feb 7, 2017

Version: Keypirinha 2.11 (66a575a) for x64

  • I type the key combination (Ctrl+Insert) to make K's window appear
  • I type "Translate" and get what you see in screenshot 01.
    Which is OK since my googletranslate.ini file contains this:
    [defaults]
    item_label = Translate from English to Dutch
    input_lang = en
    output_lang = nl
  • I press the Space bar and I type a sentence which is indeed translated into Dutch (cf. screenshot02)
  • I type the key combination (Ctrl+Insert) to make K's window appear
  • I type kconfig and choose the entry to config the GoogleTranslate package
  • I ADD these lines to the googletranslate.ini file:
    [custom_item/NederlandsNaarEngels]
    item_label = Translate from Dutch to English
    input_lang = nl
    output_lang = en
  • I save the changed file and then close both files.
  • I type the key combination (Ctrl+Insert) to make K's window appear
  • I type Translate and get what you see in screenshot 03
    So, I get twice the text "Translate from Dutch to English". The original (default) "Translate from English to Dutch" is apparently also affected by the last change.
  • I exit Keypirinha and start it up again.
  • I type the key combination (Ctrl+Insert) to make K's window appear
  • I type Translate and now get the expected result (cf. screenshot 04)

Thumbs up and a big thanks for Keypirinha.
Kind regards,
Peter
screenshot 01
screenshot 02
screenshot 03
screenshot 04

@polyvertex
Copy link
Member

polyvertex commented Mar 17, 2017

Should be fixed as of v2.12, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants