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.

Register for Webinar

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

Register for Webinar

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

Globalyzer i18n Express – A Free i18n Analysis on GitHub

Globalyzer i18n Express – A free i18n analysis on GitHub

    • Create software that’s ready for localization and the world
    • Find i18n issues in source code as you develop, before they become a problem
    • Super easy and fast way to get basic i18n code analysis for GitHub users
    • Free for now on the GitHub Marketplace

What is Internationalization (i18n) and Why Does It Matter?

I18n is the practice of writing software so that it will function well in any targeted locale. Locale will include language (translation) and formatting (i.e. date formats, sorting, character support and much more).

With access to global customers faster and easier than ever, attention to i18n and ultimately, localization is more important than ever. Global technology companies frequently report 50% or more of their revenues coming from outside home markets, and often, these are the same areas with the highest sales and user growth potential.

Software that is written without quality attention towards locale requirements will not make for a good user experience in new markets, and will likely create all kinds of translation and formatting bugs that are expensive and time consuming to fix later on.

I18n issues are not always as straightforward as telling your team not to embed or concatenate a string within the U/I. For example, a correct calendar class might be used, but a developer may forget to include locale. Like issues around security, there are mistakes that are made. Those mistakes are often found late or after any development cycle, making i18n issues especially expensive to revisit and fix.

Globalyzer i18n Express

Lingoport’s Globalyzer is used by many of the world’s leading technology companies to scale i18n support across their development teams.

Globalyzer i18n Express is a simplified functionality version of the full Globalyzer system, intended to help developers on GitHub get up and running with i18n analysis quickly and easily, and without necessitating IT department involvement. It is Lingoport’s intention to spread the adaptation of systematic i18n analysis, making it a measured and automated component of coding quality. For a limited time, we are making it available free from the GitHub marketplace.

Globalyzer i18n Express will detect:

  • Embedded strings
  • Concatenated strings
  • I18n unsafe methods, functions and classes for leading programming languages
  • Programming patterns, such as fixed fonts
  • Static files, such as images that could be locale dependent

Globalyzer i18n Express will find i18n issues in a wide range of programming languages, including Java, C#, JavaScript including variants for React, Node and jQuery, C++ and more.

See links for more information about Globalyzer i18n detection and programming language i18n support.

How Globalyzer i18n Express Works

Globalyzer i18n Express uses a basic set of Globalyzer capabilities, and it’s fast and easy to get i18n checking into GitHub projects. I18n Express uses basic Globalyzer rule sets to provide i18n detection to developer commits automatically as developers engage their usual workflow.

Getting Started

Step 1: Go to the GitHub Marketplace and select Globalyzer i18n Express:

lingoport globalyzer express github install


Step 2: Set up your plan

setup directions screenshot


Step 3: Get Started

lingoport globalyzer express github


Step 4: Work as usual, and after a commit, inspect any detected issues. For example:

i18n express github notes


For more information about Globalyzer as well as the Lingoport Suite, supporting continuous i18n, Localization (L10n) automation and Linguistic QA, please visit: https://lingoport.com/products

Lingoport’s Lean Localization Process

The Lean Localization Process delivers ongoing localized software development that’s integrated into each sprint for development, testing, review and release. Using several Lingoport products in concert, the process delivers speed and quality results that remove developer burdens and delays, gives the localization team an opportunity to deliver in synchronization, and saves time and budget overall. The process is enabled via continuous integration systems, and recommended use of high quality machine translation engines. A final critical aspect is the ability to instantly review and update translations within application context, without creating new linguistic update bug fixing hassles for the development team.

The status quo using human driven localization processes outside the development path, and adding steps or proxies outside of the sprint cycle will always create a gap between development and localization. The Lean Localization process is designed to make localization truly continuous and visible, and not delayed by days, weeks or more. 

The TL/DR (too long/didn’t read) version is:

  • Internationalize during development with Globalyzer
  • Automate translations with Resource Manager
  • Integrated Machine Translation gives immediate results, with no minimums or waiting late in a sprint for string rewrites
  • Review and adapt automated translations in your software with InContext QA within test and review cycles
  • Release sprints with localization built in!

lingoport lean l10n process

How the Lean Localization Process Works:

1. Globalyzer for Internationalization (i18n): The first step is to make sure that as code is created, that i18n is included in requirements. Software must be internationalized to support languages and locale formatting properly.  During development, Globalyzer is used to automatically check for i18n issues either from within a developers IDE or during pull requests and commits. Any issues are automatically delivered to the developer, including where they occur, with help on many fixes. This is a non-invasive method to deliver i18n quality feedback that makes fixing much faster and easier than later during QA or post release when it’s much more expensive.

2. Lingoport Resource Manager (LRM): As developers create new interface elements, LRM automatically analyzes and verifies resource files containing the strings/messages, transforms as necessary, and sends for translation. This is a no-touch system that takes all manual developer burden away from string resource management.

3. Translation: Machine Translation, or optionally human translation, is queued up and delivered next via LRM. Completed translation files are automatically checked for correctness and pushed back into their respective development repositories for testing. Our Lean Localization process recommends machine translation. Machine translation quality has improved considerably over the past few years.

Using Machine translation, there’s no concern about minimum charges, or the time it takes to retranslate a string as it may change later in the sprint and translations are returned in seconds rather than hours to days. Localization becomes truly continuous, and easy review via InContext QA provides accuracy. Using machine translation also lets teams instantly see translated results. When teams can see language impacts in a matter of seconds, the feedback loop for correction is shortened. LRM supports connectivity to multiple machine translation engines.

4. InContext QA: Traditional linguistic review is an important step to make sure translation accurately supports end users, but past methods make that a slow process that piles on bugs that usually trail releases. In the Lean Localization Process, we use our InContext QA automation and file instrumentation to bring linguistic reviews (post-translation editing) into the same timeframe as other sprint functional reviews. A linguistic reviewer navigates to the new sprint functionality within the application and literally can click on a word or message they want to change, enter the re-translation via the InContext extension and it is pushed back to the repository, with an update to the translation memory or machine  translation corpus.

Time consuming localization QA tasks are eliminated, such as gathering screenshots,  filing bugs that pile up, tracking down linguistic bugs in code and files, and manual file updates. The InContext QA review method also lets in-country stakeholders have input in the quality of the new release translation deliverables. The speed and ease of post editing during the review phase further justifies a machine translation approach, because if a human can review and update the results quickly and in the context of the application, an initial human translation effort is redundant. LRM has the capability of delivering context into several translation management systems, however the advances in machine translation quality, the speed and nearly free processing costs make machine translation a better fit for software development.

5. Release Localization at Scale: From a localization perspective, your software is always release-ready with a high degree of quality. Lingoport Suite dashboards give management status overview and drill-down issue visibility across an organization. The Lean Localization process scales exceptionally well to agile teams using many repositories over multiple products and microservices teams, supporting diverse worldwide user locale requirements.

The number one complaint we have heard in all of our software localization industry surveys from software providers is that localization is not well synchronized and understood creating gaps between localization teams and developers. The lean localization process brings localization into continuous engineering and agile principles for fast and efficient delivery.

For presentation of the process, click here:

To discuss how the Lean Localization process might help you, click here

Lingochat | Join L10n Industry Leaders for Peer Discussions

What is Lingochat?

“Lingochat” is a weekly small group discussion, created to share ideas, troubleshoot issues, and help identify to solutions to problems. The groups are intentionally kept small so that everyone has an opportunity to interact and participate, and attendees will primarily be localization specialists and managers. 

There is no cost and the only thing required is that you have a problem you wish to solve, you have solved a problem in your organization, or you wish to brainstorm.  Also, you don’t have to commit to being there every week.  It is just a great way to help each other with solutions.  To join, simply email lingochat@lingoport.com.

A general topic will be published each week as a way to get started.  But what we REALLY want is for the community to suggest topics. 

1st Lingochat Meeting Notes

We had the first Lingochat on the 19th of May, 2020. Below please find the the problems, suggestions, and solutions discussed during the meeting.   

Problem #1

We have a continuous localization process where GitHub is connected to the TMS.

In one product, certain languages require us to deviate from the source content. Our typical issue is between English source and Japanese target.  

We have three different cases:

  1. English strings should not show up in the Japanese locale
  2. There are Japanese strings that need to be there that do not have English source
    1. This case also requires back-translation (see below)
  3. English strings need to have translations that are different

Back-translation:  We currently back translate to English for case 2 because there are times that people in the Japan locale want to view it in English

The way this is handled right now is through override files, and these files contain strings that override the standard strings for specific locales.  But there are many problems with the override files.  They require manual translation and they are hard to maintain over time.

Solution suggestions that could eliminate the override files

  1. Cases 1 and 3 above can be solved by simply modifying the target resource file directly.  In case 1, a null string can be inserted.  In case 3, the modified string can be substituted.
  2. Case 2 might be solved by simply adding a second string in the resource file that is only used for the specific locale.  This approach would require some i18n code changes.  

