[zanata-bugs] [Bug 1035959] [RFE] Zanata should recognise file types individually, not from the target project

bugzilla at redhat.com bugzilla at redhat.com
Fri Nov 29 07:02:00 UTC 2013


https://bugzilla.redhat.com/show_bug.cgi?id=1035959

Sean Flanigan <sflaniga at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sflaniga at redhat.com



--- Comment #1 from Sean Flanigan <sflaniga at redhat.com> ---
We currently use project type so that the server will know about files (eg
.xlf, .properties) which were converted into Zanata format by the client.  (We
need to know this to produce an "offline PO" safely.)  By the time the server
sees the file, it is just XML, with no file extension.

Another significant limitation with the idea of "project type" is that it means
a given project can only support one type of file (xliff, properties, gettext,
podir or "raw").

One way to solve this would be use the FileService for all files (as we do for
"raw" files).  It would need to be extended to handle XLIFF/Properties/Gettext
files, but the FileService already knows about file types, and it stores the
original file, which could be very useful.

This would imply that clients would send their .xlf, .properties or .po files
to the server for conversion by the FileService, just like, say, .odt files
("raw").  The difference is that the FileService would probably not use Okapi
for the conversion of these file types.

Deciding on the best migration strategy for existing projects would be the
tricky bit, especially if the project type hasn't been set (or is wrong!).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=oyn5fdWEo8&a=cc_unsubscribe




More information about the zanata-bugs mailing list