<div id="main-content" class="wiki-content group">
<h1 id="TraduçãodeProcessos-Índice">Index</h1>
<p>
<style type='text/css'>/*<![CDATA[*/
div.rbtoc1412695698790 {
padding: 0px;
}
div.rbtoc1412695698790 ul {
list-style: none;
margin-left: 0px;
}
div.rbtoc1412695698790 li {
margin-left: 0px;
padding-left: 0px;
}
/*]]>*/
</style>
<div class='toc-macro rbtoc1412695698790'>
<ul class='toc-indentation'>
<li><span class='TOCOutline'>1</span> <a
href='#TraduçãodeProcessos-Objetivo'>Objective</a></li>
<li><span class='TOCOutline'>2</span> <a
href='#TraduçãodeProcessos-GerandoArquivosdeLiterais'>Generating
Literal Files</a></li>
<li><span class='TOCOutline'>3</span> <a
href='#TraduçãodeProcessos-TraduzindoInformaçõesdeAtividades,ObjetoseFluxos'>Translating
Information from Activities, Objects and Flows</a></li>
</ul>
</div>
</p>
<h1 id="TraduçãodeProcessos-Objetivo">Objective</h1>
<p>The objective of this guide is to demonstrate the operation of
Fluig process translation system.</p>
<h1 id="TraduçãodeProcessos-GerandoArquivosdeLiterais">Generating
Literal Files</h1>
<p>
<span>In order to generate literal files for a new diagram,
just check "Creates literal files" on the following screen:</span>
</p>
<p>
<span><br /></span>
</p>
<p>
<span><img class="confluence-embedded-image image-center"
src="http://tdn.totvs.com/download/attachments/160105353/TraducaoProcesso1.png?version=1&modificationDate=1410373914000&api=v2"
data-image-src="http://tdn.totvs.com/download/attachments/160105353/TraducaoProcesso1.png?version=1&modificationDate=1410373914000&api=v2"><br /></span>
</p>
<p>
<span>When you check “Creates literal files”, three <em>properties</em>
files are created, where literals are stored for the languages
supported by Fluig - English, Portuguese, Spanish, as in the
following image:
</span>
</p>
<p>
<span><br /></span>
</p>
<p>
<span><img class="confluence-embedded-image image-center"
src="http://tdn.totvs.com/download/attachments/160105353/TraducaoProcesso1.png?version=1&modificationDate=1410373914000&api=v2"
data-image-src="http://tdn.totvs.com/download/attachments/160105353/TraducaoProcesso1.png?version=1&modificationDate=1410373914000&api=v2"><br /></span>
</p>
<p>
<span>These files are created with three properties that are
related to process information:</span>
</p>
<ul>
<li><strong>process.category</strong> = process category;</li>
<li><strong>process.description</strong> = process description;</li>
<li><strong>process.instructions</strong> = process instructions.</li>
</ul>
<p>The category, description and instructions fields can be
regularly completed when modeling the process, without the need of any
special translation technique.</p>
<p>
However, this provided information is only used when importing,
exporting and modeling processes. For opening and moving processes,
literal file <em>strings</em> are used.
</p>
<p> </p>
<div class="aui-message warning shadowed information-macro">
<p class="title">Please note!</p>
<span class="aui-icon icon-warning">Icon</span>
<div class="message-content">
<p>These categories are internal and cannot be used elsewhere in
the process.</p>
</div>
</div>
<p> </p>
<p>
For older projects, the folder "literals" is created automatically,
both when creating new diagrams and when importing processes with
defined literals. For old projects and diagrams, the folder and the
properties files can be created using the Eclipse <em>"New
Folder"</em> and "<em>New File</em>" options, which also are available in
Fluig <em>mouse</em> context menu.
</p>
<p> </p>
<p>
<img class="confluence-embedded-image image-center"
src="http://tdn.totvs.com/download/attachments/160105353/TraducaoProcesso3.png?version=1&modificationDate=1410373951000&api=v2"
data-image-src="http://tdn.totvs.com/download/attachments/160105353/TraducaoProcesso3.png?version=1&modificationDate=1410373951000&api=v2">
</p>
<p> </p>
<p>The literal files created this way must follow the this
convention:</p>
<p>
<strong>(Diagram name) + “_en_US.properties” </strong>or<strong>
“_es.properties” </strong>or<strong> “_pt_BR.properties”</strong>.
</p>
<p>All three files must be created so that the process can be
exported. All files should contain the three basic variables mentioned
above as well as all the variables created elsewhere in the process.</p>
<p> </p>
<p>For the content of literal files, we recommend the use of the
Unicode system for replacing special characters, such as accented
characters and the use of the cedilla and tilde.</p>
<p>
The following is an example of the <em>string </em><strong>"Aprovação
de documentos fiscais"</strong> converted to Unicode:
</p>
<p>
<strong>process.description=<u>Aprova</u>\u00e7\u00e3o <u>de</u>
<u>documentos</u> <u>fiscais</u></strong>
</p>
<p>The use of Unicode prevents code inconsistencies in process
translation.</p>
<p> </p>
<h1
id="TraduçãodeProcessos-TraduzindoInformaçõesdeAtividades,ObjetoseFluxos">Translating
Information from Activities, Objects and Flows</h1>
<p>In order to translate information from activities, literals
should be created using the following semantics:</p>
<p>
<strong>(activity code) + "." + field to be translated =
"desired <em>string</em>"
</strong>.
</p>
<p>Where:</p>
<p>
<strong>Activity code:</strong> can be obtained by checking the
properties of each element of the diagram, as in the following image:
</p>
<p> </p>
<p>
<img class="confluence-embedded-image image-center"
src="http://tdn.totvs.com/download/attachments/160105353/TraducaoProcesso4.png?version=1&modificationDate=1410373968000&api=v2"
data-image-src="http://tdn.totvs.com/download/attachments/160105353/TraducaoProcesso4.png?version=1&modificationDate=1410373968000&api=v2">
</p>
<p> </p>
<p>
<strong>Field to be translated:</strong> is what you want to
translate. The field "<em>name</em>" represents the name and the field
"<em>instructions</em>" represents its instructions.
</p>
<p>
<span>In this line, when translating the activity with the code
"task6", literal file will have the following activity:</span>
</p>
<ul>
<li><strong>6.<em>name </em>= "<em>Financial
approvement</em>"
</strong>.</li>
<li><strong>6.<em>instructions</em> = "<em>In this
point of the process we have the financial approvement</em>"
</strong>.</li>
</ul>
<p> </p>
<p>
For flows, besides the "<em>name</em>" property, two other properties
can be used:
</p>
<ul>
<li><strong><em>Flow</em>:</strong> <em>string</em> used as the
value for the "Flow Activity" field;</li>
<li><strong><em>Return</em>:</strong> <em>string</em> used as the
value for the "Return Activity" field;</li>
</ul>
<p> </p>
</div>
|