{"id":22523,"date":"2026-06-09T16:51:01","date_gmt":"2026-06-09T14:51:01","guid":{"rendered":"https:\/\/asialocalize.com\/?p=22523"},"modified":"2026-06-09T16:51:02","modified_gmt":"2026-06-09T14:51:02","slug":"translation-quality-assurance","status":"publish","type":"post","link":"https:\/\/asialocalize.com\/ja\/blog\/translation-quality-assurance\/","title":{"rendered":"Translation Quality Assurance: A Practical QA Checklist for Error-Free Localization"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Before anyone argues about tone, terminology, or \u201cstyle preferences,\u201d <strong>Translation Quality Assurance<\/strong> quietly decides whether your content will work\u2014or fail\u2014once it leaves your source language.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Because poor translation doesn\u2019t usually explode on launch day. It leaks. It shows up as customer hesitation, compliance questions, internal rework cycles, and brand messages that sound <em>almost<\/em> right but not quite trustworthy.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The risk is measurable. 76% of consumers prefer to buy products with information in their own language, and 40% say they won\u2019t purchase at all if the content isn\u2019t localized\u2014even when price and product quality are equal.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A single missed nuance can trigger legal review delays, regulatory pushback, or expensive post-launch corrections, often costing more than getting it right before release.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you\u2019ve ever fixed the same translation twice\u2014or wondered why \u201capproved\u201d content still feels off, this checklist will give you the answer.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Translation Quality Assurance by Content Type<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Not every translation needs the same QA depth. A product UI, legal document, medical label, and marketing page each carry different risks. The best translation quality assurance process adjusts the review level based on content visibility, complexity, and potential business impact.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Content Type<\/th><th>Main QA Risk<\/th><th>Recommended QA Level<\/th><\/tr><\/thead><tbody><tr><td>Website content<\/td><td>Tone, SEO meaning, cultural fit, formatting<\/td><td>Linguistic review + locale review + SEO checks<\/td><\/tr><tr><td>Software and app UI<\/td><td>Truncation, placeholders, broken strings, poor context<\/td><td>In-context review + functional localization QA<\/td><\/tr><tr><td>Legal documents<\/td><td>Ambiguity, clause meaning, jurisdiction-specific wording<\/td><td>Expert legal review + terminology validation<\/td><\/tr><tr><td>Medical and life sciences content<\/td><td>Safety, terminology, regulatory meaning<\/td><td>Subject-matter review + strict LQA scoring<\/td><\/tr><tr><td>Marketing content<\/td><td>Brand voice, persuasion, cultural relevance<\/td><td>Transcreation review + native market validation<\/td><\/tr><tr><td>Technical documentation<\/td><td>Terminology, consistency, formatting, usability<\/td><td>CAT-tool QA + glossary checks + layout review<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This is where translation quality assurance becomes more than a final proofreading step. It helps teams choose the right level of control before the project begins, so high-risk content receives deeper review while lower-risk content moves faster.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What Is Translation Quality Assurance?<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In mature localization programs, TQA serves as the framework that ensures translated content is accurate, consistent, compliant, and relevant to real users in the target market. It\u2019s what turns translation from a deliverable into a reliable business asset.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At its core, <strong>Translation Quality Assurance<\/strong> is a structured process used to verify that translated content meets predefined linguistic, technical, and contextual standards <em>before<\/em> it reaches the end user.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A solid TQA framework typically evaluates whether the translation is:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Accurate<\/strong> \u2013 Faithful to the source meaning, intent, and tone<\/li>\n\n\n\n<li><strong>Consistent<\/strong> \u2013 Terminology, style, and phrasing align across files, products, and releases<\/li>\n\n\n\n<li><strong>Fit for purpose<\/strong> \u2013 Appropriate for the target audience, culture, and use case<\/li>\n\n\n\n<li><strong>Technically sound<\/strong> \u2013 Free of formatting, truncation, encoding, or UI-related issues<\/li>\n\n\n\n<li><strong>Compliant<\/strong> \u2013 Aligned with regulatory, legal, or brand requirements where applicable<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This aligns closely with the quality principles defined in ISO 17100, the international standard for translation services, which emphasizes qualified linguists, defined workflows, and systematic quality control<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1024\" height=\"538\" src=\"https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-02-1024x538.webp\" alt=\"Translation quality control vs quality assurance showing output checks and process improvement\" class=\"wp-image-22528\" srcset=\"https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-02-1024x538.webp 1024w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-02-300x158.webp 300w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-02-768x403.webp 768w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-02.webp 1200w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Translation Quality Control vs. Translation Quality Assurance: Checking the Output vs. Protecting the Outcome<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you\u2019ve worked in localization long enough, you\u2019ve probably heard the terms <em>Quality Control<\/em> and <em>Quality Assurance<\/em> used interchangeably. They\u2019re not. And confusing them is one of the fastest ways teams end up fixing the same problems release after release.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At a glance, the difference sounds subtle. In practice, it defines whether quality is reactive or designed into the process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Quality Control tells you <em>what went wrong<\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Quality Assurance helps you understand <em>why it went wrong and how to stop it from happening again<\/em>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Translation Quality Control (QC) focuses on the finished output.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It typically involves spot checks or post-translation reviews that look for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Linguistic errors (grammar, spelling, mistranslations)<\/li>\n\n\n\n<li>Terminology mismatches<\/li>\n\n\n\n<li>Formatting or layout issues<\/li>\n\n\n\n<li>Missing or truncated content<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">QC answers an important question:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Does this specific translation meet our basic quality expectations right now?<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead of only checking results, QA evaluates the <strong>entire translation ecosystem<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Source content readiness<\/li>\n\n\n\n<li>Briefing quality and context availability<\/li>\n\n\n\n<li>Terminology governance and style guidance<\/li>\n\n\n\n<li>Linguist qualifications and specialization<\/li>\n\n\n\n<li>Tooling, workflows, and handoffs<\/li>\n\n\n\n<li>Review criteria and feedback loops<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">QA asks different questions:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Are translators set up to succeed before they start?<\/li>\n\n\n\n<li>Are errors traceable to unclear source text, missing glossaries, or poor handover?<\/li>\n\n\n\n<li>Are reviewer comments being analyzed\u2014or just applied and forgotten?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The Translation Quality Assurance Workflow<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When translation quality breaks, it rarely fails at a single point. It fails across a chain of decisions\u2014some made before translation begins, others during production, review, or handoff. By the time a problem is visible to stakeholders or users, it has usually passed through several stages unchecked.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The process below breaks Translation Quality Assurance into practical stages that reflect how professional localization teams actually work. Each step has a clear purpose, a specific risk it addresses, and a measurable impact on consistency, cost, and brand credibility.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Once you see how the pieces connect, the checklist stops feeling like bureaucracy and starts feeling like control.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"538\" src=\"https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-03-1024x538.webp\" alt=\"Translation quality assurance workflow from preparation and production to linguistic review and final checks\" class=\"wp-image-22530\" srcset=\"https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-03-1024x538.webp 1024w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-03-300x158.webp 300w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-03-768x403.webp 768w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-03.webp 1200w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. Preparation: Where Most Quality Is Won\u2014or Lost<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The most common QA failure happens before translation even starts.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Preparation ensures translators aren\u2019t forced to guess\u2014and guessing is where inconsistency, rework, and tone drift begin.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A strong prep stage includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Source content cleanup<\/strong>: resolving ambiguity, inconsistencies, or last-minute copy changes<\/li>\n\n\n\n<li><strong>Style guides<\/strong> that define tone, formality, punctuation, and brand voice<\/li>\n\n\n\n<li><strong>Approved terminology<\/strong> aligned with product, legal, and marketing teams<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This stage directly supports the quality principles defined in <strong>ISO 17100<\/strong>, which emphasize clear specifications and reference materials as prerequisites for quality outcomes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. Production: Quality at Scale with the Right Guardrails<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">During production, quality depends on <strong>controlled reuse<\/strong>, not repetition.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Professional teams rely on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>CAT tools<\/strong> to enforce terminology and structural consistency<\/li>\n\n\n\n<li><strong>Translation memory (TM)<\/strong> to reuse validated segments and reduce variation<\/li>\n\n\n\n<li><strong>In-context constraints<\/strong> that protect formatting, tags, and variables<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Review: Linguistic Validation<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Review works best when it\u2019s <strong>targeted<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead of reviewing everything the same way, mature QA programs apply:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Editing and proofreading<\/strong> by qualified native reviewers<\/li>\n\n\n\n<li><strong>LQA sampling<\/strong>, using defined error categories and severity levels<\/li>\n\n\n\n<li><strong>Objective scoring models<\/strong> to track trends over time\u2014not subjective preferences<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Because Quality Is Earned in the Details.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Explore our<\/strong><a href=\"https:\/\/asialocalize.com\/editing-and-proofreading\/\"> <strong>editing and proofreading<\/strong><\/a><strong> services.<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. Final Checks: Automated QA and Layout Validation<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Before delivery, automated QA acts as a final safety net.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This stage typically includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Automated checks for numbers, tags, punctuation, and consistency<\/li>\n\n\n\n<li>Encoding and character validation (critical for non-Latin scripts)<\/li>\n\n\n\n<li><strong>DTP and layout checks<\/strong> to catch truncation, overflow, or UI breakage<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These checks don\u2019t replace human review\u2014they protect it. They ensure that approved linguistic quality survives real-world formats and platforms.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. The Feedback Loop: Where QA Becomes Strategy<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">This is the step many teams skip\u2014and the one that separates QA from QC.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A real <strong>Translation Quality Assurance process<\/strong> closes the loop:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reviewer feedback feeds back into <strong>terminology and translation memory updates.<\/strong><\/li>\n\n\n\n<li>Recurring issues trigger <strong>rule adjustments, tooling changes, or training.<\/strong><\/li>\n\n\n\n<li>Quality data is tracked across releases to <strong>identify areas for improvement.<\/strong><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Our structured<\/strong><a href=\"https:\/\/asialocalize.com\/translation-process\/\"> <strong>translation process<\/strong><\/a><strong> aligns people, tools, and QA checks.<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Linguistic Quality Assurance: How LQA Measures Translation Quality<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">At some point, every localization team hits the same wall: <em>\u201cWe know something feels off\u2014but how bad is it, really?\u201d<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">LQA is the measurement layer inside <strong>Translation Quality Assurance<\/strong>. It takes subjective feedback, <em>\u201cthis sounds wrong,\u201d \u201cthe tone is off,\u201d \u201cterminology isn\u2019t consistent,\u201d<\/em> and turns it into structured data that teams can analyze, compare, and act on.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">LQA exists to catch those issues <em>before<\/em> users do and to explain <em>why<\/em> they happen.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>What Linguistic Quality Assurance Actually Measures<\/strong><\/h3>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"538\" src=\"https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-04-1024x538.webp\" alt=\"Linguistic quality assurance measures including terminology, accuracy, fluency, locale, style, and severity scoring\" class=\"wp-image-22532\" srcset=\"https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-04-1024x538.webp 1024w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-04-300x158.webp 300w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-04-768x403.webp 768w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/04\/Translation-Quality-Assurance-04.webp 1200w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Most professional LQA frameworks measure errors across three dimensions:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. Error Categories<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Errors are classified by type so teams can see <em>patterns<\/em>. Widely adopted models group issues into categories like:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Terminology<\/strong> \u2013 incorrect or inconsistent use of approved terms<\/li>\n\n\n\n<li><strong>Accuracy<\/strong> \u2013 mistranslations, omissions, or additions that distort meaning<\/li>\n\n\n\n<li><strong>Fluency<\/strong> \u2013 grammar, syntax, or unnatural phrasing in the target language<\/li>\n\n\n\n<li><strong>Locale conventions<\/strong> \u2013 date formats, numbers, cultural norms, regulatory usage<\/li>\n\n\n\n<li><strong>Style and tone<\/strong> \u2013 deviations from brand voice or audience expectations<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. Severity Levels<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Not all errors carry the same weight. LQA distinguishes between:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Critical errors<\/strong> that change meaning or introduce legal, safety, or reputational risk<\/li>\n\n\n\n<li><strong>Major errors<\/strong> that significantly affect clarity or user trust<\/li>\n\n\n\n<li><strong>Minor errors<\/strong> that don\u2019t block understanding but reduce polish<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Scoring and Thresholds<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Once errors are categorized and weighted, LQA produces a <strong>quality score<\/strong>. This allows teams to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Track quality trends across languages, vendors, or releases<\/li>\n\n\n\n<li>Set acceptance thresholds for different content types<\/li>\n\n\n\n<li>Identify recurring weak points that require process changes<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Translation QA Checklist: The Non-Negotiables to Check Every Time<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This checklist distills the essentials. It\u2019s what you should verify every single time, across languages and content types.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Terminology &amp; Glossary Alignment<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Approved terms are used consistently across files<\/li>\n\n\n\n<li>No unauthorized synonyms for product, legal, or brand-critical terms<\/li>\n\n\n\n<li>Updates from recent releases are reflected in the glossary and TM<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Numbers, Dates, Units, and Measurements<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Numbers match the source exactly (including decimals and separators)<\/li>\n\n\n\n<li>Dates, currencies, and units follow <strong>local conventions<\/strong>, not source habits<\/li>\n\n\n\n<li>No hardcoded values carried over incorrectly<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Tags, Placeholders, and Formatting<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>All tags, variables, and placeholders are intact and correctly positioned<\/li>\n\n\n\n<li>No broken strings, missing brackets, or reordered variables<\/li>\n\n\n\n<li>Formatting survives copy expansion or contraction<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Consistency Across Files and Screens<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Repeated strings read the same way everywhere they appear<\/li>\n\n\n\n<li>Tone and phrasing are stable across modules, screens, or documents<\/li>\n\n\n\n<li>No unexplained variation caused by parallel translation or rushed updates<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Locale and Cultural Fit<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Content respects local norms, formality levels, and expectations<\/li>\n\n\n\n<li>No culturally awkward phrasing, imagery references, or metaphors<\/li>\n\n\n\n<li>Regulatory or market-specific wording is appropriate<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Final DTP and Visual Checks<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>No text overflow, truncation, or layout breaks<\/li>\n\n\n\n<li>Line breaks, alignment, and reading order make sense in context<\/li>\n\n\n\n<li>Visual hierarchy still works after translation<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The difference between content that <em>passes review<\/em> and content that <em>earns trust<\/em> is almost always the same: a Translation Quality Assurance process that\u2019s intentional, repeatable, and grounded in how real users read, buy, and decide.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At AsiaLocalize, Translation Quality Assurance is embedded across our workflows, from source preparation and terminology governance to CAT-tool-driven consistency, structured linguistic QA, and feedback loops that actually reduce rework over time. Our teams design processes that prevent them from recurring.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/asialocalize.com\/professional-translation-services\/\"><strong>Professional Translation Services<\/strong><\/a><strong> Backed by Real QA.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Before anyone argues about tone, terminology, or \u201cstyle preferences,\u201d Translation Quality Assurance quietly de&hellip;<\/p>\n","protected":false},"author":10,"featured_media":22526,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[84,85],"tags":[148,147,149,138,141,145,142,144,146,140,139,143,150],"class_list":["post-22523","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-translation-qa","category-localization","tag-cat-tools","tag-dtp-checks","tag-iso-17100","tag-linguistic-quality-assurance","tag-localization-checklist","tag-localization-qa","tag-lqa","tag-terminology-management","tag-translation-memory","tag-translation-qa","tag-translation-quality-assurance","tag-translation-quality-control","tag-translation-review","category-84","category-85","description-off"],"_links":{"self":[{"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/posts\/22523","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/comments?post=22523"}],"version-history":[{"count":2,"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/posts\/22523\/revisions"}],"predecessor-version":[{"id":22953,"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/posts\/22523\/revisions\/22953"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/media\/22526"}],"wp:attachment":[{"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/media?parent=22523"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/categories?post=22523"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/tags?post=22523"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}