According to wikipedia there are some 9.6 to 12 million people speaking Haitian Creole worldwide.  I had no idea it was such a widely spoken language until I was asked a question this week about why the Google Translate machine translation provider in Studio returned French translations when the project was en(US) – fr(HT) (French-Haiti).

In fact I had no idea that French-Haiti was most likely intended to be the language that should be used in Studio for Haitian Creole as this isn’t a language I come across very often.

But before I can ask a developer to fix this problem I have to be able to understand it myself, so the first thing I wanted to know was whether French-Haiti was the same as Haitian Creole or not.  And for anyone interested, as I was, to read more on this I found these three interesting links below explaining how the language came around and it does have a very interesting history:

The next thing I did was see if it was really so different to French… using a few basic sentences.  I used Google Translate to check this since the request was to make Googles Haitian Creole available when fr(HT) is the target language in a Studio Project.  Based on this example alone it certainly looks like a different language and not just a few words here and there as we have between English US and English UK:

I guess Google would not have provided it if 12 million Haitians were wrong!  I can’t judge whether the translation is good or not, but that doesn’t matter as much as making sure that Haitian Creole is returned when you use fr(HT) in your project.  Perhaps it’s also wrong for the language to be called French-Haiti in the first place and not Haitian Creole?  Maybe we should have ht(HT), ht(BS), ht(CA) etc.  I don’t know, and more to the point I can’t do anything about that either as Studio uses the Windows Language Code Identifiers (LCID) which are all fully qualified with a country code and a language code.  There is no Haiti on its own, only fr(HT).  But based on Google and these basic sentences it certainly looks as though it could be a separate language altogether.

So the task was how to resolve the problem of the machine translation results being French since Studio does not have Haitian Creole available to it because of the LCIDs.   I turned to the SDL AppStore team, and Andrea-Melinda Ghişa in particular as she had done some work in bringing Google NMT and Microsoft NMT to the MT Enhanced plugin on the SDL AppStore.  In the space of an hour or so Andrea had the answer!  After a little research she found this site, Google Web Interface and Search Language Codes, which shows that Google is not using the fully qualified LCIDs, only a web interface code which in this case is ht.  When Studio used fr(HT) as the target language the code being sent to Google was fr which makes sense as there are 47 varieties of French in Studio where most are very similar to each other and Google certainly doesn’t have 47 corresponding varieties to apply machine translation to.  But fr(HT) is clearly an exception so Andrea changed the code in the MT Enhanced plugin so that when Studio presented fr(HT) the plugin would send ht to Google:

As simple as that, and the result really shows the benefit of having the API approach for these kinds of things because it means anyone who knows how to develop can implement a solution in their own time.  There’s no need to submit a request to the product management team for SDL Trados Studio and then work through the request lifecycle based on its position in the overall priority list and then all the process and controls that take place after that.  You can implement a solution right now!  Under your own control without the need to engage the development team for the core product at all.  This is a very powerful capability offered by the Studio platform… of course you do need to be, or have access to, an Andrea!!

In Studio, if I use the out of the box Google Translate alongside the updated MT Enhanced plugin (now v1.7) for my fr(HT) project you can see the difference:

Longer term the community API team would like to implement a mapping feature to this plugin so if Google adds more languages in the future, which is quite likely, then it will be simple for a user to change the mapping table in a simple UI themselves.  Now that would be cool!  But all good things have to wait their turn even in the appstore team.  But as the code is opensource, if you are a developer and would like to implement this idea and share it with others then please go ahead and do it… the sourcecode is here!  In fact you can find more information about the SDL OpenSource Community here:

Looking forward to any contributions!!

I’ve always had a secret desire to be able to program computers… the problem is it’s not something you can do just like that!  I can recall starting off with a Commodore PET 2001 some time in the late 70’s and I can remember how enjoyable it was to be able to create simple scripts that could react to whatever you pressed on the keyboard.  I should have realised back then it would have been smart to focus on technology, but instead I took a bit of a detour in my career and computers didn’t feature at all until around 1987 when I was introduced to the HP41c from Hewlett Packard.  This had very basic programming functions, a magnetic card reader and a thermal printer and I loved it!  In fact I loved the way HP calculators worked so much I had an 11c for years until I dropped it trying to align a laser while being dangled headfirst into a catchpit on a construction site!  And we think the Studio alignment process is tricky 😉

