Webinar: Lean Localization Innovation Webinar Series

Software localization is a widely reported friction point and is ripe for innovation. Developers usually want to focus on features while the localization team is at a disadvantage trying to keep up and have their message understood.

In this 2-part webinar series, we’re going to discuss innovations and new technologies to realize a faster and more localized product future, turning localization into a development super power. When you register, you’ll automatically be signed up for both sessions. You won’t have to attend both to get value, but they do build upon one another.

Dates:

  • Session 1: Wednesday, December 16, 9AM PT, Noon ET, 18:00 CET
  • Session 2: Wednesday, January 20, 9AM PT, Noon ET, 18:00 CET

Register for Webinar

A History of Inefficient Waterfall Processes

Even with faster localization and automation, the industry is still slapping a words-focused waterfall process onto agile development, and that costs time, money and productivity.

Most development teams are using agile principles and continuous integration, but development and localization are still challenging to execute on the same timetables.

  • Translators are reduced to firing out short bursts of words, typically without much context to go on
  • Engineers are reduced to clerks for file changes
  • Localization testing is late and a nest of manual processes

It’s time to change all that.

What You Will Learn:

Session 1:

Our first webinar will look at the overall agile localization process with an emphasis on the components of QA, integration and scale and how that gives rise to faster and earlier localization during development.

  • Understanding the developer’s world and continuous systems
  • Your TMS is not part of the developer’s world
  • Pain around Localization QA and why it’s a fulcrum for speed
  • Our solution – New product innovation
  • TMS v. MT in the world of LocalyzerQA
  • An overall approach to faster, better software localization (quick i18n, L10n, QA together)

Session 2:

Our second webinar will focus deeper on a new way to look at linguistic and functional QA, quick i18n & localization on-boarding, and how that impacts localization upstream. You won’t have to attend both to get value, but they do build upon one another.

  • Software as agile, localization stuck in waterfall
  • Overview of the lean localization process
  • Linguistic QA and how that impacts software localization
  • Localizers with a bigger role than banging out words
  • A new opportunity for MT vs. Humans and TMS for software development
  • Fast i18n & L10n impacts with Lingoport’s new Express products
  • Scaling up from small to large teams and multiple products

All of this will be shown with examples, code and real-time translation.

Who Should Attend

  • Product managers
  • Localization leaders
  • Software leaders and developers who are thinking globally

Register for Webinar

A Cheatsheet Guide to i18n Gremlins (Issues)

Explore our cheatsheet infographic guide to the 5 most common i18n gremlins (issues) so you can identify the issues quickly, fix them, and prevent them in the future.

i18n issues infographic

Leadership Effectiveness in Minutes a Day

Your brain is designed to run on cheap fuel. That’s not really a design flaw. It was optimal when our ancestors lived on the African Savannah. But it really gets in your way of being an optimal leader because you (and the rest of us) are in habit mode, or automatic pilot, almost all day. That doesn’t mean you’re not effective, but likely you’re treading water. You’re not improving your leadership capacity.

We define leadership capacity as the ability to lead more effectively in times of increasing VUCA (volatility, uncertainty, complexity, ambiguity) and rapid change. You can read this in-depth article for the vital but little-understood distinction between leadership capacity (your operating system) and leadership competencies (the software you run).
We know how to increase leadership capacity in just minutes a day, and we look forward to telling you how.

Step One: Why?

The first step is getting clear about why you care about increasing your leadership capacity. Change is hard for us humans. It inevitably involves experiencing some discomfort in service of something that really matters to us. What is your “why”? What is your vision for you as a leader?

It can help to ask yourself what you hope people at your retirement party say about you as leader before you arrive. Is it just, “She really hit her numbers?” or something deeper than that?

Step Two: Understand some basic neuroscience.

It takes a lot of energy to run the frontal lobes, the seat of executive functioning. This includes insight, response flexibility, empathy, intuition, moral awareness, attuned communication, reflection, perspective taking and perspective seeking. and emotional regulation. Important abilities! But to save energy, your brain naturally reverts to automatic pilot or “habit mode.” In doing so much of what makes you a more effective leader goes offline. You’re still getting stuff done, but you’re not able to optimize our current capacity, nor build new capacity.

Step Three: Learn the process of Goal-Plan-Action-Reflection

In order to increase your capacity you have to “wake up” many times throughout the day, coming off “automatic pilot” and making more conscious choices. Building capacity requires a mindful approach, with short cycles of action and reflection.
We have developed a specific practice that will take you just minutes a day. Our leadership clients consistently report their overall effectiveness takes a quantum leap in both organizational results and employee engagement. Many report it having just as powerful an impact on their personal lives as well.

Check out the recording from our October webinar, Upgrade Your Leadership Operating System to learn more!

