Task #3443
closedThe file name of the Zip file downloaded by Weblate is incorrect.
0%
Description
STR:
1. Open a LibreOffice UI - master
e.g. https://translations.documentfoundation.org/languages/ja/libo_ui-master/
2 Download a original translation file
Files -> Download translation Files as ZIP file
The zip file has only the extension and no file name.
Related issues
Updated by Guilhem Moulin almost 4 years ago
bafflan 日陰のコスモス wrote:
STR:
[…]
The zip file has only the extension and no file name.
Scriptable version:
$ curl -sI https://translations.documentfoundation.org/download-language/ja/libo_ui-master/?format=zip \ | grep -Ei "^Content-(type|disposition):" content-type: application/zip content-disposition: attachment; filename=".zip"
Updated by Guilhem Moulin almost 4 years ago
- Status changed from New to Closed
- Assignee set to Guilhem Moulin
Backported that trivial upstream bugfix: https://github.com/WeblateOrg/weblate/commit/060e4a86421191e932f7093d5fd0548766bd9988 .
But right now it seems it refuses to create the archive because https://translations.documentfoundation.org/projects/libo_ui-master/connectivityregistrymorkorgopenofficeofficedataaccess/ has no Japanese .po file. AFAICT the code doesn't guard against missing/deleted files and I suppose https://github.com/LibreOffice/translations-weblate/commit/0e6775f7419128b709b282db328a8c04c419cd53 needs to propagate first.
Updated by bafflan 日陰のコスモス almost 4 years ago
Cannot download a ZIP file.
Error message:
Internal Server Error
Server Error
The server had serious problems serving your request. Trained monkeys are en-route fixing the issue.
Updated by Guilhem Moulin almost 4 years ago
That's precisely what I meant in my last paragraph.
Updated by Guilhem Moulin almost 4 years ago
No idea how to force-refresh the file list in weblate, also. Maybe Christian Lohmaier knows? (It has nothing to do with the present issue though.)
Updated by Jun Nogata almost 4 years ago
- Related to Task #3446: Cannot download PO file from Weblate with error added
Updated by Christian Lohmaier almost 4 years ago
The problem is not that the propagation to the translations didn't make it through, the problem now is that the component still exists despite the all of the templates and translations being removed for that component.
Propagation from changes to the github repo are propagated via a hook, so weblate gets notified ~immediately. But of course that change was pretty large, and that probably confused some of the mechanisms in weblate. E.g. the language consistency plugin created files for a few langauges where the weblate default language-aliases differs from our use (we only use nb not nb-NB and use pa-IN instead of just pa despite us having those translations - the plugin just triggered at a time where the files weren't processed yet.)
Long story short: I manually removed the component from weblate (and verified that the download now works).