{"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":"READ"},{"name":"CREATE"},{"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":"READ"},{"name":"CREATE"},{"name":"UPDATE"},{"name":"DELETE"}]},{"resourceType":"PIN","capabilities":[{"name":"READ"},{"name":"CREATE"},{"name":"UPDATE"},{"name":"DELETE"}]}],"modStatus":"MODERATOR","subStatus":"NORMAL","groupUrl":"groups.yahoo.com","intlCode":"us"},"comscore":"pageview_candidate","ygData":{"userId":229380146,"authorName":"JC Helary","from":"JC Helary &lt;fusion@mx6.tiki.ne.jp&gt;","profile":"jc_helary","replyTo":"LIST","senderId":"hcF4WEVOOHc97pSZ1isItxTbDVH3c9DNcWito8G-JjIlW_x8qeOzRB7YeAI5YFvNF2zSfD2vuz23yDpK6xp0uvyxp_XzwObR","spamInfo":{"isSpam":false,"reason":"12"},"subject":"OmegaT 1.6 review (was Cracow)","postDate":"1132531362","msgId":3524,"canDelete":true,"contentTrasformed":false,"systemMessage":false,"headers":{"messageIdInHeader":"PDA4REFFNUVFLTI4M0EtNENBNC05MkVELTBFRkIxQ0Y5QzEwNUBteDYudGlraS5uZS5qcD4=","inReplyToHeader":"PDQzODBBMDlBLjgwNzAyMDZAeWFob28uaXQ+","referencesHeader":"PDQzODBBMDlBLjgwNzAyMDZAeWFob28uaXQ+"},"prevInTopic":3523,"nextInTopic":3525,"prevInTime":3523,"nextInTime":3525,"topicId":3520,"numMessagesInTopic":7,"msgSnippet":"Sabine, Here is the review I wrote for the ATA meeting in Seattle 2 weeks ago, it was used by Corrine McCay (Open Source Update). There my be a few typos","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 53707 invoked from network); 21 Nov 2005 00:02:46 -0000\r\nReceived: from unknown (66.218.66.166)\n  by m28.grp.scd.yahoo.com with QMQP; 21 Nov 2005 00:02:46 -0000\r\nReceived: from unknown (HELO mx6.tiki.ne.jp) (218.40.30.133)\n  by mta5.grp.scd.yahoo.com with SMTP; 21 Nov 2005 00:02:45 -0000\r\nReceived: from [192.168.11.5] (pl034.nas932.takamatsu.nttpc.ne.jp [210.136.180.34])\n\tby mx6.tiki.ne.jp (8.9.3p2.1/3.7W) with ESMTP id JAA23941\n\tfor &lt;OmegaT@yahoogroups.com&gt;; Mon, 21 Nov 2005 09:02:43 +0900 (JST)\r\nMime-Version: 1.0 (Apple Message framework v746.2)\r\nIn-Reply-To: &lt;4380A09A.8070206@yahoo.it&gt;\r\nReferences: &lt;4380A09A.8070206@yahoo.it&gt;\r\nContent-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed\r\nMessage-Id: &lt;08DAE5EE-283A-4CA4-92ED-0EFB1CF9C105@mx6.tiki.ne.jp&gt;\r\nContent-Transfer-Encoding: 7bit\r\nDate: Mon, 21 Nov 2005 09:02:42 +0900\r\nTo: OmegaT@yahoogroups.com\r\nX-Mailer: Apple Mail (2.746.2)\r\nX-Originating-IP: 218.40.30.133\r\nX-eGroups-Msg-Info: 1:12:0:0\r\nFrom: JC Helary &lt;fusion@mx6.tiki.ne.jp&gt;\r\nSubject: OmegaT 1.6 review (was Cracow)\r\nX-Yahoo-Group-Post: member; u=229380146; y=p_UBv6ei6TqtvDwE9dHi3QWXPsENls4BCSxJQIsV_ZGqh3jV6w\r\nX-Yahoo-Profile: jc_helary\r\n\r\nSabine,\n\nHere is the &quot;review&quot; I wrote for the ATA meeting in Seattle 2 weeks  \nago, it was used by Corrine McCay (Open Source Update).\n\nThere my be a few typos left so feel free to edit.\n\nJC\n\n--------------------------------\nOmegaT 1.6, a pre-release short review.\n\nOfficial page:\nhttp://www.omegat.org/omegat/omegat.html\nUser group:\nhttp://groups.yahoo.com/group/OmegaT/\nDevelopment/Download page:\nhttp://sourceforge.net/projects/omegat\n\n\nThe last time OmegaT was covered in Open Source Update was about 9  \nmonths ago. A lot of things have happened since, and now the OmegaT  \nProject Team is proud to introduce you to the next major upgrade:  \nOmegaT number 1.4.6RC, which is planned to be released as version 1.6.\n\nChances are that when you read these lines, the available version  \nwill still be a release candidate with a few rough edges.\n\nBefore we look at the good stuff, let me talk about the bad and the  \nstill-some-room-for-improvement first (although, you may want to skip  \nthese and read them only after you&#39;ve read about the good stuff).\n\n\n&lt;&lt; The Bad &gt;&gt;\n\nFirst of all, a piece of old bad news: OmegaT had for a long time  \nsome degree of useful support for TMX. It could read TMX files  \ngenerated by other apps and vice-versa. It is not that our opinion  \nhas changed, but that this degree of compatibility was broken at some  \nstage.\n\nOmegaT is close to supporting TMX 1.1 at level 2. Roughly speaking,  \nlevel 1 support means translation units not including formating tags,  \nand level 2 means including formatting tags as well as specific ways  \nto handle them. Currently OmegaT supports formatting tags, but not  \nthe way it is specified in TMX standard.\n\nThe result is that translators using OmegaT TMX files elsewhere will  \nsee OmegaT-specific tags in the segments (if present) as plain text  \nand thus matching to similar segments will be less efficient. We have  \ndiscussed this issue on the user and developer mailing lists and  \nwe&#39;re in the process of fixing it. This is not something that we&#39;ve  \njust discovered, but we think it is important to let you know some of  \nOmegaT&#39;s limitations when technical buzz words are involved.\n\nBesides, TMX support is only relevant if you need to exchange TMX  \nfiles. TMX files created for use in OmegaT only will still work  \nperfectly within OmegaT, and ultimately that is really what matters  \nto the freelance translator who will get few if any TMX files from  \nclients.\n\nThe second piece of bad news is that OmegaT is still clumsy at  \nhandling right-to-left languages. We would love to see OmegaT being  \nused by translators in Arabic, Hebrew or other RTL languages, but to  \nimprove this feature we need more tester and user reports.\n\n\n\n&lt;&lt; The Still-Some-Room-For-Improvement &gt;&gt;\n\n\nThe still-some-room-for-improvement is really not all that bad when  \nyou think about it. OmegaT is a Java application. In other words, it  \nwas not developed with one specific platform in mind. The latest  \nversions of OmegaT will work on any platform that supports Java 1.4,  \nsuch as Windows 98 and newer, MacOSX 10.2 and newer, Linux, etc.  \nSometimes OmegaT will seem to interfere with your workflow,  \nespecially when it doesn&#39;t behave quite like the native animals of  \nyour computer&#39;s ecology (Mac users may be slightly disoriented  \nsometimes), but the non-nativeness of OmegaT is more than compensated  \nfor by the fact that it is platform independent.\n\n\n\n&lt;&lt; The Good &gt;&gt;\n\n\nOmegaT has come a long way since I started using it.\n\nAt first, I wasn&#39;t able to do much with it. OmegaT did not support  \nlanguage pairs that were not covered by a common character set. For  \nthat reason I was unable to work in my pairs, Japanese and French.  \nThe first major evolution in OmegaT was support for such pairs by  \nenabling the user to set a font that covered both character sets.  \nAnother major step forward was support for glossary files in the  \nUTF-8 flavour of Unicode. The most recent big advancement was  \nenabling the user to set default encoding recognition for specific  \nfiles using configurable filters.\n\nOnce the basics of strong multilingualism were included in OmegaT, we  \nwere ready to address workflow and project related ergonomics as well  \nas other translation memory technology related issues. We overhauled  \nthe matching engine so that languages with no spaces between language  \nunits would still produce matches. After that, we were confronted  \nwith several choices: should we first do segmentation rules exchange  \n(SRX), or should we first implement full TMX support? For which  \nadditional file formats should we develop filters? Which improvements  \nto the user interface and work flow management should we pursue?\n\nOmegaT 1.4.6RC is a first attempt at answering these questions, based  \non lengthy exchanges between the developers and the ever growing user  \nbase. The following improvements indicate the general direction  \nOmegaT is taking:\n\n1) OmegaT has now access to simple and configurable sentence level  \nsegmenting thanks to SRX-like segmentation rules, which can be used  \nin addition to the existing default segmentation methods based on  \nfile type. The rules are simple regular expressions that describe two  \npatterns, namely the pattern before the break and the pattern after  \nthe break. When OmegaT finds both patterns, it creates a segment  \nstarting right there where the first pattern stops. The same  \nprinciple is used to create exception rules to eliminate potential  \nbreaks (like after &quot;Mr. &quot; in English, although the general rule would  \nbe to break after a &quot;.&quot; followed by a space).\n\nThis new function has been successfully used to create a pseudo LateX  \nfiles filter based on the text file support of OmegaT. It promises to  \nbe useful in other creative ways to produce not only finer matches  \nbut also access to patternable file formats.\n\nIt must be mentioned that OmegaT&#39;s matching engine will in future be  \nreplaced by a text search engine which originated from the Apache  \nProject: Apache Lucene.\n\n2) OmegaT supports TMX 1.1 compliant files (or more precisely, it  \nsupports the output of CSVConverter). We have also significantly  \nreduced the problems created by the interference of OmegaT&#39;s own TMX  \nwith the matching engine. Note that formatting tags are not taken  \ninto account when calculating the match percentage.\n\nThe next (or next after next) version of OmegaT will be reconstructed  \nfrom the ground up for full support of TMX 1.4 level 2. It will be a  \ncomplex task which will take much of the development time available  \nfor OmegaT, but we are already working on it.\n\n3) There is a new workflow option for selecting what is displayed in  \nthe target language field - either a copy of the source segment or  \nthe best match available from the translation memories (with a  \nconfigurable minimum match percentage level, and the possibility of  \ninserting a warning marker).\n\nOmegaT now also features an embryo of project management from within  \nOmegaT. With previous versions, translators had OmegaT create folders  \nbut had to manually copy files into those folders. The latest version  \nof OmegaT can import source files directly and automatically copy  \nthem to the selected source folder.\n\nChances are that this function will also be implemented for glossary  \nand TM files in the near future, with a focus on project management  \ntools.\n\n4) On the file format support front, I have great news: OmegaT has  \ntrashed its old HTML parser in favour of a brand new one that  \nreproduces the original HTML code 99,99% accurately, and which gives  \naccess to all the translatable segments within HTML tags (such as  \nattribute values, image alternative text, etc). We are currently  \ninvestigating the possibility of generic XML support.\n\nWe have discussed the issue of OpenOffice.org documents with  \ntranslatable texts in embedded objects (for example, spreadsheets in  \na text file). No CAT tool on the market currently supports such  \ndocuments directly. We are trying to find ways to deal with this huge  \nproblem, which will be solved during the planned overhaul of OmegaT.  \nAt the moment, OmegaT regards a project file to be the template of a  \nsingle document only. Embedded files are files that are included in a  \nmaster file, and OmegaT will have to be told how to link one project  \nfile to multiple documents.\n\n\n\n&lt;&lt; The Very Good! &gt;&gt;\n\n\nThis &quot;bonus track&quot; is an attempt to show how successful OmegaT is at  \nfulfilling translators&#39; requirements.\n\nFirstly, OmegaT is free, and you are free to use it, modify it,  \ndistribute it and make money from it. On the free market of CAT  \ntools, OmegaT is probably the one with the highest power:usability  \nratio. OmegaT is simple to use. And with the new Instant Tutorial, no- \none can say that OmegaT&#39;s workflow is obscure.\n\nOmegaT has acquired a fair amount of popularity. It is one of the few  \nCAT tools mentioned on professional forum polls (Proz.com, for  \nexample.) It has been downloaded roughly 1000 times a month in the  \nlast 8 months, and now ranks as approximately the 600th most dynamic  \nproject on SourceForge.\n\nA user mailing list was created at Yahoogoups on 1 March 2004.  \nRecently, the archives have been made public, which means that you  \ndon&#39;t need to be a subscriber to read them. About 150 people joined  \nthe list between March and October 2004. Between March and October  \n2005, roughly another 170 people subscribed, bringing the total to  \napproximately 350 subscribers. During this time discussions on the  \nlist has increased by 60%, and the average number of messages per  \nmonth totals 200.\n\nMany people have offered to help. We are currently working on  \nPortuguese, Italian and Greek versions of the program and  \ndocumentation, and existing localisations (Belorussian, English,  \nEsperanto, French, German, Japanese, Spanish) are constantly being  \nkept up to date. Some power users and Java programers have joined the  \nhappy developer crowd to support Maxym Mykhalchuk in his daily  \nefforts, and some of them are already busy with new independent  \nfeatures and bug fixes.\n\nOmegaT is yet another piece of evidence (if that was needed today)  \nthat open source development can be used to create software used by  \nnon-programmers daily, where those same non-programmers can  \nparticipate in and influence the evolution of the product.\n\nTranslators should not be bound by the technical limits imposed by  \nthe source text format. OmegaT is an open and free proposition for  \ntranslation professionals. It helps them to retain focus on the  \ntranslation and not the tool. We realise that OmegaT is far from  \ncomplete, but quite a few of us are already making a living as  \ntranslators with it.\n\nWe are waiting for you to join us in the user mailing list. People  \nwho would like to give us a hand, are also welcome to join the  \ndevelopment at SourceForge.\n\nJean-Christophe Helary\n\nPS: Thanks to Sonja Tomaskovic, Martin Wunderlich, Marc Prior and  \nMaxym Mykhalchuk for their useful comments and to Samuel Murray for  \nhis editing.\n\n"}}