Prompting - Revision history

Olibouban at 19:05, 3 April 2026

2026-04-03T19:05:49Z

← Older revision		Revision as of 19:05, 3 April 2026
Line 21:		Line 21:

	[[File:ProjectPrompt.png\|center\|600px]]		[[File:ProjectPrompt.png\|center\|600px]]

			== String Level Prompting ==

			From the String Manager, open the expanded view for a string, add the specific prompt, and click the 'save' button to the right of the input text:

			[[File:StringPrompting.png\|center\|600px]]

	== Context Prompting ==		== Context Prompting ==

Olibouban: /* Sample PXML */

2025-12-10T22:34:04Z

Sample PXML

← Older revision		Revision as of 22:34, 10 December 2025
Line 53:		Line 53:

	== Sample PXML ==		== Sample PXML ==
	The PXML section will look like, if the translation level prompting is configured with <code>{SRC} to {TARGET}</code>:		The PXML section will look like, if the translation level prompting is configured with <code>{SRC} to {TARGET}</code> (see the Note above):

	<pre>		<pre>

Olibouban: /* Sample PXML */

2025-12-10T22:33:26Z

Sample PXML

← Older revision		Revision as of 22:33, 10 December 2025
Line 53:		Line 53:

	== Sample PXML ==		== Sample PXML ==
	The PXML section will look like, if the translation level prompting is configured with <code>{{SRC}} to {{TARGET}}</code>:		The PXML section will look like, if the translation level prompting is configured with <code>{SRC} to {TARGET}</code>:

	<pre>		<pre>
