「translation」の検索結果

Provides bidirectional translation (Chinese/English), grammar checking, and sentence polishing. Supports specific tense constraints, context-aware tone adjustment, and natural expression optimization. Outputs direct text without formatting.

日本語の概要は準備中です。原文の説明を表示しています。

Maintain Operately translations when adding or changing user-visible copy, fixing missing translations, or adding a supported language. Covers shared Gettext/i18next catalogs, glossaries, generation, and completeness checks; excludes translating user-authored content or general prose outside the product.

日本語の概要は準備中です。原文の説明を表示しています。

Routes CUT/FastCUT/SinCUT workflows, dataset preparation, and launcher presets for the contrastive-unpaired-translation repository.

日本語の概要は準備中です。原文の説明を表示しています。

Translate text between languages with cultural adaptation, terminology consistency, and support for multiple document types including technical docs, marketing copy, and UI strings. Use when the user requests translation or provides relevant inputs for this workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Use when user asks to translate videos, dub video content, or localize videos into other languages. Translate videos with AI-powered dubbing using iFlytek (Xfei) Video Translation API. Supports video language translation, voice dubbing, multilingual video localization, 视频翻译, 视频配音, 视频本地化. Features task creation, task list, task details retrieval. Ideal for content creators and localization teams.

日本語の概要は準備中です。原文の説明を表示しています。

Build and evaluate low-latency spoken, multimodal, and translation experiences with Google Gemini Live API and Gemini Enterprise Agent Platform Live API. Use when a media-production or voice-agent workflow needs real-time audio input/output, barge-in, voice configuration, live transcription, live translation, tool/function calling during a spoken session, WebSocket session design, latency QA, quotas/cost review, or Google/Vertex data-governance tradeoffs.

日本語の概要は準備中です。原文の説明を表示しています。

Professional translation and localization for 8 languages (ES, JA, FR, DE, PT, ZH, KO, AR). Covers tone matrix, formality levels, i18n patterns (react-intl, i18next, ICU), RTL layout, cultural adaptation, and locale formatting. Use when user asks to translate text, localize an app, adapt tone, review translations, add i18n, or set up RTL.

日本語の概要は準備中です。原文の説明を表示しています。

当用户写出的内容读起来像产品公告/官方更新(如"我们发布了X""支持Y功能""效果很好")，需要翻译成读者能拿走的外部语言时调用。也适用于:用户问"怎么把公告式表达改成强推文""这条推文为什么没人理"(若原因是只讲自己不讲读者)、"怎么把功能介绍写得吸引人"。Trigger 词:公告式表达/内部语言/外部语言/帮助式表达/announcement tone/helpful expression/show don't tell/translate to reader value。不适用于:从零起草新内容(用 x-short-content-craft)、检查内容五件套完备性(用 x-five-piece-checklist)、评估内容值不值得发(用 x-four-saves)。

日本語の概要は準備中です。原文の説明を表示しています。

