Problem/Motivation
The local translator supports communication, workflows, metadata.
With high probability translators will want to download an xliff to work on it.
Still the server and/local translator will help them a lot in the job:
Dealing with transactions, versioning, job comments, assignment to the person, communication/feedback, statistics, ...
In future also preview and more.
So we want to use the local translator and add the xliff support. AND want to have comments in.
Later we want to export only what is unaccepted / came back for revision.
We have discussed about this topic in the Basel MeetUp in March 2016.
Comment | File | Size | Author |
---|---|---|---|
#16 | file_management_local_1998066_16.patch | 8.13 KB | cgalli |
| |||
#16 | file_management_local_1998066_16.interdiff.txt | 2.71 KB | cgalli |
#15 | file_management_local_1998066_15.patch | 8.14 KB | cgalli |
| |||
#13 | file_management_local_1998066_13.patch | 7.96 KB | cgalli |
| |||
#12 | file_management_local_1998066_12.patch | 4.77 KB | cgalli |
|
Comments
Comment #1
miro_dietikerComment #2
miro_dietikerComment #3
johnchqueComment #4
miro_dietikerOh, didn't find this, because it was still 7.x
Comment #5
cgalli CreditAttribution: cgalli as a volunteer commentedFirst proof of concept.
I chose the option to build an XLIFF file for every job created in the local translator. This simplifies the UI. But it also adds load to the process and may create unnecessary files.
Option 2 could be to have a button in the 'Manage file' pane to create the file when needed.
Comment #6
cgalli CreditAttribution: cgalli as a volunteer commentedComment #8
miro_dietikerWe would prefer to generate the file in a page callback on request.
The UI thus still just needs to have a link to that.
What do you think?
Comment #9
cgalli CreditAttribution: cgalli as a volunteer commentedFair enough. Will work on that.
As far as reuse/duplication of code is concerned. I will continue in the same fashion until told otherwise. It seems clear though that some sort of reusable code bits could be useful...
Comment #10
cgalli CreditAttribution: cgalli as a volunteer commentedBuilt the controller for export.
Got stuck when sending $data as file content
Please advise.
Comment #11
cgalli CreditAttribution: cgalli as a volunteer commentedFile export working. Unfortunately, the redirect is included in the file text as well. Any idea how to prevent this?
Comment #12
cgalli CreditAttribution: cgalli as a volunteer commentedExport working
Import started. Data from the file will go into the task item fields, right?
Please advise
Comment #13
cgalli CreditAttribution: cgalli as a volunteer commentedInitial patch with export and import working.
Questions to be resolved:
- What status should an imported data item have. Checked?
- What happens to an imported task item? Should it be submitted automatically? Or does the user have to go through each item, saving and submitting individually?
Comment #14
miro_dietikerIf we want to support marking it as completed, it needs a checkbox on upload. By default it should not autoconfirm IMHO.
It's about local translator. The external tool can not support a real preview and people should use it before finalising. Also the external tool is likely to do less validation and that's why each item should be opened once and finalised, at least recommendedly.
Clearly, the local translator is not there yet, but it will improve into this direction step by step.
Comment #15
cgalli CreditAttribution: cgalli as a volunteer commentedadded support for multiple field instances
Comment #16
cgalli CreditAttribution: cgalli as a volunteer commentedReworked the data access for job items to comply with tmgmt methods.
Comment #17
miro_dietikerBump :-)
Comment #18
miro_dietikerIt seems we need to raise prio to make this more visible.
Comment #19
cgalli CreditAttribution: cgalli commentedgood to know:-)