Read More

SDL Trados Studio is up to Studio 2017 which is the fifth major version since Studio 2009 was first released some eight years ago now.  During these eight years I think it’s fair to say we have seen less and less requirement for the old Trados features, yet despite that we do see some interesting tools making an appearance in the SDL AppStore that mirror some of the old functionality.  In fact some of these apps are quite recent and seem to have been driven by requests from users who miss some of the things you could do in Trados but still cannot do in the out of the box Studio solution.  So I thought it might be fun to take a look at some of these apps and if you are one of those translators who remembers all the good things Trados could do… and can I say forgotten the things it could not… then perhaps you’ll find these apps useful!

Read More

A nice picture of a cutie cat… although I’m really looking for a cutie linguist and didn’t think it would be appropriate to share my vision for that!  More seriously the truth isn’t as risqué… I’m really after Qt Linguist.  Now maybe you come across this more often than I do so the solutions for dealing with files from the Qt product, often shared as *.TS files, may simply role off your tongue.  I think the first time I saw them I just looked at the format with a text editor, saw they looked pretty simple and created a custom filetype to deal with them in Studio 2009.  Since that date I’ve only been asked a handful of times so I don’t think about this a lot… in fact the cutie cat would get more attention!  But in the last few weeks I’ve been asked four times by different people and I’ve seen a question on proZ so I thought it may be worth looking a little deeper.

Read More

There’s been a few ups and downs getting SDL Analyse off the ground, but it’s finally there and it’s worth it!  If you have no idea what I’m referring to then perhaps review this article first for a little history.  This app was actually released as the 200th app on the SDL AppStore in February this year, but in addition to the applause it received for its functionality there has been less positive aspects for some users that needed to be addressed.

But first, what does it do?  Quite simply it allows you to get an analysis of your files without even having to start Studio, or without having to create a Project in Studio.  If you’re a regular reader of this blog you may recall I wrote an article in 2014, and in 2011 before that, on how to do an analysis in Studio by using a dummy project.  In all that time there has been only one app on the appstore that supports the analysis of files without having to use Studio and this is goAnalyze from Kaleidoscope.  In fact goAnalyze can do a lot more than SDL Analyse but there is one significant difference between these apps that makes this one pretty interesting… you don’t require the Professional version of Studio to use it.  But it’s also this difference that has been the cause of the ups and downs for some users since SDL Analyse was released.  In order to resolve the problem of needing to use the Project Automation API, which needs the Professional version of Studio, the app needed to use a windows service that was hooked into Studio.  For the technically minded we had a few things to resolve:

Read More

… in with the new!

Although I’m not part of the core support team anymore the knowledgebase has always been something that held a particular interest for me.  When I joined SDL in 2006 we had two knowledgebase systems, each integrated into the support systems that were being used at the time.  These were Salesforce and RightNow Technologies.  The first big change I was involved in with regard to systems was moving the support teams onto one ticketing system and one knowledgebase.  We wanted Salesforce as the ticketing system as it gave good visibility into the tickets being raised to everyone at SDL because Salesforce was being used as the CRM tool of choice.  But in those days the knowledgebase component wasn’t great, so we adopted a new system.  The system we chose was Talisma.

Read More

001aWhat a horrible name… lurkers!  It carries all kinds of negative connotations from science fiction monsters to the stuff of nightmares where we think of spying and being followed by something or someone we don’t like.  Of course I’m not using this term in these contexts so I better explain.  I’m talking about communities and user participation, or more specifically about users who read and observe but rarely contribute to the conversations at all.

Community managers often think about user participation based on a 90:9:1 rule where 90% of users are referred to as lurkers who read all the activity but don’t contribute themselves, 9% contribute from time to time and 1% are pretty active and probably account for most of the contributions.  I guess I can see why this negatively charged name is used, but in addition to being a horrible name it doesn’t really do justice to how important this group of community users are.

Read More

%d bloggers like this: