CSV, or files with “comma separated values”, is a simple format that everyone should be able to handle. Certainly you’d think so except nothing is ever that straightforward and if you’ve ever spent time trying to work with these files and having to deal with all the problems inherent to this format then you’ll know exactly what I’m talking about. In our industry, localization, the number of problems can even increase because we also have to deal with converting the content from one language to another. I also wondered if there is a standard for CSV and the closest things to one is more of a recommendation, called RFC 4180. It doesn’t seem to have been updated since 2005 and doesn’t take account of many of the problems that can be caused by not managing these files carefully.
So what sort of things are we talking about? Here’s a few…
Whilst I would definitely not claim to be an expert, writing this blog has allowed me to learn a reasonable amount about XML over the years. Most of the articles I’ve written have been about explaining how to manage the many amazing features in the filetypes that are supported by Trados Studio… and of course how to deal with the many changes over the years as the filetypes have become more and more sophisticated catering for the demands of our customers and the changes in the technologies applied to XML in general. The result of these changes has led to some… let’s say… less than user friendly interfaces and features and you’d certainly be forgiven if you thought things were becoming a little chaotic!
Localization engineers are the miracle workers behind the scenes of localization workflows, and without them many of the projects we see couldn’t happen. The skillsets they possess go far beyond the sort of things that most translators know how to do, and often require the ability to code. I’ve already 
As I’m getting lost in my own thoughts around just what to talk about next with regard to AI technologies and in particular ChatGPT… and as I’m pondering about the effect this is going to have on our industry I recalled a couple of questions around the use of XPath in the community. One of these questions was yesterday and it related to how to use XPath to extract one of the languages in a TMX file using the XML filetype in Trados Studio. Not a particularly tricky thing to do, and I imagined the user was just editing the content or maybe changing the language pair by translating one of the languages into something else, or something like that. But what struck me was 
Continuing the theme of how to make use of AI technologies to help with the more technical nature of localization I thought I could revisit 
I was compelled to make a return to a previous theme around Marvel Comics because it’s the only way I can do justice to the amazing work the RWS AppStore team carry out on a daily basis. There are some things you just can’t wait to get up in the morning for, and for me, one of these things is being able to work with this team on a daily basis. The first meeting of every day for me is with this team and what a fantastic way to start the day it is! I started this article by mentioning Marvel, but as you’ll see, the hero of this story is probably a Honey Badger!
I wrote 
When we released the new Trados 2021 last week I fully intended to make my first article, after the 
After attending the