In the finale of our first series about E-Learning focusing mainly on language engineering, Word is our protagonist, the arch adversary to xml-based localization. Microsoft has been taking steps towards reinventing Word as a mature document processing tool, but its legacy still bogs it down and prevents it from being a full-fledged content management solution. After 30 years, it is still green around the gills. Mentioning Word in the same paragraph with the concept of content management might sound off to you who are familiar with Word’s capabilities, design and purpose; however, it is still in widespread use for creating localization-sensitive material and documentation due to its accessibility and soft learning curve.
In our previous post, we floated the idea of how multilingual adaptation of a certain type of E-Learning content can be managed. We’ve chosen a poster child for meticulousness; however, more straightforward materials may not need such an approach. But let’s push forward with investigating a complex case, and look into the technical localization of MS Office content.
When we came up with the idea of starting a blog for localization professionals and everyone else interested, with an intent of ignoring the marketing and purely business-related aspects, the array of relevant topics still appeared to be overwhelming. With all the pruning and grafting, we still feel like Winnie-the-Pooh, with a hand in every honeypot. If you don’t have a knack for the overly technical, don’t worry, we are not married to our gadgetry. You will find plenty of content on more strategic and philosophical concepts.