Editing source text
Thread poster: Van Der Sman
Van Der Sman
Germany
Local time: 17:58
English to Dutch
+ ...
May 8, 2015

Is it possible to edit the source text while working on a translation?

In other words, is possible to: 1. delete sentences in the source text, or 2. to correct spelling mistakes in the source text?

My client has sent me a number of sentences that are to be deleted and it would be quite useful if this could be done directly in the source text. I have not, however, been able to find any threads on this subject on Proz, nor is there an entry to that effect in the Across Help/Faq sections.


Direct link Reply with quote
 

Henry Hinds  Identity Verified
United States
Local time: 09:58
English to Spanish
+ ...
Tell May 10, 2015

Tell the client to send you the source text after editing it as he wants it, then translate it for him, and that's it.

Direct link Reply with quote
 
lprd027
Local time: 03:58
German to English
+ ...
Not after the document has been checked in May 10, 2015

As far as I know, you can only make corrections to the source text prior to checking it in to Across.

However, you can make corrections prior to storing the translated segment in the TM (crossTank). Of course, the source text will still be incorrect but the TM entry will be correct.

Refer to this FAQ item for instructions on how to do this:

http://www.across.net/en/support/faq/c/crossdesk-1/

"I found a spelling mistake in the source document. How can I prevent the mistake from being stored in crossTank?"

I hope this helps.

Regards
Lars Peter


Direct link Reply with quote
 
Van Der Sman
Germany
Local time: 17:58
English to Dutch
+ ...
TOPIC STARTER
clarification May 11, 2015

Thanks for the extensive replies, much appreciated!

I see now that I haven't formulated my question carefully enough so I would like to provide you with some more context.

The situation is as follows:

I translated the entire document, around 8000 words, had it proofread by a collaborator and then sent it to my client with some questions and remarks. Those were answered and, additionally, the client edited the text: rewrote a number of sentences, added a few sentences and omitted some that were redundant.

The reason I would like to work directly in the source text, is that I collaborate with a specialist in the field (as mentioned above). She checks for mistakes in terminology and idiom, but also quite simply for omissions and general translation mistakes.

It would make communication a lot easier if we could make sure we are all (myself, client, collaborator) always working on the same document. Adapting the source text as well as the translation while working on it would be the most economical way of ensuring that that is the case.

However, it doesn't look like that is possible.

I wouldn't mind too much if it were only this one text, actually - but there are around 15 more coming...

[Edited at 2015-05-11 07:32 GMT]

[Edited at 2015-05-11 12:58 GMT]


Direct link Reply with quote
 
lprd027
Local time: 03:58
German to English
+ ...
This is a work-flow management issue….. May 13, 2015

It appears to me that you are conflating two separate but parallel processes here; (1) development of the source text [ST], with (2) translation of the source text to produce the translated text [TT].

Generally speaking, the ST is produced independently, with translation only commencing after the ST is complete, or at least nearly complete; indeed, minor amendments are often made to the ST while translation is in progress, but this is no problem, provided you adopt a structured approach.

If you (as translator) are collaborating on the ST, then this would be best done by using a cloud-based service such as Google Docs. However, Across is not designed to do this: it is not a collaborative authoring tool.

The usual way to translate documents in development is to use version numbering. You can import version 1 of the source document (ST-01 say) into ACROSS and translate it to produce TT-01. When completed, crossTank (Across' TM database) will contain all of the translated segments pertaining to this document/language pair.

You can now iterate the ST authoring process to produce the next version of your ST (ST-02). It should be substantially similar to ST-01.

Now, when you import ST-02 into Across, pre-translation will translate all segments in ST-02 that also appear in ST-01. Segments deleted from ST-01 are of no concern, since they are absent from ST-02. You only need to translate the changed segments, which are likely to be few in number. Even here, fuzzy matching from the TM will help you translate the amended segments.

Having produced TT-02, you can further iterate the process (ST-03/TT-03 etc.) until completion, whereby you are leveraging the contents of the TM to manage this process efficiently.

You mention that you have 15 documents to translate. This is absolutely no problem if you adopt the structured approach that I have described. What is more, if there is any commonality between the texts, you can leverage the TM even more as you proceed to translate them.


[Edited at 2015-05-13 01:58 GMT]


Direct link Reply with quote
 
Van Der Sman
Germany
Local time: 17:58
English to Dutch
+ ...
TOPIC STARTER
many thanks! question answered May 13, 2015

Thank you lprd27, your reply addresses all the issues I found myself dealing with.

I fully agree that it is essentially a work-flow issue.

So far, I have had little experience with translating texts that are simultaneously being developed. The ST was usually a finished and relatively polished product and did not need much revision. These texts, written by a research scientist working under a deadline with the research running parallel, are different. I found myself in unfamiliar territory, and had trouble working out a clear structure: your reply has given me a road map.


I will adopt the structure you suggested, thanks again for this clear and simple solution and for taking the time to describe it so well.


Direct link Reply with quote
 
lprd027
Local time: 03:58
German to English
+ ...
More suggestions… May 14, 2015

Managing multiple versions of multiple documents along with their translations can be difficult, more so when you are collaborating with others over an extended period of time.

I suggest you develop a robust file naming convention that clearly identifies the content, version number and language of each document.

Also, I suggest you appoint a "controller" for each document, who co-ordinates the editing process and manages the "master" document through its various revisions. This would be normally be the original author, but need not be. Failure to do so may lead to lost amendments and confusion.

Once a particular ST version has been closed (for amendments) and issued for translation, it is effectively frozen and must not be changed. The resulting translation will match exactly the issued version. Any further amendments must be made to the next version.

In regard to the translation process, here are two features of Across you might find useful:

(1) Within crossView you can attach a comment to any segment. It is up to you how you use this: you can use it to record reminders, or to remark on some aspect of either segment. (NB: the comments do not appear in the final TT).

(2) You can switch crossView to "Correction Mode" to see your translation in a side-by-side, bilingual view. You have the option here to display (or not) any comments you have entered during the translation. You can output this view to a printer, or save it as a pseudo-bilingual file in either PDF-format or HTML-format. If you elected to display your comments, they will be included in the output.

I find the printed hard-copy option most useful as I prefer to edit offline from a printed hard-copy - I mark it up with a pencil and then make the corrections in Across later in one pass.

In your situation, the bilingual file might be more useful as you can send it to your colleagues, if this is useful, alongside the TT; in this case, you could enter comments for their benefit.

One final comment: you have not so far made any mention of terminology. I hope you are using Across to manage your terminology. You should be making use of existing terminology databases - if they exist in your field - to ensure your terminology translation is accurate and consistent. This is especially important in scientific and technical fields. Or you can build your own terminology database within Across - refer to the relevant documentation.


[Edited at 2015-05-14 03:47 GMT]


Direct link Reply with quote
 


To report site rules violations or get help, contact a site moderator:


You can also contact site staff by submitting a support request »

Editing source text

Advanced search






PerfectIt consistency checker
Faster Checking, Greater Accuracy

PerfectIt helps deliver error-free documents. It improves consistency, ensures quality and helps to enforce style guides. It’s a powerful tool for pro users, and comes with the assurance of a 30-day money back guarantee.

More info »
Déjà Vu X3
Try it, Love it

Find out why Déjà Vu is today the most flexible, customizable and user-friendly tool on the market. See the brand new features in action: *Completely redesigned user interface *Live Preview *Inline spell checking *Inline

More info »



Forums
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search