Marking non translatable text in for Studio 20xx
Thread poster: Jean-Christophe Duc

Jean-Christophe Duc  Identity Verified
France
Local time: 03:30
English to French
+ ...
Jun 22, 2015

Hello,
is there a way of marking non translatable text for Studio 20xx like in olden Trados 7 and its tw4External style?
(I need to translate a text file where the translatable text is between square brackets. Possibly a part of an xml file by the look of it.)
Example:


Direct link Reply with quote
 
Stanislav Okhvat
Local time: 05:30
English to Russian
Re: Marking non translatable text in for Studio 20xx Jun 22, 2015

Hello, Jean-Christophe,

To hide portions of the text, you can use Ctrl+Shift+H key combination which sets the Hidden font attribute, or do the same by pressing Ctrl+D (Font properties) and checking the Hidden box.

A more straightforward way is to use a free tool called Hide/Unhide Text in TransTools for Word: the text you want to hide must be formatted with a specific font color (red is best) or highlight color (e.g., yellow). Open Hide/Unhide Text tool in Word, use the second option (Hide colored text only), choose the color and press Continue. This will hide the colored text.

For example, here are the options for hiding red text:
http://screencast.com/t/4agE3LPOE

Then save the document, import into Studio (by default. hidden text is not imported for translation), translate, export, then open in Word and run Hide / Unhide Text tool with the third option (Unhide all text).

If the text is not exactly Red, choose [Selected Text Font Color] from the dropdown list and then pick the desired color of selected text.

You can find more details here:
http://translatortools.net/word-hideunhide.html

Best regards,
Stanislav Okhvat
TransTools – Useful tools for every translator


Direct link Reply with quote
 

Jaime Oriard  Identity Verified
Mexico
Local time: 20:30
Member (2005)
English to Spanish
+ ...
It's the same Jun 22, 2015

You can use the same styles as before (tw4winInternal, tw4winExternal). You can use other if you want, like mqInternal (to process MemoQ files).

You use the file type settings to set-up non-translatable text.


Direct link Reply with quote
 

SDL Community  Identity Verified
United Kingdom
Local time: 03:30
English
I redid your example... Jun 23, 2015

Jean-Christophe Duc wrote:

Example:
<subject_line>
<password_reset><![CDATA[Choose a new password for your XXX iD account]]></password_reset>
<password_changed><![CDATA[The password for your XXX iD account has been changed]]></password_changed>
<registration><![CDATA[Your account with XXX has been created]]></registration>
</subject_line>


... so we could see the text. You always need to convert reserved characters to xml entities if you want them to display in a forum like this.

If your text has been pasted into a word file (and I sort of assume this is the case) then you can still do the same as before. This article might help.

Regards

Paul
SDL Community Support


Direct link Reply with quote
 

Jean-Christophe Duc  Identity Verified
France
Local time: 03:30
English to French
+ ...
TOPIC STARTER
No way around preping files in Word then? Jun 23, 2015

Thank you all for your answers, I have kept a note of them.

I suppose there is no way to prepare the files directly into Studio?

Would the text marked as hidden display as tags in Studio (I have not had the time to experiment yet...)?

Or even better, is there any possibility to display 3 columns, one for the source, one for the translatable text and ... one for the codes? (A bit like in Idiom with the Comment/SID columns.)


Direct link Reply with quote
 
Stanislav Okhvat
Local time: 05:30
English to Russian
How to mark text as hidden for your example Jun 23, 2015

Jean-Christophe,

Thanks to Paul, we can now see your example so I would like to give you a solution to this problem:

1) Run several search-replace operations in Word using Advanced Find dialogue (press Ctrl+H or use Find->Advanced Find from the Home tab):

Find What: \<[!\!>]@\>
Replace With: Formatting - Font Color - Red
Use Wildcards option - ON
http://screencast.com/t/anmLGH3U4hyE

Find What: <![CDATA[
Replace With: Formatting - Font Color - Red
Use Wildcards option - OFF
http://screencast.com/t/IITiZy2eM

Find What: ]]>
Replace With: Formatting - Font Color - Red
Use Wildcards option - OFF
http://screencast.com/t/IgaHDZoFWKDL

Here is the full result formatted in red:
http://screencast.com/t/HCUsOq7rTW72

2) Use Hide/Unhide Text to hide text formatted with red font color as specified in my previous post.
After exporting from the CAT tool, use Hide/Unhide Text tool and choose the third option to unhide everything.

Result hidden:
http://screencast.com/t/GEuDXwz5Q

Best regards,
Stanislav Okhvat
TransTools – Useful tools for every translator


Direct link Reply with quote
 
_stephan  Identity Verified
Germany
Local time: 03:30
English to German
Native format Jun 23, 2015

I do like TransTools, but since you have to prepare this file from scratch with no highlighted text I suppose you can also use Word's advanced find options to batch-select all the text you want to hide and hide it without the intermediate step.

But to be honest, I'd rather ask the client for a native file format. I often deal with developers who go to great lengths to prepare files for translation, simply because they can't imagine that I can handle their xmls or properties or whatever file type they may be working with, effectively creating more work for both of us.

I'd rather discuss possible file types before these files are piling up, and your client may also appreciate the reduced hassle when they can work with native files all the way.

Stephan


Direct link Reply with quote
 
Stanislav Okhvat
Local time: 05:30
English to Russian
Re: Native format Jun 23, 2015

Hello, Stephan,

I agree with you regarding the source format. It would be much easier to import the original XML file into Studio rather than this text in Word format.

The idea behind painting the text first as the intermediate step is that you see everything that is going to be hidden rather than hiding it in several stages. If need be, it is even possible to translate the text in Studio without hiding, as red text stands out in Word documents with semi-WYSIWYG tag mode activated (default).

Best regards,
Stanislav Okhvat
TransTools – Useful tools for every translator


Direct link Reply with quote
 
_stephan  Identity Verified
Germany
Local time: 03:30
English to German
Highlight Jun 24, 2015

okhvatstas wrote:

The idea behind painting the text first as the intermediate step is that you see everything that is going to be hidden rather than hiding it in several stages.



Good point, I hadn't seen it from that angle. It's certainly less prone to error.

Stephan


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 »

Marking non translatable text in for Studio 20xx

Advanced search







LSP.expert
You’re a freelance translator? LSP.expert helps you manage your daily translation jobs. It’s easy, fast and secure.

How about you start tracking translation jobs and sending invoices in minutes? You can also manage your clients and generate reports about your business activities. So you always keep a clear view on your planning, AND you get a free 30 day trial period!

More info »
BaccS – Business Accounting Software
Modern desktop project management for freelance translators

BaccS makes it easy for translators to manage their projects, schedule tasks, create invoices, and view highly customizable reports. User-friendly, ProZ.com integration, community-driven development – a few reasons BaccS is trusted by translators!

More info »



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