Forum: SDL Trados support
Topic: Studio 2011: no blanket "copy source" for non-alpha segments?
Poster: SDL Support
Post title: Long question, and it’s better for replies...
... if you keep the posts simple and ask one question per post. It takes less effort for anyone who might be reading the posts.
[quote]Andrew052 wrote:
1) I would be grateful, if you explain, how "regex" works, as I've never heard about it before.
[/quote]
This isn't a Studio thing. Regex is short for Regular Expressions and they can be used to search, or search and replace, for text in many applications. Even Microsoft Word has a flavour of Regex you can use. The link I provided is worth reading I think as this will show you how they work and where they can be used in different ways in SDL Trados Studio. Here it is again : [url removed] There are four articles specifically on this subject and the other three are linked at the end of the first article. These might be helpful for you.
[quote]Andrew052 wrote:
2) You have said something about "mering the files together" -- what did you mean. I am really interested in trying to find new ways to tackle this issue and if this "merging process" does something to make it quicker to work with "number-only" segments or range the segments alphabetically in trados, I would be grateful to find you more about it.
[/quote]
If you have a Project with multiple files then you can open as many of the files as you like in one go by selecting them in the Files View in Studio and then clicking the Open for Translation button in the ribbon. They will also be ordered in the order you selected the files.
[quote]Andrew052 wrote:
bushing for system 2
bushing for system 2
bushing for system 2
bushing for system No. 2
bushing for system No. 2
bushing for system No. 2
bushing for system Number 2
bushing for system Number 2
bushing for system Number 2
bushing for system Number 2
Benefits:
1. clearly great with "bushing for system 2" segments
[/quote]
Long question... best for other translators to answer this one. But my take on this, whilst I can see the benefits of sorting as you can in memoQ, would be this.
Things like "bushing for system 2" segments, or the others, are probably no problem. Once you translate one then the rest, wherever they are will be automatically translated, even if the number changes. So no need to have to sort these.
But I can see how sorting makes it easier to tackle all these similar segments before you start as you will be able to see them immediately. So the only suggestion I would have in this regard, as a workaround, would be to export the translation to Excel using the [b]SDLXLIFF for Microsoft Office Converter[/b] (installed with Studio 2011 and Studio 2014 in the OpenExchange apps program group) and then sort the segments in Excel so you can see them more easily. Then you can either find and translate them in Studio, or using the SDLXLIFF Toolkit, or add the sorted Excel file (at least just the segments that are relevant to this exercise) to the Project and then translate these so they are in the TM. Then pretranslate the whole Project. So this is a workaround I know... but perhaps it’s helpful.
Then of course you also have the Terminjector that might be useful as you can set up the patterns to be automatically translated... but you will need to learn a little about regex to use it ;-) The Terminjector is described here : [url removed] There are many avid fans of this app ikn this forum, so perhaps some of them can share their views on using it to help you.
Regards
Paul
Topic: Studio 2011: no blanket "copy source" for non-alpha segments?
Poster: SDL Support
Post title: Long question, and it’s better for replies...
... if you keep the posts simple and ask one question per post. It takes less effort for anyone who might be reading the posts.
[quote]Andrew052 wrote:
1) I would be grateful, if you explain, how "regex" works, as I've never heard about it before.
[/quote]
This isn't a Studio thing. Regex is short for Regular Expressions and they can be used to search, or search and replace, for text in many applications. Even Microsoft Word has a flavour of Regex you can use. The link I provided is worth reading I think as this will show you how they work and where they can be used in different ways in SDL Trados Studio. Here it is again : [url removed] There are four articles specifically on this subject and the other three are linked at the end of the first article. These might be helpful for you.
[quote]Andrew052 wrote:
2) You have said something about "mering the files together" -- what did you mean. I am really interested in trying to find new ways to tackle this issue and if this "merging process" does something to make it quicker to work with "number-only" segments or range the segments alphabetically in trados, I would be grateful to find you more about it.
[/quote]
If you have a Project with multiple files then you can open as many of the files as you like in one go by selecting them in the Files View in Studio and then clicking the Open for Translation button in the ribbon. They will also be ordered in the order you selected the files.
[quote]Andrew052 wrote:
bushing for system 2
bushing for system 2
bushing for system 2
bushing for system No. 2
bushing for system No. 2
bushing for system No. 2
bushing for system Number 2
bushing for system Number 2
bushing for system Number 2
bushing for system Number 2
Benefits:
1. clearly great with "bushing for system 2" segments
[/quote]
Long question... best for other translators to answer this one. But my take on this, whilst I can see the benefits of sorting as you can in memoQ, would be this.
Things like "bushing for system 2" segments, or the others, are probably no problem. Once you translate one then the rest, wherever they are will be automatically translated, even if the number changes. So no need to have to sort these.
But I can see how sorting makes it easier to tackle all these similar segments before you start as you will be able to see them immediately. So the only suggestion I would have in this regard, as a workaround, would be to export the translation to Excel using the [b]SDLXLIFF for Microsoft Office Converter[/b] (installed with Studio 2011 and Studio 2014 in the OpenExchange apps program group) and then sort the segments in Excel so you can see them more easily. Then you can either find and translate them in Studio, or using the SDLXLIFF Toolkit, or add the sorted Excel file (at least just the segments that are relevant to this exercise) to the Project and then translate these so they are in the TM. Then pretranslate the whole Project. So this is a workaround I know... but perhaps it’s helpful.
Then of course you also have the Terminjector that might be useful as you can set up the patterns to be automatically translated... but you will need to learn a little about regex to use it ;-) The Terminjector is described here : [url removed] There are many avid fans of this app ikn this forum, so perhaps some of them can share their views on using it to help you.
Regards
Paul