RFE: Remove Project Type, Zanata should recognise file types individually

Description

Description of problem:

Files types should be recognised by their extension or, failing that, metadata.
It seems somewhat pointless and restrictive to force a project version to be one type.

Users should be able to simply upload their sources, and have:

  • Zanata set the type,

  • Ask them if it can't work it out,

  • Allow the maintainer to set it to something else if Zanata gets it wrong,

  • A little icon in the file list telling the user what kind of file it is

Version-Release number of selected component (if applicable):
3.2

Activity

Show:

Former user 20 April 2018 at 00:24

We are closing all the old issues to have more clarity in our backlog for Zanata project. Feel free to re-open or leave a comment if you require our attention on your Jira.

Bugzilla Migration 29 July 2015 at 03:23

Damian Jansen commented:

Reassigned to PM

Bugzilla Migration 29 July 2015 at 03:23

John Skeoch commented:

User irooskov@redhat.com's account has been closed

Bugzilla Migration 29 July 2015 at 03:23

Ding-Yi Chen commented:

One of the good test case is Freemind, it has translation for .odt and .properties.

Bugzilla Migration 29 July 2015 at 03:23

David Mason commented:

(In reply to Ding-Yi Chen from comment #15)
> Command hook won't help the people that use WebUI and download all
> translation as zip. It will be better to make the rule available on
> serverside, so download from WebUi and pull with client get consistant
> result.

I agree fully - I am only suggesting command hooks as a workaround to avoid some manual work until different project structures are supported. Since the server generates zip files with translations, we definitely need to implement support for arbitrary project structures on both the client and the server.

Not Applicable

Details

Assignee

Reporter

Labels

Components

Priority

More fields

Created 29 July 2015 at 03:23
Updated 20 April 2018 at 00:30
Resolved 20 April 2018 at 00:30