Information about becoming a localization engineer

Hello all,

I am working as a technical writer (8+ years) and taking a Master in Technical Communication in the evening. One of my favourite courses is GUI Localization, mostly with Passolo.

I would not want to work in GUI localization, but I am collecting information about what it takes to become a localization engineer.

If there are localization engineers (LEs) on this forum, can you take the time to answer questions like:

- What are some common tasks that you do in your work?
- What is the preferred background for a LE?
- What programming languages do you use?
- What tools and specifications do you need to know?
- Can you sketch your career until now?
- Do you work as a freelance or as an employee?

Thank you for any information you might want to share.

Best regards,

Diego Schiavon

Parents
  • This is the legendary article about Localization Engineers written by Bert Esselink long time ago: http://www.fti.uab.es/tradumatica/revista/articles/besselink/besselink.pdf
    And at that time it was sooo true...

    These days it really depends on the employer/client - I've seen way too many "loc engineers" being in reality just a dumb manual clickmonkeys taken directly from street, without proper skills, just performing some stupid copy&paste-like tasks...
    And the employer's attitude was like "why would you spend your valuable time putting together some automation when we can let these cheapo manuelos do it manually for a fraction of your salary?!"
    Go figure...

    But on a more positive side...

    Really skilled LocEngineer can be asked to do basically anything... anything what it takes to make something localizable.
    I know this is perhaps not what you wanted to hear, but it's true...

    Therefore the preferred background is definitely extremely good knowledge of basically anything concerning IT - SW, HW, file formats, communication protocols, etc. Any piece of knowledge can make you better than the others, can make you find easier, more effective, faster, or even actually CORRECT(!) solution for a problem.

    Programming language again depends on the environment you would be working in/for.
    For example, I grew up in the times of good old DOS batch scripting... and that, together with a knowledge of wide variety of additional tools (very often coming from Unix world and compiled for Windows) makes me, well, quite good in that area, I dare to say...
    Although I did some experiments with Turbo Pascal back in late 80's I admit that only very recently I digged a bit deeper into programming(?) and started combining my batch scripts with Windows Automation via Windows Scripting Host (namely JScript, since I hate VBScript, simply because "everybody" uses VBScript, so I don't want to), also known as ActiveX. Creating a batch script which is able to automate file handling and additionally process the file automatically in MS Office via Office Automation is very cool thing and can do a magic!

    Tools and specifications? Again - the more the better!
    Using the right tools for specific tasks is a key... so knowing which tool is good/best for a specific task is definitely a competitive advantage.
    And knowing various specifications like HTML, XML, XLIFF, characters encodings, and many more only add to to this advantage... so that then you can recognize when someone is asking you to do a stupid or impossible thing and stop people thinking/going into this apparently incorrect direction and direct them the right way...

    For my career you can check my LinkedIn profile... though you won't find too many details there, because first, it's impossible to describe every little thing I know or did, and second, nobody would read it anyway ;-)

    I worked as both employee and freelancer... though the freelancing was more like an employment anyway - one company gave so much work that I had hardly time for anything else.
    Which is better again really depends on your particular conditions... but these jobs usually require quick (read: immediate) turnarounds, so being a freelancer is probably not a particular advantage from the working time and work/life balance perspective...
    For example, when I woke up in the morning in Europe, the Asian guys were already working a few hours and managed to cause enough issues and screwups which I could start fixing it right away at 7 AM... then the European guys started causing their issues which I had to fix... and in the evening the Americans took over... So, more often than I liked I hardly had a time to take a sh*t... because someone would start causing new issues in the meantime... ;-)

    So, yeah... are you ready for that?! :)

  • Hi Evzen,

    Thanks a lot for the reply, it reads almost like a reference work on the subject!

    I suppose that in the beginning I would be a "dumb manual clickmonkey taken directly from street, without proper skills, just performing some stupid copy&paste-like tasks". But I feel at home with XML specifications,
    can do some XSL (XML to XSL:FO), some basic regular expressions, I know the basics of languages like Python, JS, Java, PHP.

    >So, yeah... are you ready for that?! :)

    I do not know. What you wrote is not completely discouraging, I think I will continue collecting information. And then, I'll see.

    How about Passolo or Catalyst? Do you get to use them often in your work?

    Regards,

    Diego

  • But I feel at home with XML specifications,
    can do some XSL (XML to XSL:FO), some basic regular expressions, I know the basics of languages like Python, JS, Java, PHP.

    See, I personally am basically hopeless with XSL... simply because I never had a need for it, since everything I needed I could do using different tools like XML Starlet, or lately using a more-or-less simple JScript which used MSXML ActiveX component.

    Python... I personally hate Python... because "everyone uses it", but they do it mainly because they don't know anything else, not because it has some particular advantages for them... because it's not part of Windows and needs to be installed, which is a no-go for many potential users of my scripts... and also because the concept of indentation being a part of syntax is IMO totally stupid (it's me who defines how my scripts will be pretty-printed and readable, not someone who thought it's a cool thing to define loops by indentation!!!... it's purely MY decision whether to indent or not and by how many spaces, not anyone else's!)

    How about Passolo or Catalyst? Do you get to use them often in your work?

    It depends :)
    There were times back in the early 00's when I used Passolo daily (and even worked very closely with Achim Herrmann from Pass Engineering (now SDL) on testing the then-brand-new betaversion of Passolo 4.0 and the .NET parser...

    And I also used Alchemy Catalyst 3 and then 4 at that times... and then only like 15 years later Catalyst 11 and 12 occasionally...

    But the tool I used most has actually nothing to do with localization itself, but it's something I cannot imagine my career without - the absolutely FANTASTIC and versatile FAR Manager.
    This thing just confirms that basically ANY computer tool made by Russians or Ukrainians is LOADED with extremely useful features, but extremely lightweight at the same time (anyone remembers Volkov Commander? that thingie was less than 64 kB in size!!!).

    And if FAR Manager, then of course with conjunction with ConEmu... another extremely useful tool not directly connected with localization...

    Total Commander?! Uffff, NO, thanks...
    No one who is serious about scripting (i.e. command line), should use a GUI file manager! That would be just a pure nonsense.

  • Dear Evzen

    Thank you for the list of applications. I will keep them in mind.

    Best regards,

    Diego

Reply Children
No Data