Is XML easier to Translate?

I've always been a proponent of XML content. I think it's faster to get things translated, and with a CMS it alleviates unnecessary emails and creates a translation work flow. However, there are a couple of fundamental problems in XML construction that you should address before setting up a translation work flow. One common problem is using CDATA sections.

Problem:
It's a very bad idea to use CDATA sections to separate
database content from database structure if you want to translate this content. CDATA sections make it impossible for third party tools to parse/separate the text and tags/elements within the CDATA sections. CDATA sections are designed this way because they are explicitly used to hold text and tags to prevent parsing. This makes it almost impossible for third party tools like Translation Memory Systems (TRADOS/SDLX) to parse the text and tags within the CDATA sections. TRADOS/SDLX exposes the CDATA content for translation without further parsing. Therefore, you get all the tags as "real text".

Solution:
You should considers using name spaces instead by placing the database structure, XML into it's own name space and have the database content in a second name space (or have it without a name space). SDL TRADOS Snippet might be a more or less usable workaround here, but it limits the tags you can "hide", and text within CDATA sections that are not closed will be hidden as well.

I hope this helps those of you out there who use XML as a content editor, or are planning to send XML files for translation. It's always a good idea to communicate with you translation vendor, or potential translation vendor when they are bidding on your project. Work together on finding ways to solve potential structural problems within the XML file. You certainly don't want unnecessary content translated, and this will allow you to preempt any exporting problems you might face with deleted or missing tags when you want to publish your translated content.

ICD's You Tube Channel

ICD has set up a You Tube channel. We plan on having a few interviews, and maybe some demos of the software we use. Hopefully, this is will give you a deeper insight into the world of translation. Right now, we have 2 videos. The latest is an interview with Ann Zdunczyk from A2Z Publishing.  Ann helps out with DTP and she attended the STC conference with us.

Interview with Catherine Potter

This is an interview with Catherine Potter. She gives her insights and perspective on this year's STC conference.

Photos from the 56th Annual STC Conference

As promised, here are a few pictures from the 56th Annual STC Conference that was held in Atlanta, GA. Catherine, Ann, and I had a great time meeting people, and seeing the sights in Atlanta. We met some interesting exhibitors including the creators of Guimags. A bright idea that allows designers to save time and money by creating their layouts on a board with customized magnets. It also eases the UI testing process with a more interactive experience. Check them out. Overall, the conference was geared more towards writing content in the new age of blog, wikis, and twitter. There was less of a focus on translation and localization even though the majority of the exhibitors were translation companies.

Mobile Blogging Failed, STC Conference Day 2

Well, the mobile blogging idea failed. I didn't have the patience to key in every single word with my not smartphone phone. I should get an Iphone if I want to seriously mobile blog. Yesterday, Catherine and I arrived in Atlanta, and we had to set up our booth. The new booth looks awesome, pictures to come. Now, I'm sitting in a session about blogging and using wikis and blogging about it. Hilarious. Anyway, the blogging aspect wasn't anything new, but the info on wiki's is pretty neat. The speaker is explaining the whole wiki process: setting it up, expanding it, and updating. ICD is considering creating a wiki to update our clients on what's going on with their projects. Twitter would work, but no one seems to think it's very professional. "Wiki Wars" the speaker just said that. Apparently, it happens. People battle it out to see what's actually "true" content. I know, I went off on a tangent. Ok, back to wikis.

The speaker is a writer for Floss manuals, and they use the wiki they created to run book sprints. Book Sprints are a collaborative writing effort to create a book or manual in a short period of time. One option is to use the wiki as a collaborative writing community like a writers block, but on an online community where things can be debated, edited and changed all at the same time. Floss Manuals was able to create a manual for Firefox users in 5 days, and it was a collaborative effort with Mozilla developers. That's pretty quick. There's so much out there in the online community, that people are starting to make business connections and promote their services through the internet. In order to succeed though, you have to be able to utilize the internet effectively, and manage and update your blogs, and wikis so people continue to follow your posts and stay connected.

Esprit d'ICD Spring 2009

Hello All,

ICD's Newsletter Esprit d'ICD has received a face lift for 2009. Gone are "Catherine's Column", "Employee Profile", and "Puzzler" (Ipod's are to valuable to give away during hard economic times). We have more content now and the articles are more concise. Now, you get more stuff to read and more information. We have tried to add article that are a little more widespread and encompass different issues and industries. Some highlights include: "New strides in machine interpretation", "Instant sharing of views and news through Twitter", "The first GPS without a screen", and "What's in a car name?" You can read the newsletter here

We have tried to include what's relevant in today's world, and what's going on in the translation industry. I hope you enjoy reading this issue. If you want to subscribe to our mailing list and receive a copy, email: translate@icdtranslation.com

I'll be in Alanta this coming week for the STC conference, and I'm going to try mobile blogging. Hopefully, I'll be able to inform you about the goings on at the STC, and stuff that might happen with the ICD team as we take on Atlanta.

How Language Crashed a Plane?

I was watching CNN this morning and they were talking about a new book (I don't remember the title), but it was about language and education and how cultural barriers are being broken. As they were talking, one of the highlights appeared on the bottom of the screen: "How Language Crashed a Plane?" That immediately caught my attention, and I listened intensely to the reporting. Apparently, there was a plane crash involving a Korean Airlines flight a few years ago (I tried searching for the story, but it seems Korean Air has a checkered history of airplane crashes and problems, and there were countless crashes. They've improved since the late 90's though. I was on a Korean Airlines flight last October, and it was actually really nice, service was great, all the booze you can drink etc.) Anyway, the reason this particular plane crashed was due to a disagreement between the pilot and co-pilot on the way to solve a problem with landing the plane, and to make matters worse there was a disagreement with ground control in Korea. This all stemmed from their communications in Korean because Korean is a hierarchical language where honorifics and speech level play and important part in grammar and verbiage used between conversations of people with different status. By status I mean either ones job position, age, and education level.

Allegedly, there was verbiage and tone that was incorrectly used between the co-pilot (lower status), and the pilot (higher status) as they disputed ideas to solve the problem they were encountering. This created an argument, and when the ground control officer got involved it elevated the communication breakdown that had occurred between the pilot and co-pilot. The language hierarchical problem that occurred was a costly life-ending event for Korean Airlines and since that incident, they have enforced the use of English for all instructions and commands on their airplanes. This lesson serves as an important factor when considering the use of language. When you get something translated, quality matters. You need to consider cultural aspect and important tone and verb usage. It's important to understand the culture, and experienced high quality translators are able to understand the culture, and translate appropriately.