Bug 836982
| Summary: | RFE: Zanata should provide UI to upload multiple translated files from local repository | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Zanata | Reporter: | Parag Nemade <pnemade> | ||||
| Component: | Component-UI | Assignee: | Michelle Kim <mkim> | ||||
| Status: | CLOSED UPSTREAM | QA Contact: | Zanata-QA Mailling List <zanata-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | unspecified | CC: | chepioq, damason, djansen, jfenal, lbrooker, mkim, yshao, zanata-bugs | ||||
| Target Milestone: | --- | Flags: | djansen:
needinfo-
|
||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-07-29 03:33:01 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Parag Nemade
2012-07-02 12:13:26 UTC
Just to confirm, this is a requirement for multiple language files to be uploaded from a project management perspective and privileges? Thanks. Yes. The UI will ask the po files directory path and this feature will read the contents of directory and then upload all the available language po files to Zanata. zanata-python-client-1.3.5-1.fc17.noarch zanata python client version: 1.3.5, zanata server API version: 1.5.0 Request for Technical Evaluation. Can anyone check what is the update for this issue? is this resolved or deferred or denied? I have not yet got any update since last 5 months. It is possible to implement this feature in Zanata. The 'scanning' feature is mostly implemented in desktop application but not web application as there is a high security risk to consider when allowing browser to scan through local drive/directory which is not recommended. From most of the upload features I've seen from web, there's no "scanning" features involve and the interaction has always been selecting individual files from local drive. As an alternative, our client supports pushing of all documents from local drive. Please contact us if you have any problem setting up zanata client. Can anyone check what is the update for this issue? is this resolved or deferred or denied? (In reply to Parag from comment #6) > Can anyone check what is the update for this issue? is this resolved or > deferred or denied? I don't think we have any plans to work on this in the next release since we are working on improving the server and the cli client, but I certainly think a GUI client is something that should be implemented at some point. In my own time I have made a start to coding a GUI client targeted at translators, a lot of that code could be reused to make a GUI client for maintainers, but development is slow since I'm usually quite busy these days. It is also worth pointing out that any client just needs to use Zanata's REST API, so it is possible to make clients without any need to fit in with server development or the core development team. Any updates here? This feature, if I understand correctly the initial request, would be to have the same Transifex provides, with the ability for a translator working offline with a tool such as kbabek/lokalize to upload, via the web interface (e.g. lower the access barrier to their contributions), a single translated .po. Transifex allows it from the resource dialog. See attached transifex-upload-download-dialog.png for illustration. Created attachment 943160 [details]
transifex-upload-download-dialog.png
Translators can work offline and then upload translated work as they wish. Translation file upload is supported for .po and .properties with the command line client, and .po for web upload. Other file types (txt, html, etc.) allow translated file upload, but it is not recommended since their structure makes it difficult to reliably match translations to the appropriate source. There has been work done on a GUI client built for offline translation. Other improvements have been given priority over this in the past, however it is something we can raise the priority on if it is seen as a necessity. Thanks, Isaac If we are looking at an offline editor, I think we are better off making the new(in progress) editor capable of doing a lot of tasks offline. This would enhance the experience for everyone and mean we don't need to maintain 2 editing tools. If users still want to use another offline tool for translation, they can still upload new translations via the web UI in a similar way to Transifex. We have made some improvements to the file uploader in the UI for source files, we should add these enhancements to translation file uploads too, allowing whole directory uploads of translations if needed. I lost the interest in zanata bugs now. This feature (Multiple translated file upload via UI) would become more useful for users in near future. Setting the priority high. Estimated implementation: Update the dialog window - use the new style dialogue for single translated source file upload + more meaningful tooltips for merge - 2 story points I created a separate bug for the 2 story points - updating the dialogue window https://bugzilla.redhat.com/show_bug.cgi?id=1207951 This bug's scope is to provide a way for maintainers/translators to upload multiple translated files via GUI. Implementation details to be discussed. Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-317 |