globalization

June 03, 2009

Economy Impacts Content Localization Decisions

Blogger: Craig Roth

The Global Watchtower reported on companies that had localized their websites changing their minds:

Recently, we’ve noticed two reports of companies claiming that “it just isn’t worth it” to have websites in other languages. Last week, the New York Times profiled several web-based businesses that elected to decrease or eliminate their web presence in some parts of the world, in spite of popularity in the local markets. This weekend, the Wall Street Journal broke the news that Home Depot is shutting down its Spanish-language site. This begs the question, “Is it ever a bad idea to localize?”

I have heard such questions from clients as well.  One client asked yesterday in which countries they can get away with just using English content inside the company for companywide policy information.  I pointed the client to the Ethnologue, a great source of information on the 7,299 languages they cover and where they are spoken.

However, Global Watchtower doesn't state the reason that I suspect for this abandonment of extra localized websites: the economic downturn.  It hints at cases where "the business case simply does not justify localization", but let's face it - there's one big reason that business cases have changed recently and that's the economy. As I wrote back in April ("The Hemline Index Redux"), projects that used to get approved with only "soft" benefits are now requiring "hard" proof of benefit. If your website isn't e-commerce, the cost/benefit equation for localizing is difficult to calculate.  Well, actually the cost is easy to calculate.  But the benefit of having, for example, a customer service website translated and localized for a country where 70% of your customers speak English at a moderate level of fluency is very difficult to determine.

If I'm right, we'll continue to see more organizations trimmed back on the number of localized versions of their websites until the economy improves, then see a reversal of interest in the languages, customs, and local differences of target audiences in other countries.

March 05, 2009

Software Due Diligence: What If All The Growth Comes from Emerging Markets?

Blogger: Craig Roth

In a conversation with a major software vendor recently, a product manager got (very) touchy when I questioned a statement that the growth opportunity outside the G7 (top 7 industrialized nations) was much greater than inside.  I hadn't looked at these figures since the recession reared its ugly head, so I checked and it turns out I was indeed wrong to question it. 

Overall GDP growth figures (I follow the IMF data) show that emerging countries are expected to grow faster than then G7, although the difference has shrunken from the previous eight years when emerging economies were strongly outpacing developed ones.  Reduction in commodity prices, tightening of credit for growth, limits on growth due to carbon controls, and increasing protectionism are having a disproportionate depressing effect on emerging markets, shrinking the gap with G7 growth.  IT spending figures show flat to slightly negative growth in developed countries compared to single-digit to 10% increases in emerging ones (see "2009 IT Spending").

Still, I could tell I hit a nerve.  It became obvious that a major part of the growth strategy for this large software unit was to count on sales in emerging markets to satisfy a substantial portion of 2009 growth.  Indeed, examples of account wins were much more globetrotting than in recent years.  One product slide listed accounts in China, India, Sri Lanka, and Brazil.  Another product slide listed wins in China, India, Singapore, and Taiwan.  It is not unusual for a large, worldwide software company to have so many accounts in emerging markets.  And the BRIC countries have been reliably strong in this decade.  But I've been an industry analyst for ten years and seen hundreds of these presentations and have never seen so many emerging market reference accounts (roughly half of those listed) from a global software firm.  I think emerging market accounts existed before, but didn't make the cut on the logo slide until the recent dearth of G2000 (the 2,000 largest global companies) wins let them surface.

I think shifting to or enhancing sales focus on emerging economies is a good growth strategy for a large software company in 2009.  If I'm an investor I would be comforted by the efforts of this company to quickly adapt to the economic environment and use global channels to seek penetration in unsaturated markets.  But I'm not a financial analyst - I'm an industry analyst representing the interests of my end user clients who happen to be in large G2000 organizations in developed countries.  For one of my clients, how should I interpret growth figures I receive from a vendor as part of due diligence that show strong growth even in this recessionary period?

It is good practice to evaluate product and vendor growth during due diligence phases of software acquisition and during upgrade, migration, and sunset decisions.  But evaluators now need to dig deeper into these growth figures during due diligence since some of the underlying assumptions have changed if a substantial part of this growth comes form geographic regions different than those of the evaluator.  The evaluator should ask how much of that growth came from "my geographical region" and "organizations similar to mine".