Line 60:		Line 60:
	<pxml>		<pxml>
	<!-- system_prompt is a concatenation of the translation connection system prompt and the project prompt in Localyzer -->		<!-- system_prompt is a concatenation of the translation connection system prompt and the project prompt in Localyzer -->
	<system_prompt><![CDATA[ As a professional translator, translate an application user interface text from {{SRC}} to {{TARGET}}. Special considerations for UI: Brevity is crucial, Clarity over creativity, Consistency with UI patterns, Action-oriented language. Return only the translated text-no explanation. The application is Globalyzer and Localyzer described here https://lingoport.com/software-localization-tools/localyzer-l10n/. ]]></system_prompt>		<system_prompt><![CDATA[ As a professional translator, translate an application user interface text from {SRC} to {TARGET}. Special considerations for UI: Brevity is crucial, Clarity over creativity, Consistency with UI patterns, Action-oriented language. Return only the translated text-no explanation. The application is Globalyzer and Localyzer described here https://lingoport.com/software-localization-tools/localyzer-l10n/. ]]></system_prompt>
	<resources>		<resources>
	<string translate="1" segmentID="2" minLength="" maxLength="10">		<string translate="1" segmentID="2" minLength="" maxLength="10">

Olibouban: /* Sample PXML */

2025-12-10T22:32:29Z

Sample PXML

← Older revision		Revision as of 22:32, 10 December 2025
Line 53:		Line 53:

	== Sample PXML ==		== Sample PXML ==
	The PXML section will look like, if the translation level prompting is configured with <code>[[SRC]] to [[TARGET]]</code>:		The PXML section will look like, if the translation level prompting is configured with <code>{{SRC}} to {{TARGET}}</code>:

	<pre>		<pre>
Line 60:		Line 60:
	<pxml>		<pxml>
	<!-- system_prompt is a concatenation of the translation connection system prompt and the project prompt in Localyzer -->		<!-- system_prompt is a concatenation of the translation connection system prompt and the project prompt in Localyzer -->
	<system_prompt><![CDATA[ As a professional translator, translate an application user interface text from [[SRC]] to [[TARGET]]. Special considerations for UI: Brevity is crucial, Clarity over creativity, Consistency with UI patterns, Action-oriented language. Return only the translated text-no explanation. The application is Globalyzer and Localyzer described here https://lingoport.com/software-localization-tools/localyzer-l10n/. ]]></system_prompt>		<system_prompt><![CDATA[ As a professional translator, translate an application user interface text from {{SRC}} to {{TARGET}}. Special considerations for UI: Brevity is crucial, Clarity over creativity, Consistency with UI patterns, Action-oriented language. Return only the translated text-no explanation. The application is Globalyzer and Localyzer described here https://lingoport.com/software-localization-tools/localyzer-l10n/. ]]></system_prompt>
	<resources>		<resources>
	<string translate="1" segmentID="2" minLength="" maxLength="10">		<string translate="1" segmentID="2" minLength="" maxLength="10">

Olibouban: /* Sample PXML */

2025-12-10T22:31:44Z

Sample PXML

← Older revision		Revision as of 22:31, 10 December 2025
Line 53:		Line 53:

	== Sample PXML ==		== Sample PXML ==
	The PXML section will look like, if t :		The PXML section will look like, if the translation level prompting is configured with <code>[[SRC]] to [[TARGET]]</code>:

	<pre>		<pre>

Olibouban: /* Sample PXML */

2025-12-10T22:30:58Z

Sample PXML

← Older revision		Revision as of 22:30, 10 December 2025
Line 53:		Line 53:

	== Sample PXML ==		== Sample PXML ==
	The PXML section will look like:		The PXML section will look like, if t :

	<pre>		<pre>
Line 60:		Line 60:
	<pxml>		<pxml>
	<!-- system_prompt is a concatenation of the translation connection system prompt and the project prompt in Localyzer -->		<!-- system_prompt is a concatenation of the translation connection system prompt and the project prompt in Localyzer -->
	<system_prompt><![CDATA[ As a professional translator, translate an application user interface text from ~~English~~ to ~~Latin~~. Special considerations for UI: Brevity is crucial, Clarity over creativity, Consistency with UI patterns, Action-oriented language. Return only the translated text-no explanation. The application is Globalyzer and Localyzer described here https://lingoport.com/software-localization-tools/localyzer-l10n/. ]]></system_prompt>		<system_prompt><![CDATA[ As a professional translator, translate an application user interface text from [[SRC]] to [[TARGET]]. Special considerations for UI: Brevity is crucial, Clarity over creativity, Consistency with UI patterns, Action-oriented language. Return only the translated text-no explanation. The application is Globalyzer and Localyzer described here https://lingoport.com/software-localization-tools/localyzer-l10n/. ]]></system_prompt>
	<resources>		<resources>
	<string translate="1" segmentID="2" minLength="" maxLength="10">		<string translate="1" segmentID="2" minLength="" maxLength="10">

Olibouban: /* Translation Connection Level */

2025-12-10T22:29:27Z

Translation Connection Level

← Older revision		Revision as of 22:29, 10 December 2025
Line 14:		Line 14:
	Notes:		Notes:
	* For LLMs, the variables <code>${SOURCE_LOCALE}</code> and <code>${TARGET_LOCALE}</code> must be part of the prompt.		* For LLMs, the variables <code>${SOURCE_LOCALE}</code> and <code>${TARGET_LOCALE}</code> must be part of the prompt.
	* For TMSs with PXML, check with the TMS as to how the locale code can be parameterized. It should use <code>${SOURCE_LOCALE}</code> and <code>${TARGET_LOCALE}</code> only when sending one prep kit per locale. The TMS may not want any indication or maybe parameters '''such as''' [SRC] and [TARGET].		* For TMSs with PXML, check with the TMS as to how the locale code can be parameterized. It should use <code>${SOURCE_LOCALE}</code> and <code>${TARGET_LOCALE}</code> only when sending one prep kit per locale. The TMS may not want any indication. Or maybe parameters '''such as''' [SRC] and [TARGET] can be leverage.

	== Project Level Prompting ==		== Project Level Prompting ==

Olibouban: /* Translation Connection Level */

2025-12-10T22:28:45Z

Translation Connection Level

← Older revision		Revision as of 22:28, 10 December 2025
Line 14:		Line 14:
	Notes:		Notes:
	* For LLMs, the variables <code>${SOURCE_LOCALE}</code> and <code>${TARGET_LOCALE}</code> must be part of the prompt.		* For LLMs, the variables <code>${SOURCE_LOCALE}</code> and <code>${TARGET_LOCALE}</code> must be part of the prompt.
	* For TMSs with PXML, check with the TMS as to how the locale code can be parameterized. It should use <code>${SOURCE_LOCALE}</code> and <code>${TARGET_LOCALE}</code> only when sending one prep kit per locale.		* For TMSs with PXML, check with the TMS as to how the locale code can be parameterized. It should use <code>${SOURCE_LOCALE}</code> and <code>${TARGET_LOCALE}</code> only when sending one prep kit per locale. The TMS may not want any indication or maybe parameters '''such as''' [SRC] and [TARGET].

	== Project Level Prompting ==		== Project Level Prompting ==

Olibouban: /* Translation Connection Level */

2025-12-10T22:27:45Z

Translation Connection Level

← Older revision		Revision as of 22:27, 10 December 2025
Line 12:		Line 12:
	[[File:ConnectionPrompt.png\|center\|600px]]		[[File:ConnectionPrompt.png\|center\|600px]]

	~~Note~~: ~~The~~ variables <code>${SOURCE_LOCALE}</code> and <code>${TARGET_LOCALE}</code> must be part of the prompt.		Notes:
			* For LLMs, the variables <code>${SOURCE_LOCALE}</code> and <code>${TARGET_LOCALE}</code> must be part of the prompt.
			* For TMSs with PXML, check with the TMS as to how the locale code can be parameterized. It should use <code>${SOURCE_LOCALE}</code> and <code>${TARGET_LOCALE}</code> only when sending one prep kit per locale.

	== Project Level Prompting ==		== Project Level Prompting ==

Olibouban: /* Overview */

2025-12-04T15:38:52Z

Overview

← Older revision		Revision as of 15:38, 4 December 2025
Line 1:		Line 1:
	== ~~Overview~~ ==		== Introduction ==

	Some translation connections can take advantage of LLM style prompting. Lingoport provides the ability to pass prompting Localyzer to either TMS with LLM as part of their workflow, or directly to an LLM.		Some translation connections can take advantage of LLM style prompting. Lingoport provides the ability to pass prompting Localyzer to either TMS with LLM as part of their workflow, or directly to an LLM.