From 9dfd54ea123555c2cf0d686cde9469d1fe8d1d41 Mon Sep 17 00:00:00 2001 From: jianwei1 Date: Tue, 27 Jan 2026 00:45:34 +0000 Subject: [PATCH 1/2] fix: update Bible content handling guidelines in translation schema --- .../journeyAiTranslate/journeyAiTranslate.ts | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/apis/api-journeys-modern/src/schema/journeyAiTranslate/journeyAiTranslate.ts b/apis/api-journeys-modern/src/schema/journeyAiTranslate/journeyAiTranslate.ts index b1896bf65a5..f7cc71d8458 100644 --- a/apis/api-journeys-modern/src/schema/journeyAiTranslate/journeyAiTranslate.ts +++ b/apis/api-journeys-modern/src/schema/journeyAiTranslate/journeyAiTranslate.ts @@ -366,11 +366,22 @@ Field names to translate per block type: Ensure translations maintain the meaning while being culturally appropriate for ${input.textLanguageName}. Keep translations concise and effective for UI context (e.g., button labels should remain short). -If you are in the process of translating and you recognize passages from the +IMPORTANT - Bible Content Handling: +- If you are in the process of translating and you recognize passages from the Bible you should not translate that content. Instead, you should rely on a Bible translation available from the previous journey analysis and use that content directly. You must never make changes to content from the Bible yourself. -If there is no Bible translation was available, use the the most popular English Bible translation available. +If there is no Bible translation available, use the the most popular English Bible translation available. + +- Bible REFERENCES (book names like "Luke", "Mark", "James" followed by chapter:verse + notation like "2:10" or "13:1") MUST be translated to the target language. + Examples: "Luke 2:10" should become "Lucas 2:10" in Spanish, "Lukas 2,10" in German + (note German uses comma instead of colon). Translate the book name and adapt the + chapter:verse separator to match the target language's conventions. + + - References may appear in various formats (e.g., "Luke 2:10", "Luke 2:10-12", + "Mark 10:1, 3"). Always translate the book name and preserve the reference structure + while adapting formatting to the target language. ` // Create a map of valid block IDs for quick lookup From d6e1273a9fcc980dab6ef036be4c8f23af988fc6 Mon Sep 17 00:00:00 2001 From: jianwei1 Date: Tue, 27 Jan 2026 20:17:57 +0000 Subject: [PATCH 2/2] fix: update reference formats in Bible translation guidelines --- .../src/schema/journeyAiTranslate/journeyAiTranslate.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apis/api-journeys-modern/src/schema/journeyAiTranslate/journeyAiTranslate.ts b/apis/api-journeys-modern/src/schema/journeyAiTranslate/journeyAiTranslate.ts index f7cc71d8458..f1db185fbce 100644 --- a/apis/api-journeys-modern/src/schema/journeyAiTranslate/journeyAiTranslate.ts +++ b/apis/api-journeys-modern/src/schema/journeyAiTranslate/journeyAiTranslate.ts @@ -380,7 +380,7 @@ If there is no Bible translation available, use the the most popular English Bib chapter:verse separator to match the target language's conventions. - References may appear in various formats (e.g., "Luke 2:10", "Luke 2:10-12", - "Mark 10:1, 3"). Always translate the book name and preserve the reference structure + "Mark 10:1, 3", "1 Peter 3:15"). Always translate the book name and preserve the reference structure while adapting formatting to the target language. `