Welcome back to the series on image localization. As I said in the last post, image localization tends to sap more time and money than any other single piece of a job. If you can master a few principles, then you’ll save exponentially when it comes time to localize. The best part is that these few principles are incredibly simple.
Today I want to address white space. All too often we forget to account for it. Did you know that it’s not uncommon for target language text to expand up to 30% from the English? 30%! I have personally witnessed the unfortunate expansion of one tiny word on one tiny button to 300%. That’s an outlier, and perhaps statistically irrelevant, but it makes the point. We need to expect text expansion, and to account for it we need to include white space.
Consider the example in the pictures of “Try Again” buttons to the right. In English, this is a very nice button; the text fills the button nicely, and it is consistent with the style of the course it came from. Now consider the two Spanish examples, “Vuelve a intentarlo.” Note that our only options include breaking onto two lines and dramatically reducing the font size. The French “Recommence” also requires a font size reduction despite increasing the button size.
As part of series on image localization, I’ll be sharing information about common internationalization and localization gotchas. Images consistently cost my clients more in time and money than any other single component of their localization project. Some planning and work up front can save a good deal at the localization stage. In this post, I’ll address one of many considerations: static v editable images.
With the recent news that Adobe will be deprecating both their Mobile Flash and Flex development, this leaves application and content developers in a period of uncertainty and, most likely, having to duplicate work for the foreseeable future.
We think that most developers will move towards a dual-pronged effort for content creation: Flash will remain in the dominant position on the desktop for the short- to mid-term future, but mobile device constraints means that more and more work will migrate towards HTML5-based solutions.
Content is king. It’s still true, and if you want people to be able to witness its majesty you need to use the right technology to support each character. Character encoding tells the browser (or whatever GUI application the content comes through) how to properly interpret the characters so that they render as expected. You’ve undoubtedly seen examples of when this has gone wrong. You will have seen either empty boxes or black diamonds or capitalized, strangely accented letters instead of legible text strings.
Charles J. Beech, CEO and Chairman of the Board of Directors of Trivantis, announced today the acquisition of Flypaper Studio, Inc. Trivantis is perhaps best known for its rapid e-learning development tool Lectora. While Lectora and Flypaper are not dissimilar products, it’s unlikely that the acquisition was simply a matter of eliminating competition. It is more likely that the two companies have teamed up to help one another climb to higher reaches. Flypaper has nowhere near the presence and reputation that Trivantis has. Trivantis however seems to have stagnated some in their technology, and Flypaper has a lot of promise and product already on offer.
We had a great time at Learning Solutions Conference 2011 last week. We met a lot of great people at our exhibit, in our Master Class (Use Familiar Tools for Global Learning) and milling about. A special congratulations to our prize giveaway winners!
There are a LOT of rapid elearning platforms out there. Many of them are based on MS PowerPoint. My personal development preferences do not include PPT, but that’s irrelevant. There are clearly enough course designers out there who use PowerPoint to justify myriad rapid dev tools to be built around it. Some producers of such tools include small but excellent companies like eLearning Brothers as well as some big players like Adobe.
Ever wonder which browser is most used in the world? Most of us can probably guess that Internet Explorer dominates. Well, most of us would be right then. However, Google Chrome is making a significant impact on IE market share. You can see in the graph below (from http://gs.statcounter.com/) that while Firefox use has pretty much remained stable over the past year, IE has been declining as Chrome grows more popular. In the past year, IE lost 8.78% of global market share while Chrome picked up 9.4%, which means it’s presence nearly tripled in 12 months. Meanwhile, Firefox use declined by about 1%. StatCounter Also tracks things like browser versions, platforms and mobile devices…even some social media. They drill down to the continent and country level as well, which is extremely helpful when developing courses for specific geographic markets.It will be interesting to watch the trends to see how we tought to change
standards and methods.