Translating trilingual source

I have a Visual C++ .RC file that contains EN source UI strings and DE & FR target strings.

I am told that Passolo cannot handle this file.

Is there a way it can be managed in Trados?

I have attached a partial file sample (file extension changed).

Thanks for any suggestions.

.
.
.

/////////////////////////////////////////////////////////////////////////////
//
// String Table
//

STRINGTABLE
BEGIN
    IDS_RCES_NOLICENSE      "English string"
    IDS_RCES_EXPIRED        "English string"
    IDS_RCES_RDERT          "English string"
    IDS_RCES_CITRIX         "English string"
    IDS_RCES_GENERAL        "English string"
    IDS_RCES_EVALLEFT       "English string"
	IDS_RCES_VBA_LAST_CALL	"English string"
	IDS_LICENSE_TITLE       "English string"
END

#endif

/////////////////////////////////////////////////////////////////////////////
// German resources

#if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENU)
LANGUAGE LANG_GERMAN, SUBLANG_GERMAN

/////////////////////////////////////////////////////////////////////////////
//
// String Table
//

STRINGTABLE
BEGIN
    IDS_RCES_NOLICENSE      "German string"
    IDS_RCES_EXPIRED        "German string"
    IDS_RCES_RDERT          "German string"
    IDS_RCES_CITRIX         "German string"
    IDS_RCES_GENERAL        "German string"
    IDS_RCES_EVALLEFT       "German string"
	IDS_RCES_VBA_LAST_CALL	"German string"
	IDS_LICENSE_TITLE		"German string"
END

#endif

/////////////////////////////////////////////////////////////////////////////
// French resources

#if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENU)
LANGUAGE LANG_FRENCH, SUBLANG_FRENCH

/////////////////////////////////////////////////////////////////////////////
//
// String Table
//

STRINGTABLE
BEGIN
    IDS_RCES_NOLICENSE      "French string"
    IDS_RCES_EXPIRED        "French string"
    IDS_RCES_RDERT          "French string"
    IDS_RCES_CITRIX         "French string"
    IDS_RCES_GENERAL        "French string"
    IDS_RCES_EVALLEFT       "French string"
	IDS_RCES_VBA_LAST_CALL	"French string"
	IDS_LICENSE_TITLE		"French string"
END

#endif

.
.
.

Translate

Rate translation

Suggest better translation

Moderator UI