View i18n Webinar Recording

A New Approach to Continuous Internationalization & Localization | IMUG

Our industry is ripe for a new way to deliver software internationalization and localization. Localization runs behind development, as a bolt on process. Even current continuous localization practices are built on old linguist-centric models of translation tools and handling. By nature, localization and its QA are an additional lag. Engaging input from in-country reviewers adds even more delay and overhead into the process. In this presentation, we will show you what we’re working on to change all this. We’re looking to make both internationalization and localization immediate, right in the developer workspace, with in application review and updating that’s quick, easy and doesn’t require knowledge of translation tools.

We will show a connected system from Slack and Teams, to the IDE, to the repo, any commit or pull request, testing and deployment. We’ll show internationalization and localization, plus review on a live application. We think this is the future for our industry – an exciting change that makes localization a natural and scalable deliverable of product development. We’ll also welcome your input as the session will involve technology that hasn’t been released yet to the public.

Check out the recording!

 

Webinar: Localization Leadership with Loy Searle

Check out our September webinar where we interview Loy Searle, Sr. Director of Localization & InfoDev at Workday,to get an insider’s view into the future of localization and discover how to improve team efficiencies for a much faster higher quality product.

Loy has a tremendous amount of knowledge and strategic insights from her experience leading localization efforts at a number of global powerhouse companies.

“I am a great advocate of upstream intervention to prevent downstream pain and reduce costs and believe data, technology and teamwork can accomplish almost anything.” – Loy Searle

Register for Webinar

Learn from a G11n Pro

In this webinar, you’ll learn from a pro about taking the reins of enterprise globalization, with a lively discussion around the following topics:

  • Overcoming organizational resistance
  • Strategic planning 
  • Optimizing your team
  • Winning the budget!

Loy Searle

Loy Searle has 25+ years of experience within the globalization industry, working for some of the largest and most complex globalized organizations in the world including Google, Intuit, Delux Entertainment & more.

Loy’s specialities include but are certainly NOT limited to:

  • Single-sourcing processes leadership from content creation through translation & product management
  • Process optimization work to grow scalable solutions
  • Transforming and leading global teams – fixing what’s broken and creating what’s needed
  • Leveraging data to make solid decisions
  • Building, buying, and implementing strong technical solutions that support efficiently delivering quality offerings

Key Discussion Points Include:

  • The Most Common Localization Pain points
  • How to Create a better Partnership Between Dev and L10n
  • How to Save Time and Money Caused by Blockers
  • Real-World Examples of L10n Challenges
  • The Leading Ways to Solve and Prevent Future L10n Issues

Who Should Attend

  • Localization Management
  • Localization Engineers
  • Development Managers
  • Product and Project Managers
  • Anyone interested in improving their G11n/L10n process

Register for Webinar

An Overview of The 5 Most Common i18n Gremlins

I18n Gremlins come in many nasty and disruptive forms. Maybe a concatenated or embedded string. Perhaps the date format shows up wrong or you see square boxes and gobbledegook in your user interface.

They are annoying bugs for localized products that detract from your product quality for worldwide users. Typically, they are found late in a development cycle and sometimes sit for months to years in bug tracking backlogs. But you can find these Gremlins and eliminate them as code is being written, when internationalization (i18n) is fast and easy to fix.

Let me explain. When developers are creating new products and features, it is easy to inadvertently add i18n Gremlin issues. Some are pretty obvious, like embedding a string (messages in a product interface), rather than using a locale framework and a key, so that words that will need to be translated are all in resource files. It’s one of the most basic practices for i18n – writing software that can be quickly and efficiently translated for worldwide customers. Other i18n Gremlins are a bit more complex. For instance, embedding a font that might work fine in English but is illegible in Chinese, or forgetting to pass locale into a calendar class.

We came up with the term Gremlins because, like the mythical sprites they remain hidden and cause sabotage. i18n Gremlins aren’t immediately obvious and often are not found until later, when it costs much more in time and distraction to locate the gremlins’ source and fix the issues.

Here are some of the fundamental areas of i18n Gremlins that Lingoport’s Globalyzer software will detect as developers write software:

1. Concatenations

Issues: It’s like an Embedded String which cannot be externalized as such. In many languages the word order is likely to be different, so translations will read terribly. The string first needs some redesign. This one comes in all kinds of shapes and sizes. Here is a concatenation example: “Welcome ” + username + ” to our Rebel Outfitter store”

Remedy: The typical remedy is to create a parameterized strings and keep the parameter variables outside of the string itself. For instance, the parameterized string may look like “Welcome %{userName} to our Rebel Outfitter store”.

2. Embedded Strings

Issues: When you change locale, the string stays the same. The string was hard-coded in the application and is resistant to locale changes. For example if there was simple code that looks like:

  • String d =”All the young ones”;
  • String e =”Having a good time”;

