docs: add documentation for 7 new nodes#105
Merged
Merged
Conversation
Added documentation for 7 new nodes: - Save3DAdvanced - SaveGaussianSplat - SavePointCloud - SaveText - SeedVR2TemporalChunk - SeedVR2TemporalMerge - TextOverlay Each with en.md + 11 language translations. Also includes minor updates to 11 existing node docs.
|
Warning Review limit reached
Next review available in: 8 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (22)
📝 WalkthroughWalkthroughThis PR adds and revises embedded node documentation across multiple languages, covering readable titles, input/output schemas, behavioral constraints, localized pages, editor notes, and source fingerprints. ChangesDocumentation updates
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 110
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/en.md`:
- Line 11: Update the prompt parameter description in the GeminiVideoOmni
documentation to explicitly state that validation occurs after stripping
whitespace and that whitespace-only prompts are rejected, while preserving the
minimum one-character requirement.
In `@comfyui_embedded_docs/docs/Load3DAdvanced/en.md`:
- Line 1: Update the document title in the Load3D Advanced documentation to
remove the level-one Markdown heading marker, using the project’s allowed
heading level or plain human-readable title while preserving the existing title
text.
In `@comfyui_embedded_docs/docs/LTXVContextWindows/en.md`:
- Line 1: Update the LTXV Context Windows document title by removing the
level-one Markdown heading marker and using an allowed lower-level heading while
preserving the human-readable title.
In `@comfyui_embedded_docs/docs/LumaRay32ExtendVideoNode/en.md`:
- Line 1: Update the document’s top heading from a level-one heading to a
level-two heading, preserving the existing title text and ensuring node
documentation does not use level-one headings.
In `@comfyui_embedded_docs/docs/LumaRay32ImageToVideoNode/en.md`:
- Line 1: Change the document’s top heading for “Luma Ray 3.2 Image to Video”
from a level-one heading to a non-level-one heading, preserving the existing
title text and documentation structure.
In `@comfyui_embedded_docs/docs/LumaRay32KeyframeNode/en.md`:
- Line 1: Change the document title in LumaRay32KeyframeNode/en.md from a
level-one heading to a non-level-one heading, preserving the existing “Luma Ray
3.2 Keyframe” title text.
In `@comfyui_embedded_docs/docs/LumaRay32KeyframesToVideoNode/en.md`:
- Line 1: Replace the level-one heading in the Luma Ray 3.2 Keyframes to Video
documentation with a non-level-one heading, preserving the page title and
required document structure.
In `@comfyui_embedded_docs/docs/LumaRay32TextToVideoNode/en.md`:
- Line 1: Change the top-level heading in the Luma Ray 3.2 Text to Video
documentation to a non-level-one heading, preserving the existing title text and
documentation structure.
In `@comfyui_embedded_docs/docs/LumaRay32VideoEditNode/en.md`:
- Line 1: Update the document title in the Luma Ray 3.2 Video Edit documentation
to remove the level-one Markdown heading marker, using an allowed lower heading
level while preserving the title text.
In `@comfyui_embedded_docs/docs/LumaRay32VideoReframeNode/en.md`:
- Line 1: Update the title in the Luma Ray 3.2 Video Reframe documentation by
removing the level-one heading marker and using an allowed heading level while
preserving the renamed title text.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/ar.md`:
- Around line 1-27: Update the Save3DAdvanced documentation by removing the
level-one “# Save3DAdvanced” heading and using a permitted lower-level heading.
Add localized sections for Function Description, Working Principle, Input
Parameter Description, Output Result Description, and Usage Suggestions,
preserving and organizing the existing description, inputs, and outputs under
the appropriate sections.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/en.md`:
- Around line 1-27: Update the Save3DAdvanced documentation by removing or
changing the prohibited level-one “Save3DAdvanced” heading and adding the
required Function Description, Working Principle, Input Parameter Description,
Output Result Description, and Usage Suggestions sections. Preserve the existing
parameter and output details while organizing them under the appropriate
required sections.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/es.md`:
- Around line 1-27: Actualiza la documentación de Save3DAdvanced para eliminar
el encabezado de nivel uno “# Save3DAdvanced” y añadir secciones equivalentes a
Function Description, Working Principle, Input Parameter Description, Output
Result Description y Usage Suggestions, conservando la información existente de
entradas y salidas dentro de las secciones correspondientes.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/fa.md`:
- Around line 1-27: صفحه مستندات Save3DAdvanced را با حذف عنوان سطحیک `#
Save3DAdvanced` بهروزرسانی کنید و بخشهای معادل بومیِ Function Description،
Working Principle، Input Parameter Description، Output Result Description و
Usage Suggestions را اضافه کنید؛ محتوای فعلی ورودیها و خروجیها را در بخشهای
مربوطه حفظ و سازماندهی کنید.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/fr.md`:
- Around line 1-27: Update the Save3DAdvanced documentation by removing the
top-level “# Save3DAdvanced” heading and adding localized sections for Function
Description, Working Principle, Input Parameter Description, Output Result
Description, and Usage Suggestions, while preserving the existing parameter and
output details.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/ja.md`:
- Around line 1-27: Save3DAdvanced の日本語ドキュメントからレベル1見出し「#
Save3DAdvanced」を削除し、既存内容を機能説明、動作原理、入力パラメータ説明、出力結果説明、使用上の提案に相当する日本語セクションへ整理・追加してください。既存の入力・出力情報を適切なセクションへ保持し、必須セクションをすべて含めてください。
In `@comfyui_embedded_docs/docs/Save3DAdvanced/ko.md`:
- Around line 1-27: Update the Save3DAdvanced Korean documentation by removing
the level-1 “Save3DAdvanced” heading and adding Korean sections for Function
Description, Working Principle, Input Parameter Description, Output Result
Description, and Usage Suggestions. Preserve the existing parameter and output
details while organizing them under the appropriate required sections.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/pt-BR.md`:
- Around line 1-27: Atualize a documentação de Save3DAdvanced removendo o título
de nível um “Save3DAdvanced” e adicionando seções equivalentes a Function
Description, Working Principle, Input Parameter Description, Output Result
Description e Usage Suggestions, preservando e reorganizando o conteúdo
existente nessas seções.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/ru.md`:
- Line 3: Remove the authoring note beginning with «Вот перевод документации»
from the published Russian documentation, so the page starts directly with the
node description.
- Around line 1-27: Restructure the Save3DAdvanced documentation by removing the
top-level H1 and adding dedicated Russian sections for Function Description,
Working Principle, Output Result Description, and Usage Suggestions, using the
repository’s required localized template terminology. Preserve the existing
input and output tables while placing them within the appropriate documentation
structure.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/tr.md`:
- Around line 1-25: Restructure the Save3DAdvanced documentation by removing the
H1 heading and adding the template-required localized sections for Function
Description, Working Principle, Output Result Description, and Usage
Suggestions. Preserve the existing localized input and output tables while
organizing the page under the required documentation structure.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/zh-TW.md`:
- Around line 1-25: Update the Save3DAdvanced documentation structure: remove
the level-one “Save3DAdvanced” heading, add the required Function Description,
Working Principle, Output Result Description, and Usage Suggestions sections
with appropriate Traditional Chinese content, and correct the malformed “## ##
輸入” and “## ## 輸出” headings to “## 輸入” and “## 輸出”.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/zh.md`:
- Around line 1-25: Update the Save3DAdvanced documentation structure: remove
the level-one heading, add sections for Function Description, Working Principle,
Output Result Description, and Usage Suggestions, and correct the malformed “##
## 输入” and “## ## 输出” headings to valid level-two headings while preserving the
existing tables.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/ar.md`:
- Line 3: In the Arabic description, update the demonstrative before “العقدة”
from “هذا” to “هذه”, leaving the rest of the text unchanged.
- Around line 1-27: أعد هيكلة توثيق SaveGaussianSplat وفق قالب التوثيق المطلوب:
أزل عنوان H1، وأضف الأقسام المترجمة المخصصة لوصف الوظيفة، ومبدأ العمل، ووصف
نتائج المخرجات، واقتراحات الاستخدام، مع الحفاظ على معلومات المدخلات والمخرجات
الحالية.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/en.md`:
- Around line 1-27: Restructure the SaveGaussianSplat documentation by removing
the H1 heading and adding the required Function Description, Working Principle,
Output Result Description, and Usage Suggestions sections. Preserve the existing
input and output details while organizing them according to the standard
documentation template.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/es.md`:
- Around line 1-27: Actualiza la documentación de SaveGaussianSplat para
eliminar el encabezado H1 y seguir la estructura requerida de la plantilla.
Añade las secciones localizadas equivalentes a Descripción de la función,
Principio de funcionamiento, Descripción del resultado de salida y Sugerencias
de uso, conservando las tablas existentes de entradas y salidas.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/fa.md`:
- Around line 1-27: Restructure the SaveGaussianSplat documentation to follow
the required localized template: remove the H1 heading and add dedicated
sections for Function Description, Working Principle, Output Result Description,
and Usage Suggestions using their Persian equivalents. Preserve the existing
inputs and outputs tables, incorporating their descriptions into the appropriate
sections.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/fr.md`:
- Around line 1-30: Restructure the SaveGaussianSplat documentation by replacing
the H1 with a permitted lower-level heading and adding the required Working
Principle and Usage Suggestions sections. Organize the existing overview,
Entrées, and Sorties content under the appropriate conceptual sections, while
preserving the localized section titles and unchanged English data types.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/ja.md`:
- Around line 1-30: The SaveGaussianSplat documentation needs the standardized
structure: remove the level-one “SaveGaussianSplat” heading and add the required
Japanese Working Principle and Usage Suggestions sections. Preserve the existing
Japanese input/output headings, descriptions, and English data-type names while
integrating the new sections into the page structure.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/ko.md`:
- Around line 1-30: Update the SaveGaussianSplat documentation structure by
replacing the level-one “SaveGaussianSplat” heading with a permitted lower-level
heading, then add the required “Working Principle” and “Usage Suggestions”
sections with relevant content. Preserve the existing 입력 and 출력 sections, Korean
descriptions, and English data type names.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/pt-BR.md`:
- Around line 1-30: Update the SaveGaussianSplat documentation by removing the
level-one “SaveGaussianSplat” heading, adding the required “Working Principle”
and “Usage Suggestions” sections, and restructuring the existing description
into the required layout. Preserve the standardized “Entradas” and “Saídas”
headings, all documented values, and the English data types unchanged.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/ru.md`:
- Around line 1-25: Обновите страницу SaveGaussianSplat: удалите H1, добавьте
локализованные разделы для описания функции, принципа работы, входных
параметров, выходного результата и рекомендаций по использованию, сохранив
соответствующее русское содержание. Переименуйте заголовки таблиц с «Входные
параметры» и «Выходные параметры» в «## Входы» и «## Выходы» соответственно.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/tr.md`:
- Around line 1-25: SaveGaussianSplat dokümantasyonundan mevcut “#
SaveGaussianSplat” H1 başlığını kaldırın ve Function Description, Working
Principle, Input Parameter Description, Output Result Description ile Usage
Suggestions bölümlerinin Türkçe karşılıklarını ekleyin. Mevcut giriş ve çıktı
tablolarını koruyarak bu bölümleri düğümün işlevi, çalışma mantığı,
parametreleri, sonuçları ve kullanım önerilerini açıklayacak şekilde tamamlayın.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/zh-TW.md`:
- Around line 1-25: 修正 SaveGaussianSplat 文件的標題結構：移除頂部 H1「SaveGaussianSplat」，將「##
## 輸入」和「## ## 輸出」改為「## 輸入」和「## 輸出」，並補上五個必要文件章節的繁體中文本地化內容。
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/zh.md`:
- Around line 1-25: Update the SaveGaussianSplat documentation headings from “##
## 输入/输出” to valid “## 输入/输出” headings, then add localized sections for Function
Description, Working Principle, Input Parameter Description, Output Result
Description, and Usage Suggestions. Keep the existing H1 heading and do not
introduce another H1.
In `@comfyui_embedded_docs/docs/SavePointCloud/ar.md`:
- Around line 1-25: Update the SavePointCloud documentation structure by
removing the “# SavePointCloud” H1 and adding Arabic-localized sections for
Function Description, Working Principle, Input Parameter Description, Output
Result Description, and Usage Suggestions, while preserving the existing input
and output tables.
In `@comfyui_embedded_docs/docs/SavePointCloud/en.md`:
- Around line 1-25: Reorganize the SavePointCloud documentation without a
level-one heading into the required five sections: Function Description, Working
Principle, Input Parameter Description, Output Result Description, and Usage
Suggestions. Retain the standardized Inputs and Outputs headings within the
appropriate sections, preserving all existing parameter details and adding
concise explanations where needed.
In `@comfyui_embedded_docs/docs/SavePointCloud/es.md`:
- Around line 1-25: Reorganiza la documentación de SavePointCloud para eliminar
el encabezado H1 y usar la estructura requerida de cinco secciones: descripción
de la función, principio de funcionamiento, descripción de parámetros de
entrada, descripción de resultados de salida y sugerencias de uso, con sus
equivalentes en español. Conserva la información existente de entradas y salidas
dentro de las secciones correspondientes y añade el contenido descriptivo
necesario para completar cada sección.
In `@comfyui_embedded_docs/docs/SavePointCloud/fa.md`:
- Around line 1-25: Restructure the SavePointCloud documentation to use the
required five-part node documentation format, removing the level-one
“SavePointCloud” heading and adding each section with its localized equivalent.
Move the existing description, input table, and output table into the
appropriate sections while preserving their Persian content and localized
input/output headings.
In `@comfyui_embedded_docs/docs/SavePointCloud/fr.md`:
- Around line 1-25: Reorganize the SavePointCloud documentation to remove the
level-one “SavePointCloud” heading and follow the required five-part node
documentation structure, using the established French section equivalents.
Preserve the existing “Entrées” and “Sorties” sections and their tables, while
adding or relocating the description and remaining required sections according
to the standard format.
In `@comfyui_embedded_docs/docs/SavePointCloud/ja.md`:
- Line 3: Remove the translation-pipeline preamble `以下が翻訳結果です。` from the
document so the rendered page begins directly with the user-facing
SavePointCloud documentation.
- Around line 1-29: Reorganize the SavePointCloud documentation to remove the
level-one heading and follow the required five-part node documentation
structure, adding the corresponding Japanese section headings and content.
Preserve the existing standardized 入力 and 出力 sections, translating or adapting
the remaining required sections as needed.
In `@comfyui_embedded_docs/docs/SavePointCloud/ko.md`:
- Around line 1-25: Restructure the Korean SavePointCloud documentation by
removing the level-one “SavePointCloud” heading and adding the required Function
Description, Working Principle, Output Result Description, and Usage Suggestions
sections. Retain the standardized 입력 and 출력 headings and preserve the existing
node parameter and output details.
In `@comfyui_embedded_docs/docs/SavePointCloud/pt-BR.md`:
- Around line 1-30: Reestruture a documentação do nó SavePointCloud sem o
cabeçalho de nível um, mantendo os títulos padronizados “Entradas” e “Saídas”.
Adicione as seções obrigatórias “Descrição da Função”, “Princípio de
Funcionamento”, “Descrição do Resultado da Saída” e “Sugestões de Uso”, em
português, preservando as informações existentes e organizando-as na estrutura
exigida.
In `@comfyui_embedded_docs/docs/SavePointCloud/ru.md`:
- Around line 1-34: Restructure the Russian SavePointCloud documentation to
remove the level-one “SavePointCloud” heading, the translation-process sentence,
and generation commentary. Begin directly with the node description and organize
the existing content under the required documentation sections, preserving the
documented inputs and outputs.
In `@comfyui_embedded_docs/docs/SavePointCloud/tr.md`:
- Around line 1-30: Restructure the Turkish SavePointCloud documentation by
removing the level-one “SavePointCloud” heading and adding the required Function
Description, Working Principle, Output Result Description, and Usage Suggestions
sections. Preserve the existing node details and standardized data-type names
such as FILE3D_POINT_CLOUD_ANY, LOAD3D_MODEL_INFO, and LOAD3D_CAMERA.
In `@comfyui_embedded_docs/docs/SavePointCloud/zh-TW.md`:
- Around line 1-30: Restructure the SavePointCloud documentation without a
level-one heading, adding the required Function Description, Working Principle,
Output Result Description, and Usage Suggestions sections in Traditional
Chinese. Preserve the existing localized 輸入 and 輸出 headings and their tables,
and retain the source fingerprint metadata.
In `@comfyui_embedded_docs/docs/SavePointCloud/zh.md`:
- Around line 5-17: Remove the duplicated heading markers in the SavePointCloud
documentation by changing the headings `## ## 输入` and `## ## 输出` to `## 输入` and
`## 输出`, preserving the surrounding table content.
- Around line 1-30: The SavePointCloud Chinese documentation needs the
standardized node-documentation structure. Remove the level-one “SavePointCloud”
heading, use the required “输入” and “输出” headings without duplicated heading
markers, and add the required sections “功能描述”, “工作原理”, “输出结果描述”, and “使用建议” with
content matching the node’s point-cloud saving behavior.
In `@comfyui_embedded_docs/docs/SaveText/ar.md`:
- Line 5: In the Arabic documentation sentence, update the verb agreement from
“يقوم” to “تقوم” in the description beginning with “عقدة حفظ النص,” leaving the
rest of the text unchanged.
- Around line 1-24: Restructure the Arabic SaveText documentation to use the
required node-documentation sections without a level-one heading, and make the
page begin directly with the node description. Remove the translation-process
sentence beginning “إليك ترجمة الوثيقة التقنية” and retain only user-facing
documentation content, including the relevant inputs and outputs.
In `@comfyui_embedded_docs/docs/SaveText/en.md`:
- Around line 1-22: Restructure the canonical SaveText documentation by removing
the level-one “SaveText” heading and adding the required Function Description,
Working Principle, Output Result Description, and Usage Suggestions sections.
Preserve the existing inputs, outputs, and format behavior while aligning the
page with the standard node-documentation structure before updating
translations.
In `@comfyui_embedded_docs/docs/SaveText/es.md`:
- Around line 1-22: Reorganize the SaveText documentation around the required
structure by replacing the H1 with the appropriate non-level-one title, adding
Working Principle and Usage Suggestions sections, and placing the existing
description and input/output tables under the relevant headings. Preserve the
standardized “Entradas” and “Salidas” headings and keep data types in English.
In `@comfyui_embedded_docs/docs/SaveText/fa.md`:
- Around line 1-22: Update the SaveText documentation to remove the level-one
“SaveText” heading and follow the required documentation template, adding
localized sections for Working Principle and Usage Suggestions while preserving
the existing localized content and English data types. Keep the input/output
tables and source fingerprint intact.
In `@comfyui_embedded_docs/docs/SaveText/fr.md`:
- Around line 1-22: Réorganisez la documentation de SaveText en supprimant le
titre H1 et en ajoutant les sections « Principe de fonctionnement » et «
Suggestions d’utilisation » selon la structure documentaire requise. Conservez
et repositionnez le contenu existant sous cette structure, notamment les
sections « Entrées » et « Sorties », sans traduire les types de données anglais
STRING.
In `@comfyui_embedded_docs/docs/SaveText/ja.md`:
- Around line 1-22: Restructure the SaveText documentation by removing the
level-one “SaveText” heading and adding Japanese “動作原理” and “使用上の提案” sections
with accurate node behavior and usage guidance. Preserve the existing Japanese
入力 and 出力 headings, their content, and the English data type names.
In `@comfyui_embedded_docs/docs/SaveText/ko.md`:
- Around line 1-17: Add the five missing localized documentation sections to the
SaveText page, matching the repository’s standard structure and Korean
terminology, while preserving the existing description and input/output tables.
Replace the “# SaveText” H1 with the non-H1 heading structure used by comparable
node documentation pages.
In `@comfyui_embedded_docs/docs/SaveText/pt-BR.md`:
- Around line 1-17: Atualize a documentação de SaveText removendo o título de
nível um “# SaveText” e adicionando seções localizadas em pt-BR para descrição
da função, princípio de funcionamento, descrição dos parâmetros de entrada,
descrição do resultado de saída e sugestões de uso, preservando as tabelas
existentes.
In `@comfyui_embedded_docs/docs/SaveText/ru.md`:
- Around line 1-19: Update the SaveText documentation by removing the H1 heading
and translation preface, then organize the Russian content into localized
sections for Function Description, Working Principle, Input Parameter
Description, Output Result Description, and Usage Suggestions. Preserve the
existing parameter and output details while placing them under the appropriate
required sections.
In `@comfyui_embedded_docs/docs/SaveText/tr.md`:
- Around line 1-19: Update the SaveText documentation to remove the level-one
“SaveText” heading and organize the page into the required five-part structure,
adding the missing localized Turkish sections alongside the existing “Genel
Bakış”, “Girdiler”, and “Çıktılar” sections. Preserve the current content within
the appropriate sections.
In `@comfyui_embedded_docs/docs/SaveText/zh-TW.md`:
- Around line 1-19: Reorganize the SaveText documentation to remove the
level-one “SaveText” heading and follow the required five-part node
documentation structure, adding each section’s localized equivalent while
preserving the existing Traditional Chinese input and output headings. Move the
overview and input/output tables into their appropriate sections without
changing the documented parameters or values.
In `@comfyui_embedded_docs/docs/SaveText/zh.md`:
- Around line 1-17: Restructure the SaveText documentation around the required
five-part node format: remove the level-one “SaveText” heading, add the
localized sections for description, inputs, outputs, examples, and notes as
required by the documentation contract, and rename the malformed “## ## 输入” and
“## ## 输出” headings to the standardized input/output titles without embedded
`##` text. Preserve the existing input and output tables under their corrected
sections.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalChunk/ar.md`:
- Line 3: Update the opening sentence in the SeedVR2 temporal chunk
documentation to use the feminine Arabic demonstrative “هذه العقدة” instead of
“هذا العقدة”; leave the rest of the description unchanged.
- Around line 1-28: The SeedVR2TemporalChunk documentation uses an H1 and omits
required localized sections. Replace the title with a level-two heading, then
add Function Description, Working Principle, Input Parameter Description, Output
Result Description, and Usage Suggestions sections in Arabic, while preserving
the existing المدخلات and المخرجات headings for their parameter tables.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalChunk/en.md`:
- Around line 1-28: The SeedVR2TemporalChunk documentation uses an H1 and lacks
the required sections. Replace the title with a level-two heading, then
reorganize the content under Function Description, Working Principle, Input
Parameter Description, Output Result Description, and Usage Suggestions headings
while preserving the existing parameter details and notes.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalChunk/es.md`:
- Around line 1-28: Reestructura la documentación de SeedVR2TemporalChunk para
eliminar el H1 y añadir secciones en español con encabezados de nivel 2 para
Descripción de la función, Principio de funcionamiento, Descripción de
parámetros de entrada, Descripción de resultados de salida y Sugerencias de uso.
Conserva las secciones Entradas y Salidas existentes para sus tablas,
integrándolas con la estructura requerida sin modificar la información técnica.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalChunk/fa.md`:
- Around line 1-28: Update the SeedVR2TemporalChunk documentation to remove the
H1 and add localized level-two sections for Function Description, Working
Principle, Input Parameter Description, Output Result Description, and Usage
Suggestions. Keep the existing ورودیها and خروجیها headings for their
parameter and result tables, preserving their current content.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalChunk/fr.md`:
- Around line 1-26: Update the SeedVR2TemporalChunk documentation to remove the
level-one heading and add localized sections for Function Description, Working
Principle, and Usage Suggestions using the repository’s required structure.
Preserve the existing Entrées and Sorties sections, and use a lower-level
heading or plain page title for the node name.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalChunk/ja.md`:
- Around line 1-26: Update the SeedVR2TemporalChunk documentation by removing
the H1 heading and adding Japanese sections for Function Description, Working
Principle, and Usage Suggestions using the required localized documentation
structure. Preserve the existing 入力 and 出力 sections and their content.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalChunk/ko.md`:
- Around line 1-26: The SeedVR2TemporalChunk documentation uses an H1 and lacks
required localized sections. Remove the `# SeedVR2TemporalChunk` heading, retain
the existing `입력` and `출력` sections, and add Korean sections for Function
Description, Working Principle, and Usage Suggestions using the repository’s
required documentation structure.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalChunk/pt-BR.md`:
- Around line 1-26: Update the SeedVR2TemporalChunk documentation by removing
the H1 heading and adding the required Portuguese sections for Function
Description, Working Principle, and Usage Suggestions, using the repository’s
expected localized heading structure. Preserve the existing Entradas and Saídas
sections and their content.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalChunk/ru.md`:
- Around line 1-26: Update the SeedVR2TemporalChunk documentation by removing
the H1 title and adding localized sections for Function Description, Working
Principle, and Usage Suggestions with Russian headings and appropriate content.
Preserve the existing `Входы` and `Выходы` sections.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalChunk/tr.md`:
- Around line 3-26: Add Turkish “Çalışma Prensibi” and “Kullanım Önerileri”
sections to the SeedVR2TemporalChunk documentation, describing how temporal
chunks and overlap are calculated/used and offering practical guidance for
automatic versus manual chunking. Keep the existing input and output tables
unchanged and follow the document’s established required-section structure,
including the existing function description.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalChunk/zh-TW.md`:
- Around line 3-26: 修正文件中的重複 Markdown 標題標記，將「## ## 輸入」與「## ## 輸出」改為「## 輸入」與「##
輸出」。在輸入與輸出區段之外，依標準節點文件結構補上明確的「工作原理」與「使用建議」區段，並保留現有內容與標準化輸入輸出結構。
In `@comfyui_embedded_docs/docs/SeedVR2TemporalChunk/zh.md`:
- Around line 3-26: 在文档中将“## ## 输入”和“## ## 输出”修正为“## 输入”和“##
输出”，并在输入/输出说明之外补充中文“工作原理”和“使用建议”章节，确保 SeedVR2TemporalChunk 文档符合标准节点文档结构。
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/ar.md`:
- Around line 3-18: أضف إلى صفحة SeedVR2TemporalMerge/ar.md قسمين واضحين
بالعربية بعنوان «مبدأ العمل» و«اقتراحات الاستخدام»، مع شرح سلوك الدمج بالتداخل
المتقاطع أو التسلسل المباشر، وطريقة ضبط temporal_overlap عمليًا. حافظ على
الأقسام الموجودة وأكمل بنية التوثيق المطلوبة دون تعديل وصف المعاملات أو
المخرجات.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/en.md`:
- Around line 3-18: Expand the SeedVR2TemporalMerge documentation to include the
required Function Description, Working Principle, Input Parameter Description,
Output Result Description, and Usage Suggestions sections. In Working Principle,
describe the Hann-window crossfade across overlapping temporal chunks and plain
concatenation when overlap is zero; in Usage Suggestions, document recommended
overlap usage and the requirement to reuse temporal_overlap from Split SeedVR2
Latent.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/es.md`:
- Around line 3-18: Actualiza la documentación de la página SeedVR2TemporalMerge
en español para incluir explícitamente las secciones “Principio de
funcionamiento” y “Sugerencias de uso”, describiendo el fundido cruzado con
ventana Hann en la superposición y la concatenación cuando temporal_overlap es
0. Conserva las secciones existentes y asegúrate de que la página incluya
también las cinco secciones requeridas: descripción de la función, principio de
funcionamiento, descripción de entradas, descripción de salidas y sugerencias de
uso.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/fa.md`:
- Around line 3-18: در صفحه فارسی SeedVR2TemporalMerge بخشهای «اصل کار» و
«پیشنهادهای استفاده» را اضافه کنید؛ اصل کار باید ترکیب تکهها، همپوشانی پنجره
Hann و الحاق ساده با همپوشانی صفر را توضیح دهد، و پیشنهادها باید تنظیم عملی
temporal_overlap، ترتیب تکهها و سازگاری ابعاد را پوشش دهد. ساختار موجود بخشهای
توضیح تابع، ورودیها و خروجیها را حفظ کنید.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/fr.md`:
- Around line 3-18: Ajoutez à la page française les sections explicites «
Principe de fonctionnement » et « Suggestions d’utilisation », en conservant les
sections existantes. Décrivez dans la première le fondu enchaîné avec fenêtre de
Hann sur les chevauchements, puis indiquez dans la seconde comment choisir et
utiliser une valeur de chevauchement adaptée, notamment la concaténation avec 0.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/ja.md`:
- Around line 1-20: Update the SeedVR2TemporalMerge documentation structure:
replace the top-level “SeedVR2TemporalMerge” heading with a level-two heading,
then add Japanese sections for Function Description, Working Principle, Input
Parameter Description, Output Result Description, and Usage Suggestions. Retain
the existing 入力 and 出力 headings and their tables, integrating them within the
required structure.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/ko.md`:
- Around line 1-20: Update the SeedVR2TemporalMerge documentation to remove the
H1 and use level-two headings throughout. Add Korean sections for Function
Description, Working Principle, Input Parameter Description, Output Result
Description, and Usage Suggestions, while retaining the existing 입력 and 출력
sections and their tables.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/pt-BR.md`:
- Line 18: In the `latent` output description, replace the misspelled Portuguese
word `recombindo` with `recombinado`, leaving the rest of the table entry
unchanged.
- Around line 1-20: Atualize a documentação de SeedVR2TemporalMerge para remover
o título H1 e usar títulos de nível dois. Adicione as seções em português
“Descrição da Função”, “Princípio de Funcionamento”, “Descrição dos Parâmetros
de Entrada”, “Descrição do Resultado da Saída” e “Sugestões de Uso”, mantendo
“Entradas” e “Saídas” para as tabelas existentes e preservando o conteúdo
técnico atual.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/ru.md`:
- Around line 1-20: Update the SeedVR2TemporalMerge documentation structure by
removing the H1 and adding Russian level-two sections for Function Description,
Working Principle, Input Parameter Description, Output Result Description, and
Usage Suggestions. Retain the existing Входы and Выходы sections and their
tables, incorporating the relevant parameter and result details into the new
required sections.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/tr.md`:
- Around line 1-18: Update the SeedVR2TemporalMerge documentation by removing
the H1 heading and adding the required Turkish sections for Function
Description, Working Principle, and Usage Suggestions. Preserve the existing
Turkish Inputs and Outputs sections and their content.
- Around line 3-12: Resolve the contradiction in the SeedVR2 Temporal Merge
documentation by aligning the `temporal_overlap` requirement with its documented
behavior: if omission is supported, change the input table’s required value to
`Hayır` and retain the default of 0; otherwise, remove the
unspecified-overlap/plain-concatenation behavior and default documentation.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/zh-TW.md`:
- Around line 3-12: Resolve the temporal_overlap documentation contradiction by
marking its 必要 field as optional (否), preserving the documented default value of
0 and the behavior that omitted overlap performs pure concatenation.
- Around line 1-18: 修正 SeedVR2TemporalMerge 文件的 Markdown 結構：將 `## ## 輸入` 與 `##
## 輸出` 改為 `## 輸入` 和 `##
輸出`，並在其餘內容中補上本地化的「功能描述」、「工作原理」與「使用建議」二級標題及對應說明，保留現有輸入輸出內容。
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/zh.md`:
- Around line 1-18: Update the SeedVR2TemporalMerge documentation structure:
change the malformed “## ## 输入” and “## ## 输出” headings to “## 输入” and “## 输出”,
and add localized level-two sections for Function Description, Working
Principle, and Usage Suggestions while preserving the existing content and
language.
- Around line 3-12: Resolve the temporal_overlap contract in the input table and
description: either mark temporal_overlap as optional (否) while retaining the
default value 0 and omitted-input concatenation behavior, or remove that
default/omitted-input behavior and keep it required. Ensure the table and
surrounding documentation consistently describe the chosen behavior.
In `@comfyui_embedded_docs/docs/TextOverlay/ar.md`:
- Line 3: In the TextOverlay Arabic description, replace the phrase “تقوم
بإنشاء” with the more direct verb “تنشئ” while leaving the rest of the wording
unchanged.
- Around line 1-21: Update the TextOverlay documentation to remove the level-one
heading and organize it into the required five sections: Function Description,
Working Principle, Input Parameter Description, Output Result Description, and
Usage Suggestions. Preserve the existing Arabic content and parameter details
while placing each item under the appropriate section.
In `@comfyui_embedded_docs/docs/TextOverlay/en.md`:
- Around line 1-21: Update the TextOverlay documentation to remove the level-one
“TextOverlay” heading and organize the page into the required sections: Function
Description, Working Principle, Input Parameter Description, Output Result
Description, and Usage Suggestions. Preserve the existing parameter and output
details within the appropriate sections.
In `@comfyui_embedded_docs/docs/TextOverlay/es.md`:
- Around line 1-21: The TextOverlay documentation must remove the level-one
“Superponer texto” heading and adopt the required five-part structure: Function
Description, Working Principle, Input Parameter Description, Output Result
Description, and Usage Suggestions. Preserve the existing Spanish parameter and
output details while reorganizing them under the appropriate sections.
In `@comfyui_embedded_docs/docs/TextOverlay/fa.md`:
- Around line 1-21: Update the TextOverlay documentation to remove the level-one
heading and organize the page into the required five sections: Function
Description, Working Principle, Input Parameter Description, Output Result
Description, and Usage Suggestions. Preserve the existing Persian content while
placing each detail under the appropriate section and retaining the input/output
tables.
In `@comfyui_embedded_docs/docs/TextOverlay/fr.md`:
- Around line 10-15: Update the French TextOverlay table to preserve canonical
identifiers in backticks: use text, font_size, color, position, align, outline,
and images. Translate only the descriptions, leaving the existing localized
explanatory text and parameter values unchanged.
- Around line 1-23: Update the TextOverlay documentation to remove the level-one
heading and organize the content under the required five sections: Function
Description, Working Principle, Input Parameter Description, Output Result
Description, and Usage Suggestions. Preserve the existing French descriptions
and parameter/output details while placing them in the appropriate sections.
In `@comfyui_embedded_docs/docs/TextOverlay/ja.md`:
- Around line 1-23: Update the TextOverlay Japanese documentation to remove the
level-one heading and organize its content under the required Function
Description, Working Principle, Input Parameter Description, Output Result
Description, and Usage Suggestions sections. Preserve the existing parameter and
output details while adding the required section headings and relevant content.
- Around line 9-15: Update the Japanese TextOverlay table identifiers to match
the canonical English names: keep images, text, font_size, color, position,
align, outline, and the output images unchanged in backticks, while translating
only their descriptions.
In `@comfyui_embedded_docs/docs/TextOverlay/ko.md`:
- Around line 1-23: Update the TextOverlay documentation to remove the level-one
title and organize it into the required five sections: Function Description,
Working Principle, Input Parameter Description, Output Result Description, and
Usage Suggestions. Preserve the existing parameter and output details while
placing them under the appropriate sections, using a heading level below H1.
In `@comfyui_embedded_docs/docs/TextOverlay/pt-BR.md`:
- Around line 1-23: Update the TextOverlay documentation to remove the level-one
heading and follow the required five-section structure: Function Description,
Working Principle, Input Parameter Description, Output Result Description, and
Usage Suggestions. Preserve the existing parameter and output details while
reorganizing them under the appropriate sections, using a heading level below
one.
- Around line 9-15: Update the Portuguese TextOverlay parameter table to use the
canonical API identifiers from the English documentation in backticks, replacing
the translated names while leaving the Portuguese descriptions translated. Apply
the same identifier-preservation rule to the additional affected entry,
including imagens, texto, tamanho_da_fonte, cor, posição, alinhamento, and
contorno.
In `@comfyui_embedded_docs/docs/TextOverlay/ru.md`:
- Around line 9-15: Update the TextOverlay Russian documentation table to
preserve the canonical node identifiers from the English version: keep `images`,
`text`, `font_size`, `color`, `position`, `align`, and `outline`, plus the
output `images`, unchanged in backticks while translating only their
descriptions.
- Around line 1-23: Update the TextOverlay documentation to remove the level-one
“# Наложение текста” heading and organize the content into the required five
sections: Function Description, Working Principle, Input Parameter Description,
Output Result Description, and Usage Suggestions. Preserve the existing Russian
parameter and output details while placing them under the appropriate sections
and using a non-level-one heading format.
In `@comfyui_embedded_docs/docs/TextOverlay/tr.md`:
- Around line 1-23: Update the TextOverlay documentation to remove the level-one
title and use a lower-level heading. Restructure the document to include the
required Function Description, Working Principle, Input Parameter Description,
Output Result Description, and Usage Suggestions sections, preserving the
existing Turkish content and parameter details.
- Around line 9-15: Update the Turkish TextOverlay parameter table to use the
canonical API identifiers from the English documentation in backticks, including
image, text, font size, color, position, alignment, and outline names; translate
only the descriptions and preserve the existing types, defaults, and option
values.
In `@comfyui_embedded_docs/docs/TextOverlay/zh-TW.md`:
- Around line 1-21: Update the TextOverlay documentation headings to remove the
level-one heading and correct the malformed “## ##” headings. Restructure the
page into the required five sections, including a Usage Suggestions section,
using the established heading hierarchy for node documentation.
In `@comfyui_embedded_docs/docs/TextOverlay/zh.md`:
- Around line 1-21: Update the TextOverlay documentation headings to remove the
level-one title, correct the malformed “## ## 输入” and “## ## 输出” headings, and
organize the page using the required five-part node documentation structure,
including a “Usage Suggestions” section. Preserve the existing input and output
tables under their corresponding headings.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 9b6fc606-1e6f-4557-b6c6-e193591eb99e
📒 Files selected for processing (95)
comfyui_embedded_docs/docs/CreateBoundingBoxes/en.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/en.mdcomfyui_embedded_docs/docs/LTXVContextWindows/en.mdcomfyui_embedded_docs/docs/Load3DAdvanced/en.mdcomfyui_embedded_docs/docs/LumaRay32ExtendVideoNode/en.mdcomfyui_embedded_docs/docs/LumaRay32ImageToVideoNode/en.mdcomfyui_embedded_docs/docs/LumaRay32KeyframeNode/en.mdcomfyui_embedded_docs/docs/LumaRay32KeyframesToVideoNode/en.mdcomfyui_embedded_docs/docs/LumaRay32TextToVideoNode/en.mdcomfyui_embedded_docs/docs/LumaRay32VideoEditNode/en.mdcomfyui_embedded_docs/docs/LumaRay32VideoReframeNode/en.mdcomfyui_embedded_docs/docs/Save3DAdvanced/ar.mdcomfyui_embedded_docs/docs/Save3DAdvanced/en.mdcomfyui_embedded_docs/docs/Save3DAdvanced/es.mdcomfyui_embedded_docs/docs/Save3DAdvanced/fa.mdcomfyui_embedded_docs/docs/Save3DAdvanced/fr.mdcomfyui_embedded_docs/docs/Save3DAdvanced/ja.mdcomfyui_embedded_docs/docs/Save3DAdvanced/ko.mdcomfyui_embedded_docs/docs/Save3DAdvanced/pt-BR.mdcomfyui_embedded_docs/docs/Save3DAdvanced/ru.mdcomfyui_embedded_docs/docs/Save3DAdvanced/tr.mdcomfyui_embedded_docs/docs/Save3DAdvanced/zh-TW.mdcomfyui_embedded_docs/docs/Save3DAdvanced/zh.mdcomfyui_embedded_docs/docs/SaveGaussianSplat/ar.mdcomfyui_embedded_docs/docs/SaveGaussianSplat/en.mdcomfyui_embedded_docs/docs/SaveGaussianSplat/es.mdcomfyui_embedded_docs/docs/SaveGaussianSplat/fa.mdcomfyui_embedded_docs/docs/SaveGaussianSplat/fr.mdcomfyui_embedded_docs/docs/SaveGaussianSplat/ja.mdcomfyui_embedded_docs/docs/SaveGaussianSplat/ko.mdcomfyui_embedded_docs/docs/SaveGaussianSplat/pt-BR.mdcomfyui_embedded_docs/docs/SaveGaussianSplat/ru.mdcomfyui_embedded_docs/docs/SaveGaussianSplat/tr.mdcomfyui_embedded_docs/docs/SaveGaussianSplat/zh-TW.mdcomfyui_embedded_docs/docs/SaveGaussianSplat/zh.mdcomfyui_embedded_docs/docs/SavePointCloud/ar.mdcomfyui_embedded_docs/docs/SavePointCloud/en.mdcomfyui_embedded_docs/docs/SavePointCloud/es.mdcomfyui_embedded_docs/docs/SavePointCloud/fa.mdcomfyui_embedded_docs/docs/SavePointCloud/fr.mdcomfyui_embedded_docs/docs/SavePointCloud/ja.mdcomfyui_embedded_docs/docs/SavePointCloud/ko.mdcomfyui_embedded_docs/docs/SavePointCloud/pt-BR.mdcomfyui_embedded_docs/docs/SavePointCloud/ru.mdcomfyui_embedded_docs/docs/SavePointCloud/tr.mdcomfyui_embedded_docs/docs/SavePointCloud/zh-TW.mdcomfyui_embedded_docs/docs/SavePointCloud/zh.mdcomfyui_embedded_docs/docs/SaveText/ar.mdcomfyui_embedded_docs/docs/SaveText/en.mdcomfyui_embedded_docs/docs/SaveText/es.mdcomfyui_embedded_docs/docs/SaveText/fa.mdcomfyui_embedded_docs/docs/SaveText/fr.mdcomfyui_embedded_docs/docs/SaveText/ja.mdcomfyui_embedded_docs/docs/SaveText/ko.mdcomfyui_embedded_docs/docs/SaveText/pt-BR.mdcomfyui_embedded_docs/docs/SaveText/ru.mdcomfyui_embedded_docs/docs/SaveText/tr.mdcomfyui_embedded_docs/docs/SaveText/zh-TW.mdcomfyui_embedded_docs/docs/SaveText/zh.mdcomfyui_embedded_docs/docs/SeedVR2TemporalChunk/ar.mdcomfyui_embedded_docs/docs/SeedVR2TemporalChunk/en.mdcomfyui_embedded_docs/docs/SeedVR2TemporalChunk/es.mdcomfyui_embedded_docs/docs/SeedVR2TemporalChunk/fa.mdcomfyui_embedded_docs/docs/SeedVR2TemporalChunk/fr.mdcomfyui_embedded_docs/docs/SeedVR2TemporalChunk/ja.mdcomfyui_embedded_docs/docs/SeedVR2TemporalChunk/ko.mdcomfyui_embedded_docs/docs/SeedVR2TemporalChunk/pt-BR.mdcomfyui_embedded_docs/docs/SeedVR2TemporalChunk/ru.mdcomfyui_embedded_docs/docs/SeedVR2TemporalChunk/tr.mdcomfyui_embedded_docs/docs/SeedVR2TemporalChunk/zh-TW.mdcomfyui_embedded_docs/docs/SeedVR2TemporalChunk/zh.mdcomfyui_embedded_docs/docs/SeedVR2TemporalMerge/ar.mdcomfyui_embedded_docs/docs/SeedVR2TemporalMerge/en.mdcomfyui_embedded_docs/docs/SeedVR2TemporalMerge/es.mdcomfyui_embedded_docs/docs/SeedVR2TemporalMerge/fa.mdcomfyui_embedded_docs/docs/SeedVR2TemporalMerge/fr.mdcomfyui_embedded_docs/docs/SeedVR2TemporalMerge/ja.mdcomfyui_embedded_docs/docs/SeedVR2TemporalMerge/ko.mdcomfyui_embedded_docs/docs/SeedVR2TemporalMerge/pt-BR.mdcomfyui_embedded_docs/docs/SeedVR2TemporalMerge/ru.mdcomfyui_embedded_docs/docs/SeedVR2TemporalMerge/tr.mdcomfyui_embedded_docs/docs/SeedVR2TemporalMerge/zh-TW.mdcomfyui_embedded_docs/docs/SeedVR2TemporalMerge/zh.mdcomfyui_embedded_docs/docs/TextOverlay/ar.mdcomfyui_embedded_docs/docs/TextOverlay/en.mdcomfyui_embedded_docs/docs/TextOverlay/es.mdcomfyui_embedded_docs/docs/TextOverlay/fa.mdcomfyui_embedded_docs/docs/TextOverlay/fr.mdcomfyui_embedded_docs/docs/TextOverlay/ja.mdcomfyui_embedded_docs/docs/TextOverlay/ko.mdcomfyui_embedded_docs/docs/TextOverlay/pt-BR.mdcomfyui_embedded_docs/docs/TextOverlay/ru.mdcomfyui_embedded_docs/docs/TextOverlay/tr.mdcomfyui_embedded_docs/docs/TextOverlay/zh-TW.mdcomfyui_embedded_docs/docs/TextOverlay/zh.md
| | `model` | The Gemini video model used to generate the video. | MODEL | Yes | "Omni Flash" | | ||
| | `seed` | Seed controls whether the node should re-run; results are non-deterministic regardless of seed (default: 42). | INT | Yes | 0 to 2147483647 | | ||
| | `prompt` | The text prompt describing the video to generate. | STRING | Yes | Minimum 1 character after stripping whitespace | | ||
| | `prompt` | The text prompt describing the video to generate. Minimum 1 character after stripping whitespace. | STRING | Yes | Minimum 1 character | |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Keep the whitespace-stripping constraint explicit.
This wording can imply that a whitespace-only prompt is valid, whereas the previous description documented validation after stripping whitespace. Restore that constraint or state explicitly that whitespace-only prompts are rejected.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/en.md` at line 11, Update the
prompt parameter description in the GeminiVideoOmni documentation to explicitly
state that validation occurs after stripping whitespace and that whitespace-only
prompts are rejected, while preserving the minimum one-character requirement.
| @@ -1,4 +1,4 @@ | |||
| # Load3DAdvanced | |||
| # Load 3D (Advanced) | |||
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Remove the level-one heading marker.
Use the new human-readable title without # or with an allowed heading level.
As per coding guidelines, Markdown documentation must not use level-one headings.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/Load3DAdvanced/en.md` at line 1, Update the
document title in the Load3D Advanced documentation to remove the level-one
Markdown heading marker, using the project’s allowed heading level or plain
human-readable title while preserving the existing title text.
Source: Coding guidelines
| @@ -1,4 +1,4 @@ | |||
| # LTXVContextWindows | |||
| # LTXV Context Windows | |||
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Remove the level-one heading marker.
Keep the human-readable title, but remove # or use an allowed heading level. One level too high makes the documentation hierarchy fly.
As per coding guidelines, Markdown documentation must not use level-one headings.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/LTXVContextWindows/en.md` at line 1, Update the
LTXV Context Windows document title by removing the level-one Markdown heading
marker and using an allowed lower-level heading while preserving the
human-readable title.
Source: Coding guidelines
| @@ -1,4 +1,4 @@ | |||
| # LumaRay32ExtendVideoNode | |||
| # Luma Ray 3.2 Extend Video | |||
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Avoid the level-one heading.
Change # Luma Ray 3.2 Extend Video to a non-level-one heading, such as ## Luma Ray 3.2 Extend Video, to comply with the documentation structure. Keep the heading hierarchy from climbing too high.
As per coding guidelines, node documentation must not use level-one headings.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/LumaRay32ExtendVideoNode/en.md` at line 1, Update
the document’s top heading from a level-one heading to a level-two heading,
preserving the existing title text and ensuring node documentation does not use
level-one headings.
Source: Coding guidelines
| @@ -1,4 +1,4 @@ | |||
| # LumaRay32ImageToVideoNode | |||
| # Luma Ray 3.2 Image to Video | |||
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Avoid the level-one heading.
Use a non-level-one heading for Luma Ray 3.2 Image to Video to comply with the documentation structure.
As per coding guidelines, node documentation must not use level-one headings.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/LumaRay32ImageToVideoNode/en.md` at line 1, Change
the document’s top heading for “Luma Ray 3.2 Image to Video” from a level-one
heading to a non-level-one heading, preserving the existing title text and
documentation structure.
Source: Coding guidelines
Comment on lines
+9
to
+15
| | `изображения` | Входное изображение или пакет изображений для нанесения текста | IMAGE | Да | | | ||
| | `текст` | Текст для наложения на изображение (по умолчанию: "") | STRING | Да | | | ||
| | `размер_шрифта` | Размер шрифта в процентах от высоты изображения (по умолчанию: 5.0) | FLOAT | Да | от 0.5 до 50.0 | | ||
| | `цвет` | Цвет текста (по умолчанию: "#ffffff") | STRING | Да | | | ||
| | `позиция` | Вертикальное положение текста на изображении (по умолчанию: "top") | COMBO | Да | `"top"`<br>`"bottom"` | | ||
| | `выравнивание` | Горизонтальное выравнивание текста (по умолчанию: "left") | COMBO | Да | `"left"`<br>`"center"`<br>`"right"` | | ||
| | `контур` | Рисовать черный контур вокруг текста (по умолчанию: True) | BOOLEAN | Да | | |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Preserve canonical node identifiers in the Russian tables.
The translated identifiers such as изображения, текст, and размер_шрифта do not match the canonical identifiers in comfyui_embedded_docs/docs/TextOverlay/en.md:5-26. Keep images, text, font_size, color, position, align, outline, and output images unchanged in backticks.
Also applies to: 21-21
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/TextOverlay/ru.md` around lines 9 - 15, Update the
TextOverlay Russian documentation table to preserve the canonical node
identifiers from the English version: keep `images`, `text`, `font_size`,
`color`, `position`, `align`, and `outline`, plus the output `images`, unchanged
in backticks while translating only their descriptions.
Comment on lines
+1
to
+23
| # Metin Yer Paylaşımı Çiz | ||
|
|
||
| Bu düğüm, bir görüntü veya görüntü grubu üzerine metin çizer. Özelleştirilebilir yazı tipi boyutu, renk, konum, hizalama ve isteğe bağlı bir anahat ile bir metin katmanı oluşturur ve ardından metni orijinal görüntülerin üzerine yerleştirir. | ||
|
|
||
| ## Girdiler | ||
|
|
||
| | Parametre | Açıklama | Veri Türü | Zorunlu | Aralık | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `görüntüler` | Metin çizilecek giriş görüntüsü veya görüntü grubu | IMAGE | Evet | | | ||
| | `metin` | Görüntü üzerine yerleştirilecek metin (varsayılan: "") | STRING | Evet | | | ||
| | `yazı tipi boyutu` | Görüntü yüksekliğinin yüzdesi olarak yazı tipi boyutu (varsayılan: 5.0) | FLOAT | Evet | 0.5 ila 50.0 | | ||
| | `renk` | Metnin rengi (varsayılan: "#ffffff") | STRING | Evet | | | ||
| | `konum` | Metnin görüntü üzerindeki dikey konumu (varsayılan: "top") | COMBO | Evet | `"top"`<br>`"bottom"` | | ||
| | `hizalama` | Metnin yatay hizalaması (varsayılan: "left") | COMBO | Evet | `"left"`<br>`"center"`<br>`"right"` | | ||
| | `dış çizgi` | Metnin etrafına siyah bir anahat çizer (varsayılan: True) | BOOLEAN | Evet | | | ||
|
|
||
| ## Çıktılar | ||
|
|
||
| | Çıktı Adı | Açıklama | Veri Türü | | ||
| |-------------|-------------|-----------| | ||
| | `görüntüler` | Üzerine metin katmanı yerleştirilmiş giriş görüntüleri | IMAGE | | ||
|
|
||
| > Bu belge yapay zeka tarafından oluşturulmuştur. Herhangi bir hata bulursanız veya iyileştirme önerileriniz varsa, katkıda bulunmaktan çekinmeyin! [GitHub'da Düzenle](https://github.com/Comfy-Org/embedded-docs/blob/main/comfyui_embedded_docs/docs/TextOverlay/tr.md) |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Use the required documentation structure and remove the level-one heading.
Add the required Function Description, Working Principle, Input Parameter Description, Output Result Description, and Usage Suggestions sections, and replace the # heading with a non-level-one heading.
As per coding guidelines: ComfyUI node documentation must use the required five-section structure and must not use level-one headings.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/TextOverlay/tr.md` around lines 1 - 23, Update the
TextOverlay documentation to remove the level-one title and use a lower-level
heading. Restructure the document to include the required Function Description,
Working Principle, Input Parameter Description, Output Result Description, and
Usage Suggestions sections, preserving the existing Turkish content and
parameter details.
Source: Coding guidelines
Comment on lines
+9
to
+15
| | `görüntüler` | Metin çizilecek giriş görüntüsü veya görüntü grubu | IMAGE | Evet | | | ||
| | `metin` | Görüntü üzerine yerleştirilecek metin (varsayılan: "") | STRING | Evet | | | ||
| | `yazı tipi boyutu` | Görüntü yüksekliğinin yüzdesi olarak yazı tipi boyutu (varsayılan: 5.0) | FLOAT | Evet | 0.5 ila 50.0 | | ||
| | `renk` | Metnin rengi (varsayılan: "#ffffff") | STRING | Evet | | | ||
| | `konum` | Metnin görüntü üzerindeki dikey konumu (varsayılan: "top") | COMBO | Evet | `"top"`<br>`"bottom"` | | ||
| | `hizalama` | Metnin yatay hizalaması (varsayılan: "left") | COMBO | Evet | `"left"`<br>`"center"`<br>`"right"` | | ||
| | `dış çizgi` | Metnin etrafına siyah bir anahat çizer (varsayılan: True) | BOOLEAN | Evet | | |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Preserve canonical node identifiers in the Turkish tables.
The translated identifiers such as görüntüler, metin, yazı tipi boyutu, and dış çizgi do not match the canonical identifiers in comfyui_embedded_docs/docs/TextOverlay/en.md:5-26. Keep the API names unchanged in backticks and translate only descriptions.
Also applies to: 21-21
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/TextOverlay/tr.md` around lines 9 - 15, Update the
Turkish TextOverlay parameter table to use the canonical API identifiers from
the English documentation in backticks, including image, text, font size, color,
position, alignment, and outline names; translate only the descriptions and
preserve the existing types, defaults, and option values.
Comment on lines
+1
to
+21
| # 绘制文字覆盖 | ||
|
|
||
| 此节点在单张图像或一批图像上绘制文本。它会创建一个可自定义字体大小、颜色、位置、对齐方式以及可选描边的文本叠加层，然后将文本合成到原始图像上。 | ||
|
|
||
| ## ## 输入 | ||
|
|
||
| | 参数 | 描述 | 数据类型 | 是否必填 | 范围 | | ||
| |------|------|----------|----------|------| | ||
| | `图像` | 要绘制文本的输入图像或图像批次 | IMAGE | 是 | | | ||
| | `文字` | 要叠加在图像上的文本（默认：""） | STRING | 是 | | | ||
| | `字体大小` | 字体大小，以图像高度的百分比表示（默认：5.0） | FLOAT | 是 | 0.5 至 50.0 | | ||
| | `颜色` | 文本颜色（默认："#ffffff"） | STRING | 是 | | | ||
| | `位置` | 文本在图像上的垂直位置（默认："top"） | COMBO | 是 | `"top"`<br>`"bottom"` | | ||
| | `对齐` | 文本的水平对齐方式（默认："left"） | COMBO | 是 | `"left"`<br>`"center"`<br>`"right"` | | ||
| | `描边` | 在文本周围绘制黑色描边（默认：True） | BOOLEAN | 是 | | | ||
|
|
||
| ## ## 输出 | ||
|
|
||
| | 输出名称 | 描述 | 数据类型 | | ||
| |----------|------|----------| | ||
| | `图像` | 叠加了文本的输入图像 | IMAGE | |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix the heading structure.
Line 1 uses a prohibited level-one heading, lines 5 and 17 contain malformed ## ## headings instead of ## 输入 and ## 输出, and the page omits the required five-part documentation structure, including Usage Suggestions.
As per coding guidelines, node documentation must use the required five-part structure and must not use level-one headings.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/TextOverlay/zh.md` around lines 1 - 21, Update the
TextOverlay documentation headings to remove the level-one title, correct the
malformed “## ## 输入” and “## ## 输出” headings, and organize the page using the
required five-part node documentation structure, including a “Usage Suggestions”
section. Preserve the existing input and output tables under their corresponding
headings.
Source: Coding guidelines
Comment on lines
+1
to
+27
| # Save3DAdvanced | ||
|
|
||
| هذه العقدة تحفظ نموذجًا ثلاثي الأبعاد في ملف داخل دليل الإخراج الخاص بـ ComfyUI، مع تحكم متقدم في أبعاد الإخراج وإعدادات الكاميرا/منفذ العرض. كما تقوم بتمرير النموذج ثلاثي الأبعاد، ومعلومات النموذج، ومعلومات الكاميرا، والأبعاد إلى العقد اللاحقة. | ||
|
|
||
| ## المدخلات | ||
|
|
||
| | المعامل | الوصف | نوع البيانات | إلزامي | النطاق | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `model_3d` | ملف النموذج ثلاثي الأبعاد من عقدة ثلاثية الأبعاد سابقة. | FILE3D | نعم | GLB, GLTF, FBX, OBJ, STL, USDZ, أي | | ||
| | `filename_prefix` | بادئة لاسم الملف المحفوظ (الافتراضي: "3d/ComfyUI"). | STRING | نعم | نص حر | | ||
| | `viewport_state` | حالة منفذ العرض من عقدة تحميل ثلاثي الأبعاد، تحتوي على معلومات الكاميرا والنموذج. | LOAD3D | نعم | - | | ||
| | `model_3d_info` | معلومات نموذج ثلاثي الأبعاد اختيارية لتجاوز حالة منفذ العرض. | LOAD3DMODELINFO | لا | - | | ||
| | `camera_info` | معلومات كاميرا اختيارية لتجاوز حالة منفذ العرض. | LOAD3DCAMERA | لا | - | | ||
| | `width` | عرض المعاينة الناتجة بالبكسل (الافتراضي: 1024). | INT | نعم | 1 إلى 4096 | | ||
| | `height` | ارتفاع المعاينة الناتجة بالبكسل (الافتراضي: 1024). | INT | نعم | 1 إلى 4096 | | ||
|
|
||
| ## المخرجات | ||
|
|
||
| | اسم المخرج | الوصف | نوع البيانات | | ||
| |-------------|-------------|-----------| | ||
| | `model_3d` | ملف النموذج ثلاثي الأبعاد الذي تم تمريره من المدخلات. | FILE3D | | ||
| | `model_3d_info` | معلومات النموذج، إما من حالة منفذ العرض أو من المدخلات الاختيارية. | LOAD3DMODELINFO | | ||
| | `camera_info` | معلومات الكاميرا، إما من حالة منفذ العرض أو من المدخلات الاختيارية. | LOAD3DCAMERA | | ||
| | `width` | قيمة العرض التي تم تمريرها من المدخلات. | INT | | ||
| | `height` | قيمة الارتفاع التي تم تمريرها من المدخلات. | INT | | ||
|
|
||
| > تم إنشاء هذه الوثيقة بواسطة الذكاء الاصطناعي. إذا وجدت أي أخطاء أو لديك اقتراحات للتحسين، فلا تتردد في المساهمة! [تحرير على GitHub](https://github.com/Comfy-Org/embedded-docs/blob/main/comfyui_embedded_docs/docs/Save3DAdvanced/ar.md) |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Add the required documentation sections and remove the level-one heading.
This page currently contains a # heading and only a description plus inputs/outputs. Add localized sections for Function Description, Working Principle, Input Parameter Description, Output Result Description, and Usage Suggestions, and replace the level-one heading with a permitted heading level.
🧰 Tools
🪛 LanguageTool
[style] ~3-~3: المِلَفّ بكسر الميم
Context: ...ذه العقدة تحفظ نموذجًا ثلاثي الأبعاد في ملف داخل دليل الإخراج الخاص بـ ComfyUI، مع ...
(AR_DIACRITICS_REPLACE)
[grammar] ~3-~3: تعبير "القيام بـالأمر" ركيك يستحسن تجنبه إلى تصريف المصدر الموالي، قل ضربت بدلا من القيام بالضرب.
Context: ...إخراج وإعدادات الكاميرا/منفذ العرض. كما تقوم بتمرير النموذج ثلاثي الأبعاد، ومعلومات النموذج...
(syntax_0000_Qam_bi_test)
[style] ~9-~9: المِلَفّ بكسر الميم
Context: ...----|----------|-------| | model_3d | ملف النموذج ثلاثي الأبعاد من عقدة ثلاثية ال...
(AR_DIACRITICS_REPLACE)
[style] ~10-~10: المِلَفّ بكسر الميم
Context: ..., أي | | filename_prefix | بادئة لاسم الملف المحفوظ (الافتراضي: "3d/ComfyUI"). | ST...
(AR_DIACRITICS_REPLACE)
[style] ~21-~21: المِلَفّ بكسر الميم
Context: ...-----------|-----------| | model_3d | ملف النموذج ثلاثي الأبعاد الذي تم تمريره من...
(AR_DIACRITICS_REPLACE)
[grammar] ~24-~24: هل تقصد "العرض الذي"?
Context: ...ارية. | LOAD3DCAMERA | | width | قيمة العرض التي تم تمريرها من المدخلات. | INT | | `heig...
(gender_0010_alladhi)
[grammar] ~25-~25: هل تقصد "الارتفاع الذي"?
Context: ... من المدخلات. | INT | | height | قيمة الارتفاع التي تم تمريرها من المدخلات. | INT | > تم إ...
(gender_0010_alladhi)
[typographical] ~27-~27: علامات تحتاج إلى غلق: ']' تبدو مفقودة
Context: ...قتراحات للتحسين، فلا تتردد في المساهمة! [تحرير على GitHub](https://github.com/Com...
(UNPAIRED_BRACKETS)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/ar.md` around lines 1 - 27, Update
the Save3DAdvanced documentation by removing the level-one “# Save3DAdvanced”
heading and using a permitted lower-level heading. Add localized sections for
Function Description, Working Principle, Input Parameter Description, Output
Result Description, and Usage Suggestions, preserving and organizing the
existing description, inputs, and outputs under the appropriate sections.
Source: Coding guidelines
Comment on lines
+1
to
+27
| # Save3DAdvanced | ||
|
|
||
| This node saves a 3D model to a file in the ComfyUI output directory, with advanced control over the output dimensions and camera/viewport settings. It also passes through the 3D model, model information, camera information, and dimensions for downstream nodes. | ||
|
|
||
| ## Inputs | ||
|
|
||
| | Parameter | Description | Data Type | Required | Range | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `model_3d` | 3D model file from an upstream 3D node. | FILE3D | Yes | GLB, GLTF, FBX, OBJ, STL, USDZ, Any | | ||
| | `filename_prefix` | Prefix for the saved file name (default: "3d/ComfyUI"). | STRING | Yes | Free text | | ||
| | `viewport_state` | Viewport state from a Load 3D node, containing camera and model information. | LOAD3D | Yes | - | | ||
| | `model_3d_info` | Optional 3D model information to override the viewport state. | LOAD3DMODELINFO | No | - | | ||
| | `camera_info` | Optional camera information to override the viewport state. | LOAD3DCAMERA | No | - | | ||
| | `width` | Width of the output preview in pixels (default: 1024). | INT | Yes | 1 to 4096 | | ||
| | `height` | Height of the output preview in pixels (default: 1024). | INT | Yes | 1 to 4096 | | ||
|
|
||
| ## Outputs | ||
|
|
||
| | Output Name | Description | Data Type | | ||
| |-------------|-------------|-----------| | ||
| | `model_3d` | The 3D model file passed through from the input. | FILE3D | | ||
| | `model_3d_info` | Model information, either from the viewport state or the optional input. | LOAD3DMODELINFO | | ||
| | `camera_info` | Camera information, either from the viewport state or the optional input. | LOAD3DCAMERA | | ||
| | `width` | The width value passed through from the input. | INT | | ||
| | `height` | The height value passed through from the input. | INT | | ||
|
|
||
| > This documentation was AI-generated. If you find any errors or have suggestions for improvement, please feel free to contribute! [Edit on GitHub](https://github.com/Comfy-Org/embedded-docs/blob/main/comfyui_embedded_docs/docs/Save3DAdvanced/en.md) |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Add the required documentation sections and remove the level-one heading.
The page must include Function Description, Working Principle, Input Parameter Description, Output Result Description, and Usage Suggestions. It also currently uses the prohibited # Save3DAdvanced heading; change it to a permitted level or remove it.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/en.md` around lines 1 - 27, Update
the Save3DAdvanced documentation by removing or changing the prohibited
level-one “Save3DAdvanced” heading and adding the required Function Description,
Working Principle, Input Parameter Description, Output Result Description, and
Usage Suggestions sections. Preserve the existing parameter and output details
while organizing them under the appropriate required sections.
Source: Coding guidelines
Comment on lines
+1
to
+27
| # Save3DAdvanced | ||
|
|
||
| Este nodo guarda un modelo 3D en un archivo dentro del directorio de salida de ComfyUI, con control avanzado sobre las dimensiones de salida y la configuración de cámara/visor. También transmite el modelo 3D, la información del modelo, la información de la cámara y las dimensiones para nodos posteriores. | ||
|
|
||
| ## Entradas | ||
|
|
||
| | Parámetro | Descripción | Tipo de Dato | Requerido | Rango | | ||
| |-----------|-------------|--------------|-----------|-------| | ||
| | `model_3d` | Archivo de modelo 3D proveniente de un nodo 3D anterior. | FILE3D | Sí | GLB, GLTF, FBX, OBJ, STL, USDZ, Cualquiera | | ||
| | `filename_prefix` | Prefijo para el nombre del archivo guardado (predeterminado: "3d/ComfyUI"). | STRING | Sí | Texto libre | | ||
| | `viewport_state` | Estado del visor proveniente de un nodo Cargar 3D, que contiene información de la cámara y del modelo. | LOAD3D | Sí | - | | ||
| | `model_3d_info` | Información opcional del modelo 3D para sobrescribir el estado del visor. | LOAD3DMODELINFO | No | - | | ||
| | `camera_info` | Información opcional de la cámara para sobrescribir el estado del visor. | LOAD3DCAMERA | No | - | | ||
| | `width` | Ancho de la vista previa de salida en píxeles (predeterminado: 1024). | INT | Sí | 1 a 4096 | | ||
| | `height` | Alto de la vista previa de salida en píxeles (predeterminado: 1024). | INT | Sí | 1 a 4096 | | ||
|
|
||
| ## Salidas | ||
|
|
||
| | Nombre de Salida | Descripción | Tipo de Dato | | ||
| |------------------|-------------|--------------| | ||
| | `model_3d` | El archivo de modelo 3D transmitido desde la entrada. | FILE3D | | ||
| | `model_3d_info` | Información del modelo, ya sea desde el estado del visor o desde la entrada opcional. | LOAD3DMODELINFO | | ||
| | `camera_info` | Información de la cámara, ya sea desde el estado del visor o desde la entrada opcional. | LOAD3DCAMERA | | ||
| | `width` | El valor de ancho transmitido desde la entrada. | INT | | ||
| | `height` | El valor de alto transmitido desde la entrada. | INT | | ||
|
|
||
| > Esta documentación fue generada por IA. Si encuentra algún error o tiene sugerencias de mejora, ¡no dude en contribuir! [Editar en GitHub](https://github.com/Comfy-Org/embedded-docs/blob/main/comfyui_embedded_docs/docs/Save3DAdvanced/es.md) |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Añade las secciones obligatorias y elimina el encabezado de nivel uno.
La página debe incluir las secciones equivalentes a Function Description, Working Principle, Input Parameter Description, Output Result Description y Usage Suggestions. Además, # Save3DAdvanced incumple la prohibición de encabezados de nivel uno.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/es.md` around lines 1 - 27,
Actualiza la documentación de Save3DAdvanced para eliminar el encabezado de
nivel uno “# Save3DAdvanced” y añadir secciones equivalentes a Function
Description, Working Principle, Input Parameter Description, Output Result
Description y Usage Suggestions, conservando la información existente de
entradas y salidas dentro de las secciones correspondientes.
Source: Coding guidelines
Comment on lines
+1
to
+27
| # Save3DAdvanced | ||
|
|
||
| این گره یک مدل سهبعدی را در دایرکتوری خروجی ComfyUI ذخیره میکند و کنترل پیشرفتهای بر ابعاد خروجی و تنظیمات دوربین/نمایشگر ارائه میدهد. همچنین مدل سهبعدی، اطلاعات مدل، اطلاعات دوربین و ابعاد را برای گرههای پاییندستی عبور میدهد. | ||
|
|
||
| ## ورودیها | ||
|
|
||
| | پارامتر | توضیحات | نوع داده | الزامی | محدوده | | ||
| |---------|---------|----------|--------|--------| | ||
| | `model_3d` | فایل مدل سهبعدی از یک گره سهبعدی بالادستی. | FILE3D | بله | GLB, GLTF, FBX, OBJ, STL, USDZ, هر نوع | | ||
| | `filename_prefix` | پیشوند نام فایل ذخیرهشده (پیشفرض: "3d/ComfyUI"). | STRING | بله | متن آزاد | | ||
| | `viewport_state` | وضعیت نمایشگر از یک گره Load 3D، شامل اطلاعات دوربین و مدل. | LOAD3D | بله | - | | ||
| | `model_3d_info` | اطلاعات اختیاری مدل سهبعدی برای بازنویسی وضعیت نمایشگر. | LOAD3DMODELINFO | خیر | - | | ||
| | `camera_info` | اطلاعات اختیاری دوربین برای بازنویسی وضعیت نمایشگر. | LOAD3DCAMERA | خیر | - | | ||
| | `width` | عرض پیشنمایش خروجی بر حسب پیکسل (پیشفرض: 1024). | INT | بله | 1 تا 4096 | | ||
| | `height` | ارتفاع پیشنمایش خروجی بر حسب پیکسل (پیشفرض: 1024). | INT | بله | 1 تا 4096 | | ||
|
|
||
| ## خروجیها | ||
|
|
||
| | نام خروجی | توضیحات | نوع داده | | ||
| |-----------|---------|----------| | ||
| | `model_3d` | فایل مدل سهبعدی عبور دادهشده از ورودی. | FILE3D | | ||
| | `model_3d_info` | اطلاعات مدل، یا از وضعیت نمایشگر یا از ورودی اختیاری. | LOAD3DMODELINFO | | ||
| | `camera_info` | اطلاعات دوربین، یا از وضعیت نمایشگر یا از ورودی اختیاری. | LOAD3DCAMERA | | ||
| | `width` | مقدار عرض عبور دادهشده از ورودی. | INT | | ||
| | `height` | مقدار ارتفاع عبور دادهشده از ورودی. | INT | | ||
|
|
||
| > این مستند با هوش مصنوعی تهیه شده است. اگر خطایی دیدید یا پیشنهادی برای بهبود دارید، خوشحال میشویم مشارکت کنید! [ویرایش در GitHub](https://github.com/Comfy-Org/embedded-docs/blob/main/comfyui_embedded_docs/docs/Save3DAdvanced/fa.md) |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
بخشهای الزامی مستندات را اضافه کنید و عنوان سطح یک را حذف کنید.
این صفحه باید معادلهای بومیِ Function Description، Working Principle، Input Parameter Description، Output Result Description و Usage Suggestions را داشته باشد. همچنین عنوان # Save3DAdvanced با ممنوعیت عنوانهای سطح یک مغایرت دارد.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/fa.md` around lines 1 - 27, صفحه
مستندات Save3DAdvanced را با حذف عنوان سطحیک `# Save3DAdvanced` بهروزرسانی
کنید و بخشهای معادل بومیِ Function Description، Working Principle، Input
Parameter Description، Output Result Description و Usage Suggestions را اضافه
کنید؛ محتوای فعلی ورودیها و خروجیها را در بخشهای مربوطه حفظ و سازماندهی
کنید.
Source: Coding guidelines
Comment on lines
+1
to
+27
| # Save3DAdvanced | ||
|
|
||
| Ce nœud enregistre un modèle 3D dans un fichier situé dans le répertoire de sortie de ComfyUI, avec un contrôle avancé sur les dimensions de sortie et les paramètres de la caméra/du viewport. Il transmet également le modèle 3D, les informations du modèle, les informations de la caméra et les dimensions aux nœuds en aval. | ||
|
|
||
| ## Entrées | ||
|
|
||
| | Paramètre | Description | Type de données | Requis | Plage | | ||
| |-----------|-------------|-----------------|--------|-------| | ||
| | `model_3d` | Fichier de modèle 3D provenant d'un nœud 3D en amont. | FILE3D | Oui | GLB, GLTF, FBX, OBJ, STL, USDZ, Any | | ||
| | `filename_prefix` | Préfixe pour le nom du fichier enregistré (par défaut : "3d/ComfyUI"). | STRING | Oui | Texte libre | | ||
| | `viewport_state` | État du viewport provenant d'un nœud Load 3D, contenant les informations de la caméra et du modèle. | LOAD3D | Oui | - | | ||
| | `model_3d_info` | Informations facultatives sur le modèle 3D pour remplacer l'état du viewport. | LOAD3DMODELINFO | Non | - | | ||
| | `camera_info` | Informations facultatives sur la caméra pour remplacer l'état du viewport. | LOAD3DCAMERA | Non | - | | ||
| | `width` | Largeur de l'aperçu de sortie en pixels (par défaut : 1024). | INT | Oui | 1 à 4096 | | ||
| | `height` | Hauteur de l'aperçu de sortie en pixels (par défaut : 1024). | INT | Oui | 1 à 4096 | | ||
|
|
||
| ## Sorties | ||
|
|
||
| | Nom de sortie | Description | Type de données | | ||
| |---------------|-------------|-----------------| | ||
| | `model_3d` | Le fichier de modèle 3D transmis depuis l'entrée. | FILE3D | | ||
| | `model_3d_info` | Informations sur le modèle, provenant soit de l'état du viewport, soit de l'entrée facultative. | LOAD3DMODELINFO | | ||
| | `camera_info` | Informations sur la caméra, provenant soit de l'état du viewport, soit de l'entrée facultative. | LOAD3DCAMERA | | ||
| | `width` | La valeur de largeur transmise depuis l'entrée. | INT | | ||
| | `height` | La valeur de hauteur transmise depuis l'entrée. | INT | | ||
|
|
||
| > Cette documentation a été générée par IA. Si vous trouvez des erreurs ou avez des suggestions d'amélioration, n'hésitez pas à contribuer ! [Modifier sur GitHub](https://github.com/Comfy-Org/embedded-docs/blob/main/comfyui_embedded_docs/docs/Save3DAdvanced/fr.md) |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Ajoutez les sections obligatoires et supprimez le titre de niveau un.
La page doit contenir les équivalents localisés de Function Description, Working Principle, Input Parameter Description, Output Result Description et Usage Suggestions. Le titre # Save3DAdvanced est également interdit par les règles de documentation.
🧰 Tools
🪛 LanguageTool
[typographical] ~14-~14: Une espace peut être insérée afin d’améliorer la lisibilité de ce nombre.
Context: ... (par défaut : 1024). | INT | Oui | 1 à 4096 | | height | Hauteur de l'aperçu de s...
(ESPACE_UNITES)
[typographical] ~15-~15: Une espace peut être insérée afin d’améliorer la lisibilité de ce nombre.
Context: ... (par défaut : 1024). | INT | Oui | 1 à 4096 | ## Sorties | Nom de sortie | Descri...
(ESPACE_UNITES)
[typographical] ~27-~27: Pas de correspondance fermante ou ouvrante pour le caractère « ] »
Context: ...lioration, n'hésitez pas à contribuer ! [Modifier sur GitHub](https://github.com/...
(UNPAIRED_BRACKETS)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/Save3DAdvanced/fr.md` around lines 1 - 27, Update
the Save3DAdvanced documentation by removing the top-level “# Save3DAdvanced”
heading and adding localized sections for Function Description, Working
Principle, Input Parameter Description, Output Result Description, and Usage
Suggestions, while preserving the existing parameter and output details.
Source: Coding guidelines
Comment on lines
+3
to
+12
| Bu düğüm, örneklenmiş SeedVR2 latent zamansal parçalarını tek bir tam uzunlukta latent halinde yeniden birleştirir. Parçalar arasındaki örtüşme bölgesinde yumuşak geçişler oluşturmak için Hann penceresi çapraz geçişi kullanır veya örtüşme belirtilmediğinde düz birleştirme gerçekleştirir. | ||
|
|
||
| ## Girişler | ||
|
|
||
| | Parametre | Açıklama | Veri Türü | Gerekli | Aralık | | ||
| |-----------|-------------|-----------|----------|--------| | ||
| | `latents` | Sıralı olarak örneklenmiş zamansal parçalar. | LATENT | Evet | Latent listesi | | ||
| | `temporal_overlap` | Split SeedVR2 Latent çıktısının temporal_overlap değeri. 0 = düz birleştirme. (varsayılan: 0) | INT | Evet | 0 ile 16384 arası | | ||
|
|
||
| **Not:** `temporal_overlap` değeri 0'dan büyük veya eşit olmalıdır. Dizideki son parça, diğer parçalardan daha az zamansal kareye sahip olabilir. Tüm parçalar, zamansal eksen (T) dışında eşleşen boyutlara sahip olmalıdır ve ilk parça 5 boyutlu (B, C, T, H, W) olmalıdır. |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Resolve the temporal_overlap required/default contradiction.
The description says plain concatenation is used when overlap is not specified, but the input table marks temporal_overlap as required and documents a default of 0. Either mark it optional (Hayır) if omission is supported, or remove the omission/default behavior.
🧰 Tools
🪛 LanguageTool
[misspelling] ~3-~3: Söz ve sayı arasında defis yoqtur: "SeedVR-2"
Context: ...VR2TemporalMerge Bu düğüm, örneklenmiş SeedVR2 latent zamansal parçalarını tek bir tam...
(NUMBER_BEFORE_DEFIS_MISSING)
[misspelling] ~10-~10: Söz ve sayı arasında defis yoqtur: "SeedVR-2"
Context: ... listesi | | temporal_overlap | Split SeedVR2 Latent çıktısının temporal_overlap değe...
(NUMBER_BEFORE_DEFIS_MISSING)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/tr.md` around lines 3 - 12,
Resolve the contradiction in the SeedVR2 Temporal Merge documentation by
aligning the `temporal_overlap` requirement with its documented behavior: if
omission is supported, change the input table’s required value to `Hayır` and
retain the default of 0; otherwise, remove the
unspecified-overlap/plain-concatenation behavior and default documentation.
Comment on lines
+1
to
+18
| # SeedVR2TemporalMerge | ||
|
|
||
| 此節點將取樣的 SeedVR2 潛在時間區塊重新組合成單一完整長度的潛在表示。它使用重疊區域上的漢寧窗交叉淡入淡出來創建平滑過渡，或在未指定重疊時執行純粹的串接。 | ||
|
|
||
| ## ## 輸入 | ||
|
|
||
| | 參數 | 描述 | 資料類型 | 必要 | 範圍 | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `latents` | 按順序排列的取樣時間區塊。 | LATENT | 是 | 潛在列表 | | ||
| | `temporal_overlap` | 分割 SeedVR2 潛在節點的 temporal_overlap 輸出。0 = 純粹串接。（預設值：0） | INT | 是 | 0 至 16384 | | ||
|
|
||
| **注意：** `temporal_overlap` 值必須大於或等於 0。序列中的最後一個區塊可能比其他區塊擁有更少的時間幀。所有區塊除了時間軸（T）之外必須具有匹配的維度，且第一個區塊必須是 5 維（B、C、T、H、W）。 | ||
|
|
||
| ## ## 輸出 | ||
|
|
||
| | 輸出名稱 | 描述 | 資料類型 | | ||
| |-------------|-------------|-----------| | ||
| | `latent` | 重新組合後的完整長度潛在表示。 | LATENT | |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Use the required structure and fix the malformed headings.
This page starts with a level-one heading, omits the required Function Description, Working Principle, and Usage Suggestions sections, and uses ## ## 輸入/## ## 輸出. Replace the duplicated markers with ## 輸入 and ## 輸出, then add the missing localized sections so the Markdown does not head off course.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/zh-TW.md` around lines 1 -
18, 修正 SeedVR2TemporalMerge 文件的 Markdown 結構：將 `## ## 輸入` 與 `## ## 輸出` 改為 `## 輸入`
和 `## 輸出`，並在其餘內容中補上本地化的「功能描述」、「工作原理」與「使用建議」二級標題及對應說明，保留現有輸入輸出內容。
Source: Coding guidelines
Comment on lines
+3
to
+12
| 此節點將取樣的 SeedVR2 潛在時間區塊重新組合成單一完整長度的潛在表示。它使用重疊區域上的漢寧窗交叉淡入淡出來創建平滑過渡，或在未指定重疊時執行純粹的串接。 | ||
|
|
||
| ## ## 輸入 | ||
|
|
||
| | 參數 | 描述 | 資料類型 | 必要 | 範圍 | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `latents` | 按順序排列的取樣時間區塊。 | LATENT | 是 | 潛在列表 | | ||
| | `temporal_overlap` | 分割 SeedVR2 潛在節點的 temporal_overlap 輸出。0 = 純粹串接。（預設值：0） | INT | 是 | 0 至 16384 | | ||
|
|
||
| **注意：** `temporal_overlap` 值必須大於或等於 0。序列中的最後一個區塊可能比其他區塊擁有更少的時間幀。所有區塊除了時間軸（T）之外必須具有匹配的維度，且第一個區塊必須是 5 維（B、C、T、H、W）。 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Resolve the temporal_overlap required/default contradiction.
The description says concatenation is used when overlap is not specified, but the table marks temporal_overlap as required and gives it a default of 0. Either mark it optional (否) or remove the omitted-input/default behavior.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/zh-TW.md` around lines 3 -
12, Resolve the temporal_overlap documentation contradiction by marking its 必要
field as optional (否), preserving the documented default value of 0 and the
behavior that omitted overlap performs pure concatenation.
Comment on lines
+1
to
+18
| # SeedVR2TemporalMerge | ||
|
|
||
| 此节点将采样的 SeedVR2 潜在时间块重新组合为单个全长潜在变量。它使用汉宁窗交叉淡入淡出处理块之间的重叠区域，以创建平滑过渡，或在未指定重叠时执行简单拼接。 | ||
|
|
||
| ## ## 输入 | ||
|
|
||
| | 参数 | 描述 | 数据类型 | 是否必需 | 范围 | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `latents` | 按顺序排列的采样时间块。 | LATENT | 是 | 潜在变量列表 | | ||
| | `temporal_overlap` | 分割 SeedVR2 潜在变量的 `temporal_overlap` 输出。0 = 简单拼接。（默认值：0） | INT | 是 | 0 至 16384 | | ||
|
|
||
| **注意：** `temporal_overlap` 值必须大于或等于 0。序列中的最后一个块可能比其他块具有更少的时间帧。所有块除时间轴（T）外必须具有匹配的维度，且第一个块必须是 5 维的（B, C, T, H, W）。 | ||
|
|
||
| ## ## 输出 | ||
|
|
||
| | 输出名 | 描述 | 数据类型 | | ||
| |-------------|-------------|-----------| | ||
| | `latent` | 重新组合后的全长潜在变量。 | LATENT | |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Use the required structure and fix the malformed headings.
This page starts with a level-one heading, omits the required Function Description, Working Principle, and Usage Suggestions sections, and uses ## ## 输入/## ## 输出. Replace the duplicated markers with ## 输入 and ## 输出, then add the missing localized sections.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/zh.md` around lines 1 - 18,
Update the SeedVR2TemporalMerge documentation structure: change the malformed
“## ## 输入” and “## ## 输出” headings to “## 输入” and “## 输出”, and add localized
level-two sections for Function Description, Working Principle, and Usage
Suggestions while preserving the existing content and language.
Source: Coding guidelines
Comment on lines
+3
to
+12
| 此节点将采样的 SeedVR2 潜在时间块重新组合为单个全长潜在变量。它使用汉宁窗交叉淡入淡出处理块之间的重叠区域，以创建平滑过渡，或在未指定重叠时执行简单拼接。 | ||
|
|
||
| ## ## 输入 | ||
|
|
||
| | 参数 | 描述 | 数据类型 | 是否必需 | 范围 | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `latents` | 按顺序排列的采样时间块。 | LATENT | 是 | 潜在变量列表 | | ||
| | `temporal_overlap` | 分割 SeedVR2 潜在变量的 `temporal_overlap` 输出。0 = 简单拼接。（默认值：0） | INT | 是 | 0 至 16384 | | ||
|
|
||
| **注意：** `temporal_overlap` 值必须大于或等于 0。序列中的最后一个块可能比其他块具有更少的时间帧。所有块除时间轴（T）外必须具有匹配的维度，且第一个块必须是 5 维的（B, C, T, H, W）。 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Resolve the temporal_overlap required/default contradiction.
The description says concatenation is used when overlap is not specified, but the table marks temporal_overlap as required and gives it a default of 0. Either mark it optional (否) or remove the omitted-input/default behavior.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SeedVR2TemporalMerge/zh.md` around lines 3 - 12,
Resolve the temporal_overlap contract in the input table and description: either
mark temporal_overlap as optional (否) while retaining the default value 0 and
omitted-input concatenation behavior, or remove that default/omitted-input
behavior and keep it required. Ensure the table and surrounding documentation
consistently describe the chosen behavior.
Comment on lines
+1
to
+30
| # SaveGaussianSplat | ||
|
|
||
| Ce nœud enregistre un fichier 3D de type Gaussian splat dans le répertoire de sortie. Il gère le processus de sauvegarde du fichier et fournit des données d'aperçu pour la fenêtre 3D. | ||
|
|
||
| ## Entrées | ||
|
|
||
| | Paramètre | Description | Type de données | Requis | Plage | | ||
| |-----------|-------------|-----------------|--------|-------| | ||
| | `model_3d` | Un fichier 3D de type Gaussian splat. | FILE3D | Oui | SplatAny<br>PLY<br>SPLAT<br>SPZ<br>KSPLAT | | ||
| | `filename_prefix` | Le préfixe pour le nom du fichier enregistré (par défaut : "3d/ComfyUI"). | STRING | Oui | Tout préfixe de nom de fichier valide | | ||
| | `viewport_state` | L'état actuel de la fenêtre contenant les informations de caméra et de modèle. | LOAD3D | Oui | - | | ||
| | `model_3d_info` | Informations supplémentaires sur le modèle 3D pour la fenêtre. | LOAD3DMODELINFO | Non | - | | ||
| | `camera_info` | Informations sur la caméra pour l'aperçu dans la fenêtre. | LOAD3DCAMERA | Non | - | | ||
| | `width` | La largeur de l'aperçu (par défaut : 1024). | INT | Oui | 1 à 4096 | | ||
| | `height` | La hauteur de l'aperçu (par défaut : 1024). | INT | Oui | 1 à 4096 | | ||
|
|
||
| ## Sorties | ||
|
|
||
| | Nom de sortie | Description | Type de données | | ||
| |---------------|-------------|-----------------| | ||
| | `model_3d` | Le fichier 3D Gaussian splat enregistré. | FILE3D | | ||
| | `model_3d_info` | Informations sur le modèle 3D pour la fenêtre. | LOAD3DMODELINFO | | ||
| | `camera_info` | Informations sur la caméra pour l'aperçu dans la fenêtre. | LOAD3DCAMERA | | ||
| | `width` | La largeur de l'aperçu. | INT | | ||
| | `height` | La hauteur de l'aperçu. | INT | | ||
|
|
||
| > Cette documentation a été générée par IA. Si vous trouvez des erreurs ou avez des suggestions d'amélioration, n'hésitez pas à contribuer ! [Modifier sur GitHub](https://github.com/Comfy-Org/embedded-docs/blob/main/comfyui_embedded_docs/docs/SaveGaussianSplat/fr.md) | ||
|
|
||
| --- | ||
| **Source fingerprint (SHA-256):** `f2d6b98d2ce1fe11df8ba440b7f46a21e2308966c15daa5ca0bdca7dab1726cc` |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Apply the required documentation structure and remove the H1.
This page contains only an overview plus Inputs/Outputs. Add the required Working Principle and Usage Suggestions sections, organize the existing content under the required conceptual sections, and replace the level-one heading at Line 1 with a permitted heading level. Keep the localized Entrées/Sorties titles and English data types unchanged.
🧰 Tools
🪛 LanguageTool
[style] ~3-~3: Ce verbe peut être considéré comme familier dans un contexte formel.
Context: ... splat dans le répertoire de sortie. Il gère le processus de sauvegarde du fichier e...
(VERBES_FAMILIERS_PREMIUM)
[typographical] ~14-~14: Une espace peut être insérée afin d’améliorer la lisibilité de ce nombre.
Context: ... (par défaut : 1024). | INT | Oui | 1 à 4096 | | height | La hauteur de l'aperçu (...
(ESPACE_UNITES)
[typographical] ~15-~15: Une espace peut être insérée afin d’améliorer la lisibilité de ce nombre.
Context: ... (par défaut : 1024). | INT | Oui | 1 à 4096 | ## Sorties | Nom de sortie | Descri...
(ESPACE_UNITES)
[typographical] ~27-~27: Pas de correspondance fermante ou ouvrante pour le caractère « ] »
Context: ...lioration, n'hésitez pas à contribuer ! [Modifier sur GitHub](https://github.com/...
(UNPAIRED_BRACKETS)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/fr.md` around lines 1 - 30,
Restructure the SaveGaussianSplat documentation by replacing the H1 with a
permitted lower-level heading and adding the required Working Principle and
Usage Suggestions sections. Organize the existing overview, Entrées, and Sorties
content under the appropriate conceptual sections, while preserving the
localized section titles and unchanged English data types.
Source: Coding guidelines
Comment on lines
+1
to
+30
| # SaveGaussianSplat | ||
|
|
||
| 이 노드는 가우시안 스플랫 3D 파일을 출력 디렉토리에 저장합니다. 파일 저장 과정을 처리하고 3D 뷰포트를 위한 미리보기 데이터를 제공합니다. | ||
|
|
||
| ## 입력 | ||
|
|
||
| | 매개변수 | 설명 | 데이터 타입 | 필수 | 범위 | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `model_3d` | 가우시안 스플랫 3D 파일입니다. | FILE3D | 예 | SplatAny<br>PLY<br>SPLAT<br>SPZ<br>KSPLAT | | ||
| | `filename_prefix` | 저장된 파일 이름의 접두사입니다(기본값: "3d/ComfyUI"). | STRING | 예 | 유효한 모든 파일 이름 접두사 | | ||
| | `viewport_state` | 카메라 및 모델 정보를 포함하는 현재 뷰포트 상태입니다. | LOAD3D | 예 | - | | ||
| | `model_3d_info` | 뷰포트를 위한 추가 모델 3D 정보입니다. | LOAD3DMODELINFO | 아니요 | - | | ||
| | `camera_info` | 뷰포트 미리보기를 위한 카메라 정보입니다. | LOAD3DCAMERA | 아니요 | - | | ||
| | `width` | 미리보기의 너비입니다(기본값: 1024). | INT | 예 | 1 ~ 4096 | | ||
| | `height` | 미리보기의 높이입니다(기본값: 1024). | INT | 예 | 1 ~ 4096 | | ||
|
|
||
| ## 출력 | ||
|
|
||
| | 출력 이름 | 설명 | 데이터 타입 | | ||
| |-------------|-------------|-----------| | ||
| | `model_3d` | 저장된 가우시안 스플랫 3D 파일입니다. | FILE3D | | ||
| | `model_3d_info` | 뷰포트를 위한 모델 3D 정보입니다. | LOAD3DMODELINFO | | ||
| | `camera_info` | 뷰포트 미리보기를 위한 카메라 정보입니다. | LOAD3DCAMERA | | ||
| | `width` | 미리보기의 너비입니다. | INT | | ||
| | `height` | 미리보기의 높이입니다. | INT | | ||
|
|
||
| > 이 문서는 AI에 의해 생성되었습니다. 오류를 발견하거나 개선 제안이 있으시면 기여해 주세요! [GitHub에서 편집](https://github.com/Comfy-Org/embedded-docs/blob/main/comfyui_embedded_docs/docs/SaveGaussianSplat/ko.md) | ||
|
|
||
| --- | ||
| **Source fingerprint (SHA-256):** `f2d6b98d2ce1fe11df8ba440b7f46a21e2308966c15daa5ca0bdca7dab1726cc` |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Apply the required documentation structure and remove the H1.
Add the missing Working Principle and Usage Suggestions sections and organize the page according to the required documentation structure. Also replace the level-one heading at Line 1 with a permitted heading level; retain 입력/출력 and the English data types.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/ko.md` around lines 1 - 30,
Update the SaveGaussianSplat documentation structure by replacing the level-one
“SaveGaussianSplat” heading with a permitted lower-level heading, then add the
required “Working Principle” and “Usage Suggestions” sections with relevant
content. Preserve the existing 입력 and 출력 sections, Korean descriptions, and
English data type names.
Source: Coding guidelines
Comment on lines
+1
to
+25
| # SaveGaussianSplat | ||
|
|
||
| Этот узел сохраняет файл гауссова сплаттинга 3D в выходной каталог. Он обрабатывает процесс сохранения файла и предоставляет данные предварительного просмотра для 3D-вьюпорта. | ||
|
|
||
| ## Входные параметры | ||
|
|
||
| | Параметр | Описание | Тип данных | Обязательный | Диапазон | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `model_3d` | Файл гауссова сплаттинга 3D. | FILE3D | Да | SplatAny<br>PLY<br>SPLAT<br>SPZ<br>KSPLAT | | ||
| | `filename_prefix` | Префикс для сохраняемого имени файла (по умолчанию: "3d/ComfyUI"). | STRING | Да | Любой допустимый префикс имени файла | | ||
| | `viewport_state` | Текущее состояние вьюпорта, содержащее информацию о камере и модели. | LOAD3D | Да | - | | ||
| | `model_3d_info` | Дополнительная информация о 3D-модели для вьюпорта. | LOAD3DMODELINFO | Нет | - | | ||
| | `camera_info` | Информация о камере для предварительного просмотра во вьюпорте. | LOAD3DCAMERA | Нет | - | | ||
| | `width` | Ширина предварительного просмотра (по умолчанию: 1024). | INT | Да | от 1 до 4096 | | ||
| | `height` | Высота предварительного просмотра (по умолчанию: 1024). | INT | Да | от 1 до 4096 | | ||
|
|
||
| ## Выходные параметры | ||
|
|
||
| | Имя выхода | Описание | Тип данных | | ||
| |-------------|-------------|-----------| | ||
| | `model_3d` | Сохраненный файл гауссова сплаттинга 3D. | FILE3D | | ||
| | `model_3d_info` | Информация о 3D-модели для вьюпорта. | LOAD3DMODELINFO | | ||
| | `camera_info` | Информация о камере для предварительного просмотра во вьюпорте. | LOAD3DCAMERA | | ||
| | `width` | Ширина предварительного просмотра. | INT | | ||
| | `height` | Высота предварительного просмотра. | INT | |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | 🏗️ Heavy lift
Align this page with the required documentation structure.
The page must use localized equivalents of Function Description, Working Principle, Input Parameter Description, Output Result Description, and Usage Suggestions. Remove the H1 heading, and rename the section headings to ## Входы and ## Выходы. The tables are tidy, but the required structure is still hiding.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/ru.md` around lines 1 - 25,
Обновите страницу SaveGaussianSplat: удалите H1, добавьте локализованные разделы
для описания функции, принципа работы, входных параметров, выходного результата
и рекомендаций по использованию, сохранив соответствующее русское содержание.
Переименуйте заголовки таблиц с «Входные параметры» и «Выходные параметры» в «##
Входы» и «## Выходы» соответственно.
Source: Coding guidelines
Comment on lines
+1
to
+25
| # SaveGaussianSplat | ||
|
|
||
| Bu düğüm, bir Gaussian splat 3B dosyasını çıktı dizinine kaydeder. Dosya kaydetme işlemini yönetir ve 3B görünüm alanı için önizleme verileri sağlar. | ||
|
|
||
| ## Girişler | ||
|
|
||
| | Parametre | Açıklama | Veri Türü | Zorunlu | Aralık | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `model_3d` | Bir Gaussian splat 3B dosyası. | FILE3D | Evet | SplatAny<br>PLY<br>SPLAT<br>SPZ<br>KSPLAT | | ||
| | `filename_prefix` | Kaydedilen dosya adı için ön ek (varsayılan: "3d/ComfyUI"). | STRING | Evet | Geçerli herhangi bir dosya adı ön eki | | ||
| | `viewport_state` | Kamera ve model bilgilerini içeren mevcut görünüm alanı durumu. | LOAD3D | Evet | - | | ||
| | `model_3d_info` | Görünüm alanı için ek model 3B bilgisi. | LOAD3DMODELINFO | Hayır | - | | ||
| | `camera_info` | Görünüm alanı önizlemesi için kamera bilgisi. | LOAD3DCAMERA | Hayır | - | | ||
| | `width` | Önizlemenin genişliği (varsayılan: 1024). | INT | Evet | 1 ila 4096 | | ||
| | `height` | Önizlemenin yüksekliği (varsayılan: 1024). | INT | Evet | 1 ila 4096 | | ||
|
|
||
| ## Çıktılar | ||
|
|
||
| | Çıktı Adı | Açıklama | Veri Türü | | ||
| |-------------|-------------|-----------| | ||
| | `model_3d` | Kaydedilen Gaussian splat 3B dosyası. | FILE3D | | ||
| | `model_3d_info` | Görünüm alanı için model 3B bilgisi. | LOAD3DMODELINFO | | ||
| | `camera_info` | Görünüm alanı önizlemesi için kamera bilgisi. | LOAD3DCAMERA | | ||
| | `width` | Önizlemenin genişliği. | INT | | ||
| | `height` | Önizlemenin yüksekliği. | INT | |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | 🏗️ Heavy lift
Add the required documentation sections and remove the H1.
Provide localized equivalents of Function Description, Working Principle, Input Parameter Description, Output Result Description, and Usage Suggestions. The current # SaveGaussianSplat heading also violates the prohibition on level-one headings.
🧰 Tools
🪛 LanguageTool
[misspelling] ~3-~3: Söz ve sayı arasında defis yoqtur:
Context: ...sianSplat Bu düğüm, bir Gaussian splat 3B dosyasını çıktı dizinine kaydeder. Dosy...
(COMPLEX_NUMBER_DEFIS_MISSING)
[misspelling] ~3-~3: Söz ve sayı arasında defis yoqtur:
Context: ...der. Dosya kaydetme işlemini yönetir ve 3B görünüm alanı için önizleme verileri sa...
(COMPLEX_NUMBER_DEFIS_MISSING)
[misspelling] ~9-~9: Söz ve sayı arasında defis yoqtur:
Context: ...----| | model_3d | Bir Gaussian splat 3B dosyası. | FILE3D | Evet | SplatAny
...
(COMPLEX_NUMBER_DEFIS_MISSING)
[misspelling] ~10-~10: Söz ve sayı arasında defis yoqtur:
Context: ...ilen dosya adı için ön ek (varsayılan: "3d/ComfyUI"). | STRING | Evet | Geçerli he...
(COMPLEX_NUMBER_DEFIS_MISSING)
[misspelling] ~12-~12: Söz ve sayı arasında defis yoqtur:
Context: ..._3d_info` | Görünüm alanı için ek model 3B bilgisi. | LOAD3DMODELINFO | Hayır | - ...
(COMPLEX_NUMBER_DEFIS_MISSING)
[misspelling] ~21-~21: Söz ve sayı arasında defis yoqtur:
Context: ... model_3d | Kaydedilen Gaussian splat 3B dosyası. | FILE3D | | model_3d_info |...
(COMPLEX_NUMBER_DEFIS_MISSING)
[misspelling] ~22-~22: Söz ve sayı arasında defis yoqtur:
Context: ...del_3d_info| Görünüm alanı için model 3B bilgisi. | LOAD3DMODELINFO | |camera_...
(COMPLEX_NUMBER_DEFIS_MISSING)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/tr.md` around lines 1 - 25,
SaveGaussianSplat dokümantasyonundan mevcut “# SaveGaussianSplat” H1 başlığını
kaldırın ve Function Description, Working Principle, Input Parameter
Description, Output Result Description ile Usage Suggestions bölümlerinin Türkçe
karşılıklarını ekleyin. Mevcut giriş ve çıktı tablolarını koruyarak bu bölümleri
düğümün işlevi, çalışma mantığı, parametreleri, sonuçları ve kullanım
önerilerini açıklayacak şekilde tamamlayın.
Source: Coding guidelines
Comment on lines
+1
to
+25
| # SaveGaussianSplat | ||
|
|
||
| 此節點將高斯潑濺 3D 檔案儲存至輸出目錄。它負責處理檔案儲存流程，並為 3D 視埠提供預覽資料。 | ||
|
|
||
| ## ## 輸入 | ||
|
|
||
| | 參數 | 說明 | 資料類型 | 必要 | 範圍 | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `model_3d` | 一個高斯潑濺 3D 檔案。 | FILE3D | 是 | SplatAny<br>PLY<br>SPLAT<br>SPZ<br>KSPLAT | | ||
| | `filename_prefix` | 儲存檔案名稱的前綴（預設值："3d/ComfyUI"）。 | STRING | 是 | 任何有效的檔案名稱前綴 | | ||
| | `viewport_state` | 包含相機與模型資訊的當前視埠狀態。 | LOAD3D | 是 | - | | ||
| | `model_3d_info` | 視埠的附加模型 3D 資訊。 | LOAD3DMODELINFO | 否 | - | | ||
| | `camera_info` | 視埠預覽的相機資訊。 | LOAD3DCAMERA | 否 | - | | ||
| | `width` | 預覽的寬度（預設值：1024）。 | INT | 是 | 1 至 4096 | | ||
| | `height` | 預覽的高度（預設值：1024）。 | INT | 是 | 1 至 4096 | | ||
|
|
||
| ## ## 輸出 | ||
|
|
||
| | 輸出名稱 | 說明 | 資料類型 | | ||
| |-------------|-------------|-----------| | ||
| | `model_3d` | 已儲存的高斯潑濺 3D 檔案。 | FILE3D | | ||
| | `model_3d_info` | 視埠的模型 3D 資訊。 | LOAD3DMODELINFO | | ||
| | `camera_info` | 視埠預覽的相機資訊。 | LOAD3DCAMERA | | ||
| | `width` | 預覽的寬度。 | INT | | ||
| | `height` | 預覽的高度。 | INT | |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift
Fix the malformed headings and add the required sections.
## ## 輸入 and ## ## 輸出 render with extra heading markers; use ## 輸入 and ## 輸出. Also add localized equivalents of the five required documentation sections and remove the H1 heading.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SaveGaussianSplat/zh-TW.md` around lines 1 - 25,
修正 SaveGaussianSplat 文件的標題結構：移除頂部 H1「SaveGaussianSplat」，將「## ## 輸入」和「## ##
輸出」改為「## 輸入」和「## 輸出」，並補上五個必要文件章節的繁體中文本地化內容。
Source: Coding guidelines
Comment on lines
+1
to
+17
| # SaveText | ||
|
|
||
| O nó Save Text grava o conteúdo de texto em um arquivo no diretório de saída. Ele suporta salvamento nos formatos .txt, .md ou .json e lida automaticamente com a formatação JSON pretty-printing quando um JSON válido é fornecido. | ||
|
|
||
| ## Entradas | ||
|
|
||
| | Parâmetro | Descrição | Tipo de Dado | Obrigatório | Faixa | | ||
| |-----------|-------------|--------------|-------------|-------| | ||
| | `text` | O conteúdo de texto a ser salvo em um arquivo | STRING | Sim | - | | ||
| | `filename_prefix` | Prefixo para o nome do arquivo de saída (padrão: "ComfyUI") | STRING | Não | - | | ||
| | `format` | O formato do arquivo para salvar o texto (padrão: "txt") | STRING | Não | `"txt"`<br>`"md"`<br>`"json"` | | ||
|
|
||
| ## Saídas | ||
|
|
||
| | Nome da Saída | Descrição | Tipo de Dado | | ||
| |---------------|-----------|--------------| | ||
| | `text` | O conteúdo de texto original que foi salvo no arquivo | STRING | |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | 🏗️ Heavy lift
Add the missing documentation sections and remove the H1.
Provide localized equivalents of Function Description, Working Principle, Input Parameter Description, Output Result Description, and Usage Suggestions. The # SaveText heading violates the rule against level-one headings.
🧰 Tools
🪛 LanguageTool
[style] ~17-~17: Para conferir mais clareza ao seu texto, busque usar uma linguagem mais concisa.
Context: ...| text | O conteúdo de texto original que foi salvo no arquivo | STRING | > Esta documenta...
(QUE_É_PARTPASS_PARTPASS)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SaveText/pt-BR.md` around lines 1 - 17, Atualize a
documentação de SaveText removendo o título de nível um “# SaveText” e
adicionando seções localizadas em pt-BR para descrição da função, princípio de
funcionamento, descrição dos parâmetros de entrada, descrição do resultado de
saída e sugestões de uso, preservando as tabelas existentes.
Source: Coding guidelines
Comment on lines
+1
to
+19
| # SaveText | ||
|
|
||
| Вот перевод документации для узла ComfyUI **Save Text** на русский язык: | ||
|
|
||
| Узел Save Text записывает текстовое содержимое в файл в выходной директории. Он поддерживает сохранение в форматах .txt, .md или .json и автоматически выполняет форматирование JSON с отступами, если предоставлен корректный JSON. | ||
|
|
||
| ## Входы | ||
|
|
||
| | Параметр | Описание | Тип данных | Обязательный | Диапазон | | ||
| |----------|----------|------------|--------------|----------| | ||
| | `text` | Текстовое содержимое для сохранения в файл | STRING | Да | - | | ||
| | `filename_prefix` | Префикс для имени выходного файла (по умолчанию: "ComfyUI") | STRING | Нет | - | | ||
| | `format` | Формат файла для сохранения текста (по умолчанию: "txt") | STRING | Нет | `"txt"`<br>`"md"`<br>`"json"` | | ||
|
|
||
| ## Выходы | ||
|
|
||
| | Имя выхода | Описание | Тип данных | | ||
| |------------|----------|------------| | ||
| | `text` | Исходное текстовое содержимое, которое было сохранено в файл | STRING | |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | 🏗️ Heavy lift
Replace the translation preface with the required documentation structure.
Remove the meta-introduction on Line 3 and add localized equivalents of Function Description, Working Principle, Input Parameter Description, Output Result Description, and Usage Suggestions. Also remove the prohibited H1 heading.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SaveText/ru.md` around lines 1 - 19, Update the
SaveText documentation by removing the H1 heading and translation preface, then
organize the Russian content into localized sections for Function Description,
Working Principle, Input Parameter Description, Output Result Description, and
Usage Suggestions. Preserve the existing parameter and output details while
placing them under the appropriate required sections.
Source: Coding guidelines
Comment on lines
+1
to
+19
| # SaveText | ||
|
|
||
| ## Genel Bakış | ||
|
|
||
| Save Text düğümü, metin içeriğini çıktı dizinindeki bir dosyaya yazar. .txt, .md veya .json formatında kaydetmeyi destekler ve geçerli bir JSON sağlandığında otomatik olarak JSON düzgün yazdırma işlemini gerçekleştirir. | ||
|
|
||
| ## Girdiler | ||
|
|
||
| | Parametre | Açıklama | Veri Türü | Gerekli | Aralık | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `text` | Bir dosyaya kaydedilecek metin içeriği | STRING | Evet | - | | ||
| | `filename_prefix` | Çıktı dosya adı için ön ek (varsayılan: "ComfyUI") | STRING | Hayır | - | | ||
| | `format` | Metnin kaydedileceği dosya biçimi (varsayılan: "txt") | STRING | Hayır | `"txt"`<br>`"md"`<br>`"json"` | | ||
|
|
||
| ## Çıktılar | ||
|
|
||
| | Çıktı Adı | Açıklama | Veri Türü | | ||
| |-------------|-------------|-----------| | ||
| | `text` | Dosyaya kaydedilen orijinal metin içeriği | STRING | |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Use the required documentation structure.
This page starts with an H1 and uses only Genel Bakış, Girdiler, and Çıktılar, omitting the required five-part structure. Add the localized equivalents of the required sections and remove the level-one heading.
As per coding guidelines: Markdown node documentation must use the required five-part structure and must not use level-one headings.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SaveText/tr.md` around lines 1 - 19, Update the
SaveText documentation to remove the level-one “SaveText” heading and organize
the page into the required five-part structure, adding the missing localized
Turkish sections alongside the existing “Genel Bakış”, “Girdiler”, and
“Çıktılar” sections. Preserve the current content within the appropriate
sections.
Source: Coding guidelines
Comment on lines
+1
to
+19
| # SaveText | ||
|
|
||
| ## 概述 | ||
|
|
||
| 儲存文字節點將文字內容寫入輸出目錄中的檔案。它支援以 .txt、.md 或 .json 格式儲存，並在提供有效 JSON 時自動處理 JSON 美化排版。 | ||
|
|
||
| ## 輸入 | ||
|
|
||
| | 參數 | 說明 | 資料類型 | 必要 | 範圍 | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `text` | 要儲存到檔案的文字內容 | STRING | 是 | - | | ||
| | `filename_prefix` | 輸出檔案名稱的前綴（預設："ComfyUI"） | STRING | 否 | - | | ||
| | `format` | 儲存文字的檔案格式（預設："txt"） | STRING | 否 | `"txt"`<br>`"md"`<br>`"json"` | | ||
|
|
||
| ## 輸出 | ||
|
|
||
| | 輸出名稱 | 說明 | 資料類型 | | ||
| |-------------|-------------|-----------| | ||
| | `text` | 已儲存到檔案的原始文字內容 | STRING | |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Use the required documentation structure.
This page starts with an H1 and omits the five required documentation sections and their localized equivalents. Reorganize the overview and tables accordingly while retaining the localized input/output headings.
As per coding guidelines: Markdown node documentation must use the required five-part structure and must not use level-one headings.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SaveText/zh-TW.md` around lines 1 - 19, Reorganize
the SaveText documentation to remove the level-one “SaveText” heading and follow
the required five-part node documentation structure, adding each section’s
localized equivalent while preserving the existing Traditional Chinese input and
output headings. Move the overview and input/output tables into their
appropriate sections without changing the documented parameters or values.
Source: Coding guidelines
Comment on lines
+1
to
+17
| # SaveText | ||
|
|
||
| 保存文本节点将文本内容写入输出目录中的文件。它支持以 .txt、.md 或 .json 格式保存，并在提供有效 JSON 时自动处理 JSON 美化打印。 | ||
|
|
||
| ## ## 输入 | ||
|
|
||
| | 参数 | 描述 | 数据类型 | 是否必填 | 范围 | | ||
| |-----------|-------------|-----------|----------|-------| | ||
| | `text` | 要保存到文件的文本内容 | STRING | 是 | - | | ||
| | `filename_prefix` | 输出文件名的前缀（默认值："ComfyUI"） | STRING | 否 | - | | ||
| | `format` | 保存文本的文件格式（默认值："txt"） | STRING | 否 | `"txt"`<br>`"md"`<br>`"json"` | | ||
|
|
||
| ## ## 输出 | ||
|
|
||
| | 输出名 | 描述 | 数据类型 | | ||
| |-------------|-------------|-----------| | ||
| | `text` | 已保存到文件的原始文本内容 | STRING | |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
Fix the malformed headings and add the required sections.
The page starts with an H1, omits the required five-part structure, and uses ## ## 输入 / ## ## 输出, which can render stray ## text in the headings. Replace these with properly localized section headings and restructure the page according to the documentation contract.
As per coding guidelines: Markdown node documentation must use the required five-part structure, must not use level-one headings, and must use standardized input/output titles.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/SaveText/zh.md` around lines 1 - 17, Restructure
the SaveText documentation around the required five-part node format: remove the
level-one “SaveText” heading, add the localized sections for description,
inputs, outputs, examples, and notes as required by the documentation contract,
and rename the malformed “## ## 输入” and “## ## 输出” headings to the standardized
input/output titles without embedded `##` text. Preserve the existing input and
output tables under their corrected sections.
Source: Coding guidelines
… constraint
- Fix 3 files with AI translation preamble leaked into doc body
- Fix 2 zh/zh-TW files with doubled '## ##' heading markers
- Clarify GeminiVideoOmni whitespace-strip constraint wording
- Add strip_ai_preamble() to batch_translate_docs.py with 11-language patterns
- Fix replace_heading_placeholders to handle '## {heading_xxx}' from AI
- Fix doubled heading markers (## ## 输入 → ## 输入) in zh/zh-TW translations - Remove Japanese preamble leak in GeminiVideoOmni/ja.md - Rewrite corrupted Arabic GeminiVideoOmni/ar.md (had prompt template instead of translation) - All translations now match updated en.md content (parameter description changes)
…niVideoOmni" This reverts commit c74e9f9.
…deoOmni - Uses fixed batch_translate_docs.py (preamble stripping, heading dedup, frontend param names) - Fixes Arabic preamble leak in GeminiVideoOmni/ar.md - Fixes Persian heading level in GeminiVideoOmni/fa.md (H3→H2) - Fixes TextOverlay zh/zh-TW doubled output headings
There was a problem hiding this comment.
Actionable comments posted: 13
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@comfyui_embedded_docs/docs/CreateBoundingBoxes/ar.md`:
- Line 14: Correct the Arabic gender agreement in the last_incoming description
by replacing the feminine relative pronoun “التي” with the masculine “الذي” when
referring to “المنبع”.
- Line 13: Update the Arabic documentation text in the “حالة المحرر” table entry
by changing “أولاً” to the correctly placed tanwin form “أولًا”; leave the
surrounding wording unchanged.
In `@comfyui_embedded_docs/docs/CreateBoundingBoxes/zh-TW.md`:
- Around line 5-6: Add a blank line after the `## 輸入` and `## 輸出` headings in
the documented Markdown sections before their respective tables, matching the
formatting used in the sibling `zh.md` file and satisfying markdownlint
MD022/MD058.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/ar.md`:
- Line 1: Update the document title heading from level one to level two, and
demote the existing input and output section headings from level two to level
three. Preserve the heading text and document content.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/es.md`:
- Line 1: Update the document title from a level-one heading to ##, then shift
each existing section heading down one level to preserve the heading hierarchy.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/fa.md`:
- Line 1: Update the document title in the Gemini Omni documentation from a
level-one heading to level two, and increase each existing section heading by
one level so the heading hierarchy remains consistent.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/fr.md`:
- Line 1: Update the document title in the GeminiVideoOmni French documentation
from a level-one heading to level two, and shift each existing section heading
down one level accordingly while preserving the document structure and content.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/ja.md`:
- Line 1: Update the document title heading from level one to level two by
replacing the single-hash heading marker in “Google Gemini Omni（動画）” with a
double-hash marker.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/ru.md`:
- Line 5: Update the section titles in ru.md from “Входные данные” and “Выходные
данные” to the standardized “Входы” and “Выходы”, preserving the surrounding
document content.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/tr.md`:
- Line 1: Change the document title heading from a level-one heading to a
level-two heading, preserving the existing “Google Gemini Omni (Video)” title
text and applying the documentation convention that node docs must not use
level-one headings.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/zh-TW.md`:
- Line 1: Replace the level-one heading at the start of the document with the
appropriate lower-level heading, preserving the existing title text and
documentation content.
- Around line 5-6: Insert a blank line between the “輸入” and “輸出” headings and
their following tables in the GeminiVideoOmni documentation, matching the
spacing used in zh.md and satisfying Markdown heading/table spacing rules.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/zh.md`:
- Line 1: Change the document’s top-level heading from a level-one heading to
the appropriate lower-level heading, preserving the existing title text “Google
Gemini Omni（视频）”.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 7b53cbbd-2b9a-43aa-a78e-ec933cef9814
📒 Files selected for processing (28)
comfyui_embedded_docs/docs/CreateBoundingBoxes/ar.mdcomfyui_embedded_docs/docs/CreateBoundingBoxes/es.mdcomfyui_embedded_docs/docs/CreateBoundingBoxes/fa.mdcomfyui_embedded_docs/docs/CreateBoundingBoxes/fr.mdcomfyui_embedded_docs/docs/CreateBoundingBoxes/ja.mdcomfyui_embedded_docs/docs/CreateBoundingBoxes/ko.mdcomfyui_embedded_docs/docs/CreateBoundingBoxes/pt-BR.mdcomfyui_embedded_docs/docs/CreateBoundingBoxes/ru.mdcomfyui_embedded_docs/docs/CreateBoundingBoxes/tr.mdcomfyui_embedded_docs/docs/CreateBoundingBoxes/zh-TW.mdcomfyui_embedded_docs/docs/CreateBoundingBoxes/zh.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/ar.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/en.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/es.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/fa.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/fr.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/ja.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/ko.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/pt-BR.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/ru.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/tr.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/zh-TW.mdcomfyui_embedded_docs/docs/GeminiVideoOmni/zh.mdcomfyui_embedded_docs/docs/Save3DAdvanced/ru.mdcomfyui_embedded_docs/docs/SavePointCloud/ja.mdcomfyui_embedded_docs/docs/SaveText/ru.mdcomfyui_embedded_docs/docs/TextOverlay/zh-TW.mdcomfyui_embedded_docs/docs/TextOverlay/zh.md
💤 Files with no reviewable changes (3)
- comfyui_embedded_docs/docs/SaveText/ru.md
- comfyui_embedded_docs/docs/SavePointCloud/ja.md
- comfyui_embedded_docs/docs/Save3DAdvanced/ru.md
| | `bboxes` | مربعات إحاطة أو عناصر أو سلسلة JSON لتهيئة مساحة الرسم. قيمة جديدة من المنبع تُهيئ مساحة الرسم؛ التعديلات التي تُجرى على مساحة الرسم لها الأولوية وتُحتفظ بها حتى تتغير القيمة القادمة من المنبع مرة أخرى. | BOUNDING_BOX, ARRAY, STRING | لا | - | | ||
| | `العرض` | عرض مساحة الرسم وشبكة البكسل لمربعات الإحاطة (الافتراضي: 1024). | INT | نعم | 64 إلى 16384 (الخطوة: 16) | | ||
| | `الارتفاع` | ارتفاع مساحة الرسم وشبكة البكسل لمربعات الإحاطة (الافتراضي: 1024). | INT | نعم | 64 إلى 16384 (الخطوة: 16) | | ||
| | `حالة المحرر` | ارسم مربعات إحاطة واضبط نوع كل مربع ونصه ووصفه ولوحة ألوانه. ابدأ بعنصر الخلفية أولاً وانتهي بالمقدمة أخيرًا. | BOUNDING_BOXES | نعم | - | |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix tanwin placement: "أولاً" → "أولًا".
The tanwin should be written on the letter preceding the alif (lam), not on the alif itself, per standard Arabic orthography rules.
✏️ Proposed fix
-| `حالة المحرر` | ارسم مربعات إحاطة واضبط نوع كل مربع ونصه ووصفه ولوحة ألوانه. ابدأ بعنصر الخلفية أولاً وانتهي بالمقدمة أخيرًا. | BOUNDING_BOXES | نعم | - |
+| `حالة المحرر` | ارسم مربعات إحاطة واضبط نوع كل مربع ونصه ووصفه ولوحة ألوانه. ابدأ بعنصر الخلفية أولًا وانتهي بالمقدمة أخيرًا. | BOUNDING_BOXES | نعم | - |📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| | `حالة المحرر` | ارسم مربعات إحاطة واضبط نوع كل مربع ونصه ووصفه ولوحة ألوانه. ابدأ بعنصر الخلفية أولاً وانتهي بالمقدمة أخيرًا. | BOUNDING_BOXES | نعم | - | | |
| | `حالة المحرر` | ارسم مربعات إحاطة واضبط نوع كل مربع ونصه ووصفه ولوحة ألوانه. ابدأ بعنصر الخلفية أولًا وانتهي بالمقدمة أخيرًا. | BOUNDING_BOXES | نعم | - | |
🧰 Tools
🪛 LanguageTool
[typographical] ~13-~13: لأنه من الأخطاء الشائعة كتابة التنوين على الألف، والصحيح أن تُكتب على الحرف الذي قبل الألف؛ لأن التنوين نون ساكنة والألف ساكنة، فلا يجتمع ساكنان
: "أولًا"
Context: ... ووصفه ولوحة ألوانه. ابدأ بعنصر الخلفية أولاً وانتهي بالمقدمة أخيرًا. | BOUNDING_BOXE...
(typo_000_tanwin_nasb)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/CreateBoundingBoxes/ar.md` at line 13, Update the
Arabic documentation text in the “حالة المحرر” table entry by changing “أولاً”
to the correctly placed tanwin form “أولًا”; leave the surrounding wording
unchanged.
Source: Linters/SAST tools
| | `العرض` | عرض مساحة الرسم وشبكة البكسل لمربعات الإحاطة (الافتراضي: 1024). | INT | نعم | 64 إلى 16384 (الخطوة: 16) | | ||
| | `الارتفاع` | ارتفاع مساحة الرسم وشبكة البكسل لمربعات الإحاطة (الافتراضي: 1024). | INT | نعم | 64 إلى 16384 (الخطوة: 16) | | ||
| | `حالة المحرر` | ارسم مربعات إحاطة واضبط نوع كل مربع ونصه ووصفه ولوحة ألوانه. ابدأ بعنصر الخلفية أولاً وانتهي بالمقدمة أخيرًا. | BOUNDING_BOXES | نعم | - | | ||
| | `last_incoming` | حالة داخلية تُدار بواسطة مساحة الرسم: قيمة مربعات الإحاطة القادمة من المنبع التي قامت بتهيئتها آخر مرة. اتركه فارغًا لإعادة تهيئة مساحة الرسم من مدخل مربعات الإحاطة في التشغيل التالي. | BOUNDING_BOXES | لا | - | |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix gender agreement: "المنبع التي" → "المنبع الذي".
"المنبع" is masculine, so the relative pronoun should be "الذي" not "التي".
✏️ Proposed fix
-| `last_incoming` | حالة داخلية تُدار بواسطة مساحة الرسم: قيمة مربعات الإحاطة القادمة من المنبع التي قامت بتهيئتها آخر مرة. اتركه فارغًا لإعادة تهيئة مساحة الرسم من مدخل مربعات الإحاطة في التشغيل التالي. | BOUNDING_BOXES | لا | - |
+| `last_incoming` | حالة داخلية تُدار بواسطة مساحة الرسم: قيمة مربعات الإحاطة القادمة من المنبع الذي قام بتهيئتها آخر مرة. اتركه فارغًا لإعادة تهيئة مساحة الرسم من مدخل مربعات الإحاطة في التشغيل التالي. | BOUNDING_BOXES | لا | - |📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| | `last_incoming` | حالة داخلية تُدار بواسطة مساحة الرسم: قيمة مربعات الإحاطة القادمة من المنبع التي قامت بتهيئتها آخر مرة. اتركه فارغًا لإعادة تهيئة مساحة الرسم من مدخل مربعات الإحاطة في التشغيل التالي. | BOUNDING_BOXES | لا | - | | |
| | `last_incoming` | حالة داخلية تُدار بواسطة مساحة الرسم: قيمة مربعات الإحاطة القادمة من المنبع الذي قام بتهيئتها آخر مرة. اتركه فارغًا لإعادة تهيئة مساحة الرسم من مدخل مربعات الإحاطة في التشغيل التالي. | BOUNDING_BOXES | لا | - | |
🧰 Tools
🪛 LanguageTool
[grammar] ~14-~14: هل تقصد "المنبع الذي"?
Context: ...ة الرسم: قيمة مربعات الإحاطة القادمة من المنبع التي قامت بتهيئتها آخر مرة. اتركه فارغًا لإع...
(gender_0010_alladhi)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/CreateBoundingBoxes/ar.md` at line 14, Correct the
Arabic gender agreement in the last_incoming description by replacing the
feminine relative pronoun “التي” with the masculine “الذي” when referring to
“المنبع”.
Source: Linters/SAST tools
| @@ -1,45 +1,17 @@ | |||
| # GeminiVideoOmni | |||
| # Google Gemini Omni (فيديو) | |||
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Use ## or lower instead of a level-one heading.
As per coding guidelines, ComfyUI node documentation should not use level-one (#) headings. Change the title to ## and shift section headings (## المدخلات, ## المخرجات) to ### accordingly.
🔧 Proposed fix
-# Google Gemini Omni (فيديو)
+## Google Gemini Omni (فيديو)And cascade section headings:
-## المدخلات
+### المدخلات-## المخرجات
+### المخرجات📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| # Google Gemini Omni (فيديو) | |
| ## Google Gemini Omni (فيديو) |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/ar.md` at line 1, Update the
document title heading from level one to level two, and demote the existing
input and output section headings from level two to level three. Preserve the
heading text and document content.
Source: Coding guidelines
| @@ -1,16 +1,16 @@ | |||
| # GeminiVideoOmni | |||
| # Google Gemini Omni (Video) | |||
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Use ## or lower instead of a level-one heading.
As per coding guidelines, ComfyUI node documentation should not use level-one (#) headings. Change the title to ## and shift section headings to ### accordingly.
🔧 Proposed fix
-# Google Gemini Omni (Video)
+## Google Gemini Omni (Video)And cascade section headings:
-## Entradas
+### Entradas-## Salidas
+### Salidas🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/es.md` at line 1, Update the
document title from a level-one heading to ##, then shift each existing section
heading down one level to preserve the heading hierarchy.
Source: Coding guidelines
| Создайте видео со звуком по текстовому запросу, используя модель Google Gemini Omni Flash. При необходимости можно предоставить референсные изображения и/или видео для управления результатом или его редактирования. Укажите желаемую длительность (3–10 с) и соотношение сторон (16:9 или 9:16) непосредственно в запросе. | ||
|
|
||
| ## Входные параметры | ||
| ## Входные данные |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix section titles to match the standardized Russian titles.
As per coding guidelines, ru.md files should use "Входы/Выходы" as section titles. The file uses "Входные данные" and "Выходные данные" instead.
✏️ Proposed fix
-## Входные данные
+## Входы-## Выходные данные
+## ВыходыAlso applies to: 17-17
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/ru.md` at line 5, Update the
section titles in ru.md from “Входные данные” and “Выходные данные” to the
standardized “Входы” and “Выходы”, preserving the surrounding document content.
Source: Coding guidelines
| @@ -1,25 +1,25 @@ | |||
| # GeminiVideoOmni | |||
| # Google Gemini Omni (Video) | |||
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value
Level-one heading violates documentation guidelines.
As per coding guidelines, ComfyUI node documentation should not use level-one headings. Line 1 uses # Google Gemini Omni (Video). This appears to be a systematic pattern across all node docs, but the guideline is explicit. Consider using ## or a different convention consistently.
As per coding guidelines: "Do not use level-one headings."
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/tr.md` at line 1, Change the
document title heading from a level-one heading to a level-two heading,
preserving the existing “Google Gemini Omni (Video)” title text and applying the
documentation convention that node docs must not use level-one headings.
Source: Coding guidelines
| @@ -1,25 +1,23 @@ | |||
| # GeminiVideoOmni | |||
| # Google Gemini Omni（影片） | |||
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value
Level-one heading violates documentation guidelines.
As per coding guidelines, ComfyUI node documentation should not use level-one headings. Line 1 uses # Google Gemini Omni（影片）. This is a systematic pattern across all node docs.
As per coding guidelines: "Do not use level-one headings."
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/zh-TW.md` at line 1, Replace the
level-one heading at the start of the document with the appropriate lower-level
heading, preserving the existing title text and documentation content.
Source: Coding guidelines
| @@ -1,25 +1,25 @@ | |||
| # GeminiVideoOmni | |||
| # Google Gemini Omni（视频） | |||
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value
Level-one heading violates documentation guidelines.
As per coding guidelines, ComfyUI node documentation should not use level-one headings. Line 1 uses # Google Gemini Omni（视频）. This is a systematic pattern across all node docs.
As per coding guidelines: "Do not use level-one headings."
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@comfyui_embedded_docs/docs/GeminiVideoOmni/zh.md` at line 1, Change the
document’s top-level heading from a level-one heading to the appropriate
lower-level heading, preserving the existing title text “Google Gemini
Omni（视频）”.
Source: Coding guidelines
- Restore all 22 translation files from origin/main (preserving original quality) - CreateBoundingBoxes: add new bboxes + last_incoming rows with translated descriptions - GeminiVideoOmni: update prompt description with whitespace-stripping constraint - GeminiVideoOmni/ar.md: strip 30-line AI prompt template leak, keep clean translation - Zero existing content re-translated — only additions and one description update
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Added documentation for 7 new nodes:
Each with en.md + 11 language translations (zh, zh-TW, es, fr, ja, ko, ru, ar, tr, pt-BR, fa).
Files
95 files changed, 2333 insertions(+), 11 deletions(-)
Source
Generated via doc_automation pipeline.
Checklist