Format handling - Revision history

Unhammer: /* Protecting text from translation */

2025-01-03T14:09:01Z

Protecting text from translation

2025-01-03T14:08:47Z

Protecting text from translation

2025-01-03T14:06:08Z

Protecting text from translation

2025-01-03T14:05:33Z

Official formats carried out by Apertium

2014-10-06T09:49:41Z

Link to French page

2014-05-30T09:14:31Z

Official formats carried out by Apertium

2014-05-30T09:14:03Z

2014-05-25T17:40:55Z

Formats carried out by separate packages

2014-03-17T07:59:21Z

Official formats carried out by Apertium

2014-03-17T07:56:52Z

← Older revision		Revision as of 14:09, 3 January 2025
Line 41:		Line 41:

	The format handlers protect markup from translation. But sometimes you want to protect more than what the general format handlers do. You have two main choices:		The format handlers protect markup from translation. But sometimes you want to protect more than what the general format handlers do. You have two main choices:


	* for html/xml-based formatters, surround content '''<apertium-notrans>'''. The translation pipeline will see it similarly as an empty div, and it'll pass through unchanged. This is often used in scripting or if the user knows beforehand that certain easily matchable content should not be translated.		* for html/xml-based formatters, surround content '''<apertium-notrans>'''. The translation pipeline will see it similarly as an empty div, and it'll pass through unchanged. This is often used in scripting or if the user knows beforehand that certain easily matchable content should not be translated.

@@ Line 42: / Line 42: @@
 The format handlers protect markup from translation. But sometimes you want to protect more than what the general format handlers do. You have two main choices:
-* for html/xml-based formatters, surround content in &lt;apertium-notrans&gt;. The translation pipeline will see it similarly as an empty div, and it'll pass through unchanged.
+* for html/xml-based formatters, surround content '''&lt;apertium-notrans&gt;'''. The translation pipeline will see it similarly as an empty div, and it'll pass through unchanged. This is often used in scripting or if the user knows beforehand that certain easily matchable content should not be translated.
-* Use [[CG]] (or some other tool) to add the tags MERGE_BEG / MERGE_END to the start and end of what you want protected, followed by [https://github.com/apertium/lttoolbox/pull/193 lt-merge] to protect it. This lets you dynamically protect content, with full access to linguistic analyses.
+* Use [[CG]] (or some other tool) to add the tags '''MERGE_BEG / MERGE_END''' to the start and end of what you want protected, followed by [https://github.com/apertium/lttoolbox/pull/193 lt-merge] to protect it. This lets you dynamically protect content, with full access to linguistic analyses. This is used in nno-nob to avoid translating quotes.
 == Formats carried out by separate packages ==

@@ Line 43: / Line 43: @@
 * for html/xml-based formatters, surround content in &lt;apertium-notrans&gt;. The translation pipeline will see it similarly as an empty div, and it'll pass through unchanged.
-* Use [[CG]] (or some other tool) to add MERGE_BEG / MERGE_END to the start and end of what you want protected, followed by [https://github.com/apertium/lttoolbox/pull/193 lt-merge] to protect it. This lets you dynamically protect content, with full access to linguistic analyses.
+* Use [[CG]] (or some other tool) to add the tags MERGE_BEG / MERGE_END to the start and end of what you want protected, followed by [https://github.com/apertium/lttoolbox/pull/193 lt-merge] to protect it. This lets you dynamically protect content, with full access to linguistic analyses.
 == Formats carried out by separate packages ==

@@ Line 37: / Line 37: @@
 *: <pre>text to be translated<apertium-notrans>don't translate me</apertium-notrans> translate again</pre>
 * To translate document formats like ODT, you may have to pass the infile/outfile on the command line instead of piping, e.g. do <code>apertium -f odt oc-ca in.odt out.odt</code>, not <strike><code>cat in.odt | apertium -f odt oc-ca > out.odt</code></strike>.
+== Protecting text from translation ==
+The format handlers protect markup from translation. But sometimes you want to protect more than what the general format handlers do. You have two main choices:
+* for html/xml-based formatters, surround content in &lt;apertium-notrans&gt;. The translation pipeline will see it similarly as an empty div, and it'll pass through unchanged.
+* Use [[CG]] (or some other tool) to add MERGE_BEG / MERGE_END to the start and end of what you want protected, followed by [https://github.com/apertium/lttoolbox/pull/193 lt-merge] to protect it. This lets you dynamically protect content, with full access to linguistic analyses.
 == Formats carried out by separate packages ==

← Older revision		Revision as of 09:49, 6 October 2014
Line 1:		Line 1:
			[[Support du format d'un document\|En français]]

	{{TOCD}}		{{TOCD}}

@@ Line 28: / Line 28: @@
 * '''MediaWiki''': <code>-f wikimedia</code> (<code>apertium-desmediawiki</code> -- still a work in progress, see [[Translating wikimedia]])
-There is as of yet no built-in handling of '''gettext''' <code>.po</code> files or subtitle formats, but see [[Translating gettext]] and [[Translating subtitles]] for very simple solutions.
+There is as of yet no built-in handling of '''gettext''' <code>.po</code> files or subtitle formats, but see [[Translating gettext]] and [[Translating subtitles]] for very simple solutions. More formats at [[Tips for translators]].
 Some "special" features and gotcha's:

@@ Line 220: / Line 220: @@
 * [[Apertium stream format]]
-* [[Translating gettext]]
+* [[Tips for translators]]
 [[Category:Documentation]]

@@ Line 45: / Line 45: @@
 ** [[Translating man pages|man pages]]
 ** [[Translating mnemonic files|mnemonic files]] (an alternative to <code>.po</code> files for multilingual user interfaces).
+== Limitations ==
+The apertium tools can not deal with reordered superblanks. The following example shows what happens when superblanks exist betweeen reordered words/chunks:
+<pre>
+$ echo '<i>Perro</i> <b>blanco</b>' |apertium es-en -f html
+<i>White</i> <b>dog</b>
+</pre>
+This is currently a ''hard'' problem to fix and will require changes to both the transfer engine and the transfer rules.
+Read more at [[Reordering superblanks]].
 == Format specification ==

@@ Line 10: / Line 10: @@
 <em>this is</em> a <b>test</b>
 </pre>
+To tell the whole translator to use a certain format, use <code>-f</code>, e.g. <code>apertium -f html oc-ca infile outfile</code>.
 == Official formats carried out by Apertium ==