Two questions came up on ProZ today which Studio can handle very nicely. Despite this I often see some very clever and amazing workarounds that are probably not necessary at all. So I thought I’d write this quick post for two reasons… the first just to share these great and easy to use features in Studio, and secondly because I thought I’d use FastStoneCapture to record a video to explain the process when I answered both questions on ProZ this afternoon, and I blogged about this brilliant little tool last week.
Using the Regex Filetype in Studio
So, the first question was about how to extract the text after the equals sign when translating LNG files. The sample text provided was this:
OptimizingPars=Optimizing paragraph structure
GettingParData=Getting paragraph data
AnalyzingPars=Analyzing paragraph structure
Studio has a great regex filetype that has been in the software since the early Trados days as well, but it’s even better now. So my video is here:
Translating columns of text prepared in Microsoft Excel using Studio
Update 21 Dec 2015
Studio 2015 introduced a bilingual Excel filetype which could be used in preference to the CSV filetype.
Update 1 Sept 2017
Studio 2017 added the ability to apply embedded content rules using regular expressions in the bilingual excel filetype.
The second question that came up related to being able to translate a column of text in excel, but place the translated text into a different column. Then, just to add to this problem, some of the text was already translated and was already in the second column.
Studio can also handle this a couple of ways really nicely, so I did another quick video to address this as well: