Why Localization Tools Are Failing Buyers and How to Fix It with Boryana Nenova

Introduction to Agile Localization Podcast

Host and Guest Introduction

• The podcast is hosted by Stefan Yui, focusing on strategies for fast, scalable, and efficient localization.

• Today's guest is Borana Ninova from the Czech Republic, discussing the shift in localization tools from translator-centric to buyer-centric approaches.

Borana's Background

• Borana introduces herself as a Bulgarian with two decades of experience in the localization industry.

• She has transitioned from being a translator to project management and program management roles, providing insights from both perspectives.

Evolution of Localization Tools

Early Experiences

• Borana began her career in 2003 after completing her degree in English language, initially working with desktop-based software localization.

• Her early experiences included using basic tools like Excel before transitioning to more advanced translation memory systems (TMS).

Key Features of Modern Localization Tools

Buyer Perspective on Tool Features

• Connectivity is identified as the top criterion for buyers; integration with existing tools should be seamless and require minimal effort.

• Recent integrations include email builders, Google Drive, proprietary content management systems (CMS), and design tools like Figma.

Translator Perspective on Tool Features

• From a translator's viewpoint, quality handling of text is paramount; they prioritize features that enhance their work rather than just speed.

• A balance between speed for buyers and quality for linguists is essential; both perspectives must be considered when developing tools.

Developer Considerations in Localization Tools

Technical Requirements

Understanding the Role of Tools in Localization

Importance of Tool Integration

• The speaker emphasizes the need for an easy interface and communication between tools, highlighting Figma's code-oriented nature.

• Proper segmentation and parsing rules are crucial for transferring text accurately, especially when dealing with line breaks within segments.

• Tools must support exporting and importing texts across multiple languages, accommodating various scripts and characters.

Trade-offs Between Developer-first Tools and Traditional Systems

• A discussion on trade-offs reveals that developer-first tools may lack a linguistic perspective compared to traditional translation memory systems.

• The speaker shares their background in manual translation before the advent of translation memories, emphasizing the evolution of tools from desktop to cloud-based solutions.

• The shift towards cloud-based systems has changed user needs significantly; modern tools cater to different use cases than those developed earlier.

Perspectives on Localization Tools

• Modern localization tools often reflect a developer-centric approach, which can overlook linguistic considerations important for translators.

• While older tools were less accommodating to developers, newer ones sometimes miss out on providing necessary features for linguists.

• Localization has become more agile and continuous due to advancements in technology.

Anecdotes from Early Localization Experiences

• The speaker recounts their early experiences at eTranslate, where project managers faced delays due to reliance on spreadsheets for website localization projects.

• They proposed creating a database solution over a weekend to streamline processes instead of waiting for spreadsheet access.

Evolution of File Management Systems

• An oversimplified comparison is made between Dropbox as an early file management system and modern version control systems like Git.

• Traditional tools were designed for different customer needs focused on static documents rather than continuous workflows prevalent today.

Addressing Translator Needs with Modern Tools

• The conversation shifts towards how translators can be satisfied while meeting buyer-side demands; gaps in tool functionality are identified.

Quality Assurance in Linguistic Tools

Importance of Quality Assurance (QA) in Translation

• QA is a primary concern for linguists, who seek more advanced features in translation tools.

• Modern translations require complex checks, such as verifying the presence of all necessary elements and ensuring accuracy.

Linguistic Tool Features

• Effective glossary management and user-friendly interfaces are crucial for quickly finding relevant results.

• Ideal tools should consolidate resources on one screen with keyboard shortcuts to enhance efficiency.

Machine Translation Expectations

• Users desire high-quality machine translation that is continuously improved through machine learning.

• There is often a lack of investment in training linguists to effectively use available systems, leading to underutilization of features.

Collaboration Among Translators

• Instant messaging capabilities within translation management systems can facilitate direct feedback among team members.

• In multilingual projects, shared visibility of questions enhances collaboration and understanding among linguists.

AI Integration in Translation Tools

Current State of AI in Localization

• The conversation around AI integration has evolved slowly; initial expectations have not yet been fully realized.

• Despite advancements, significant improvements in AI tools remain limited over time.

Challenges with Language Quality

• Improvements in language processing quality have plateaued; notable differences exist between major languages like Spanish and French versus smaller languages.

Continuous Localization and Optimization Challenges

The Gap Between Buyer Expectations and Linguist Realities

• The buyer expects the linguists to perform their tasks effectively, but there is a disconnect in the actual situation faced by linguists.

• Continuous localization has evolved into a continuous optimization loop, with new tools and features emerging frequently, raising questions about the longevity of processes established years ago.

Integration Challenges in Established Workflows

• Larger companies hesitate to implement new tools due to fears of disrupting long-standing workflows that have developed over decades.

• Migration to new systems can be painful, requiring significant changes in workflows that may not be well-documented or remembered.

Evolving Tools and Security Considerations

• As companies grow, the tools they use also evolve; older integrations may no longer meet current security requirements.

• Increased demand for security necessitates higher contracts and more robust solutions to comply with modern standards.

The Need for Comprehensive Translation Management Systems (TMS)

• A TMS should encompass all aspects of project management alongside translation capabilities, reducing reliance on emails and improving workflow efficiency.

• There is a desire for TMS solutions that integrate project management features such as tracking team availability without manual checks.

Self-Service Localization Goals

• Aiming for self-service localization involves creating an environment where stakeholders can easily access information about ongoing projects.

Insights on Localization Tools

Discussion on Technical Insights

• The conversation highlights the excitement of discussing technical aspects related to localization tools, indicating a shared enthusiasm between the speakers.

• The speaker expresses gratitude for the insights provided regarding what buyers and translators seek in localization tools, emphasizing the value of this feedback for technical teams at Crowden.

• Acknowledgment is made towards Borana's contributions, suggesting that further discussions could be beneficial in the future, indicating an ongoing interest in collaboration.

Conclusion of Podcast Episode

• The episode wraps up with a call to action for listeners to subscribe for more insights on managing multilingual content efficiently, reinforcing the podcast's educational purpose.