Why does that matter?  The vendor will surely argue it doesn't matter since, as a measure of vendor viability (or product viability), growth is growth.  This is true - as far as viability, it doesn't matter much where the growth is from.  If I'm in France and most of the new revenue is coming from China, that's still good.  I can be reasonably assured the product isn't going to be put on life support or have the plug pulled entirely since it's making money.

But as a proxy for best practices or what my peers are doing, emerging market growth doesn't suffice.  If I use what my peers do I'm assured that, for technology that doesn't differentiate my services, my competition doesn't have a productivity edge.  And we're likely to be able to find employees, contractors, and ASPs from a shared pool of knowledgeable candidates.  But if the growth is coming from a vastly different market (like Sri Lanka is to a U.S. conglomerate), those assumptions don't apply.

Growth is also seen as an assurance that the product is likely to keep pace with the newest features.  The assumption is that a vendor is not likely to let a growing product stagnate in light of trends towards web services, rich web-based interfaces, embedded presence, social computing, SaaS delivery models, or contextual collaboration.  But if the growth comes from emerging markets, that assumption may not longer be true.  Companies in emerging markets (often partially if not wholly controlled by the government) may be at very different spots on the technology maturity curve. The weighting for the newest technology on wish lists for the next version may start skewing towards other features.

In short, due diligence for software purchases will now require you to be even more diligent.

February 12, 2009

2009 IT Spending

Blogger: Craig Roth

We are currently doing research into how IT organizations are approaching communication, collaboration, and content management needs in a recessionary environment.  Since many of the technologies in this area don't seem to be needed to keep the lights on or invoice customers, they have the potential to bear the brunt of the axe when cost cutting occurs. 

To start my research I wanted to find out what the forecasts were for IT spending this year.  Burton Group doesn't do forecasting, so I used a survey of surveys approach to come to an unscientific consensus of spending (over- and under-weighting forecasts based on my read of their methodology and applicability to our target of large enterprises).  The results are shown below.

Consensus IT spending 2009

I think it's fair to say there is a slight increase in IT spending expected for large enterprises, but this will be much lower than in previous years (perhaps lower than any year since the IT revolution).  It's also fair to say that the increase will mostly be in developing economies, while the G7 is close to flat.

Some important comments are worth noting:

1. In some cases the difference in the forecasts is simply a difference in the underlying assumptions about the economy.  For example, Forrester said: "'Our forecast for 2009 rests on the assumptions that the economic recession in the US and other major economies will start to end in the second half of 2009,' explained Andrew Bartels, a vice president and the principal analyst at Forrester."

2. Analysts and CIOs may not be thinking of the same definition of "IT spending". To analysts, IT spending generally equals "sales". For example, Goldman Sachs equates spending to hardware+software+services+networking. But to CIOs, they think in terms of IT budgets which include spending on internal employees, not just sales.  Most of these estimates are for spending "on" IT, not "by" IT, since they are targeted at IT vendors and service providers.  Some include consumer spending (The Economist and, from what I could discern of the wording, IDC).  Estimates may include telecom and networking.  The few estimates I could find that specified "budgets" (including internal employees) instead of "spending" forecasted flat (Computer Economics) or practically flat (+0.16% from Gartner) change over 2008.

3. Your results may differ.  There are strong differences by geography (emerging markets are predicted to do better than the U.S. and developed economies), locale (Michigan vs. total U.S. spending, Spain vs. Europe), and industry (government and healthcare are expected to lead the spending pack).

4. This year, forecasts must be fresh.  Usually the analysts publish estimates around September and that's it for the year.  But this year, like lemmings, all the forecasts followed each other off the cliff sometime around September as they revised their estimates downward.  For example, Gartner revised downward from 5.8% to 2.3% and Forrester revised from +6.1% to -3%.  In general, the consensus forecasts pre-Sept '08 were about +3% compared to those starting with the October revisions.

Sources for recent forecasts: Computer Economics, Economist Intelligence Unit, Forrester (and here), Gartner and here), Goldman Sachs (full survey requires registration), IDC (and here).

April 28, 2008

"Not as flat as it used to be": Globalization Hits a Roadblock?

Blogger: Craig Roth

I was having breakfast this morning before going to work to prepare for my telebriefing tomorrow on The Role of Enterprise Content Management in Content Globalization/Localization when I opened my Wall St. Journal (4/28/08 page A1; link) to read that nationalism may be thwarting globalization.  The article by Bob Davis points out that while globalization was supposed to be inevitable (hence the WSJ's reference to Thomas Friedman's famous globalization manifesto), nationalism and protectionism seem to be on the rise.