Problem #2

We don’t have a good testing process for translated strings.  The way we do it today is to ask development to take screenshots, and we send them to the translators.  With dozens or more locales, this can be a lot of screen shots and we get pushback from development.  One of the key issues is with Thailand and spaces.  Spaces can really cause problems with this language.  This is for both mobile and web applications.  

Solution suggestions

  1. Perhaps the screen shot function could be done by a QA or testing organization instead of development.  This might require getting the QA group involved earlier in the process rather than waiting until the localization process is complete.
  2. Pseudolocalization might be used early in the process to make sure page spacing is correct prior to translation.  
  3. Some TMS products allow “fake” spaces to be inserted that then allow a line break.  This might help.

(Note: Lingoport has software solutions for QA context eliminating screen shot hassles and streamlining fixes, but we do not make LingoChat a sales platform…but sorry, I couldn’t resist.)

Problem #3

How much should be budgeted for fixing internationalization (i18n) issues in source code? Is there a standard on how much it costs to fix bugs?

  1. One company did a study on how much it costs to fix an error in the source string when you consider all of the translation work etc.  For example, if there were a missing comma in a source string in a resource file, how much does it cost to fix it for all locales.  That case study was used to help educate the organization on the kind of bugs that should or should not be fixed.
  2. Lingoport services routinely fix i18n bugs in source code.  We find that the cost varies quite a bit depending on the approach.  If it is a fairly large number of bugs, the cost per bug can be fairly small.  But if it is only a few bugs, the cost per bug is much higher due to the overhead of code familiarization, setup, testing, and regression testing.  In addition, the cost is very different if the framework is not set up correctly in the first place.  Changes to the architecture take longer.
  3. One company assigns points to the bugs.  Developers go through a scrubbing process to make sure the points that are assigned are consistent.  There might be a way to gather some of the point information and convert it to a cost.  

Please email lingochat@lingoport.com if you would like to join a future LingoChat.


Webinar: A New & Painless Way to Bring i18n and L10n into Software Development

So you found some internationalization (i18n) issues during Localization (L10n) and you file a bug. Maybe it’s a concatenated string that won’t properly translate, maybe it’s a broken date time format, or maybe it’s some other issue.

The possibilities are long, and let’s face it…whatever the issues are, they can wreak havoc on your localization quality and efficiency. And what’s worse, that bug you filed may simply go into a backlog where it will sit for a while or maybe even forever. Sound familiar?

Check out our May webinar recording “A New & Painless Way to Bring i18n and L10n into Software Development” and discover how to turn this all around…with ease.


View i18n Webinar Recording


Check out our webinar teaser below.

Software Localization Hoops…With Fire

Sure your localization processes may be working…But you need to wait for late in the latest development cycle as strings are still being reworked, AND you don’t want to have to jump through hoops for translations, over and over again.

Or maybe you’re concerned about minimum charges? In any case, we’re excited to demonstrate 2 new solutions to improve and simplify your processes.

Globalyzer i18n Express – Free to run from GitHub (at least for now) where your developers can get immediate i18n feedback as they write code.

IAM Locale Process – Update localization automatically with a Linguistic QA process that mirrors the functional QA that your development teams are already engaging with.

In this webinar you’ll discover a whole new way to localize that lowers costs, increases speed and puts localization right in with the functional testing path, rather than as a separate process.

Remember, if your efforts are not part of the development loop, you’re always going to be an external process.

Live Demonstrations Include

  • I18n in the developer workflow super simplified
  • Immediate L10n gratification, at zero incremental cost
  • Instant L10n review, without cumbersome screenshots, bug management, developer updating


  • Date: May 21st, 2020
  • Time: 9AM Pacific, Noon Eastern, 18:00 CEST
  • Duration: 45 minutes, plus audience Q&A

View i18n Webinar Recording

A Transformative Approach to Software Localization

Last week, Lingoport’s VP of Development, Olivier Libouban presented and demonstrated software that Lingoport will be releasing later this quarter. We are taking a whole new approach to software localization, using automation and integration to make localization instantaneous and review simple, so that localization is finally a true part of development and not just a bolted on process.

This video starts out explaining the problem and developer view, as opposed to the localization perspective, and how to transform localization delivery and impact. Hint, TMSs and translator tools operate outside of the agile development process. They are useful, but not the answer.

We hope you enjoy this presentation and it gives you some ideas.


If you have any questions or would like to learn more about our i18n and L10n solutions email us marketing@lingoport.com.

Webinar: Internationalization (i18n) and Continuous Localization Training

