Questions?

In the 'currency' tab I can only use dropdown means with 2 default currencies and lots info re exchange rate etc.

Is there a way to select/change the default vendor PO in a Smart Project?

We would like different process templates to have different POs. Right now, we can't figure out how to change it from the XTRF default. 

Hi!

Please, tell me, is there a possibility to split a job into more than 2 parts?

Is it possible to select several source languages? For example, there is a document in English to be translated into Russian, and in this document there is a sea in Chinese also to be translated.  

Is it possible to assign one and the same document to more than one vendor? For example, a test translation when several versions are required.

Not sure if I should put this under Q&A or under suggestions, but I was wondering if there is a possibility to add client-linked (not project-linked) reference files to the client profile, so that they are accessible and downloadable by the vendor from the vendor portal for each job of that client. We have a workaround with LiveDocs in memoQ, but this option is only valid for our memoQ users and not for the other thousands of translators.

Hi,

Not sure if this topic has already been brought up by someone else... I couldn't spot it in any case, so better safe than sorry.

I don’t know about the other LSP’s, but we process hundreds of InDesign files a week for our clients. We always upload the PDF as a reference file to the project as only very few of our translators have InDesign licenses installed. But, problem is that reference files are not shared with the vendors, before they accept our job offers. So unless we manually send the PDFs in an e-mail, our vendors just accept the job without even having watched the files upfront. Risky business, often leading to frustration.

It would be great to have such files available on vendor portal before job approval by vendor.

Hello, we are trying to find some ways how to (temporarily) disable the possibility to issue quotes for certain clients (who are not paying for example). Is there any way how this can be achieved without actually deleting the client completely?

We are getting language-specific files from a client, and would like to use Smart projects but I don't see a way of adding files to be translated to specific languages only.

In a classic project you can use bundles to categorize files that will go through a specific workflow, so I am looking for an equivalent way of doing this in a Smart project.

Does anyone have any idea how this can be done?

Hi,

It seems that the ${providerPortalURL} in the email templates is no longer working. Checking with Firefox, instead of point to the correct address, this has now added some characters in the end and points to: 
https://xtrf.eurologos-thessaloniki.com/vendors/%E2%80%8B

I don't think this is possible, but I believe it is a useful feature. We have some customers who have several connected companies, but the contact persons for these are the same. 

Would it be possible to share the same contact person with several connected customers, without having duplicate contact persons?

We are facing one specific issue concerning XTRF and the automated workflows that use the Trados integration. It's given by our specific setup where the Trados Agent/Trados Studio is installed on our US server where also all the XTRF resources (TM's, termbases).

Now, the unpleasant issue is that the people in French office (PM's, linguists) don't have direct access to the US server (although they can connect through VPN) so whenever they open a package created by the Agent in Trados Studio they receive an error message that the TM's cannot be accessed so in the end they have to add the TM's manually which takes time especially with multilingual projects.

So we were trying to modify the settings in a way that TM's are always attached into the packages, but it doesn't seem to work.

So far we checked the workflow definitions and tried to change the settings regarding TM (see the attached screenshot). We tried both of the following:

• Create a new file-based project translation memory for every package
• Include the existing project translation memory in every package

Neither of it makes any difference, there are still only remote TM's attached in the package.

If anyone has some ideas what to try to get rid of this obstacle we will be really grateful.