Trade talks are shelved.  Barriers to foreign investment are rising around the world. State-owned companies are expanding, particularly in oil and gas. Public support of immigration restriction is growing in countries from the U.S. to India.

So what do I say tomorrow about the need for IT organizations to get involved in content globalization and localization efforts?  I think I'm still on track in saying that there is a sharp increase in content globalization occurring and that IT can help.  It's possible that some expansion plans in industries that could be brought under state control (energy and foodstuffs in particular) could be put on hold.  But for other industries, the drivers of IT involvement in globalization efforts that I discuss in my telebriefing are still very relevant.  These include:

  • Containing or reducing costs: Whatever degree of globalization occurs, there will be a need to contain globalization costs
  • Clarification of central and local control through governance: If power shifts are occurring and barriers are rising between central and local branches, governance takes on increasing importance
  • Timing/responsiveness: The uncertainty of the globalization landscape places even more emphasis on an organizations ability to react quickly to changes
  • Safeguarding brand image: Increased nationalism means increased attention must be paid to local culture and customs, so proper translation and QA processes become more important for a deeper swath of content
  • Improving consistency: As with safeguarding brand image, inconsistent translations will have increased risk of harming the brand
  • Need to handle increased complexity: Potential increases in regulation will increase the need for complex workflow that can handle documents based upon content typing

I'm not a politician or economist, so I'm (way) out of my element in predicting what effecting nationalism, protectionism, and a global backlash may have on international relations.  The article isn't saying the slowdown is definite, but a possibility when certain threads in the news are connected.  But from an enterprise content management perspective I think the globalization storm is looking even more vicious than before.

February 20, 2008

Part 4: What IT Can and Should Do About Content Globalization

Blogger: Craig Roth

This is the final blog companion for my 4 part podcast series on “What IT needs to know about content globalization, localization, and translation”. I previously posted part 1, part 2, and part 3.

Audio URL: Download Content Globalization Part 4 (10 minutes)

  1. Open lines of communication with the business about globalization
    • Don’t wait. Take the initiative by setting up a presentation for interested business partners and marketing to find out what their globalization plans are and talk about how IT can help
  2. Determine your Content Globalization Maturity

    Content Globalization Maturity

  3. Look Beyond Paragraph Text When Planning Localization
    • Metadata around the content components
    • Graphics often have text embedded and pictures may need to be changed to match the locale
    • Audio in music or spoken mp3s or video
    • Data such as conversion of currency, English/metric measurements, date/time formats
    • Descriptions of processes such as support
    • Style sheets and graphical layout (including colors, whitespace)
  4. Build Globalization into the ECM Process
  5. Move Localization from the End of the Content Process to the Beginning
    • Make globalization a forethought, not an afterthought

I welcome your feedback! Please provide feedback on this podcast and blog series by clicking on “comments”

February 19, 2008

Part 3: Content Globalization: Do the Big Vendors Care?

Blogger: Craig Roth

This is the blog companion for part three of my 4 part podcast series on “What IT needs to know about content globalization, localization, and translation”. I previously posted part 1 and part 2.

Audio URL: Download Content Globalization Part 3 (17 minutes)

  • Vendor segmentation
    • Look beyond internationalization (e.g., can they support other languages) to include localization assistance such as support for translation memory, translation workflows, and integration with language service providers
    • Content Globalization Value Chain (Note: the podcast lists sample vendors in each space)

      Globalization value chain

      • Authoring: Content creation tools have a part to play in globalization, mostly through plug-ins that add localization assistance and XML-based authoring tools that create content in componentized form and allow a content designer to apply rules and structure to their content
      • Enterprise Content Management: Standard features in ECMs help with globalization, but ECMs specifically built to help with localization (such as by supporting XML content components or out-of-the-box integration to globalization management systems and language service providers) can help even more
      • Globalization Management Systems (aka Translation Management Systems): A GMS handles the translation process with features like project management, localization workflows, costing, and adapters between ECM and language service providers. Terminology management and translation memory tools are sometimes part of a GMS suite
      • Translation: Divides into human (the largest segment; provided by Language Service Providers) and machine translation
      • Assembly: Dynamic assembly such as portals can leverage personalization and the capability to dynamically determine which version of content to display
    • Some larger players (Microsoft, IBM) haven’t woken up to content globalization yet
    • One reason is that customers haven’t demanded they respond yet since the need is currently felt outside IT and the LSPs and GMSs have been addressing the problem
    • Innovation has been coming from smaller vendors, many of them European
    • The value chain will get tighter over time and acquisitions are likely, especially in the GMS space
  • Buyer segmentation
    • Some types of industries and roles are more affected by the increase in content globalization
      • International organizations that attempt to maintain a single global brand image (i.e., hospitality, transportation, travel, automotive, and pharmaceutical) tend to change content frequently and need consistency and timeliness in localization
      • Industries that write lots of technical or service manuals (i.e., medical devices, technical manufacturing, and discrete manufacturing) need to translate complex documents and are more likely to use and benefit from componentized content creation
    • Roles: Many people may never get involved in globalized content creation if they work only on low visibility, internal documents. But for other roles, content globalization is an issue
      • Professional, technical writer
      • Line of business content owner
      • Local website owner
      • Marketing communications
      • Web designer
      • Programmer

