Connecting Development and Localization, New Technology Automates Translated File Management
Today, Lingoport announced that it has released Lingoport Resource Manager (LRM) to support development projects in their localization efforts. By optimizing the manual and often error-prone process of resource file management, LRM effectively bridges the gap between development and localization, ridding the two areas of unnecessary testing iterations and file confusion.
In a press release sent out today, Lingoport President noted:
“During our product
…
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 …
In working with project and localization managers, localization sales people and those who are just new to the internationalization (i18n) process, I regularly encounter confusion regarding the technical terms that describe the encoding that will be needed to support particular sets of locales and their respective languages. This post is here to simplify things and make them digestible for a topic that’s important, if you want your software to support localization, but makes many people’s …
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 …
In an informal poll conducted by Lingoport, 73% of respondents who have been involved in an internationalization project indicated that their biggest headache during an internationalization project was accounting for quality issues. This data, collected in a recent webinar, stems from a common misconception of i18n being solely about string externalization. While the visual element of a program is certainly important, having an architecture that detects and adapts to the locale of a user …
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)
