{"id":6289,"date":"2025-04-24T10:34:28","date_gmt":"2025-04-24T10:34:28","guid":{"rendered":"https:\/\/poeditor.com\/blog\/?p=6289"},"modified":"2025-04-24T10:34:30","modified_gmt":"2025-04-24T10:34:30","slug":"localization-bugs","status":"publish","type":"post","link":"https:\/\/poeditor.com\/blog\/localization-bugs\/","title":{"rendered":"9 Common localization bugs (and how to avoid them)"},"content":{"rendered":"\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"787\" src=\"https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2025\/04\/localization-bugs-1024x787.png\" alt=\"localization bugs\" class=\"wp-image-6319\" srcset=\"https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2025\/04\/localization-bugs-1024x787.png 1024w, https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2025\/04\/localization-bugs-300x230.png 300w, https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2025\/04\/localization-bugs-768x590.png 768w, https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2025\/04\/localization-bugs-1536x1180.png 1536w, https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2025\/04\/localization-bugs.png 2045w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Are you a developer, product manager, or localization engineer? Then you need to understand the most common localization bugs can save you countless hours and protect your brand&#8217;s reputation. Here\u2019s a deep dive into the bugs that haunt localization efforts. We&#8217;ll also tell you how to steer clear of them.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Text expansion and truncation<\/h2>\n\n\n\n<p>One of the most frequent localization bugs is, without a doubt, text truncation caused by language expansion. As we <a href=\"\/blog\/text-expansion-and-contraction-localization\/\">previously discussed<\/a>, when translating from one language to another, the resulting text can be 30\u201350% longer or shorter. <\/p>\n\n\n\n<p>So if your UI isn\u2019t built to accommodate these variations, buttons, labels, and menus can end up with text cut off, overlapping, or overflowing their containers. Here&#8217;s an example: the word \u201cSettings\u201d becomes \u201cEinstellungen\u201d in German\u2014almost twice as long. <\/p>\n\n\n\n<p>Without flexible layouts, what looks perfect in English becomes unusable in translation. To prevent this, developers should use auto-sizing components, flexible containers like flexbox or auto-layouts, and test with <a href=\"\/blog\/what-is-pseudolocalization\/\">pseudo-localization<\/a>, which simulates longer text to catch these issues early.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Hardcoded strings<\/h2>\n\n\n\n<p>Hardcoding strings directly into source code is a classic anti-pattern in localization. When a string like <code>printf(\"Enter password:\");<\/code> is embedded in code, it becomes invisible to localization tools and remains untranslated in the final product. <\/p>\n\n\n\n<p>Possible outcome? Mixed-language experiences where parts of the interface remain in English, regardless of the selected language. Luckily, the solution is simple: externalize all user-facing strings using proper <a href=\"\/localization\/files\">localization files<\/a> (.resx, .po, or .json, and so on). You get efficient <a href=\"https:\/\/poeditor.com\/\">translation management<\/a> but a consistent voice across your application.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Incorrect text direction (LTR\/RTL issues)<\/h2>\n\n\n\n<p>About 215 languages worldwide read from <a href=\"\/blog\/rtl-localization\/\">right to left<\/a>, which doesn&#8217;t just affect the text direction but also the entire user interface. In these cases, navigation elements, icons, and layout structure must be flipped to reflect a mirrored experience. When this isn&#8217;t done, you risk an awkward (and even unreadable) UI. Developers have to make sure that their platforms support bidirectional layouts and test thoroughly with RTL locales using appropriate HTML attributes (like <code>dir=\"rtl\"<\/code>) or platform-specific layout mirroring.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Locale-sensitive formatting errors<\/h2>\n\n\n\n<p><a href=\"\/blog\/date-and-time-localization\/\">Date, time<\/a>, <a href=\"\/blog\/currency-localization\/\">currency<\/a>, and numerical formats differ drastically between regions. If you see \u201c04\/05\/2025\u201d and you live in the United States, you probably read this as April 5th. However, most Europeans will think it&#8217;s May 4th. Similarly, a number written as \u201c1.000\u201d could represent one thousand in Germany, but one in the U.S. <\/p>\n\n\n\n<p>If one tries to manually format these strings, they could end up introducing bugs and confusion. To avoid this, developers should rely on locale-aware formatting libraries such as Moment.js or date-fns, which automatically adjust output based on the user\u2019s locale settings. But it&#8217;s important to test these formats across multiple regions to catch any inconsistencies before release.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Concatenated or split strings<\/h2>\n\n\n\n<p>Concatenating strings in code to form dynamic sentences might work in English but often breaks in translation due to differing grammar rules and word orders. A phrase like <code>\"Hello \" + userName + \", welcome!\"<\/code> seems harmless until you need to translate it into a language where the verb comes before the subject or where adjectives follow nouns. <\/p>\n\n\n\n<p>You may end up with grammatically incorrect or awkward translations. The correct approach is to use full-sentence strings with placeholders\u2014such as <code>\"Hello {userName}, welcome!\"<\/code>\u2014allowing translators to rearrange the sentence structure naturally within a single translatable unit.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Missing or broken translations<\/h2>\n\n\n\n<p>Nothing undermines the credibility of a localized app faster than seeing untranslated strings, placeholder keys, or missing content. These typically appear as <code>translation_missing<\/code> or as blank spaces in the UI. They occur when translation files are incomplete, misconfigured, or not loaded properly. <\/p>\n\n\n\n<p>How to prevent this? Implement robust fallback, track missing keys through logging or error monitoring, and integrate completeness checks into your CI\/CD pipeline. These are great ways to catch the issues before they reach users.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Untranslated third-party content<\/h2>\n\n\n\n<p>Third-party components can be things like chat widgets, analytics popups, or payment modules. Unfortunately, they are often not included in the <a href=\"\/blog\/localization-workflow\/\">localization workflow<\/a>. Users then get an inconsistent experience where parts of the interface remain in the base language while the rest of the app is localized. Choose third-party tools that support localization, and ensure that their configuration files include the correct locale settings. But if translation isn\u2019t available, you could hide or disable those features in specific markets.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Overlooked assets<\/h2>\n\n\n\n<p>Other elements that often gets left behind during localization are embedded PDFs, videos, and text inside images. So if you have onboarding flows, tutorials, or a documentation-heavy app, this is quite problematic. <\/p>\n\n\n\n<p>Prevent this by designing assets <a href=\"http:\/\/blog\/how-to-design-for-localization\/\">with localization in mind<\/a>: use translatable overlays instead of baked-in text, maintain multi-language versions of PDFs, and provide subtitles or dubbed audio for video content. Build a process that integrates these asset types into your translation pipeline from the beginning.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Cultural insensitivity<\/h2>\n\n\n\n<p>What\u2019s appropriate in one culture may be offensive or confusing in another. <a href=\"\/blog\/color-symbolism-localization\/\">Colors<\/a>, emojis, <a href=\"https:\/\/www.businessinsider.com\/hand-gestures-offensive-different-countries-2018-6#the-v-sign-represents-peace--1\" rel=\"nofollow\">gestures<\/a>, idioms, and even animal imagery carry different connotations across cultures. A thumbs-up emoji is a friendly gesture in many Western cultures but \u2014 believe it or not \u2014 is offensive in some Middle Eastern countries. <\/p>\n\n\n\n<p>And then we have <a href=\"\/blog\/translating-idioms\/\">idioms<\/a>. If you say something like \u201chit the ground running\u201d or \u201ckilling two birds with one stone\u201d, it will often not translate well or may be misunderstood. To avoid this, it\u2019s important to work with regional experts, avoid culturally loaded visuals, and aim for neutral, universally understandable content.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Final thoughts<\/h2>\n\n\n\n<p>Now you know how to recognize and avoid these common bugs to keep your product feeling natural and intuitive, no matter where it\u2019s used. Remember, localization is not a \u201cset-it-and-forget-it\u201d task. Don&#8217;t ignore its complexities otherwise you risk alienating your global users.<\/p>\n\n\n<div class=\"call-action my-4 d-flex justify-content-between align-items-md-center gap-4 flex-column flex-lg-row\"><div><h3 class=\"fs-4\">Ready to power up localization?<\/h3><span class=\"fs-6\">Subscribe to the POEditor platform today!<\/span><\/div><a class=\"btn btn-b-primary d-flex align-items-center justify-content-center px-4 py-3 flex-shrink-0\" \n\t\t\t\t\thref=\"https:\/\/poeditor.com\/pricing\/?utm_source=blog&#038;utm_medium=btn&#038;utm_campaign=cta_pricing\">See pricing<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Are you a developer, product manager, or localization engineer? Then you need to understand the most common localization bugs can save you countless hours and protect your brand&#8217;s reputation. Here\u2019s a deep dive into the bugs that haunt localization efforts. We&#8217;ll also tell you how to steer clear of them. Text expansion and truncation One [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17],"tags":[],"class_list":["post-6289","post","type-post","status-publish","format-standard","hentry","category-localization"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.3 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>9 Common localization bugs (and how to avoid them) - POEditor Blog<\/title>\n<meta name=\"description\" content=\"Let&#039;s take a deep dive into the localization bugs that haunt localization efforts and how to proactively avoid them.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/poeditor.com\/blog\/localization-bugs\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"9 Common localization bugs (and how to avoid them) - POEditor Blog\" \/>\n<meta property=\"og:description\" content=\"Let&#039;s take a deep dive into the localization bugs that haunt localization efforts and how to proactively avoid them.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/poeditor.com\/blog\/localization-bugs\/\" \/>\n<meta property=\"og:site_name\" content=\"POEditor Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/POEditor\" \/>\n<meta property=\"article:published_time\" content=\"2025-04-24T10:34:28+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-04-24T10:34:30+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2025\/04\/localization-bugs.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2045\" \/>\n\t<meta property=\"og:image:height\" content=\"1571\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Mirela\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@poeditor\" \/>\n<meta name=\"twitter:site\" content=\"@poeditor\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Mirela\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/localization-bugs\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/localization-bugs\\\/\"},\"author\":{\"name\":\"Mirela\",\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/#\\\/schema\\\/person\\\/6a85f18ccb24eb15a62355922ef34bd9\"},\"headline\":\"9 Common localization bugs (and how to avoid them)\",\"datePublished\":\"2025-04-24T10:34:28+00:00\",\"dateModified\":\"2025-04-24T10:34:30+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/localization-bugs\\\/\"},\"wordCount\":982,\"publisher\":{\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/localization-bugs\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/04\\\/localization-bugs-1024x787.png\",\"articleSection\":[\"Localization\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/localization-bugs\\\/\",\"url\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/localization-bugs\\\/\",\"name\":\"9 Common localization bugs (and how to avoid them) - POEditor Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/localization-bugs\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/localization-bugs\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/04\\\/localization-bugs-1024x787.png\",\"datePublished\":\"2025-04-24T10:34:28+00:00\",\"dateModified\":\"2025-04-24T10:34:30+00:00\",\"description\":\"Let's take a deep dive into the localization bugs that haunt localization efforts and how to proactively avoid them.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/localization-bugs\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/poeditor.com\\\/blog\\\/localization-bugs\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/localization-bugs\\\/#primaryimage\",\"url\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/04\\\/localization-bugs.png\",\"contentUrl\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/04\\\/localization-bugs.png\",\"width\":2045,\"height\":1571,\"caption\":\"localization bugs\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/localization-bugs\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"9 Common localization bugs (and how to avoid them)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/\",\"name\":\"POEditor Blog\",\"description\":\"All about translation and localization management\",\"publisher\":{\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/#organization\",\"name\":\"POEditor\",\"url\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/wp-content\\\/uploads\\\/2019\\\/11\\\/logo_head_512_transparent.png\",\"contentUrl\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/wp-content\\\/uploads\\\/2019\\\/11\\\/logo_head_512_transparent.png\",\"width\":512,\"height\":512,\"caption\":\"POEditor\"},\"image\":{\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/POEditor\",\"https:\\\/\\\/x.com\\\/poeditor\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/poeditor\\\/\",\"https:\\\/\\\/www.youtube.com\\\/channel\\\/UCXAk1u8N49VRMAqNneENCFA\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/#\\\/schema\\\/person\\\/6a85f18ccb24eb15a62355922ef34bd9\",\"name\":\"Mirela\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/48ad917fc39b526701e6811cdd80b11584aeb54b8bc6c2f99a5c6ecf944ed5ae?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/48ad917fc39b526701e6811cdd80b11584aeb54b8bc6c2f99a5c6ecf944ed5ae?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/48ad917fc39b526701e6811cdd80b11584aeb54b8bc6c2f99a5c6ecf944ed5ae?s=96&d=mm&r=g\",\"caption\":\"Mirela\"},\"url\":\"https:\\\/\\\/poeditor.com\\\/blog\\\/author\\\/mirela\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"9 Common localization bugs (and how to avoid them) - POEditor Blog","description":"Let's take a deep dive into the localization bugs that haunt localization efforts and how to proactively avoid them.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/poeditor.com\/blog\/localization-bugs\/","og_locale":"en_US","og_type":"article","og_title":"9 Common localization bugs (and how to avoid them) - POEditor Blog","og_description":"Let's take a deep dive into the localization bugs that haunt localization efforts and how to proactively avoid them.","og_url":"https:\/\/poeditor.com\/blog\/localization-bugs\/","og_site_name":"POEditor Blog","article_publisher":"https:\/\/www.facebook.com\/POEditor","article_published_time":"2025-04-24T10:34:28+00:00","article_modified_time":"2025-04-24T10:34:30+00:00","og_image":[{"width":2045,"height":1571,"url":"https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2025\/04\/localization-bugs.png","type":"image\/png"}],"author":"Mirela","twitter_card":"summary_large_image","twitter_creator":"@poeditor","twitter_site":"@poeditor","twitter_misc":{"Written by":"Mirela","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/poeditor.com\/blog\/localization-bugs\/#article","isPartOf":{"@id":"https:\/\/poeditor.com\/blog\/localization-bugs\/"},"author":{"name":"Mirela","@id":"https:\/\/poeditor.com\/blog\/#\/schema\/person\/6a85f18ccb24eb15a62355922ef34bd9"},"headline":"9 Common localization bugs (and how to avoid them)","datePublished":"2025-04-24T10:34:28+00:00","dateModified":"2025-04-24T10:34:30+00:00","mainEntityOfPage":{"@id":"https:\/\/poeditor.com\/blog\/localization-bugs\/"},"wordCount":982,"publisher":{"@id":"https:\/\/poeditor.com\/blog\/#organization"},"image":{"@id":"https:\/\/poeditor.com\/blog\/localization-bugs\/#primaryimage"},"thumbnailUrl":"https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2025\/04\/localization-bugs-1024x787.png","articleSection":["Localization"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/poeditor.com\/blog\/localization-bugs\/","url":"https:\/\/poeditor.com\/blog\/localization-bugs\/","name":"9 Common localization bugs (and how to avoid them) - POEditor Blog","isPartOf":{"@id":"https:\/\/poeditor.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/poeditor.com\/blog\/localization-bugs\/#primaryimage"},"image":{"@id":"https:\/\/poeditor.com\/blog\/localization-bugs\/#primaryimage"},"thumbnailUrl":"https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2025\/04\/localization-bugs-1024x787.png","datePublished":"2025-04-24T10:34:28+00:00","dateModified":"2025-04-24T10:34:30+00:00","description":"Let's take a deep dive into the localization bugs that haunt localization efforts and how to proactively avoid them.","breadcrumb":{"@id":"https:\/\/poeditor.com\/blog\/localization-bugs\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/poeditor.com\/blog\/localization-bugs\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/poeditor.com\/blog\/localization-bugs\/#primaryimage","url":"https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2025\/04\/localization-bugs.png","contentUrl":"https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2025\/04\/localization-bugs.png","width":2045,"height":1571,"caption":"localization bugs"},{"@type":"BreadcrumbList","@id":"https:\/\/poeditor.com\/blog\/localization-bugs\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/poeditor.com\/blog\/"},{"@type":"ListItem","position":2,"name":"9 Common localization bugs (and how to avoid them)"}]},{"@type":"WebSite","@id":"https:\/\/poeditor.com\/blog\/#website","url":"https:\/\/poeditor.com\/blog\/","name":"POEditor Blog","description":"All about translation and localization management","publisher":{"@id":"https:\/\/poeditor.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/poeditor.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/poeditor.com\/blog\/#organization","name":"POEditor","url":"https:\/\/poeditor.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/poeditor.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2019\/11\/logo_head_512_transparent.png","contentUrl":"https:\/\/poeditor.com\/blog\/wp-content\/uploads\/2019\/11\/logo_head_512_transparent.png","width":512,"height":512,"caption":"POEditor"},"image":{"@id":"https:\/\/poeditor.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/POEditor","https:\/\/x.com\/poeditor","https:\/\/www.linkedin.com\/company\/poeditor\/","https:\/\/www.youtube.com\/channel\/UCXAk1u8N49VRMAqNneENCFA"]},{"@type":"Person","@id":"https:\/\/poeditor.com\/blog\/#\/schema\/person\/6a85f18ccb24eb15a62355922ef34bd9","name":"Mirela","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/48ad917fc39b526701e6811cdd80b11584aeb54b8bc6c2f99a5c6ecf944ed5ae?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/48ad917fc39b526701e6811cdd80b11584aeb54b8bc6c2f99a5c6ecf944ed5ae?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/48ad917fc39b526701e6811cdd80b11584aeb54b8bc6c2f99a5c6ecf944ed5ae?s=96&d=mm&r=g","caption":"Mirela"},"url":"https:\/\/poeditor.com\/blog\/author\/mirela\/"}]}},"_links":{"self":[{"href":"https:\/\/poeditor.com\/blog\/wp-json\/wp\/v2\/posts\/6289","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/poeditor.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/poeditor.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/poeditor.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/poeditor.com\/blog\/wp-json\/wp\/v2\/comments?post=6289"}],"version-history":[{"count":11,"href":"https:\/\/poeditor.com\/blog\/wp-json\/wp\/v2\/posts\/6289\/revisions"}],"predecessor-version":[{"id":6325,"href":"https:\/\/poeditor.com\/blog\/wp-json\/wp\/v2\/posts\/6289\/revisions\/6325"}],"wp:attachment":[{"href":"https:\/\/poeditor.com\/blog\/wp-json\/wp\/v2\/media?parent=6289"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/poeditor.com\/blog\/wp-json\/wp\/v2\/categories?post=6289"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/poeditor.com\/blog\/wp-json\/wp\/v2\/tags?post=6289"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}