https://bugs.kde.org/show_bug.cgi?id=527427
--- Comment #4 from Eric Beuchel <[email protected]> --- # Google translation retest Google translation was tested again on 20 October 2026. Translating a description directly in digiKam reproduced **HTTP 429**. A separate minimal HTTP request from the same PC succeeded, so that request alone does not establish that digiKam translation works. ## Test environment - digiKam 9.2.0 on Microsoft Windows. - Separate test instance, configuration and SQLite database under `D:\Test\digiKam\Google_20261020`. - Six copied images from an existing metadata test set: DNG, HEIC, JPG, PNG and two TIFF files. - Target language displayed in digiKam: **Deutsch (Deutschland), de-DE**. - Translation settings in the test configuration: `TranslatorEngine=0`, `TranslatorLang=de-DE`. - The description translation error dialog explicitly identifies the service as **Google**. - The production digiKam instance was not used for these tests; no test edits were made to the production image archive. ## Test 1: Minimal direct HTTP request outside digiKam A single request was sent using PowerShell `Invoke-WebRequest`: ```text https://translate.googleapis.com/translate_a/single?client=gtx&sl=en&tl=de&dt=t&q=dog ``` Result: ```text HTTP 200 Translation: Hund ``` This tests only that particular request. It is not identical to the request subsequently shown in digiKam's error dialog, which uses automatic source-language detection and additional parameters. The reason for the different responses has not been established. ## Test 2: Automatic tag generation with German translation enabled The automatic tag scan was run on the six test images with these settings: - Search mode: **All**. - Assignment mode: **Replace Existing**. - Model: **EfficientNet B7**. - Target language: **de-DE**. The scan finished and the interface reported no active process. The following newly generated assignments were confirmed in the test database and visible in the interface: | Test image | Tag hierarchy | Generated tag | | ---------------- | ------------- | ---------------------------------------- | | `PNG.png` | `auto/de-DE` | `web site, website, internet site, site` | | `TIFF_valid.tif` | `auto/de-DE` | `envelope` | The generated terms remained English despite the German target language. Existing German tags elsewhere in the copied database were not treated as evidence of successful translation. No HTTP 429 dialog was observed during this automatic scan, and no HTTP 429 message was found in the captured standard-error log. This does not prove that the translation requests succeeded or establish why the terms remained English. ## Test 3: Translate a description directly in digiKam Steps performed in the isolated test instance: 1. Select `PNG.png`. 2. Open the right sidebar **Captions → Description** (German interface: **Beschriftungen → Beschreibung**). 3. Enter this newly written test sentence in the caption field with source entry `x-default`: ```text A red ladybird is sitting on a green leaf. ``` 4. Open the translation menu next to the caption field and select **de-DE**. Result: digiKam displayed this error dialog: ```text Der String kann nicht mit dem Web-Service „Google“ übersetzt werden ``` The error details displayed: ```text Fehlermeldung: Error transferring https://translate.googleapis.com/translate_a/single?client=gtx&ie=UTF-8&oe=UTF-8&dt=bd&dt=ex&dt=ld&dt=md&dt=rw&dt=rm&dt=ss&dt=t&dt=at&dt=qc&sl=auto&tl=de&hl=de&q=A red ladybird is sitting on a green leaf. - server replied with status code 429 ``` The URL above is transcribed from the visible dialog; it is not a packet capture. The description was not translated. The **Apply** button was not pressed to save the test description. The error dialog was left open for inspection. ## Findings for the bug report - **Confirmed:** A single description translation from digiKam to German is currently rejected with HTTP 429. - **Confirmed:** A minimal direct request outside digiKam returned HTTP 200 and a German translation. - **Confirmed:** The automatic tag test produced English terms under `auto/de-DE`. - **Not established:** Why Google accepts the minimal request but rejects the request made by digiKam. - **Not established:** Whether the cause is request parameters, request headers, rate limiting, or another service-side condition. No conclusion about a shared API key or a permanent block is supported by these tests. - **Not retested in this run:** Other translation services. Their previously reported failures should be kept separate from these Google retest results. ## Suggested reply to the developer I retested Google translation in digiKam 9.2.0 on Windows using a separate test database and configuration. Translating the single caption “A red ladybird is sitting on a green leaf.” to German (de-DE) immediately produced the error “Der String kann nicht mit dem Web-Service ‚Google‘ übersetzt werden”, with “server replied with status code 429”. The request shown in the dialog uses `translate.googleapis.com/translate_a/single`, `client=gtx`, `sl=auto`, `tl=de`, `hl=de`, and several `dt` parameters. A separate minimal request from the same PC, using `client=gtx&sl=en&tl=de&dt=t&q=dog`, returned HTTP 200 and “Hund”. These requests differ, so I cannot determine the reason for the different responses. An automatic tag scan with de-DE selected also generated English terms such as “envelope” under `auto/de-DE`. I did not retest the other translation services in this run. -- You are receiving this mail because: You are watching all bug changes.