Remedy: Externalize the Embedded String from the source code. Generate a Key/Value pair in a resource file, refer to that key in the code to retrieve the value. The value is the string itself. With your locale framework, you can then retrieve the string from a locale dependent resource file.

When the string is externalized, the code looks like:

  • String d =getString(“JAVA_TESTSTR_105”);
  • String e =getString(“JAVA_TESTSTR_106”);

And the key/value pair in the resource file looks like:

  • JAVA_TESTSTR_105=All the young ones
  • JAVA_TESTSTR_106=Having a good time

3. Locale Sensitive Methods

There can be hundreds o these locale sensitive methods, functions and classes depending upon the programming language. They effect issues like date formatting, numerical formatting, character encoding, currency handling, measurements and more. Here are some examples:

Date/Time Format

Issues: The application may look right but provides the wrong information. If the date shown is 05/06/07 independently of the locale, it means:

  • May 6, 2007 for an American
  • June 5, 2007 for a Frenchman
  • 2005, June 7 for a Japanese

Remedy: The application needs to format the data based on the user’s locale and, for instance, show May 6, 2007 as

  • 05/06/07 to an American user
  • 06/05/07 to a French user
  • 07/06/05 to a Japanese user

In addition, the date/time may be displayed using Time Zone. The entity or value itself may need to be a GMT date / time.

Currency Format

Issues: The application displays the same amount whatever the locale/region of the user. For instance, a Canadian user sees $5000 and may think that in Canadian dollars when it’s in US Dollars.

Remedy: The application needs to format the number, display the symbol, and most likely use some exchange rate to display the actual currency amount for the user’s language / region.

4. General Patterns

Issues: This gremlin may take the form of an encoding like ISO8859-1 when UTF-8 is required, or set a font that cannot be used in Chinese, even decides a format output.

Remedy: Make sure to check for each pattern to decide if it is a General Pattern, if more need to be added to your specific application, and how to refactor the code.

5. Static Files

Issues: The application serves the same file, maybe a video or a legal HTML file, independently of the locale. For example, a Chinese video is shown to a Russian application user. For example:

placemarkAttributes.imageSource = “./img/marker.png”;

Remedy: The locale framework needs to provide for an internationalization way to refer to the file so that a locale with a static file name will result in serving a Russian video to the Russian user.

All of these types of Gremlins are quickly and easily found using Globalyzer, which can detect i18n Gremlins in a number of ways:

  • In the developer’s IDE – A developer can add Globalyzer i18n detection to their development environment and see i18n issues as they work.
  • During commits or pull requests: As a developer submits her day’s work, a Globalyzer scan can run automatically illustrating any i18n issues. That makes it easy to fix any i18n issues that can arise and then move on.
  • Dashboards for specific repositories, entire development products, or software across your enterprise – gives a broad view of i18n readiness, while also enabling issue drill downs, assignments and other management features.

—————————————–

Learn more about i18n Gremlins:

There are other problems of course that our software suite will solve for you, so that you localization is fast and in tune with software development. To discuss your own localization process, continuous localization and Linguistic QA, please reach out to Gremlins@lingoport.com.

Webinar: Agile Localization Bottlenecks and the Cure

There are common blockers that interfere with agile localization for software, which puts localization behind feature development and sparks the common rift between developers and localization teams. This in turn, costs time and money over and over…and over again.

It doesn’t have to be that way, but it takes some planning, technology and advocacy to impact your development teams.

In our August webinar, we explore the common blockers that interfere with agile localization for software and solutions for how to fix them and avoid them in the future.

Register for Webinar

 

 

The pain is real, especially when you localize at scale. The solutions are about much more than a git connector and we will be demonstrating solutions that address the most common challenges and bring localization in line with modern development practices.

This webinar is an education for some, with real-world examples, intended to provide good illustrations to help you get ahead of frequent real world problems.

We explore the following common challenges:

  • Broken or irregular file formats
  • Errors introduced with human processing
  • Frequent iterations on U/I content
  • Why even fast localization turn around is still late
  • Translator errors
  • Linguistic QA backlogs
  • I18n gremlins
  • L10n bugs going to JIRA to die!

What We Discuss:

  • The Most Common Localization Pain points
  • How to Create a better Partnership Between Dev and L10n
  • How to Save Time and Money Caused by Blockers
  • Real-World Examples of L10n Challenges
  • The Leading Ways to Solve and Prevent Future L10n Issues

Who Should Attend

  • Localization management
  • Localization engineers
  • Development managers
  • Product and project managers

Register for Webinar

Lingoport Suite – New releases, Machine Translation and More

We are pleased to announce the latest new releases of Lingoport Suite products, including enhancements to Globalyzer and Lingoport Resource Manager (LRM).

