Asmir Mustafic

The issue is that the XLIFF files have a single state, and as soon a file has been written, there is a potential that those changes might land in production....

Even if changing the other tooling, there will be a moment when a wrong translation is on production. Case: 1. dev uploads translation 2. translator translates 3. reviewer approves the...

A write policy sounds a good idea. Regarding the authorship I do not see the issue, git allows to define multiple people as authors for one commit, and if you...

I personally would like to avoid having relations added at runtime. I prefer to declare relations when possible and then allow to exclude them at runtime. The main advantages of...

@lstrojny sorry for the misunderstanding, but yes that sounds a good idea. this change needs also some adaptations in the builder class to allow you to pass the custom implementation...

From the readme of this project: > Only document/literal style is supported and the webservice should follow the WS-I guidelines. Im not sure if the XMLSchema-instance usage you are tying...

Well, it might work... but you did not answer to my previous comment: > Im not sure if the XMLSchema-instance usage you are tying is WS-I and document/literal style compliant

If somebody is interested in sponsoring this feature I can continue to work on it. Pricing can be agreed (compatible with west-european hourly rates).

is the file mentioned by the error accessible?

> is the file mentioned by the error accessible? Can it be that the PHP client is not allowed to access the file for same reason? from what I know...