{"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":"READ_DATA"},{"name":"CREATE"}]},{"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":"UPDATE"},{"name":"CREATE"},{"name":"DELETE"}]},{"resourceType":"PIN","capabilities":[{"name":"READ"},{"name":"UPDATE"},{"name":"CREATE"},{"name":"DELETE"}]}],"modStatus":"MODERATOR","subStatus":"NORMAL","groupUrl":"groups.yahoo.com","intlCode":"us"},"comscore":"pageview_candidate","ygData":{"userId":307682680,"authorName":"larusalka","from":"&quot;larusalka&quot; &lt;silvia.florez@gmail.com&gt;","profile":"larusalka","replyTo":"LIST","senderId":"m6c52nB49v6zTc6D2_izeXtPQjJs9RxkRZ9603gkv10joIgv1MJRQrFWyAYojDFQ60ETsqkvX-rhE7ogbJ5LtKd7EV37mIrNNMFX1Q","spamInfo":{"isSpam":false,"reason":"6"},"subject":"Re: [OmT] glossary function","postDate":"1264863273","msgId":16618,"canDelete":true,"contentTrasformed":false,"systemMessage":false,"headers":{"messageIdInHeader":"PGhrMWg3OSt0b2o2QGVHcm91cHMuY29tPg==","inReplyToHeader":"PDRCNjNFN0MzLjUwMjA4QG1hcmNwcmlvci5kZT4="},"prevInTopic":16617,"nextInTopic":16619,"prevInTime":16617,"nextInTime":16619,"topicId":16567,"numMessagesInTopic":74,"msgSnippet":"Hi all, To add some more flavour to the glossary issue, I just want to bring to your attention two common extension for tab-delimited files that haven t been","rawEmail":"Return-Path: &lt;silvia.florez@gmail.com&gt;\r\nX-Sender: silvia.florez@gmail.com\r\nX-Apparently-To: OmegaT@yahoogroups.com\r\nX-Received: (qmail 62457 invoked from network); 30 Jan 2010 14:55:25 -0000\r\nX-Received: from unknown (98.137.34.45)\n  by m3.grp.sp2.yahoo.com with QMQP; 30 Jan 2010 14:55:25 -0000\r\nX-Received: from unknown (HELO n44d.bullet.mail.sp1.yahoo.com) (66.163.169.158)\n  by mta2.grp.sp2.yahoo.com with SMTP; 30 Jan 2010 14:55:25 -0000\r\nX-Received: from [69.147.65.172] by n44.bullet.mail.sp1.yahoo.com with NNFMP; 30 Jan 2010 14:54:35 -0000\r\nX-Received: from [98.137.34.34] by t14.bullet.mail.sp1.yahoo.com with NNFMP; 30 Jan 2010 14:54:35 -0000\r\nDate: Sat, 30 Jan 2010 14:54:33 -0000\r\nTo: OmegaT@yahoogroups.com\r\nMessage-ID: &lt;hk1h79+toj6@eGroups.com&gt;\r\nIn-Reply-To: &lt;4B63E7C3.50208@marcprior.de&gt;\r\nUser-Agent: eGroups-EW/0.82\r\nMIME-Version: 1.0\r\nContent-Type: text/plain; charset=&quot;ISO-8859-1&quot;\r\nContent-Transfer-Encoding: quoted-printable\r\nX-Mailer: Yahoo Groups Message Poster\r\nX-Yahoo-Newman-Property: groups-compose\r\nX-Originating-IP: 66.163.169.158\r\nX-eGroups-Msg-Info: 1:6:0:0:0\r\nX-Yahoo-Post-IP: 87.221.204.125\r\nFrom: &quot;larusalka&quot; &lt;silvia.florez@gmail.com&gt;\r\nSubject: Re: [OmT] glossary function\r\nX-Yahoo-Group-Post: member; u=307682680; y=k_JPJ4e2xQTvlbpcKfQUf2Jbg1rnHLC8U1xzby3Kxn8r341g\r\nX-Yahoo-Profile: larusalka\r\n\r\nHi all,\n\nTo add some more flavour to the glossary issue, I just want to bri=\r\nng to your attention two common extension for tab-delimited files that have=\r\nn&#39;t been mentioned yet, namely, .csv and .tsv. I think these two are worth =\r\nconsidering here, taking into account that some translators are used to han=\r\ndling their glossaries in spreadsheets. Now, if you&#39;re exporting your data =\r\nfrom a termbase or spreadsheet, .csv is probably the way to go in many case=\r\ns (in OO Calc, for instance, AFAIK there is no .txt option), with the .tsv =\r\nextension being also possible in some tools (e.g. Google SpreadSheets).  \n\n=\r\nI agree with Marc that understanding encodings and extensions is essential =\r\nfor a translator using CAT tools, and I think that understanding the tab-de=\r\nlimited text format in particular also implies an understanding of what &#39;fi=\r\neld delimiter&#39; and &#39;text delimiter&#39; are. \n\nAs a side note, IMHO &#39;foolproof&#39;=\r\n methods should not condition the user to a certain tool; instead, the conc=\r\nepts involved should be explained clearly, so that the user can achieve the=\r\n expected results with his/her tool of choice. In the case of glossaries in=\r\n particular, it seems more natural to me to use a spreadsheet rather than a=\r\n word processor, but maybe that&#39;s just me :)\n\nThanks to all the team for a =\r\ngreat tool and to all of you for the interesting discussions that take plac=\r\ne in the list.\n\nHave a nice weekend!\n\nSilvia Fl=F3rez\n\n\n--- In OmegaT@yahoo=\r\ngroups.com, Marc Prior &lt;mail@...&gt; wrote:\n&gt;\n&gt; JC\n&gt; \n&gt; I disagree. When I sai=\r\nd: &quot;The question is whether it isn&#39;t just easier \n&gt; for users to learn how =\r\nto handle extensions&quot;, I meant in the medium to \n&gt; long term. Obviously, it=\r\n is easier for us to associate the .txt \n&gt; extension with UTF-8 for glossar=\r\nies, then simply tell users to use the \n&gt; UTF-8 encoding. It is easier in t=\r\nhe context of that particular issue.\n&gt; \n&gt; However, extensions exist, and I =\r\ntend to think that sooner or later, the \n&gt; user is going to need to know ho=\r\nw to change them. For source text files, \n&gt; the .txt extension is associate=\r\nd with the system encoding, so if a user \n&gt; wishes or needs to use a non-sy=\r\nstem encoding for a plain-text source \n&gt; file, he has to change the extensi=\r\non. Toxic requires the user to change \n&gt; the extension: this was a delibera=\r\nte decision on my part, as the \n&gt; alternative was for Toxic to overwrite a =\r\nprevious file. Editing the .ini \n&gt; file manually means ensuring that the ed=\r\nitor does not add a .txt \n&gt; extension to the .ini file. Any editing of proj=\r\nect_save.tmx requires \n&gt; that when project_save.tmx is saved, a .txt extens=\r\nion is not added \n&gt; inadvertently. And so on.\n&gt; \n&gt; So, as I said before, as=\r\nsociating .txt with UTF-8 resolves the extension \n&gt; issue in the particular=\r\n context of glossaries, but it doesn&#39;t resolve it \n&gt; overall: it just postp=\r\nones it until the next issue involving plain-text \n&gt; files arises. Are file=\r\n extensions &quot;complexity&quot;? Or are they something \n&gt; that any computer user s=\r\nhould be aware of and be able to handle, and is \n&gt; hiding them just dumbing=\r\n down? Personally, I think that Microsoft&#39;s \n&gt; decision to hide file extens=\r\nions by default in Windows&#39; file manager was \n&gt; dumbing down.\n&gt; \n&gt; And, aga=\r\nin as I have already said, creating glossaries raises other \n&gt; issues (enco=\r\ndings, the plain-text file format per se), so the user will \n&gt; need to refe=\r\nr to the documentation anyway. My impression is that once \n&gt; users follow t=\r\nhe &quot;foolproof&quot; procedure in the manual, they have no \n&gt; problem creating gl=\r\nossaries.\n&gt; \n&gt; I think it is worth looking at the wider picture, and that i=\r\nncludes \n&gt; encouraging users to use the documentation in order to understan=\r\nd \n&gt; OmegaT, rather than designing OmegaT so that its use can be guessed by=\r\n \n&gt; anyone who is not willing to use the documentation.\n&gt; \n&gt; Marc\n&gt; \n&gt; \n&gt; \n=\r\n&gt; Jean-Christophe Helary wrote:\n&gt; &gt; On 30 janv. 10, at 02:54, Marc Prior wr=\r\note:\n&gt; &gt;\n&gt; &gt;   \n&gt; &gt;&gt; And, of course, the question of whether it isn&#39;t just =\r\neasier for users \n&gt; &gt;&gt; to learn how to handle extensions.\n&gt; &gt;&gt;     \n&gt; &gt;\n&gt; &gt;=\r\n No, it is not. Otherwise we would not add all the file extensions in the d=\r\nefaults.\n&gt; &gt;\n&gt; &gt; We are trying to hide the complexity by doing that. It wou=\r\nld make sense to hide the complexity for anything that we want to be the de=\r\nfault.\n&gt; &gt;\n&gt; &gt; As you wrote non standard extensions (.tab etc) are not triv=\r\nial to set. Some editors will want to add .txt. That is silly on the part o=\r\nf the editor but such editors are most likely those used by beginners (emac=\r\ns, vi, nano etc don&#39;t do that).\n&gt; &gt;\n&gt; &gt; If we want the beginners to feel co=\r\nmfortable with OmegaT we have to think of ways that are compatible with the=\r\nir process to a certain extent. Using non standard extensions is not. And h=\r\naving 2 different behaviors for the same extension (txt as &lt;auto&gt; when in s=\r\nource and as utf-8 when in glossary).\n&gt; &gt;\n&gt; &gt; Jean-Christophe Helary\n&gt; &gt; --=\r\n-------------------------------\n&gt; &gt; fun: mac4translators.blogspot.com\n&gt; &gt; w=\r\nork: www.doublet.jp (ja/en &gt; fr)\n&gt; &gt; tweets: @brandelune\n&gt; &gt;\n&gt; &gt;\n&gt; &gt;\n&gt;\n\n\n\n"}}