{"id":22215,"date":"2026-06-25T13:45:39","date_gmt":"2026-06-25T11:45:39","guid":{"rendered":"https:\/\/asialocalize.com\/?p=22215"},"modified":"2026-06-25T17:33:03","modified_gmt":"2026-06-25T15:33:03","slug":"ios-internationalization","status":"publish","type":"post","link":"https:\/\/asialocalize.com\/ja\/blog\/ios-internationalization\/","title":{"rendered":"iOS Internationalization: A Practical Guide for Localization Leads"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Every localization lead has gone through this experience before. After the release of the app \u2013 polished, fast, English-language-only content, and now everybody assumes that set too. Then, after days or even weeks have passed, you receive a message on Slack, saying: &#8220;I need 10 languages by Q3.&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That is the moment where iOS internationalization moves from being an optional feature to becoming a minefield on your roadmap.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Once internationalization isn&#8217;t a part of the process from the beginning, mobile app localization quickly becomes a feat of controlled damage limitation. Buttons overflow. Auto Layout implodes beneath German nouns. Arabic flips your entire UI unexpectedly. Dates, currency values, and plural rules don\u2019t behave how you\u2019d expect.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In short, your &#8220;easy&#8221; language launch turns into a never-ending fire drill of fixes and schedule misses, just when your stakeholders expect you to deliver rapidly.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The risk is real. CSA Research continues to show that 76% of users buy more when it is in their native language, and 40% will not buy it at all when they don\u2019t. For engineering teams building global iOS apps, this gap turns into unrealized adoption.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is precisely why good internationalization is a localization strategy. Apple gives engineering teams robust tools-<strong>based internationalization<\/strong>, Auto Layout, <strong>string catalogs,<\/strong> and locale-aware APIs, but those tools are useless if the localization team and the engineers do not create a plan upfront that the tools can support before the end of Q3.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This guide is written for localization and product leaders who do not wish to &#8220;fix strings later&#8221;. We will show how iOS internationalization really works, where teams commonly make the mistake, and how to build an iOS pipeline that can easily scale across languages.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What iOS Internationalization Really Means&nbsp;<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Within the Apple ecosystem, internationalization and localization are NOT interchangeable concepts, and mixing them up will ensure a release goes down a rabbit hole guaranteed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Internationalization is the foundation. Localization is what you build on top of it. When teams do it backward, each additional language added exponentially increases complexity rather than being a linearly scaling change.&nbsp;&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Let\u2019s reset the terms the Apple way, the way localization leads need to understand them.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Internationalization vs. Localization in Apple\u2019s World<\/strong><\/h3>\n\n\n\n<figure class=\"wp-block-image size-large\"><img fetchpriority=\"high\" decoding=\"async\" width=\"977\" height=\"1024\" src=\"https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image3-977x1024.png\" alt=\"\" class=\"wp-image-23445\" srcset=\"https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image3-977x1024.png 977w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image3-286x300.png 286w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image3-768x805.png 768w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image3-1466x1536.png 1466w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image3.png 1527w\" sizes=\"(max-width: 977px) 100vw, 977px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Apple is particularly clear on this point in its documentation:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Internationalization (i18n) is the design and development of your app to make it adaptable to new languages, cultures, and scripts without code changes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Localization (l10n) is the process of providing translations and culturally appropriate assets for each specific market.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On a technical level, internationalization will ask:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Can this UI scale up when text expands 30-40% in length?<\/li>\n\n\n\n<li>Does this app have RTL and bidirectional text support?<\/li>\n\n\n\n<li>Do dates, currency symbols, number formats, and plural forms vary depending on the user\u2019s locale?<\/li>\n\n\n\n<li>Is it possible to translate the application without changing any source code?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Whereas localization will ask:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How should this string be translated into Japanese?<\/li>\n\n\n\n<li>Are there images or colors that need to change per locale?<\/li>\n\n\n\n<li>Are there regional differences in legal requirements or UX standards?<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Xcode &amp; Foundation APIs that Make Internationalization Work Right<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The iOS platform has a well-developed infrastructure for internationalization, but it only functions as intended when developers decide to take advantage of it upfront.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">From a tooling standpoint, Xcode localization features include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Base Internationalization to separate the UI structure from localized text<\/li>\n\n\n\n<li>Strings Catalogs (.xcstrings files) for centralizing text storage and pluralization<\/li>\n\n\n\n<li>Auto Layout &amp; Size Classes to expand the app UI<\/li>\n\n\n\n<li>Localized asset catalogs<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">From a foundation standpoint, <strong>Foundation APIs <\/strong>provide the following:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Locale, Calendar, and DateFormatter classes for regional-specific formatting<\/li>\n\n\n\n<li>NumberFormatter for currency, decimals, and number groupings<\/li>\n\n\n\n<li>In-app native plurals using .stringsdict files<\/li>\n\n\n\n<li>Native RTL mirroring for Arabic &amp; Hebrew languages<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Proper implementation of these components ensures that developers can have one codebase working across different countries. Ignoring this approach leads to fragile designs, hardcoded strings, and assumptions about English-only UI.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Unfortunately, fixing these issues post-release comes with a hefty price tag. According to the Systems Sciences Institute at IBM, fixing bugs after software release is up to <a href=\"https:\/\/www.blackduck.com\/blog\/cost-to-fix-bugs-during-each-sdlc-phase.html\" target=\"_blank\" rel=\"noopener\">15x<\/a> more expensive than addressing them during development.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Why Internationalization Should Precede Localization<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In terms of localization delivery, this is where the timelines make or break.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a well-internationalized iOS application:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The translators have access to clear, standalone strings.<\/li>\n\n\n\n<li>Contextual information remains intact through comments and key structuring.<\/li>\n\n\n\n<li>Testing is concentrated on language functionality rather than correcting the UI.<\/li>\n\n\n\n<li>Adding more languages to the list requires minimal adjustment within the localization pipeline.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">For an under-internationalized application:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The strings are embedded in the code.<\/li>\n\n\n\n<li>UI trimming occurs after translation is done.<\/li>\n\n\n\n<li>Engineers find themselves fixing the same issues repeatedly.<\/li>\n\n\n\n<li>The localization process becomes increasingly delayed without initially drawing attention.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The financial implications are undeniable. Based on data from Shopify, businesses utilizing localized personalization strategies experience conversion rate increases by <a href=\"https:\/\/localizejs.com\/articles\/localization-trends\" target=\"_blank\" rel=\"noopener\">10-15%.<\/a> The lesson is straightforward for any iOS development team: the ability to support multiple languages can directly impact profitability.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">See<a href=\"https:\/\/asialocalize.com\/blog\/localization-examples\/\"> Localization Examples <\/a>Done Right.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The Practical iOS Internationalization Workflow for Localization Leads to Really Execute!<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">As a localization lead, you know that iOS internationalization happens exactly where strategy meets implementation. The clearer the workflow, the less exciting your launches will be, only in a good way! If there is a lot of confusion, then each new language turns into a nightmare.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What follows is a<strong> step-by-step iOS internationalization workflow<\/strong> geared towards localization leads.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 1 \u2013 Lock Markets, Locales, and UX Expectations Early<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Decide what \u201cdone\u201d looks like before code or translation starts.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Before touching strings or tools, clarify the expansion scope in business and UX terms.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What to define upfront<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Target markets and locales (language + region)<\/li>\n\n\n\n<li>Writing direction (LTR vs RTL)<\/li>\n\n\n\n<li>App Store localization scope vs in-app localization<\/li>\n\n\n\n<li>Locale-specific UX expectations (date formats, currencies, calendars, units)<\/li>\n\n\n\n<li>Regulatory or cultural constraints that affect content<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 2 \u2013 Audit the App for i18n Readiness<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">An internationalization audit tells you whether the app can <em>survive<\/em> localization.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Key checks to run with engineering<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Base Internationalization enabled in Xcode<\/li>\n\n\n\n<li>Auto Layout fully implemented (no fixed-width UI)<\/li>\n\n\n\n<li>No hard-coded strings in code or storyboards<\/li>\n\n\n\n<li>RTL layout mirroring tested<\/li>\n\n\n\n<li>Locale-aware APIs used for dates, numbers, and currencies<\/li>\n\n\n\n<li>Pluralization handled via .stringsdict, not concatenation<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 3 \u2013 Align with Developers on String Architecture<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><em>If strings are messy, everything downstream suffers.<\/em>This is where localization leads earn trust with engineering.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Alignment checklist<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Are strings managed through <strong>String Catalogs (<\/strong><strong>.xcstrings<\/strong><strong>)<\/strong>?<\/li>\n\n\n\n<li>Are keys stable and human-readable?<\/li>\n\n\n\n<li>Are developer comments added for context?<\/li>\n\n\n\n<li>Are plurals and gender handled structurally?<\/li>\n\n\n\n<li>Are screenshots or UI references attached to strings?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Clean string architecture accelerates translation and reduces QA churn.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 4 \u2013 Operationalize XLIFF, TMS, and Vendor Collaboration<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">At this stage, internationalization meets production reality.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>What a healthy pipeline includes<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Consistent <strong>XLIFF export<\/strong>\/import from Xcode<\/li>\n\n\n\n<li>Version-controlled string files<\/li>\n\n\n\n<li>Automated handoff into your TMS<\/li>\n\n\n\n<li>Terminology and style guides embedded in the workflow<\/li>\n\n\n\n<li>Clear ownership for string freezes and late changes<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 5 \u2013 Build a Repeatable QA and Release Loop<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Final QA is where internationalization decisions show their value or their cracks.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>QA essentials<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pseudo-localization testing before real languages<\/li>\n\n\n\n<li>Language-specific UI reviews (especially long and RTL languages)<\/li>\n\n\n\n<li>Linguistic QA tied to real devices, not screenshots alone<\/li>\n\n\n\n<li>App Store metadata checks per locale<\/li>\n\n\n\n<li>A documented sign-off process before submission<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Apps that skip structured QA often pay in public. App Store reviews consistently cite broken localization as a UX issue, directly affecting ratings and retention, especially in non-English markets.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/asialocalize.com\/industries\/business-translation-services\/\"><strong>Business Translation Services<\/strong><\/a><strong> That Keep Your Product Launch-Ready.<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Quiet Killers of Your iOS Internationalization Efforts<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">iOS localization efforts rarely fail due to inaccurate translations. Instead, it is the typical development process shortcuts that work well in English but fall flat in other languages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Apple, localization platforms, and iOS professionals have long pointed out these concerns, yet teams continue to stumble into them when time runs out.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The following is a list of some of the most prevalent iOS internationalization mistakes, why they pose such a risk, and how to avoid them.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. Hard-Coded Strings Buried in Code<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If strings reside within Swift files or storyboards without being associated with localized strings, each localization effort is doubled yet tripled.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"307\" src=\"https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image1-1024x307.png\" alt=\"\" class=\"wp-image-23447\" srcset=\"https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image1-1024x307.png 1024w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image1-300x90.png 300w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image1-768x230.png 768w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image1.png 1510w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How it\u2019s broken<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Strings are often overlooked when exporting.<\/li>\n\n\n\n<li>They don\u2019t show up on translators\u2019 radars.<\/li>\n\n\n\n<li>\u201cQuick fixes\u201d pull engineers away from their main tasks.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Solution<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Force string management with String Catalogs (.xcstrings).<\/li>\n\n\n\n<li>Prevent merging with hardcoded user strings.<\/li>\n\n\n\n<li>String extraction must be part of what \u201cdone\u201d means.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. Building Sentences by Concatenation<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Attaching pieces to make something like &#8220;You have&#8221; + count + &#8220;messages&#8221; requires an understanding of word order, grammar, and agreement conventions that are not transferable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why it hurts<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Word order is language-specific.<\/li>\n\n\n\n<li>Gender and number information disappear.<\/li>\n\n\n\n<li>Meaning cannot be reconstituted.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Solution<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use sentences with blanks.<\/li>\n\n\n\n<li>Let professional translators dictate sentence structure.<\/li>\n\n\n\n<li>Always use whole sentences.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Ignoring Pluralization and Grammatical Rules<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In English, there are two forms of the plural. In Arabic, there are six forms. Russian has many plural forms. Several languages demand grammatical agreement according to gender and number.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>How it impacts you<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>&#8220;1 item&#8221; irritates the developer as it goes live.<\/li>\n\n\n\n<li>Poor UX in markets other than English.<\/li>\n\n\n\n<li>Fixes involve redefining strings, rather than translating.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Solution<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use stringsdict for pluralization.<\/li>\n\n\n\n<li>Let iOS automatically deal with locale conventions.<\/li>\n\n\n\n<li>Don\u2019t hack around with logic for pluralization.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. Forgetting Right-to-Left Layouts<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Arabic and Hebrew need UI mirroring. Limiting testing to left-to-right leads to false satisfaction.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"438\" src=\"https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image2-1024x438.png\" alt=\"\" class=\"wp-image-23449\" srcset=\"https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image2-1024x438.png 1024w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image2-300x128.png 300w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image2-768x328.png 768w, https:\/\/asialocalize.com\/wp-content\/uploads\/2026\/03\/image2.png 1200w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why it&#8217;s bad<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Navigation is disrupted.<\/li>\n\n\n\n<li>Icons get reversed.<\/li>\n\n\n\n<li>Hierarchy disappears.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Solution<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Start RTL testing early.<\/li>\n\n\n\n<li>Utilize Auto Layout and semantic attributes.<\/li>\n\n\n\n<li>Stay away from absolutes.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This theme has been consistent throughout the article: localization becomes easier and more predictable when internationalization is handled as the foundation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">UI stays intact. Engineers maintain focus. Translators know exactly what they&#8217;re dealing with. Releases become a non-crisis event. And new markets become \u201cnot risky\u201d.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">And this is precisely the stage at which localization ceases being an expense and begins acting like a growth driver.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At AsiaLocalize, this is where we come into play. We partner with product, engineering, and localization departments to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Perform iOS app internationalization audit.<\/li>\n\n\n\n<li>Ensure proper string architecture and alignment with XLIFF workflows and TMS pipelines.<\/li>\n\n\n\n<li>Provide smooth handovers between development and translation teams.<\/li>\n\n\n\n<li>Ensure proper app localization that will withstand any international expansion, language after language.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If future plans include entering new markets, adding new languages, and\/or quickening release cycles, then internationalization is the area that requires particular attention.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Which is why we exist to help you get there right and once!<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Find out more about <a href=\"https:\/\/asialocalize.com\/industries\/technical-translation-services\/\">Technical Translation Services<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Every localization lead has gone through this experience before. After the release of the app \u2013 polished, fast&hellip;<\/p>\n","protected":false},"author":10,"featured_media":22216,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[84],"tags":[],"class_list":["post-22215","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-translation-qa","category-84","description-off"],"_links":{"self":[{"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/posts\/22215","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=22215"}],"version-history":[{"count":1,"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/posts\/22215\/revisions"}],"predecessor-version":[{"id":23451,"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/posts\/22215\/revisions\/23451"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/media\/22216"}],"wp:attachment":[{"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/media?parent=22215"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/categories?post=22215"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/asialocalize.com\/ja\/wp-json\/wp\/v2\/tags?post=22215"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}