Thread Subject & Description
Translating trilingual source I have a Visual C++ .RC file that contains EN source UI strings and DE & FR target strings. I am told that Passolo cannot handle this file. Is there a way it can be managed in Trados? I have attached a partial file sample (file extension changed). Thanks for any suggestions. .code-editor .code-editor-heading{border-top:1px solid #eaeaeb;border-left:1px solid #eaeaeb;border-right:1px solid #eaeaeb;background-color:#fbfbfb;border-radius:3px 3px 0 0;font-size:12.6px;display:flex;justify-content:space-between;align-items:center;overflow:hidden}.code-editor .code-editor-heading .icon{width:32px;height:32px;display:block;overflow:hidden;text-indent:-3000em;background-repeat:no-repeat;background-size:80%;background-position:center}.code-editor .code-editor-heading .fs{background-image:url('https://community.rws.com/cfs-filesystemfile/__key/defaultwidgets/547b4cbb4efb4c3d83533f8f35fb4b7b-1a84591e31034fac832d29ed8584666c/fullscreen.svg?_=637923381702208350')}.code-editor .code-editor-heading .dl{background-image:url('https://community.rws.com/cfs-filesystemfile/__key/defaultwidgets/547b4cbb4efb4c3d83533f8f35fb4b7b-1a84591e31034fac832d29ed8584666c/download.svg?_=637923381702118315')}.code-editor .code-editor-heading .filename{padding:10px;display:block;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}.code-editor .code-editor-heading a{color:#3e414a}.code-editor .code-editor-heading a:hover{color:teal} https://community.rws.com/# https://community.rws.com/cfs-filesystemfile/__key/communityserver-discussions-components-files/90/mfrlm.txt?_=636656184776722693 https://community.rws.com/cfs-filesystemfile/__key/communityserver-discussions-components-files/90/mfrlm.txt?_=636656184776722693 . . . ///////////////////////////////////////////////////////////////////////////// // // String Table // STRINGTABLE BEGIN IDS_RCES_NOLICENSE "English string" IDS_RCES_EXPIRED "English string" IDS_RCES_RDERT "English string" IDS_RCES_CITRIX "English string" IDS_RCES_GENERAL "English string" IDS_RCES_EVALLEFT "English string" IDS_RCES_VBA_LAST_CALL "English string" IDS_LICENSE_TITLE "English string" END #endif ///////////////////////////////////////////////////////////////////////////// // German resources #if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENU) LANGUAGE LANG_GERMAN, SUBLANG_GERMAN ///////////////////////////////////////////////////////////////////////////// // // String Table // STRINGTABLE BEGIN IDS_RCES_NOLICENSE "German string" IDS_RCES_EXPIRED "German string" IDS_RCES_RDERT "German string" IDS_RCES_CITRIX "German string" IDS_RCES_GENERAL "German string" IDS_RCES_EVALLEFT "German string" IDS_RCES_VBA_LAST_CALL "German string" IDS_LICENSE_TITLE "German string" END #endif ///////////////////////////////////////////////////////////////////////////// // French resources #if !defined(AFX_RESOURCE_DLL) || defined(AFX_TARG_ENU) LANGUAGE LANG_FRENCH, SUBLANG_FRENCH ///////////////////////////////////////////////////////////////////////////// // // String Table // STRINGTABLE BEGIN IDS_RCES_NOLICENSE "French string" IDS_RCES_EXPIRED "French string" IDS_RCES_RDERT "French string" IDS_RCES_CITRIX "French string" IDS_RCES_GENERAL "French string" IDS_RCES_EVALLEFT "French string" IDS_RCES_VBA_LAST_CALL "French string" IDS_LICENSE_TITLE "French string" END #endif . . . jQuery(function(j){ var fullScreenToggle = j('#fragment-1a84591e31034fac832d29ed8584666c1390947764_code-editor-fs'); var codeEditor = j('#fragment-1a84591e31034fac832d29ed8584666c1390947764_code-editor'); fullScreenToggle.on('click', function(){ if (codeEditor.evolutionCodeEditor('fullscreen')) { codeEditor.evolutionCodeEditor('fullscreen', false); } else { codeEditor.evolutionCodeEditor('fullscreen', true); } return false; }); });
Get AI Suggestion

AI Reply

Accept answer Reject Answer

0 Paul over 7 years ago

Hi Will Cass ,

I don't think you'll be able to handle this easily in Studio either. You'd need to create a custom filetype through the API to do this properly but it may not be worth the effort unless you get a lot of them?

If the DE and FR strings are actually EN at the start then you might be able to hack a regex filetype to pick out the relevant sections and create a separate project for each target language. But I don't think it would be straightforward.

Perhaps your best bet is to manipulate the file into a different bilingual format so it can be handled correctly in either Passolo or Studio? I think someone like Evzen Polenka might have some experience of dealing with files like this... not sure.

Paul Filkin | RWS Group

________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Will Cass over 7 years ago in reply to Paul

Thanks Paul.

At the moment, it's only one small file so I don't see the point in going to great lengths to find a solution. An easy one would have been nice though! Surely, however, I can't be the only one to have faced this issue?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Paul over 7 years ago in reply to Will Cass

Hello Will Cass

Will be interesting to find out. I’ve never seen a requirement like this before with a file like this requiring one language translating and putting the translation elsewhere in the file. Normally with files like these the languages are separated... at least that’s my experience.

Paul Filkin | RWS Group

________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
0 Evzen Polenka over 7 years ago

Yes, this is simply localization-UNFRIENDLY format, that's all.

As Paul mentioned, the usual approach which respects the traditional localization processes is to have separate resource file for each language.

This looks like typical developer-ish overcomplication... the fact that one CAN use a combination of compiler directives to create such multilingual file does not mean it's okay... the devs need some localization education.

On the other hand, the number of 'uneducated' developers (and clients in general) is growing and we see similar multilingual resources (JSONs, XMLs, various hashtables, etc.) way too often... and it's a PITA to handle those using current CAT tools focused purely on monolingual targets - one has to compile the final multilingual file manually or using additional tools/scripts... The company which creates a CAT tool able to create multilingual target directly will have a big competitive advantage, IMO...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Trados Studio > 1. Trados Studio

Translating trilingual source