We have multiple customers that are using Contao CMS (formerly TYPOlight). Unfortunately there is no good export/import tool to get the content in and out for translations. We have a plugin for Drupal and Typo3. WordPress is in development, Contao in the evaluation phase.

In the meantime what we often get are Microsoft Word files. This works perfectly for us, but is cumbersome for the client. We recommend to send us the raw HTML code. This way there is no copy&paste and modify necessary. All formats stay as the were.

Click on the HTML button in the Contao Editor Toolbar (as seen above). This will open the plain text HTML editor.

Just copy&paste this text into a normal text file and send it to us.

You will get it back in the exact same format and everything you have to do, is paste it back into this editor. Done.

If you need to translate multiple pages or your whole website, we can export all your pages automatically and reimport them again afterwards. This involves no manual work for you at all. Just contact us.

#i18n

i18n stands for internationalization.

i + 18 letters + n

Take the first letter, count up to the second last and then the last one.

Internationalization describes the process of planning and developing a product (normally software) that can be adapted into different cultures and languages without changing the core architecture of it afterwards.

#L10n

This is localization. Works the same way as #i18n.

Localization is the actual work that needs to be done to make the product support multiple cultures and languages. For example translating a  user interface.

#T9n

Again, same principle, but this means translation.

#G11n

The last one of this group. Short for globalization.

Globalization describes the whole life cycle of a global product. This starts with the design and development until marketing and adaption into different markets.

#xl8

Stands for translate.

x = trans

l = l

8 = ate

#xl8r

Similar to #xl8, just instead of translate, it means translator.

x = trans

l = l

8 = ate

r = r

Alternative you could use #t8r, but #xl8r is much wider used. At least according to a google search:

“#xl8r” translation ->About 1,010,000 results

“#t8r” translation -> About 42,400 results

Instead of the short versions, people also use the normal words, but since you have only 140 chars at your disposal, they are not very common:

#localization

#translation

#language

I’ve already made a similar post about this topic a while ago:

http://blog.supertext.ch/2010/04/was-bedeuten-l10n-und-i18n/

And Jennifer McNulty wrote another nice explanation here:
http://blog.adaquest.com/2011/09/23/g11n-i18n-l10n-translation-%E2%80%93-sure-you-know-what-these-mean-or-feeling-gilty-because-you-need-clarification-2/

You have questions about other tags? Check out #tagdef.

Are you using any SDL Server products? Are you working in a team of more than one project manager or translator?

How do you share your SDL Trados Projects, Translation Memories and Terminology Lists? Did you think this is not possible without a Trados Server Product?

You might be wrong. Below you can see how we at Supertext are doing it.

First, you need a shared network drive on a server or on any workstation that is constantly online.

Make sure this drive is mapped on every PC the same way. You do not need to assign a special drive letter, you can just use the name of that PC. Obviously every team member needs access to this folder.

In our case we named it like this:

\\STORAGE\Open\Trados

We then created the following folder structure:

Trados\SDL MultiTerm\Termbases

Trados\SDL Trados Studio\Projects

Trados\SDL Trados Studio\Translation Memories

You might notice that this is the standard Trados folder structure on your workstation. We figured it makes it easier for everybody to stay with what people are used to.

This is pretty much all there is. Just place your projects into the Projects folder, the TM into the Translation Memories folder and the Termbase into the Termbases folder.

This way everybody can access and update all  TM and Termbases without the need for an expensive Trados Server Product. You can also open all Return Packages, no matter if you created the inital Project or not. Just load the original Project first.

Does it take minutes to load Trados? In our case, it took up to 20 minutes to load Trados. Normally Trados should start in a few seconds.

We are using a floating license with a license server in our private network. I think all this does not apply if you have a local license on your PC.

If you have the same problem, check the following things first:

• Switch off the firewalls on both the client and the license server.
• If VM Ware is running parallel on the server, disable it.
• Are you using switches on the network? Could cause problems. Try a direct connection.
• The Flex License Server should run on Port 27000, make sure it does and make sure the  client connects to it on that port. Eg. 27000@<my_server>
• Make sure you everything is from Trados 2009 and that you don’t have any other versions running.
• The license server has to run on a fixed IP. This is core!

Got the hints from Grzegorz Gryc.

Now, in our case the problem was a bit complicated. Our license server was not running on a fixed IP, for some reason the DHCP server is handing out the IP addresses in some weird way (normally every PC gets the same address every time it connects). Anyway, we fixed that, but still it took ages for Trades to start up. At least we didn’t get the License Server Dialog anymore.

The 2nd problem was, that Trados was scanning all possible IP addresses that the license server ever had (even though now it was fixed).

To solve this do the following:

1. Start the SDL License Manager (under the SDL Program group)
2. Click on “License Locations”
3. Remove all locations and make sure there is just one with the right fixed IP of the license server

That’s it! I hope your Trados is starting faster now!

I wanted to setup a new SDL Multiterm 2009 Termbase to organize our Terminology. Since we have lots of stuff already in existing Excel spreadsheets, importing them would make sense. This is a post about how to do this.

First, to get a little order into the whole thing, I figured adding a Category setting to every Term would help later on.

In the picture above, you can see the Category. It’s built into Multiterm and is of the type Picklist. But that Picklist does not contain the categories that I wanted yet, so you have to add them manually.

Add a entry into the Category Picklist

First, you need to have a Termbase open. I used the predefined termbase template “Multilingual termbase”.

Extending the Category itself is actually pretty simple:

1. Go to the  Catalog of your Termbase
2. Right-click on Definition and then Edit
3. Go through the Wizard until Step 4
4. Select Category and then Properties below
5. Now you can add new Entries (see in the pictures below)

Get the Excel ready

Now that we prepared our Termbase, we can get the Excel ready. Besides the two obvious columns with the terms, we need 2 more  columns with the Category. The title needs to be exactly the same as in Multiterm. In this case “Category”. The same is true for the entries, I’ve added an entry “amount” to the termbase, which is exactly the same as in the Excel spreadsheet. Upper and Lowercase matters too. Otherwise there will be no match.

Make sure the titles are on the first line, otherwise Trados will not recognize them.

Now we have to start SDL MultiTerm Convert 2009. You cannot import an Excel directly into MultiTerm unfortunately.

The Excel import wizard is pretty straight forward. There are only two points that need a little attention. On Step 5 make sure that you set the 2 Term columns to be Index fields with the right language and the Category column to be a Descriptive field of type Picklist. Don’t worry if you only see the Category column once.

In the next step we have to add the two Category fields to the structure, as you can see in the picture below, I’ve added Category #1 to the Term below CH-DE and Category #2 to EN-US.

This all we have to do in MultiTerm Convert. Finish the wizard and go back to the SDL MultiTerm 2009 main application.

Import into MultiTerm

Go to the Catalog of your termbase, click on Import and then I would use the “default import” definition. Right-click and choose Process. You should have an *.mtf.xml file from the Excel converting process. Choose that and just follow the Wizard.

That’s about it.

Please post comments below if you run into issues.