Okapi Framework - User contributions [en]

Inline Codes Removal Step

2013-01-29T19:54:22Z

Fliden:

{{Steps Header}}
__TOC__
==Overview==

This step removes inline codes or content of inline codes in text units.

Takes: Filter Events. Sends: Filter Events.

Many text units contains inline codes, span of data that should be left untouched inside a translatable text, for example the tag <code></code> in a HTML paragraph. This steps allows you to make different types of removal of those codes.

==Parameters==

<cite>What to remove</cite> — Select the type of data to remove. A code is made of two parts: its markers (always there) and its content (optional). For example, an inline code in XLIFF can be like this:

<bpt id="1">&lt;b&gt;</bpt>

The parts in blue are the marker part, the part in yellow is the content part.

The following options are available:

* Remove code marker, but keep code content: This removes the code marker but preserve its content. In other words, the content of the code becomes part of the text.
* Remove code content, but keep code marker: This remove the code content but preserve its marker. In other words, the inline code still exists but it has been generalized and the data of the original format cannot be retrieved from it anymore.
* Remove code marker and code content: This removes the whole inline code, there is no trace of it left.

<cite>Replace line break codes with spaces (When removing content AND marker)</cite> — Set this option to replace codes with spaces where the code type = Code.TYPE_LB or the code's content contains any of the following expressions (case insensitive) or characters ( , , , \n, \r, \u0085, \u2028, \u2029). For example, inline code in XLIFF: <bpt id="1">&lt;br&gt;</bpt> NOTE: This option only applies when the "Remove code marker and code content" option is selected above.

<cite>Strip codes in the source text</cite> — Set this option to apply the removal action selected to the source text.

<cite>Strip codes in the target text</cite> — Set this option to apply the removal action selected to the target text.

<cite>Apply to non-transltable text unit</cite> — Set this option to apply the removal action even to text unit marked as non-translatable. If this option is not set, all non-translatable text units are left untouched.

==Limitations==

None known.

[[Category:Steps]]

TS Filter

2012-01-25T19:13:35Z

Fliden:

{{Filters Header}}
==Overview==

The TS Filter is an Okapi component that implements the IFilter interface for Qt TS (Translation Source) resource files. The filter is implemented in the class <code>net.sf.okapi.filters.ts.TsFilter</code> of the library.

The implementation is based on the TS specification found at http://doc.trolltech.com/4.3/linguist-ts-file-format.html.

==Processing Details==

===Line-Breaks===

The type of line-breaks of the output is the same as the one of the original input.

===Type===

In TS files the <code><translation></code> element of a message can have a <code>type</code> element indicating the state of the translation or of the message. This attribute is mapped the following way:

{| border="1" cellpadding="5" cellspacing="0"
|- valign="top"
| No <code>type</code> attribute || The entry is extracted with its target property ''approved'' set to "<code>yes</code>".
|- valign="top"
| <code>type</code> is "<code>unfinished</code>" || The entry is extracted with its target property ''approved'' set to "<code>no</code>".
|- valign="top"
| <code>type</code> is "<code>obsolete</code>" || The entry is '''not extracted'''. According the Qt manual, the entries with the translation marked as obsolete are unused entries, not just obsolete translation (with new text).
|}

===Translator Comment===

The TS filter stores <cite><translatorcomment></cite> elements as text unit Property.TRANSNOTE. This property can be used by subsequent steps or editors.

==Parameters==

===Options Tab===

====Processing mode====

<cite>Convert <byte value="[value]"/> to raw characters</cite> — Select this option to convert all <code><byte/></code> elements in the TS document to raw characters. If this option is not set, the elements will not be converted and will be treated as inline codes. Note that those characters are stored special elements in TS because they are invalid in XML, so it may be better to keep them as inline code if you are working with other XML-based formats like XLIFF or TMX.

===Inline Codes Tab===

<cite>Has inline codes as defined below:</cite> — Set this option to use the specified regular expressions on the text of the extracted items. Any match will be converted to an inline code. By default the expression is:

((%(([-0+#]?)[-0+#]?)((\d\$)?)(([\d\*]*)(\.[\d\*]*)?)[dioxXucsfeEgGpn])
|((\\r\\n)|\\a|\\b|\\f|\\n|\\r|\\t|\\v)
|(\{\d.*?\}))

{{CodeFinder Help}}

==Limitations==

None known.

[[Category:Filters]] [[Category:Translation Formats]]