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.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

miro_dietiker’s picture

Title: Xliff download /upload in local translator » XLIFF download /upload in local translator
miro_dietiker’s picture

Issue summary: View changes
Issue tags: +XLIFF
johnchque’s picture

Issue summary: View changes
miro_dietiker’s picture

Version: 7.x-1.x-dev » 8.x-1.x-dev

Oh, didn't find this, because it was still 7.x

cgalli’s picture

First 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.

cgalli’s picture

Status: Active » Needs review

Status: Needs review » Needs work

The last submitted patch, 5: file_management_local_1998066_5.patch, failed testing.

miro_dietiker’s picture

We 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?

cgalli’s picture

Fair 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...

cgalli’s picture

Status: Needs work » Needs review
FileSize
4.66 KB

Built the controller for export.

Got stuck when sending $data as file content

Please advise.

cgalli’s picture

File export working. Unfortunately, the redirect is included in the file text as well. Any idea how to prevent this?

cgalli’s picture

Export working
Import started. Data from the file will go into the task item fields, right?

Please advise

cgalli’s picture

Initial 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?

miro_dietiker’s picture

If 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.

cgalli’s picture

added support for multiple field instances

cgalli’s picture

Reworked the data access for job items to comply with tmgmt methods.

miro_dietiker’s picture

Bump :-)

miro_dietiker’s picture

Priority: Normal » Major

It seems we need to raise prio to make this more visible.

cgalli’s picture

good to know:-)