{"ygPerms":{"resourceCapabilityList":[{"resourceType":"GROUP","capabilities":[{"name":"UPDATE"},{"name":"READ"},{"name":"WELCOME_MSG"},{"name":"PENDING_COUNT"},{"name":"ACTIVITY_LOGS"}]},{"resourceType":"PHOTO","capabilities":[{"name":"READ"},{"name":"READ"},{"name":"UPLOAD"},{"name":"UPDATE"},{"name":"DELETE"},{"name":"COPY"},{"name":"MOVE"},{"name":"APPROVE"},{"name":"UPLOADTEMP"},{"name":"GROUPCOVER"}]},{"resourceType":"FILE","capabilities":[{"name":"READ"},{"name":"CREATE"},{"name":"UPDATE"},{"name":"DELETE"},{"name":"AUTO_SEND"}]},{"resourceType":"MEMBER","capabilities":[{"name":"READ"},{"name":"READ"},{"name":"EDIT_MODERATOR"},{"name":"DELETE"},{"name":"CREATE"},{"name":"UPDATE"},{"name":"BAN"}]},{"resourceType":"LINK","capabilities":[{"name":"READ"},{"name":"CREATE"},{"name":"UPDATE"},{"name":"DELETE"},{"name":"MOVE_LINK"}]},{"resourceType":"CALENDAR","capabilities":[{"name":"READ"}]},{"resourceType":"DATABASE","capabilities":[{"name":"CREATE"},{"name":"READ"},{"name":"READ_DATA"}]},{"resourceType":"POLL","capabilities":[{"name":"READ"},{"name":"VOTE"},{"name":"UPDATE"},{"name":"CREATE"},{"name":"DELETE"},{"name":"CLOSE"}]},{"resourceType":"MESSAGE","capabilities":[{"name":"CREATE"},{"name":"READ"},{"name":"DELETE"}]},{"resourceType":"PENDING_MESSAGE","capabilities":[{"name":"READ"},{"name":"UPDATE"},{"name":"DELETE"}]},{"resourceType":"ATTACHMENTS","capabilities":[{"name":"READ"},{"name":"DELETE"}]},{"resourceType":"PHOTOMATIC_ALBUMS","capabilities":[{"name":"READ"},{"name":"UPLOAD"}]},{"resourceType":"MEMBERSHIP_TYPE","capabilities":[{"name":"READ"},{"name":"CREATE"},{"name":"DELETE"},{"name":"UPDATE"}]},{"resourceType":"POST","capabilities":[{"name":"CREATE"},{"name":"DELETE"},{"name":"READ"},{"name":"UPDATE"}]},{"resourceType":"PIN","capabilities":[{"name":"CREATE"},{"name":"DELETE"},{"name":"READ"},{"name":"UPDATE"}]}],"modStatus":"MODERATOR","subStatus":"NORMAL","groupUrl":"groups.yahoo.com","intlCode":"us"},"comscore":"pageview_candidate","ygData":{"userId":229380146,"authorName":"Jean-Christophe Helary","from":"Jean-Christophe Helary &lt;fusion@mx6.tiki.ne.jp&gt;","replyTo":"LIST","senderId":"P_2wYfipOv03LkECdz1MdKMx1DAN2muNYmDSOOEwjJNXgvxvUC65xvbkzvdQhiggX5SNPWhKYBQlgHHIrzXJe20Jlw6xw3ilOcSk-rh66yDFJ-Kt7A","spamInfo":{"isSpam":false,"reason":"0"},"subject":"Working with Formatted Text (was Re: [OmT] Order of tags)","postDate":"1159277015","msgId":6065,"canDelete":true,"contentTrasformed":false,"systemMessage":false,"headers":{"messageIdInHeader":"PEREN0U0QTdBLUVENTItNEQ0RS1BNDlGLUMxMTVDODc4RDM3OEBteDYudGlraS5uZS5qcD4="},"prevInTopic":0,"nextInTopic":6070,"prevInTime":6064,"nextInTime":6066,"topicId":6065,"numMessagesInTopic":5,"msgSnippet":"First, as an answer to Kate: the manual in the Release Candidate version is not up to date. If the changes.txt file is correct (and I think it is) the","rawEmail":"Return-Path: &lt;fusion@mx6.tiki.ne.jp&gt;\r\nX-Sender: fusion@mx6.tiki.ne.jp\r\nX-Apparently-To: OmegaT@yahoogroups.com\r\nReceived: (qmail 37761 invoked from network); 26 Sep 2006 13:23:57 -0000\r\nReceived: from unknown (66.218.66.172)\n  by m24.grp.scd.yahoo.com with QMQP; 26 Sep 2006 13:23:57 -0000\r\nReceived: from unknown (HELO smtp9.tiki.ne.jp) (218.40.30.106)\n  by mta4.grp.scd.yahoo.com with SMTP; 26 Sep 2006 13:23:56 -0000\r\nReceived: from [192.168.11.4] (pl501.nas933.takamatsu.nttpc.ne.jp [210.136.183.245])\n\t(authenticated bits=0)\n\tby smtp9.tiki.ne.jp (8.12.11/8.12.11) with ESMTP id k8QDNbSv026167\n\t(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)\n\tfor &lt;OmegaT@yahoogroups.com&gt;; Tue, 26 Sep 2006 22:23:38 +0900 (JST)\n\t(envelope-from fusion@mx6.tiki.ne.jp)\r\nMime-Version: 1.0 (Apple Message framework v752.2)\r\nContent-Transfer-Encoding: quoted-printable\r\nMessage-Id: &lt;DD7E4A7A-ED52-4D4E-A49F-C115C878D378@mx6.tiki.ne.jp&gt;\r\nContent-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed\r\nTo: OmegaT@yahoogroups.com\r\nDate: Tue, 26 Sep 2006 22:23:35 +0900\r\nX-Mailer: Apple Mail (2.752.2)\r\nX-Originating-IP: 218.40.30.106\r\nX-eGroups-Msg-Info: 1:0:0:0\r\nFrom: Jean-Christophe Helary &lt;fusion@mx6.tiki.ne.jp&gt;\r\nSubject: Working with Formatted Text (was Re: [OmT] Order of tags)\r\nX-Yahoo-Group-Post: member; u=229380146; y=Wv8QWxcKlci1u-nlYEP8Ogc08qCm98y6RUe1_b6QNjafaj4ioQ\r\n\r\nFirst, as an answer to Kate: the manual in the Release Candidate  \nversion =\r\nis not up to date. If the changes.txt file is correct (and I  \nthink it is)=\r\n the modification to OmegaT that are reflected in the  \ntext I paste below =\r\nwere introduced in OmegaT RC7/\n\nHere is what will appear in the final manua=\r\nl when OmegaT is released  \nas stable:\n\n(people here are free to propose mo=\r\ndifications or edit the Wiki if  \nthey have direct access to it)\n(bonus &quot;tr=\r\nack&quot; at the end.)\n\n=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=\r\n=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=\r\n=3D\nWorking with Formatted Text\n\n From OmegaT 1.6.0 User Manual\n\n1 Formatte=\r\nd Text in OmegaT\n   1.1 Tag naming\n   1.2 Tag numbering\n   1.3 Pairs and si=\r\nngletons\n   1.4 Tags and sentence segmenting\n   1.5 Tag operations\n     1.5=\r\n.1 Tag group duplication\n     1.5.2 Tag group deletion\n     1.5.3 Tag group=\r\n order modification\n     1.5.4 Tag group nesting\n   1.6 Tag group overlappi=\r\nng\n   1.7 Tag group validation\n   1.8 Hints for tags management\n   1.9 Impo=\r\nrtant\n1. Formatted Text in OmegaT\n\nFormatting information present in the so=\r\nurce file usually needs to be  \nreproduced in the target file. OmegaT displ=\r\nays the in-line formatting  \ninformation of supported formats (at present D=\r\nocBook, HTML, XHTML,  \nOpen Document, and OpenOffice.org) as tags. Tags are=\r\n usually not  \ntaken into account when considering string similarity for ma=\r\ntching  \npurposes. Tags that you have reproduced in the translated segment =\r\n \nwill be present in the translated document.\n\n\n\n\n\n1.1. Tag naming\n\nThe tag=\r\ns consist of one to three characters and a number. Unique  \nnumber allows t=\r\no group those tag that correspond to each other, and  \ndifferentiate the ta=\r\ngs that can have the same shortcut character, but  \nare in fact different.\n=\r\n\nThe characters may or may not reflect the value of the formatting the  \nta=\r\ng represents (eg. bold, italics, etc.)\n\n\n\n\n\n1.2. Tag numbering\n\nTags are nu=\r\nmbered in an incremental way by tag group.\n\nWhat we call &quot;tag groups&quot; here =\r\nis either a single tag (like &lt;br1&gt;),  \non its own, or 2 tags forming a pair=\r\n (like &lt;f3&gt; and &lt;/f3&gt;).\n\nWithing a segment, the first group (pair or single=\r\nton) gets the  \nnumber 0, the second the number 1 etc.\n\nThe first example b=\r\nelow has 3 tag groups (a pair, a singleton, and  \nthen another pair), the s=\r\necond example only has one group (a pair).\n\n\n\n\n\n1.3. Pairs and singletons\n\n=\r\nTags always come either in singletons or in pairs.\n\nSingle tags indicate fo=\r\nrmatting information that does not affect the  \nsurrounding text (extra spa=\r\nce or line break for example).\n\n&lt;segment 2132&gt;&lt;b0&gt;&lt;Ctr+N&gt;&lt;/b0&gt;, &lt;br1&gt;&lt;b2&gt;&lt;E=\r\nnter&gt;&lt;/b2&gt;&lt;end segment&gt;\n&lt;br1&gt; is a single tag and does not affect any surro=\r\nunding text.\n\nPaired tags usually indicate style information that applies t=\r\no the  \ntext between the opening tag and the closing tag of a pair. Whateve=\r\nr  \nhappens to a pair, the opening tag should always come before the  \nclos=\r\ning tag.\n\n&lt;segment 3167&gt;Log file (&lt;f1&gt;log.txt&lt;/f1&gt;) for tracking operations=\r\n and  \nerrors.&lt;end segment&gt;\n&lt;f1&gt; and &lt;/f1&gt; are paired and affect log.txt.\n\n=\r\n\n\n\n\n1.4. Tags and sentence segmenting\n\nOmegaT creates its tags before sente=\r\nnces segmenting is applied.  \nDepending on the segmenting rules, tags may l=\r\nook like they do not  \nrespect the above rules of numbering and grouping.\n\n=\r\n&lt;segment 1554&gt; &lt;c0&gt;Before: &#92;. After: &#92;s&lt;/c0&gt;&lt;br1&gt; &lt;b2&gt;Note:&lt;/b2&gt;\n&quot;&#92;.&quot; means=\r\n the character &quot;.&quot;&lt;br3&gt; &quot;&#92;s&quot; means any white space  \ncharacter &lt;end segment=\r\n&gt;\nThere seems to be no problem here. Now, if we apply the default  \nsegment=\r\ning rules on this segment (the default OmegaT behavior) we  \nwill have the =\r\nfollowing result:\n\n&lt;segment 1990&gt; &lt;c0&gt;Before: &#92;. &lt;end segment&gt;\n&lt;segment 199=\r\n1&gt; After: &#92;s&lt;/c0&gt;&lt;br1&gt; &lt;end segment&gt;\n&lt;segment 1992&gt; &lt;b2&gt;Note:&lt;/b2&gt; &quot;&#92;.&quot; mea=\r\nns the character &quot;.&quot;&lt;br3&gt; &lt;end  \nsegment&gt;\n&lt;segment 1993&gt; &quot;&#92;s&quot; means any whi=\r\nte space character &lt;end segment&gt;\n(Segmenting rules that apply are: segment =\r\nafter a period followed by  \na space and segment after a line break tag.)\n\n=\r\nHere, we see that segments taken one by one do not respect the  \npairing an=\r\nd numbering rules: &lt;c0&gt; and &lt;/co&gt; should be paired in the  \nsame segment, b=\r\nut are separated by the segmentation rules.\n\nIn some cases that may even ca=\r\nuse problems in the translation, when  \ntags must be displaced in the targe=\r\nt language to reflect the word  \norder of that language (see Tag operations=\r\n below).\n\n\n\n\n\n1.5. Tag operations\n\nCare must be exercised with tags. If the=\r\ny are accidentally changed,  \nthe formatting of the final file may be corru=\r\npted. In the worst case  \nscenario a file may not open altogether; this occ=\r\nurs with  \nOpenOffice.org files in particular.\n\n\n\n\n\n1.5.1. Tag group duplic=\r\nation\n\nTo duplicate tag groups, just copy them in the position of your  \nch=\r\noice. Keep in mind that in a pair group the opening tag must come  \nbefore =\r\nthe closing tag.\n\nThe formating represented by the group you duplicated wil=\r\nl be applied  \nto the section where you duplicated it.\n\nexample:\n&lt;segment 0=\r\n001&gt;&lt;f0&gt;This formatting&lt;/f0&gt; is going to be duplicated  \nhere.&lt;end segment&gt;=\r\n\nafter duplication:\n&lt;segment 0001&gt;&lt;f0&gt;Ce format&lt;/f0&gt; a =E9t=E9 &lt;f0&gt;copi=E9 =\r\nici&lt;/f0&gt;.&lt;end segment&gt;\n\n\n\n\n1.5.2. Tag group deletion\n\nTo delete tag groups,=\r\n just remove them from the segment. Keep in mind  \nthat a pair group must h=\r\nave its opening as well as its closing tag  \ndeleted to ensure all traces o=\r\nf the formatting are properly erased,  \notherwise the translated file might=\r\n be corrupted and may not open.\n\nBy deleting a tag group you will remove th=\r\ne related formatting from  \nthe translated file.\n\nexample:\n&lt;segment 0001&gt;&lt;f=\r\n0&gt;This formatting&lt;/f0&gt; is going to be deleted.&lt;end  \nsegment&gt;\nafter deletio=\r\nn:\n&lt;segment 0001&gt;Ce format a =E9t=E9 effac=E9.&lt;end segment&gt;\n\n\n\n\n1.5.3. Tag =\r\ngroup order modification\n\nTo change the order of a tag group to reflect a d=\r\nifferent language  \nstructure in the translation, simply put the tag group =\r\nwhere it  \nshould be in the translation.\n\nThe formatting will follow the pa=\r\nrt it is applied to.\n\nexample:\n&lt;segment 0001&gt;&lt;f0&gt;The formatting here&lt;/f0&gt; a=\r\nnd &lt;f1&gt;the formatting  \nhere&lt;/f1&gt; are going to be moved around.&lt;end segment=\r\n&gt;\nafter order modification:\n&lt;segment 0001&gt;&lt;f1&gt;Ce format&lt;/f1&gt; et &lt;f0&gt;ce form=\r\nat&lt;/f0&gt; ont =E9t=E9  \ninvers=E9s.&lt;end segment&gt;\n\n\n\n\n1.5.4. Tag group nesting=\r\n\n\nModifying a tag group order may result into nesting a tag group  \nwithin =\r\nanother tag group. This is possible as long as the enclosing  \ngroup totall=\r\ny encloses the enclosed group. Extra care must be taken  \nwith nesting espe=\r\ncially in the case of tag pairs that are not fully  \nmoved inside an enclos=\r\ning group otherwise the translated file might  \nbe corrupted and may not op=\r\nen.\n\nThe nested part will have both formattings apply to it.\n\nexample:\n&lt;seg=\r\nment 0001&gt;&lt;f0&gt;The formatting&lt;/f0&gt; &lt;f1&gt;here&lt;/f1&gt; is going to be  \nnested.&lt;en=\r\nd segment&gt;\nafter nesting:\n&lt;segment 0001&gt;&lt;f0&gt;Le format &lt;f1&gt;ici&lt;/f1&gt;&lt;/f0&gt; a =\r\n=E9t=E9 emboit=E9 dans le  \npremier format.&lt;end segment&gt;\n\n\n\n\n1.6. Tag group=\r\n overlapping\n\nOverlapping is the result of bad manipulations of tag pairs a=\r\nnd will  \ncertainly result in formatting corruption and sometimes in the  \n=\r\ntranslating file not opening at all.\n\nexample:\n&lt;segment 0001&gt;&lt;f0&gt;the format=\r\nting&lt;/f0&gt; &lt;f1&gt;here&lt;/f1&gt; is going to be  \nmessed up.&lt;end segment&gt;\nafter bad =\r\nmanipulation:\n&lt;segment 0001&gt;&lt;f0&gt;the formatting &lt;f1&gt;here&lt;/f0&gt; &lt;/f1&gt;is very m=\r\nessed up  \nnow.&lt;end segment&gt;\n\n\n\n\n1.7. Tag group validation\n\nThe validate ta=\r\ngs function (Tag validation) detects changed tags  \n(whether done deliberat=\r\nely or by accident), and indicates the  \naffected segments. Use of this fun=\r\nction will open a dialog with any  \nsuspected broken or bad tags in a docum=\r\nent.\n\nThis function can be useful for tracking down bugs in a translated  \n=\r\ntagged text. This is often a problem in OpenDocument or  \nOpenOffice.org fi=\r\nles that will not open due to tag problems created  \nin the process of tran=\r\nslation. Fixing the tags and recreating the  \ntarget documents again can of=\r\nten remedy the problem.\n\n\n\n\n\n1.8. Hints for tags management\n\nTags generally=\r\n represent some kind of formatting in the original  \ntext. Simplifying the =\r\noriginal text formating greatly contributes to  \nreducing the number of tag=\r\ns. Unifying used fonts, font sizes, colors  \netc should be considered if po=\r\nssible, to simplify the translation and  \nreduce the number of possible tag=\r\n errors.\n\nTake a look at the Tag operations section to see what can be done=\r\n  \nwith tags.\n\nRemember that if tags bother you and formatting is not extre=\r\nmely  \nrelevant for the job at hand, removing most formatting from the  \nso=\r\nurce document will greatly ease the translation.\n\nIf you need to see the ta=\r\ngs in OmegaT but do not need to retain most  \nof the format in the translat=\r\ned document you are free not to add the  \ntags to the translation. In this =\r\ncase pay extra attention to tag  \npairs since forgetting to delete one part=\r\n of the pair will corrupt  \nyour document&#39;s formatting, which is what will =\r\nkeep a translated  \nOpenOffice.org document to open.\n\nSince tags are includ=\r\ned in the text itself, it is possible to use  \nsegmentation rules to create=\r\n segments that include less tags. This is  \nan advanced feature and should =\r\nnot be used by beginning users.\n\n\n\n\n\n1.9. Important\n\nOmegaT is not yet able=\r\n to detect mistakes in formatting fully  \nautomatically, so it will not pro=\r\nmpt you if you make an error or  \nchange formatting to fit your target lang=\r\nuage better. Sometimes,  \nhowever, your translated file will look distorted=\r\n, and in case of  \nOpenDocument / OpenOffice.org files will even refuse to =\r\nopen.\n\n\n=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=\r\n=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D\n\nI also =\r\nfound an OpenOffice plugin, not yet localized but very  \npractical: The plu=\r\ngin removes all the superfluous styling in an OOo  \nfile. It is especially =\r\nuseful on imports from Word.\n\nThe plugin is at:\nhttp://www.indesko.com/site=\r\ns/fr/telechargements/eradicateur_de_surch/ \nview\n\nJean-Christophe\n\n\n"}}