February 12, 2008

Part 2: Content Globalization 101 in Twenty Minutes

Blogger: Craig Roth

Here’s the blog companion for part two of my 4 part podcast series on “What IT needs to know about content globalization, localization, and translation”. If you missed part 1, you can find it here.

Audio URL: Download Globalization Part 2 (19 minutes, 6.6MB)

  • This part contains background information on globalization that can be handy for people coming up to speed on globalization or looking for rationale for the analysis, but can be skipped if not needed
  • Definitions
    • Content globalization (numeronym: g11n) is a strategy to convey information in the cultural, linguistic, and business context of target audiences.
    • Localization (L10n) is adapting content to a particular locale
    • Internationalization (i18n) is the work you do enable localization (prep work for localization)
    • Transliteration (t13n) is using characters from one language to represent another
  • Resources to create a statement of trends for a particular business
    • Internet World Stats to show the prevalence of the languages you want to translate into or the growth or overall percentage of users in a particular language
      • English still #1 with 365 million users, 184 million for #2 Chinese
      • Growth trends: between 2000 and 2007 for Arabic (+941%), Portuguese (+525%), and Chinese (+470%)
      • Internet usage outside of North America dwarfs usage within it: 20% north America, 37% Asia, 27% Europe
    • Ethnologue to show number of countries speaking a language or what weight a content-creating organization should place on localization issues given the makeup of a specific country being targeted
      • The Ethnologue can also show linguistic diversity in countries to demonstrate how heterogeneous a country is. It lists the probability that any two people in the country chosen at random will speak different native languages
  • Dialects
    • The Portuguese spoken in Brazil and Portugal are much different and can lead to misunderstandings or make a reader feel the author doesn’t truly understand them
    • Corporate English is a dialect
  • Code Internationalization
    • Wikipedia: “The current prevailing practice is for applications to place text in resource strings which are loaded during program execution as needed. These strings, stored in resource files, are relatively easy to translate. Programs are often built to reference resource libraries depending on the selected locale data.”
    • As with content globalization, localization concerns should be moved to the beginning of the planning process from the end and businesses need to treat globalization as a first-order imperative
    • Examples of system development guidelines
  • Standards
    • Darwin Information Typing Architecture (DITA)
      • Created for complex documents in multiple formats
      • Not specifically for globalization, but there’s a translation subcommittee
      • DITA enforces a strict structure on content which makes it easier to translate, but interferes with the writing process
      • Probably fine for technical manuals, but not artful content like ads or brochures
      • DITA requires customization before use
    • Internationalization Tag Set
      • Defines the metadata needed content globalization
      • Examples: tags to define the source language, parts that shouldn’t be translated, targeting for a right-to-left language, notes to pass to the translator
      • Still evolving
    • Translation Memory eXchange (TMX)
      • Translation memory is used to keep a record of how certain phrases have been translated in the past so those translations can be used again to save time, leverage the best translations, and ensure consistency
      • Owned by LISA – the Localization Industry Standards Association – which is trying to unify many standards for translation
    • Unicode
      • Unicode is a universal 16 bit code to represent characters in memory and on disc
      • Every language hasn’t been encoded, but most of those in commercial use are
      • Most major software is now Unicode compliant, although that doesn’t mean every language is automatically supported and there are different flavors of Unicode
  • The printed report also covers ISO 8601 Date Formats and XLIFF

          February 11, 2008

          Globalization Podcast Companion

          Blogger: Craig Roth

          I’ve posted up a 4 part podcast series on “What IT needs to know about content globalization, localization, and translation”. While the audio stands alone, I figured it would be nice to post up this companion blog entry. This way you can find the URLs for the websites I recommend in the podcast, you don’t have to take as many notes, and you have something to stare at while listening (PowerPoint has corrupted us!). It could also provide some basics for you if you don’t want to listen to the podcast.

          I thought about creating PowerPoint slides to follow along, but I think it’s better to just list the bullets in text here. This way the whole series prints on one handy page and you don’t have to download a big file just to get some simple text bullets.

          So, here it is. Your Cliff’s Notes for part one of my 4 part podcast series and report.

          Part 1: Repeatable content globalization: Ignore it at your peril

          Audio URL: Download Globalization Part 1

          • IT needs to get more involved in content globalization
            • Currently IT is often not involved since a marketing or product team just creates content (e.g., web site, technical manual), throws it over the wall to translators, and gets a pack of translated versions back
            • This process works, but content owners are going to be feeling a lot more pain soon if they don’t prepare for an increase in globalization needs
          • Decisions about content globalization are business decisions with large potential impacts on customers, employees, and brands. A poor content globalization strategy can hamstring those efforts
          • IMF data: growth for the G7 major advanced economies has been about 2-3% while various measures of new markets (such as newly industrialized Asian economies, emerging and developing countries, and central and eastern Europe) have grown at 5% or more
            • For statistics on growth in specific countries or regions, go to the IMF’s website (http://www.imf.org), click on “data and statistics”, and (if desired) “by country groups”
          • According to comScore “the U.S. share of the world's online population has fallen from 65 percent to less than 25 percent in the last 10 years"
            • comScore (www.comscore.com) tracks measurements about consumer behavior on their internet
          • Localization applies even to U.S.-centric organizations.
            • 2000 U.S. Census: 17% of households speak another language at home (8% speak English less than “very well”)
            • Some states have high proportions of non-English speakers: in California, 21.0% of respondents reported they speak English less than “very well”
            • Check U.S. census trends (www.census.gov)
          • When you make quantum leap in the number of locales supported, you need a subsequent increase in the level of sophistication with which content globalization needs to be addressed
          • Drivers:
            • Increased complexity
            • Poor governance
            • Timing and responsiveness
            • Safeguarding brand image
            • Containing or reducing costs
            • Consistency
          • These drivers have been around a long time. Why change now?
            • The pace of globalization is increasing rapidly, therefore ensnaring more and more organizations (see IMF, comScore, and census information above)
            • Improvements on the technological front
            • XML and related Standards, and Meta-data
              • XML is great for content globalization since it encourages dividing documents into content components, supports any linguistic encoding including right-to-left (RTL) languages, and enables creation of meta-data
            • Component-Oriented Content
              • Analogous to service-oriented architecture (SOA) in that it relies on the value of dividing up work into components that are independent, managed, and assembled into composite applications
              • Component-oriented content systems can handle content components that are decoupled from a specific document
              • Component-oriented content can help as there is an increase in
                • The number of localized variants the content will be translated into
                • The number of formats the content will be distributed in
                • How granular the translations need to be if it’s not the whole document or website at once
                • How frequently the content will change
              • See the CCS document “Content Reuse: DITA, XML, and Other Ways to Keep from Reinventing the Content”
          • Repeatable processes for content globalization are going to be essential for helping the business to meet globalization goals. You only ignore the processes and new technologies that can help at your peril!

          January 31, 2008

          Content Globalization and XML-based Content Creation: Goes Together Like Chicken and Rice

          Blogger: Craig Roth

          CMS Watch reported that

          Translation and Content Management vendor SDL has taken a minority stake in privately held Trisoft N.V., a Belgian-based vendor of InfoShare, a component content management system (CCM). There was no fanfare, and in fact no announcement; evidently because it wasn't a full acquisition, the two companies dispensed with any press release. However, I think it's a significant move. When it comes to translation information management, XML; and in this case DITA-based XML, can matter. SDL had previously acquired Tridion, a Web CMS that can be used for component content management, early last year.

          I think this is a good move by SDL, which has become quite a consolidator of globalization technology.  I haven't looked at InfoShare before, but buying into the XML-based content management market is prescient of SDL since component-oriented content is very useful for creating content that is going to be translated.

          Four factors are compounded to increase the value of component-oriented content:

          1. The number of localized variants that the content will be translated into

          2. The number of formats that the content will be distributed in

          3. The locality of the translation (e.g., needing to retranslate only one section of a document)

          4. The frequency with which the content will be changed (thus necessitating retranslation)

          When any of these four factors increase, component-oriented content creation starts looking better for any organization creating content that will be localized.  That means translation activities will be easier to track, take less time, make better use of translation memory, and be more consistent.

          Note: This is a cross-posting from the KnowledgeForward blog

          January 25, 2008

          Lotusphere 2008 - Innovation Lab

          Blogger: Craig Roth

          I'm back from Lotusphere and Orlando now and playing reggae to try to trick my brain into forgetting it's -1 degrees here in Chicago.  It's not working.  I posted a set of blow-by-blow notes from the sessions I attended in my personal KnowledgeForward blog (see Day 1, Day 2, and Day 3) but thought I'd post a summary of my impressions and some of the non-session activities.

          Below is a quick report of what I saw at the Innovation Lab at Lotusphere.  Three of my interests were represented there: virtual worlds, portals, and globalization. 

          Bluegrass

          • There were actually four virtual world projects, the best of which was Bluegrass, which was neat because it shows how virtual worlds can be used as a visualization mechanism for existing data
          • Architecture: It runs on Torque rather than Second Life, a good choice for business applications and one I expect to see more of to get away from the quirks of Second Life.  Torque does the visual rendering and has client and server components.  The client is C++ with a JNI layer that does the bridging between the Torque client and the interface.
          • Content: It renders information on development projects from Rational Jazz such as teams, actions taken on components, and repositories.  Jazz uses a standard textual IDE to allow access to this information.  But Bluegrass acts as an alternate view (I won't say UI since it isn't meant to replace Jazz's UI) to enable better discovery of information, socialization, and brainstorming.  Each team is represented as a tree.  People are shown as, well, people.  When people take an action it shows as a bubble floating up over their heads, like a tweet.  One can look around a busy team and see little bubbles (emitters) floating up, kind of like smoke signals.  Where there's smoke, there's fire in that project! Actions taken in Jazz have instant effect in the virtual world and vice versa.
          • Social aspects: You can enter a brainstorming house where sticky notes can be picked up and moved.  This part was ok, but not as cool to me as the rendering of real information in an alternate view.
          • Usage: Alas, there isn't a great success story on usage yet.  But it is being picked up by a few teams at IBM and hopefully they can show some sort of improvement or ideas that only came about because of Bluegrass

          Contextual Portal

          • This project demonstrated usage of pattern recognition to guide the user to pages they might be interested in but not know about, much in the way Amazon makes recommendations. 
          • It can recommend portlets, people, and pages based on what others in your same role did
          • There is a "contextual search" part that results in a custom portal page with the portlets related to that search, such as maybe entering a company name and getting a legal news portlet, financial information portlet, and ERP system data all with info on that company

          Real-Time Translation Service

          • I thought the coolest thing I saw in the Lab was the Real-Time Translation Service.  There were a number of demonstrations of IBM's various forays into translation
          • One was an IM plugin.  While there are other examples in the industry of 2-way translation to allow IM users speaking different languages to converse, I liked that this one had a dropdown to select the domain of conversation (like helpdesk versus programming), which really helps a translation engine's accuracy
          • The speech to speech translation was very good.  Well, I guess I can't judge how good considering I don't speak Arabic, but from the textual translation on the screen it seemed to be picking up the spoken English very well.  He spoke English into the microphone and a few seconds later smooth-sounding Arabic came out the speaker
          • The translation tool was like the speech to speech translation, but supported speakers on both ends and a persistent chat window between them.  The demonstration showed speaking in English to someone in Japanese and getting responses back, with the chat window keeping a record of the conversation
          • He also showed a shipping product, GALE, that does rapid translation of video feeds.  For example, you can watch Al Arabiya and English subtitles appear at the bottom.  It is useful even for English since the text is stored with the image and can then be searched to, for example, help a PR agency find every mention of a product on talk shows

          • Burton Group Free Resources Stay Connected Stay Connected Stay Connected Stay Connected


          Catalyst Conference 2009


          Blog powered by TypePad