Continuous Software Internationalization (i18n) & Localization (L10n) Sandbox
Report
Share
•0 likes•431 views
Continuous Software Internationalization (i18n) & Localization (L10n) Sandbox
•0 likes•431 views
Report
Share
What would it look like to have development and localization always connected in every feature and sprint automatically? Globally-focused companies often work hard to solve disconnects and growing backlogs regarding internationalization and localization. But still disconnects remain and the backlog grows. It’s a common complaint. Maybe your dates show up in US-centric format, or your number formats have the wrong separators. Or, perhaps the U/I defaults to English because you’re behind on translation because there are manual steps to run scripts to handle changes at the end of a sprint? The results are lots of last minute hurry up issues with potential pitfalls. Global customers default to a second tier experience of your product or site and especially new features. This webinar will show you a way to solve this using continuous globalization automation. This process forms a visible and manageable link between your developer’s source repositories and your translation processes and systems. You’ll see how: 1. To give your global users the same release timetable and quality user experience 2. Releases can be in sync automatically with internationalization and localization 3. To instantly know where your status and work needed for globalization Register for the webinar here: http://lingoport.com/webinar-continuous-globalization-sandbox/
Recommended
More Related Content
Similar to Continuous Software Internationalization (i18n) & Localization (L10n) Sandbox
Similar to Continuous Software Internationalization (i18n) & Localization (L10n) Sandbox(20)
Recently uploaded
Recently uploaded(20)
Continuous Software Internationalization (i18n) & Localization (L10n) Sandbox
- 1. Continuous Globalization Continuous Globalization Sandbox Presenters: Adam Asnes, CEO at Lingoport Olivier Libouban, VP Product Development at Lingoport Dan de Grazia, Director Solution Engineering at Lingotek
- 2. Globalization Issues • Important strategic activity • Companies develop their own processes o Excel o Scripts – must remember to run them o Iterative Testing • Subjective vs. Objective Status • Test centric • Backlogs • Is everyone getting the user experience you’d like them to have?
- 3. Lingoport Suite Painless support & actionable data to facilitate ongoing software globalization. Working in partnership:
- 4. G11n Process Challenges Most development teams have, or are in the process of implementing some form of Agile methodology. There are difficult globalization complications from Agile and frequent development iterations.
- 5. Iterations and more iterations • Continuous to 3 days to 3 weeks of new feature churn • Small number of words per feature but many times • Many source repositories • Cost of dev processing vs. Cost of a word
- 6. Defect costs per dev phase Traditional approach to SW Development in a well defined process When most i18n & L10n issues are addressed
- 7. G11n & Agile i18n & L10n issues often Fall into backlogs
- 10. Key Attributes: Continuous G11n • Automation – Not dependent on people running scripts or other tasks • Metrics – Clear and actionable measurement of status • Visibility – Everyone necessary can see progress
- 11. Measured, Automated & Visualized L10n – Resource Manager • Resource File Changes • New Words • File integrity • Key Formatting • Extraction from repository • Flow into TMS or FTP • Return to repository • Due dates • Projections • Notifications I18n - Globalyzer • Embedded Strings • Locale-Unsafe Methods (date/time, encoding, much more) • Programming Patterns • Static Files
- 12. • Subjective data is replaced by objective data reporting. Visualize via Dashboard
- 13. Globalyzer i18n: Programming Language Support • I18n static analysis of code as it’s being written • 14 programming languages plus variants (.NET, Java, JavaScript, Objective-C, PHP, C++, more) • Customizable and extensible rule sets for each programming language for tailored i18n detection • Extensive and customizable filters to reduce false positives
- 14. Resource Manager: Bridge from Dev to L10n • View the status of existing and changed resource files • Track completeness of translations • Verify quality issues such as string ID’s and encoding • Automatically generate localization kits for translation • Automatically reintegrate translated files back into your build
- 15. Continuous G11n ROI • 5 Teams X 20 sprints/year = 100 Sprints • Each sprint has 5 features = 500 features • 2 days saved per feature = 1,000 days • At $40/hour = $325,000 per year • Productivity increase of 3 people per year • Localization turnaround from 6 weeks to 3 days and on the current release cycle.
- 17. Process Overview • Developers o create or modify code and (U.S. English) resources o push changes to repository • Lingoport Dashboard is updated: i18n, L10n • Resource bundles are checked and pseudo-localized • “Good” resource bundles are sent for translation seamlessly, without human handling; Dashboard updated • Translators translate, review, approve => Submission • Translation are checked and if OK, pushed to repository • Dashboard is updated
- 18. Sandbox GitHub Project • Part of a public Nasa project • Developers push new code and resources to repo • Just like any software project • https://github.com/ptcLingoport/World-Wind-Java
- 19. Dashboard • Shows the i18n and L10n status of projects o Internationalization: Globalyzer o Resource bundles translations: Lingoport Resource Manager • http://sapphire.lingoport.com:9090/dashboard/index/19347?did=1
- 20. Translation Management System • Integrated • https://cms.lingotek.com/lingopoint/portal/startup.action
- 21. Questions & Answers Adam Asnes aasnes@lingoport.com Olivier Libouban olibouban@lingoport.com Andrew Deaver adeaver@lingoport.com Dan de Grazia ddegrazia@lingotek.com http://www.lingoport.com
Editor's Notes
- Introduce Guests Concept of Sandbox – What it is. We use it to create a real environment to demonstrate Continuous Globalization Agenda: A bit of background, product introduction to give you a bit of context and understanding how it relates to development and business case. Then Olivier will lead us with a look at the sandbox. Then we will answer questions.
- We have lots of technology to reduce the cost of a word. Development processes have changed, but there has been little to fascilitate bridging development together with localization. Localization is a highly strategic and competitive undertaking. Getting it right isn’t just about saving money, though that is a good concurrent objective. It can be as bad as a localization team essentially being forced to run their efforts like a small business, using small business tools like excel to manage an iterative process. This affects both bottom line costs as well as top line revenue as new features can be rolled out concurrently and easily to target markets around the world.
- Globalyzer: Find and fix internationalization (i18n) issues that inhibit localization and global user experience during development. Catch up on i18n technical debt. Dashboard: The hub of our suite. See it all, drill down, create notifications and manage the process. Bridge gaps between localization & development. Increase visibility and track globalization metrics. LRM: Make localization proactive. Detect & manage changes to resource files in your source code. Streamline translation jobs. Automate localization updates between development and translation. For our Sandbox, Translation Management is provide by Lingotek, a cloud based translation management system and a Lingoport partner.
- ----- Meeting Notes (6/23/15 18:33) ----- Changes in development methodology break down to smaller iterations, faster and more frequent releases. Even if your company isn't using Agile, chances are very high that aspects of Scrum are in use.
- We need systems to bring i18n and L10n into sprints. Localization should be happening in days during feature implementation, rather than after completion. This way i18n and L10n testing is part of the sprint or feature release, not the last recourse.
- ----- Meeting Notes (6/23/15 18:33) ----- If you think about supporting entire enterprises, that train is always moving. There’s product teams, features and fixes. Lots of change happing over many source repositories. Use automation, visibility and metrics to establish, maintain and reinforce internationalization and localization in development. Eliminate human error and time gaps.
- Some people will be focused on L10n some on i18n. Both are important! The logical flow is to make sure i18n is in line to support L10n Translation can be very integrated: i.e. client who integrates with WorldServer Can also integrate with your L10n Vendor’s portals, other translation systems like LingoTEK Back in to build with file quality checks. Gives you more time for staging QA.
- I18n assessment find and fix complex i18n issues across code base static analysis rather than limited iterative testing spread expertise across development teams Ongoing i18n detection and resolution detects issues proposes solutions and fixes i18n validation integrated in a build or a QA process burns into the software i18n best practices integrates with Agile environments
- Write us for access to the sandbox Whitepaper on Developing a Business Case in Progress. Will send it to everyone when complete.