Check out our latest webinar recording, “Internationalization (i18n) and Continuous Localization Training,” where we explore a blend of both technical information and automation solutions, to help bring development and localization together.

View i18n Webinar Recording

Fundamental knowledge gaps between localization and development are unfortunately common in our industry…it’s impact?

Getting products released on-time, appreciated by worldwide users, and ultimately, global revenue.

Exploring i18n  Concepts, Examples, & More

This recording will help you gather more technical knowledge regarding software development and its globalization. Covering a blend of both technical information and automation solutions, you’ll discover how to bring development and localization together.

This webinar training explores:

  • i18n concepts
  • Real-world examples
  • How to tackle L10n updates in an agile environment

An i18n Training Guide That Keeps Giving

Olivier Libouban, Lingoport’s VP of Product Development, has been delivering i18n training for the University of Washington’s localization program. We bring material from that same curriculum to you at no charge.

This is a longer webinar than usual as there is more technical information and examples to teach various i18n concepts. Please reserve two hours.

Agenda Highlights

In this webinar we go over the following key topics:

  • How to automatically handle resource files and other software localization assets
  • What i18n means for localization
  • What i18n means for developers
  • I18n issues, from simple embedded strings to more complex formatting
  • Lots more, all with real world examples


  • Date: April 30th, 2020
  • Time: 9AM Pacific, Noon Eastern, 18:00 CEST
  • Duration: 45 minutes, plus audience Q&A

View i18n Webinar Recording

Webinar: A New Approach to Software Localization

Check out the recording of one of our most exciting webinars to date, “A New Approach to Software Localization,” where we unveil a revolutionary technology that will transform localization processes forever.

View i18n Webinar Recording

After all these years, localization is still the last to the party.

Why? It’s expensive, its complicated, it’s time intensive and inefficient (even with systems and tools)…and did we mention it’s expensive? With the pace of modern development, software localization is a fractured mess, chasing 16 words to update in this file, another 68 words in that file, and a bunch of others scattered throughout repositories.

Luckily, all of that is about to change, and we can’t wait to show you what we’ve been working on. 

Preparing for an Industry Shift in L10n Efficiency

No industry is static. They are continually enhanced by innovations and advancements in technology to improve processes, profitability, scale and more.

  • GPS vs. Maps for Navigation
  • Search Engines vs. Libraries for Research
  • E-commerce vs. Malls for Holiday Shopping
  • Video Streaming vs. Blockbuster for Movies

What do these all have in common? Technology changed long standing processes and enhanced them by making them easier, more efficient and much much faster.

And now…it’s L10n’s turn!

Agenda Highlights

In this webinar we go over the following key topics:

  • A new way to scale up L10n
  • Eliminate L10n friction with development
  • Eliminate L10n backlogs
  • Empower localization QA
  • Transform in-country review
  • Be truly global in each sprint and release
  • Save gobs of budget & time


  • Date: March 26th, 2020
  • Time: 9AM Pacific, Noon Eastern, 18:00 CEST
  • Duration: 45 minutes, plus audience Q&A

View i18n Webinar Recording

Interview with Ben Sargent, Group Q | The Future of G11n and Supporting Technology

As part of Lingoport’s webinar, “How G11N Technologies Adapt to Agile Development Accelerations” we interviewed featured guest speaker, Ben Sargent, Founder and Solutions Architect of Group-Q. Ben provides a sneak peek into his thoughts and predictions around the future of G11n and supporting technology.


1. How has the localization industry evolved since your career began?

Ben Sargent: In the 1990s, LSPs would replicate the build environment and conduct bug tests and fix iterations, then deliver a “golden master” CD-ROM ready for duplication in the kitting factory — the final product would be in a shrink-wrapped box for retail. We’ve come a long way in 20 yrs! When the software publishers adopted the principle of simultaneous ship, with localized versions released the same week as the English, there were no tools for managing software updates. We had thousands of files in hundreds of directories and received updates after beginning the translation. Localization engineers griped they weren’t being engineers any more, instead they had to act as file librarians.

That’s why tools like Lingoport Resource Manager (LRM) are so important – the industry is ridding itself of librarian tasks. LRM seamlessly manages the updates so developers can keep working on code and changing the user experience even after starting the translation process. You can track which strings have changed and immediately push them into the translation workflow. Or you can hold them back and only send updates when you want, if that works better in your process. Automated dashboarding gives you the current status of each job, string, and language. Hence the manual, mundane tasks are no longer part of the workflow. And that’s a good thing for everybody!


