i18n-text-extract

Extract user-visible source-language text from program files for internationalization.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/SkylerCook/imedical.agents --skill i18n-text-extract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n-text-extract
Source: https://github.com/SkylerCook/imedical.agents/tree/main/plugins/i18n-iris-plugin/skills/i18n-text-extract
Command: npx skills add https://github.com/SkylerCook/imedical.agents --skill i18n-text-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Extracts user-visible source-language text from frontend or backend program files, simplifying the translation process into target-language i18n term tables.

Core Features & Use Cases

  • Text Extraction: Extracts text from program files for internationalization.
  • Translation Support: Generates translation tables for efficient localization.
  • Use Case: Ideal for software developers who need to manage and update text strings across multiple languages in their projects.

Quick Start

Use the i18n-text-extract skill with the target language code and scope, such as 'i18n-text-extract -targetLanguage en -scope directory /path/to/files'.

Frequently Asked Questions about i18n-text-extract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract user-visible text for software localization?

To extract user-visible text for software localization, use an automated tool that scans frontend and backend source files to identify translatable strings and generate target-language i18n term tables.

What is the best way to automate i18n text extraction from source code?

The best way to automate i18n text extraction from source code is by running a script that processes your project files based on predefined i18n rules and language catalogs, outputting structured translation tables for efficient localization.

Do I need an i18n project profile to extract translatable strings?

Yes, you need an i18n project profile, i18n rules, and a language catalog to effectively extract translatable strings. These inputs guide the extraction process to correctly identify and map user-visible text.

Can I extract strings from both frontend and backend program files?

Yes, you can extract strings from both frontend and backend program files. The extraction process is designed to handle user-visible source-language text across various system layers for comprehensive internationalization.

How do I generate a translation table from extracted source-language text?

You generate a translation table from extracted source-language text by running an extraction process that parses your program files and outputs the identified strings into a structured target-language i18n term table format.

What are the limitations of automated source code text extraction?

The limitations of automated source code text extraction include its dependency on predefined i18n rules, an accurate i18n project profile, and a language catalog to function properly. Without these inputs, the extraction may not correctly identify all user-visible text.