Regenerate the translations POT file after modifying English user-facing documentation. Use when docs/src/**/*.md files outside contributing/ are changed. Skip when only docs/src/contributing/** changes.

日本語の概要は準備中です。原文の説明を表示しています。

Fix intermittent `{:no_translation, :unicode, :latin1}` crashes in Elixir escript daemons that use length-prefixed framed IPC on stdin/stdout. Use when: (1) daemon worker crashes only on some input files, usually ones with non-ASCII bytes (kanji, cyrillic, emoji); (2) error surfaces as `Protocol error` from daemon's error branch or as garbled frame-length bytes seen by the orchestrator/client side; (3) standalone one-shot mode works fine on the same input but multi-request daemon mode fails; (4) `IO.binread(:stdio, N)` returns `{:error, {:no_translation, :unicode, :latin1}}` despite the "bin" prefix suggesting it should be encoding-agnostic. Root cause is the escript default `:standard_io` encoding — it's `:unicode`, and `IO.binread` still routes through the io_server, which translates bytes to codepoints and errors when raw binary frames contain invalid UTF-8 sequences.

日本語の概要は準備中です。原文の説明を表示しています。

Build a new-topic PPTX by reusing an existing reference deck's template (layouts / footers / fonts / palette) while replacing all content from primary sources. Use when "use this product deck's look for a different product deck", "use this deck as template for new topic", "参照デックの体裁で別内容を作る", "既存 PPTX を流用して別テーマで作り直す". Not for deck translation, from-scratch generation, or outline-only planning.

Convert web articles or blog posts into slides through a content.json pipeline, translate or rebuild existing PPTX files onto a template, and edit an already-open PowerPoint deck with COM Automation (RefURL, overflow review). Use for article-to-slides conversion, deck translation, template-based rebuilds, or live COM editing of an open deck. Not for simply reading, inspecting, or lightly editing a .pptx file. Triggers on 記事をスライド化, スライド翻訳, 開いているパワポを編集, COM自動化, RefURL, content.json.

"Apply Actor-Network Theory (Latour, Callon) to trace how human and non-human actors (actants) form networks through translation processes. Use this skill when the user needs to map sociotechnical assemblages, analyze how innovations stabilize or fail through network-building, trace the four moments of translation (problematization, interessement, enrollment, mobilization), or when they ask 'how did this technology become accepted', 'who and what holds this network together', or 'why did this innovation fail to gain traction'.".

日本語の概要は準備中です。原文の説明を表示しています。

Migrating Classic Knowledge (KnowledgeArticleVersion / Article Types) to Lightning Knowledge (Knowledge__kav with record types): article-type-to-record-type mapping, multi-language translation preservation, data category re-architecture, file attachment porting, version and publication-state retention, channel visibility translation, and downstream Case Feed / Community / Bot rewiring. NOT for new Lightning Knowledge setup or editorial publishing workflow design (use admin/knowledge-base-administration).

日本語の概要は準備中です。原文の説明を表示しています。

Migrating Classic Custom Buttons (Detail Page Buttons, List Buttons, Mass Action Buttons) and JavaScript Buttons to Lightning Quick Actions, Screen Flow Actions, LWC Quick Actions, and headless Quick Actions. Covers JavaScript-button-to-action translation patterns (sforce.apex.execute → Apex action, navigation alerts → toast events, MassAction.update → record-collection processing), URL button translation, and the irreversible loss of Classic JavaScript button capability in Lightning. NOT for new Quick Action design (use admin/global-actions-and-quick-actions) or Lightning record page composition (use admin/lightning-app-builder-advanced).

日本語の概要は準備中です。原文の説明を表示しています。

Internationalize JavaScript apps with i18next. Use when adding translations, handling plurals, loading locale files dynamically, or i18n for React/Vue/Node.

日本語の概要は準備中です。原文の説明を表示しています。

Professional translation expert covering techniques, cultural adaptation, and language pair strategies

日本語の概要は準備中です。原文の説明を表示しています。

Safely localize unknown Unity games, especially Japanese-to-Chinese projects. Use to discover Unity version/layout/backend, migrate translations across game versions, extract occurrence-mapped text from serialized assets, embedded CSV, bytecode, UI, Localization StringTables, Utage, or middleware, bridge rows through AiNiee-style translation, validate and transactionally write approved candidates, audit residual and runtime-only text or AutoTranslator diffs, diagnose TMP fonts and Addressables/IL2CPP failures, locate saves, or acceptance-test SHA-verified patches.

日本語の概要は準備中です。原文の説明を表示しています。

Translate books, documents, AiNiee projects, Unity localization caches, or flat MTool JSON dictionaries end to end on the coding agent itself without the AiNiee app. Use for requests such as "用 agent 翻译这本书", "把 epub 翻译了", "翻译 Unity CSV/cache", "把这个 MTool JSON 翻译了", or "AiNiee-style translation" that need a locked glossary, resumable batches or bounded subagent groups, terminology consistency, source-aware QA, validated cache writeback, and export. For MTool, preserve the left JSON key as immutable source text and write only the right value as translation.

日本語の概要は準備中です。原文の説明を表示しています。

Text and document translation with REST-style clients.

日本語の概要は準備中です。原文の説明を表示しています。

Expert-level molecular biology knowledge. Use when working with DNA replication, transcription, translation, gene regulation, cloning, PCR, sequencing, CRISPR, epigenetics, or molecular techniques. Also use when the user mentions 'DNA replication', 'transcription', 'translation', 'gene expression', 'PCR', 'cloning', 'restriction enzyme', 'gel electrophoresis', 'Western blot', 'CRISPR', 'epigenetics', 'promoter', 'enhancer', or 'RNA splicing'.

日本語の概要は準備中です。原文の説明を表示しています。

Manually run the extended DeepSeek Harness bilingual-document workflow, including generated briefings, delegated prose translation, whole-document translation, and scoped pairing verification.

日本語の概要は準備中です。原文の説明を表示しています。

Translating between French and US English. Use for i18n strings, a French reply to the owner, or reviewing an existing translation.

日本語の概要は準備中です。原文の説明を表示しています。

Review translated documentation for content fidelity — detect injected, off-topic, or unauthorized content by comparing against the English source. Use when reviewing translation PRs or translated docs.

日本語の概要は準備中です。原文の説明を表示しています。