Currently viewing the category:
"Software internationalization"
While most understand the business case surrounding internationalization (i18n) — establish an international footprint, make products easier to use around the world, etc. — many find it difficult to gain the necessary support to scope and assess their application. Charged with gaining executive support, learning technical i18n implementation needs, and assuring localization quality, VMware approached Lingoport with assistance on these issues. Lingoport helped VMware to generate a robust i18n assessment, and assist in …
The Second Annual Internationalization and Localization Conference is coming up in just over a month! To prepare everyone for the March 14th event in Santa Clara, California, we will share what to expect from many of our exciting presentations in the weeks leading up to the event. This week we look at a few internationalization-centric presentations as well as what to expect from this year’s fast and furious Demo Derby.
First, some General Information:…
Internationalization (i18n) is often late, incomplete and messy. Most i18n issues stem from the basic question: is it internationalized? Most don’t know the answer or underestimate the complexity of i18n (or just think it’s as basic as string externalization). Fortunately, it doesn’t have to be this way.
There is tangible value in being able to confirm global readiness of product releases. At Lingoport, we often see i18n issues start at the top, with …
From Lingoport’s October 2012 Newsletter:
While we are known for our i18n tools, many clients realize great value and successful globalized releases from our internationalization services team. We’ve got an expert team that puts our technologies to use to get i18n assessments, planning, implementation and ongoing consulting done efficiently and to high engineering standards. We can augment and work side by side with your developers and know how to plan and match a project to …
Targeting a first time internationalization effort for Canada is one of the more forgiving target locales from a technical risk perspective when working with code that is US English-centric. If there’s a missed string, chances are the user be able to work through it. Currency symbols are represented the same. Numerical units use the decimal point the same. Address formats are the same other than postal codes. However, this can also present a false sense …
Visit
Featured Content
Poll Indicates Quality Issues Biggest Headache for i18n ProjectsIn an informal poll conducted by Lingoport, 73% of respondents who have been involved in ... ∞
Bringing i18n Awareness to the Enterprise – via a DashboardA customer once told me that his organization had over five hundred dashboards to track ... ∞
Shifting Focus Within GlobalizationShifting Left: Moving the Productivity Pendulum Focus Within GlobalizationDuring my first week of customer visits ... ∞
Comparing Software Tools for World Readiness (i18n)Originally posted on http://blaufunk.blogspot.com/
I was asked the other day what the difference is between a Visual ... ∞International SEO: Top-Five ConsiderationsInternational expansion involves more than just product development. Every strategy a company uses domestically should ... ∞
Trends in Mobile & Social ApplicationsThe global marketplace is booming for online games, social & mobile games and applications. We ... ∞
About Lingoport
Archives
- March 2013 (1)
- February 2013 (6)
- January 2013 (1)
- December 2012 (2)
- November 2012 (1)
- October 2012 (3)
- September 2012 (1)
- August 2012 (2)
- July 2012 (1)
- June 2012 (1)
- April 2012 (3)
- March 2012 (3)
- February 2012 (9)
- January 2012 (9)
- December 2011 (8)
- November 2011 (9)
- October 2011 (6)
- September 2011 (8)
- August 2011 (9)
- July 2011 (6)
- June 2011 (12)
- May 2011 (11)
- April 2011 (13)
- March 2011 (10)
- February 2011 (5)
- December 2010 (2)
- November 2010 (6)
- October 2010 (4)
- September 2010 (4)
- August 2010 (5)