2. What would you describe as the leading challenge localization experts face today and in the next 5 years?

Ben Sargent: For the big translation buyers, capacity and throughput is the perennial issue and that has not changed, nor is likely to change. Automation is great, but you still need qualified experts on the receiving end of those workflows. Translation providers have had to absorb massive growth in volume over the years, and machine translation does not change that either. Right now we have adaptive neural machine translation that performs as well as human professionals for first pass translation in some environments. Of course, experienced linguists still need to review and correct the MT output, the same as with human translation. And that’s how we know MT can outperform humans, when the edit distance in the review step is lower and the throughput is faster.

So the biggest challenge still remains, where do you find those linguist resources? How do you train them and organize them and keep them motivated to deliver consistently excellent work under very tight turnaround times to meet the demands of agile and continuous localization? In that sense, technology is the easier part compared to the humans. Even with all the automation, the industry must constantly find, recruit, train and manage linguists to work in an increasingly automated world, where they are expected to add-value to a greater and greater number of words every day. So capacity and throughput are still the fundamentals that both the technologists and the humans strive to overcome.

View i18n Webinar Recording


3. What would you describe as the most impactful L10n technology innovation over the last 5 years and why?

Ben Sargent: Neural MT would have to be the most recent game-changer. But other forms of machine learning or AI are having an impact too. Several Group-Q partners use AI to optimize their production workflow. One example is an algorithm that looks at 30 different data points to screen linguists for job assignments. For some accounts, this is followed up by human vetting and training. In other workflows, it fully automates job assignments.

So-called “lights-out” project management is where the translation management system or TMS parses and preps the content, assigns the best available resources, routes the job through a multi-step workflow, and then post-processes and delivers the content, with zero intervention from a project manager. Lights-out workflows can be rules-driven to start, but eventually all that job data becomes fodder for machine learning, and you end up with AI-driven process management. Last year, CSA Research published data showing that 10% of LSP respondents on a survey were already using some form of machine-learning based AI. Lights-out workflow is used for less than 10% of jobs by most of the companies that have it, but that number is growing.

The other big game-changer is service-oriented architectures, enabling responsive workflows generated in real-time, where each step can be sent to a separate machine actor or human worker, based on the job requirements as interpreted by the machine brain. These systems will determine job requirements from meta data and by reading the content. Lingoport components including Globalyzer and LRM are good examples of services that can be called by such a system. So what we can do with technology now is super fun, super cool, and moreover impactful!


4. If you could only provide one piece of advice to L10n teams, what would it be?

Ben Sargent: Too often client managers are just trying to solve a tactical problem, their hair is on fire, they are overworked and under supported by their own management. Thus, they don’t share key information with their vendors, such as corporate strategic initiatives, organizational transformation, and long-term goals. KPIs are not connected to the larger vision. Budgets and timelines are hidden. Vendors are kept in the dark and get the impression that the client-side managers are not being fully transparent with their challenges. Balancing tactical needs and strategic initiatives begs for closer collaboration between localization buyers, suppliers, and language technology vendors.

At Group-Q, we offer the expertise to solve complex issues by developing bespoke programs, and we work hard to get beyond the tactical needs to also address strategic goals. Good vendors are strategic partners, helping client-side managers shoulder the demands of their markets, the constant pressure for growth, cost reduction, and delivery schedules. The culture that “L10n is a cost center” has not gone away, but the right service provider can help you make the business case for why localization is a revenue driver and customer retention tool. Clients that provide transparency to vendors about corporate initiatives, goals, objectives, and timelines enhance the strategic nature of the localization process. Think back to the days of “waterfall” product cycles — indeed slower development taking products to market, but the teams from all sides worked more cooperatively and planned their goals to meet the market demands. The faster pace makes that harder today, but suppliers want to be engaged and help. With the right inputs, that cooperation adds more value.

One problem is that we still don’t have a career path through-line from localization management to executive management in the enterprise, with the inevitable result that strategic planning is absent or inadequate. At Group-Q, our advice to international product managers, localization directors, and global procurement specialists is to become globalization champions, manage up, and advocate for strategic planning for localization as a driver for global market share and brand equity. We help them develop and present their business case. That’s how we make progress and how we help our clients succeed!


  • Date: February 27th, 2020
  • Time: 9AM Pacific, Noon Eastern, 18:00 CEST
  • Duration: 45 minutes, plus audience Q&A

View i18n Webinar Recording


Group-Q assists companies to solve tactical needs and achieve strategic objectives, tapping multiple eco-systems of localization skills and technologies through our portfolio of partners and preferred suppliers.