This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
Tarifas actuales.
Tarifas mínimas sugeridas por colegios y otras instituciones.
Tarifas para clientes finales o agencias, locales o extranjeros.
Tarifas de acuerdo al par de idiomas.
Tari
Métodos de cobro más convenientes para pagos locales.
Métodos de cobro más convenientes para pagos desde el exterior.
Situación impositiva y disponibilidad de fondos.
Marketing por correo electrónico.
Uso de redes sociales para la publicidad profesional.
El CV.
Tarjetería y diseño de marca profesional.
Otros métodos para atraer clientes.
Hi again, I have a question related to TMs in server projects. So, while using the server we usually use a TM for each job. We also want to keep a general, "master" TM for that client/ongoing
17:49 May 28, 2014
João Seco: 1708040
All
is there a way of automatically updating that master TM? Or should we export the project TM into a tmx and update the master TM from there?
17:50 May 28, 2014
João Seco: 1708040
All
I'm just worried that doing this might introduce duplicates or other imprecisions in the master TM, which we intend to be authoritative and squeaky clean
17:52 May 28, 2014
Lexie Sabota: 1772099
All
HI Joao, At the end of the project, you can update the master TM at once by pressing the 'Update and confirm' option within a server project.
17:52 May 28, 2014
Lexie Sabota: 1772099
All
This will ensure that the latest and reviewed translations are added to the TM
17:53 May 28, 2014
Lexie Sabota: 1772099
All
Also, in memoQ 2014, you can set an automated task so that the master TM will be updated automatcially when the project finishes. This is part of the templates option
17:56 May 28, 2014
João Seco: 1708040
All
I just have to set the master TM as primary first and then update & confirm, right?
18:11 May 28, 2014
Lexie Sabota: 1772099
All
correct
18:16 May 28, 2014
João Seco: 1708040
All
Thank you Lexie :)
18:17 May 28, 2014
João Seco: 1708040
All
One more, if someone has the time
18:17 May 28, 2014
João Seco: 1708040
All
Regarding sliced documents in server projects: For some projects with crazy deadline, we sometimes have to slice a document to perform review with 2 people on the same doc.
18:17 May 28, 2014
João Seco: 1708040
All
If reviewer 1 confirms a segment that is a repetition on the part assigned to reviewer 2, it will not propagate, correct?
18:18 May 28, 2014
João Seco: 1708040
All
since the segment is already confirmed, it is harder for R2 in this case to see immediately if the segment has already been changed by R1
18:19 May 28, 2014
João Seco: 1708040
All
is there any easy / more obvious way to do this other than relying on the QA consistency check?
18:22 May 28, 2014
Lexie Sabota: 1772099
All
I'm afraid the consistency check is the best way to do this. You can also set up the TM settings to show only the 100% matches from the reviewer
18:22 May 28, 2014
István Lengyel: 142959
All
No, I'm afraid that the consistency check is the only way to make this work. Slicing pretends that there are two documents. The other thing that the reviewer can do is a check for deviations from theT
18:22 May 28, 2014
István Lengyel: 142959
All
... TM - there is a check for segments inserted that are different from what is a 101% match in the TM.
18:23 May 28, 2014
István Lengyel: 142959
All
you see, we are both afraid :)
18:24 May 28, 2014
João Seco: 1708040
All
Maybe the best thing would be to lock the repetitions except one beforehand and just have the PM confirm them in the end