program code on a monitorAt MTM LinguaSoft, we are always keeping up-to-date with new technology and looking to save our clients time and money. In addition to that, we don’t like to say “no” to the client because of the source file format. Recently we were able to save a client time and money by using an automated tool that simplifies the preparation of php (PHP: Hypertext Preprocessing) files for translation.

Not all source files are Word documents that are easy to work with. Source files vary from the simplest Word and Excel files to html, xml, and professional design files. Files that incorporate scripting languages like php require special preparation because none of the standard CAT (computer aided translation) tools will filter out the script. Without preparation, all of the script appears as editable text in the CAT toll interface. This has at least two disadvantages. First of all the scripts are counted as translatable text by the CAT tools, inflating the estimate for translation costs. Secondly, if by chance any of these scripts is altered, the translated files would be useless to the client.

<?
//English faAltpay_lang.php
$txt[1] =”School Vouchers have assigned numbers that the FAST system will accept for payment. If you do not have a MasterCard, Visa or American Express, please contact your school. You may pay them in return for a voucher number to complete your application.<br><br>Voucher numbers should be entered in the credit card field, and the current year and month should be entered as the expiration date.”;
?>
<? gatherTime($_SERVER(‘PHP_SELF’]);?>
<? II ?>
<? gatherTime($_SERVER[‘PHP_SELF’]);?>

PHP script with out preparation. The translator will see everything as translatable text in a CAT tool.

Often the answer to this problem is to prepare the files and manually hide – or remove and later replace – any script. However, this means added time and charges for file preparation.

Recently, one of our clients contacted us about an online student application they would like to translate into French. The source files were PHP files. We decided to look for some tool that would automate the file preparation; hiding all the script before the translation process, and then unhiding it once the translation is done. After some search and recommendations we found PrepTags, a utility that, with few settings, would do exactly what we were looking for. Once the files were prepared, we did the translation as usual and delivered the files to the client.

<?
//English faAltpay_lang.php
$txt[1] =
“School Vouchers have assigned numbers that the FAST system will accept for payment. If you do not have a MasterCard, Visa or American Express, please contact your school. You may pay them in return for a voucher number to complete your application.<br><br>Voucher numbers should be entered in the credit card field, and the current year and month should be entered as the expiration date.”;
?>
<? gatherTime($_SERVER(‘PHP_SELF’]);?>
<? II ?>
<? gatherTime($_SERVER[‘PHP_SELF’]);?>

PHP script after preparation. None of the material in gray will show up in a CAT tool.

The utility also works with other types of code, such as javascript and sql. So, having invested our time in looking for and testing a new tool, we are ready to jump right in when clients provides us with these file types in the future —significantly decreasing file preparation time, saving the client money, and lessening worries about script integrity.

This is all in a day’s work at MTM LinguaSoft where we measure our success by how well we meet our client’s needs and expectations.

Related Posts: