skills.rest
logseq
logseqOFFICIAL
Explore all skills by this author →
Website𝕏@logseqGitHub

logseq-i18n

Manage and validate Logseq internationalization keys and translation files.

44.4k|2.8k|Updated May 23, 2020
Search Tags:#ui#localization#translation#i18n#editor#internationalization
One-click install
npx skills add https://github.com/logseq/logseq --skill logseq-i18n
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: logseq-i18n
Source: https://github.com/logseq/logseq/tree/main/.agents/skills/logseq-i18n
Command: npx skills add https://github.com/logseq/logseq --skill logseq-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the process of adding, editing, and reviewing user-facing strings within Logseq, ensuring consistent internationalization across the platform.

Core Features & Use Cases

  • Manage translation keys in src/resources/dicts/ by automating key reuse and creation.
  • Review and validate translation files against i18n standards and best practices.
  • Update translations efficiently for multiple locales, supporting localization workflows.
  • Use Case: Imagine updating all interface labels from English to Chinese; this Skill automates key management and updates translations accordingly.

Quick Start

Use the logseq-i18n skill to review your current translation files and ensure all user interface strings are properly internationalized.

Frequently Asked Questions about logseq-i18n

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

FAQPage Schema
How do I manage translation keys for Logseq UI internationalization?▼

Manage Logseq UI internationalization translation keys by editing files in the `src/resources/dicts/` directory. This approach automates key creation and reuse to maintain consistent localization across the platform.

What is the best way to validate localization files against i18n standards?▼

Validating localization files against i18n standards requires checking them using `*.i18n-lint.toml` configurations. This ensures all user interface strings comply with internationalization best practices before deployment.

Can I update translation files for multiple locales simultaneously in Logseq?▼

Yes, updating translation files for multiple locales simultaneously supports efficient localization workflows. This streamlines translating interface labels across different languages within the Logseq platform.

Do I need to edit source code files to integrate i18n workflows?▼

Yes, integrating i18n workflows requires editing relevant source code files alongside `src/resources/dicts/` and `*.i18n-lint.toml`. This ensures proper mapping and compliance for all UI strings.

Why does internationalization key reuse matter for UI translation?▼

Internationalization key reuse prevents duplicate translation entries and maintains consistency across UI strings. Reusing existing keys automates updates efficiently when changing interface labels across multiple locales.

Related Skills

Explore More Content & Communication Skills→
ericfitzericfitz
2

analyze_localization_files

Analyze i18n file differences and build translation task manifests.

Community
Intermediate
cyhinversecyhinverse

i18n-localization

Detect hardcoded strings and missing locale keys in React, Vue, and Python codebases.

Community
Intermediate
memoirlabsmemoirlabs
6

codegen

Transforms UI trees from json-render specs into framework-ready JSX/TSX source code.

Official
Intermediate
SergeiGolosSergeiGolos
1

i18n-localization

Detect hardcoded strings and manage translation files for i18n compliance.

Community
Intermediate