Lingoport Suite products work together to integrate internationalization (i18n), localization and QA together with modern agile development practices and continuous engineering systems. With so many software companies realizing substantial growth using language and regional customization to reach new customers, it’s more important than ever to have software systems that speed up and simplify the globalization process. Here are the release highlights:

Globalyzer – Continuous i18n

LRM – Continuous Localization:

  • Integration with Amazon Translate and SYSTRAN neural machine translation engines deliver immediate translation returns directly to and from your Git repositories, and empower developers to iterate on features without waiting for translation. Machine translations are then quickly edited using Lingoport’s InContext QA.
  • DITA support for documentation projects using .dita and .ditmap files, increasingly popular within git projects and hard to manage for localization without automation
  • XHTML parsing
  • More flexibility for locale support in file structures
  • See: https://wiki.lingoport.com/LRM_Release_Notes

Lean Localization Process

Lingoport’s patent pending Lean Localization Process combines its software suite so that applications are always internationalized and localized with all feature development, and no lag in waiting for translation. The right time to deal with i18n and Localization updates is as software is written, and the right time for human translators to correct machine translation is during QA and review. This keeps localization tightly in sync with feature development, rather than lagging development progress by days to weeks. Please visit: https://lingoport.com/lean-localization-process/ to learn more about this industry changing approach.

Make better software for the world, do it faster, and in tune with agile development.

Webinar: Can Read, Will Buy | Language’s Impact on Online Behavior

Our friends at Nimdzi have just recently released an important report looking at online behavior, buying decisions and the intimate way in which language impacts behavior. Nimdzi calls their report Project Underwear, because consuming content for personal decisions and communicating in our own language is as private as it gets.

“That is the Underwear Effect, the term to describe situations where consumers are making their buying decisions during their (almost) most private moments, with their mobile phone in hand wearing nothing but their underwear. And what clings to a person even more closely than his or her undergarments? Why, their language, of course.”

In our upcoming webinar, we’ll be exploring the takeaways from the report with special guest and Nimdzi Co-Founder, Tucker Johnson and taking questions from the audience both before via and during the webinar via chat.

View Webinar Recording

Project Underwear:

Codename: Project Underwear, Nimdzi’s internal name for this study, is one of the most ambitious projects Nimdzi has undertaken to date. This is a global project, with surveys and data collection executed across more than 70 countries. Based on an end-user survey consisting of 25 questions translated into 66 languages and carried out with native speakers living in those countries.

Project Goal: Demonstrate how language affects buying behavior and answer the following:

  • How do people engage with and consume content online?
  • How do they act if given the choice between English and their native language?
  • Would they consume more if there were more content in their native language?

Tucker Johnson:

Tucker has served in many different capacities throughout his career, from engineering to senior management. His special experience lies in:

  • On-boarding and building out large scale localization programs
  • Supply chain governance
  • Global team management
  • Advising business leaders on international strategy

Tucker’s latest endeavor is the founding of Nimdzi Insights company with a focus on the international market. Nimdzi works with international businesses, language service providers, universities, private equity firms, government agencies, and more.

What We’ll be Discussing:

  • While it’s clear that online services have proliferated magnificently, how have our language preferences and baseline expectations changed?
  • What does this mean for language and product marketing professionals?
  • How should this information affect product development planning and process?
  • What is the impact of English language proficiency on personal preferences?
  • If you had to pick between speed and accuracy for delivering in languages, which is more important?
  • What are the functional expectations for applications used by worldwide communities?

Who Should Attend

  • Localization management
  • Localization engineers
  • Development managers
  • Product and project managers

View Webinar Recording

Webinar: Continuous Localization Training for Software Development

There are excellent opportunities to join localization teams with development, but the solutions aren’t in your TMS or Translation Workbench. Even with modern deployment of “continuous localization,” it’s not really continuous like other developer services…and that should change.

We’ll show you what we mean.

Going Under the Hood of Continuous L10n

Check out our training webinar recording where we go over the mechanics of continuous localization integration and hardwiring into the developer’s world – from the developer’s IDE, to source control, collaboration beyond messaging, and systems like Jenkins.

Discover opportunities to go further.

Register for Webinar

Why it matters:

  • Deliver global products faster with less hassle
  • Built in coordination with ongoing development makes for better products
  • Opportunities to include input faster from target market stakeholders

Check out our webinar teaser below.

What You Will Learn

  • Continuous i18n and L10n overview and why that’s where L10n needs to improve
  • The developer’s perspective
  • Examples of continuous integration
  • The Lean Localization Process
  • Immediate localization feedback
  • Audience Q&A

Who Should Attend

  • Localization management
  • Localization engineers
  • Development managers
  • Product and project managers

Register for Webinar