{"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":"CREATE"},{"name":"DELETE"},{"name":"UPDATE"}]},{"resourceType":"PIN","capabilities":[{"name":"READ"},{"name":"CREATE"},{"name":"DELETE"},{"name":"UPDATE"}]}],"modStatus":"MODERATOR","subStatus":"NORMAL","groupUrl":"groups.yahoo.com","intlCode":"us"},"comscore":"pageview_candidate","ygData":{"userId":176392694,"authorName":"Samuel Murray (Durbanville)","from":"&quot;Samuel Murray (Durbanville)&quot; &lt;leuce@absamail.co.za&gt;","profile":"lacialacia","replyTo":"LIST","senderId":"EPGzsUSoOc1-0UIHuYVEkSQk7gDIHkRv9e9uuAxxfO6bv4IDJ7Af1Tka86sxh6EXTE06kfWOa6h95hzC_4EeLlkkUfW505sNgDC5KnGblKROJzUTR956NeD5Ig","spamInfo":{"isSpam":false,"reason":"12"},"subject":"Re: [OmT] glossary function","postDate":"1264955769","msgId":16627,"canDelete":true,"contentTrasformed":false,"systemMessage":false,"headers":{"messageIdInHeader":"PDRCNjVCMTc5LjcwMzA2MDNAYWJzYW1haWwuY28uemE+","inReplyToHeader":"PDRCNjVBM0I5LjIwOTAyMDZAbWFyY3ByaW9yLmRlPg==","referencesHeader":"PDI0ZWMyMGQ0MTAwMTI4MjMyMngxZmJjOWJhYWc4MmIxMDY5ZDc5MWMxYTkyQG1haWwuZ21haWwuY29tPgkgPEFPRUhLQ0tPSU9HUEdDTkxERUtCQUVJT0dIQUEuZC5icmllbEBmcmVlLmZyPiA8MjRlYzIwZDQxMDAxMjkwNDM5aDMzNTcyYTkwcjQwMDUxNDdjMWNlYmY2ZmJAbWFpbC5nbWFpbC5jb20+IDw0QjYzMDNEOS43MDUwMzA2QG1hcmNwcmlvci5kZT4gPDRCNjUzNzVFLjEwNzAwMDlAYWJzYW1haWwuY28uemE+IDw0QjY1NjUxMi45MDcwNDA4QG1hcmNwcmlvci5kZT4gPDRCNjU5QkVBLjgwODA2MDZAYWJzYW1haWwuY28uemE+IDw0QjY1QTNCOS4yMDkwMjA2QG1hcmNwcmlvci5kZT4="},"prevInTopic":16626,"nextInTopic":16628,"prevInTime":16626,"nextInTime":16628,"topicId":16567,"numMessagesInTopic":74,"msgSnippet":"... Using file extensions (for specifying subtypes of files) is very clever, but it is uncommon.  The file extension helps *users* determine what kind of a","rawEmail":"Return-Path: &lt;leuce@absamail.co.za&gt;\r\nX-Sender: leuce@absamail.co.za\r\nX-Apparently-To: OmegaT@yahoogroups.com\r\nX-Received: (qmail 94537 invoked from network); 31 Jan 2010 16:36:29 -0000\r\nX-Received: from unknown (98.137.34.46)\n  by m12.grp.re1.yahoo.com with QMQP; 31 Jan 2010 16:36:29 -0000\r\nX-Received: from unknown (HELO waveland.rdns.net) (74.200.252.232)\n  by mta3.grp.sp2.yahoo.com with SMTP; 31 Jan 2010 16:36:29 -0000\r\nX-Received: from [41.2.254.247] (port=3428)\n\tby waveland.rdns.net with esmtpsa (TLSv1:AES256-SHA:256)\n\t(Exim 4.69)\n\t(envelope-from &lt;leuce@absamail.co.za&gt;)\n\tid 1Nbcme-0003y5-UA\n\tfor OmegaT@yahoogroups.com; Sun, 31 Jan 2010 10:36:25 -0600\r\nMessage-ID: &lt;4B65B179.7030603@absamail.co.za&gt;\r\nDate: Sun, 31 Jan 2010 18:36:09 +0200\r\nUser-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.0\r\nMIME-Version: 1.0\r\nTo: OmegaT@yahoogroups.com\r\nReferences: &lt;24ec20d41001282322x1fbc9baag82b1069d791c1a92@mail.gmail.com&gt;\t &lt;AOEHKCKOIOGPGCNLDEKBAEIOGHAA.d.briel@free.fr&gt; &lt;24ec20d41001290439h33572a90r4005147c1cebf6fb@mail.gmail.com&gt; &lt;4B6303D9.7050306@marcprior.de&gt; &lt;4B65375E.1070009@absamail.co.za&gt; &lt;4B656512.9070408@marcprior.de&gt; &lt;4B659BEA.8080606@absamail.co.za&gt; &lt;4B65A3B9.2090206@marcprior.de&gt;\r\nIn-Reply-To: &lt;4B65A3B9.2090206@marcprior.de&gt;\r\nContent-Type: text/plain; charset=UTF-8; format=flowed\r\nContent-Transfer-Encoding: 7bit\r\nX-AntiAbuse: This header was added to track abuse, please include it with any abuse report\r\nX-AntiAbuse: Primary Hostname - waveland.rdns.net\r\nX-AntiAbuse: Original Domain - yahoogroups.com\r\nX-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]\r\nX-AntiAbuse: Sender Address Domain - absamail.co.za\r\nX-Originating-IP: 74.200.252.232\r\nX-eGroups-Msg-Info: 1:12:0:0:0\r\nFrom: &quot;Samuel Murray (Durbanville)&quot; &lt;leuce@absamail.co.za&gt;\r\nSubject: Re: [OmT] glossary function\r\nX-Yahoo-Group-Post: member; u=176392694; y=oERA6F-sWqTQpTUhIpFWrSIVyga4-QKXzD97KofCTbwYXmk1Vg\r\nX-Yahoo-Profile: lacialacia\r\n\r\nMarc Prior wrote:\n\n&gt; Is it \n&gt; reasonable to expect users - professional translators who are using a \n&gt; CAT tool - to be able to handle them manually, or not? I see only two \n&gt; answers to this particular question. If yes, then we continue to exploit \n&gt; extensions for OmegaT&#39;s functionality...\n\nUsing file extensions (for specifying subtypes of files) is very clever, \nbut it is uncommon.  The file extension helps *users* determine what \nkind of a file it is (and it may be used by the operating system to know \nwhat program to launch), but programs typically examine the *content* of \nthe file when they need to use the file.\n\nYou can take a plain text file, and RTF file, a Word 95 file, a Word \n2000 file and a Word 2007 file, and all give them the file extension \n&quot;DOCX&quot;, and MS Word will open the files successfully and correctly. \nDouble-clicking the &quot;DOCX&quot; files will cause MS Word to launch and open \nthem, but that is only because the operating system had associated \n&quot;DOCX&quot; with MS Word.  The operating system doesn&#39;t know what kind of a \nfile it is -- it only knows that MS Word is the default program for \nopening it.  MS Word then reads the file, but it doesn&#39;t depend on the \nfile extension to figure out how to display it -- it examines the file \nitself.\n\nTake a TMX file and rename it to file.jpg.  Then open it in an XML \ncapable text editor or word processor such as MS Word or OOo Writer. \nThe file will be opened as an XML file, regardless of file extension.\n\nIf I rename a JPG file to file.gif or file.bmp, and I double-click on \nit, it may launch my default GIF and BMP viewer instead of my default \nJPG viewer (which means I had fooled the operating system), but if those \nprograms are JPG capable, they open the file and interpret it correctly \nas JPG.  If not, they don&#39;t try to display it as a GIF or a BMP, but \ngive an error message instead.\n\nEventually OmegaT should do the same.  Until then, it will use file \nextensions to specify *subtypes* of file types (a little weird, but \neffective nonetheless).  OmegaT is opensource and volunteer developed, \nand does not have the resources to develop a more mature file reading \nsystem just yet.  So I have no objection to the use of file extensions \nto make up for OmegaT&#39;s inability to deal with file variant issues.  It \nis a simple, effective hack.\n\nI find the skill of working with file extensions to be a great strength, \nevery day, but another user would be able to do what I do without having \nto know about file extensions (even if it will take him a little longer \nto do what I do).  Can you think of normal or common situations in which \na normal computer user (with 6 months&#39; to 1 year&#39;s experience, perhaps) \nwould need to deal with and/or be aware of file extensions?  I can&#39;t... \nbut perhaps we live and work in different worlds.\n\n&gt; If no, we \n&gt; switch to TBX at the earliest possible opportunity...\n\nYour argument &quot;if changing file extensions isn&#39;t a basic skill, we \nshould use TBX for glossaries&quot; doesn&#39;t quite make sense to me...\n\n:-)\n\nAnd for the sample file issue:\n\n&gt; The reason for having more than two languages is that there would only \n&gt; need to be one &quot;sample&quot; glossary file supplied with OmegaT. That one \n&gt; file, containing a selection of common words (for example, where \n&gt; applicable, articles, the verbs to be/to have, common prepositions, \n&gt; conjunctions, personal pronouns) in perhaps a dozen languages would \n&gt; serve the vast majority of users for demonstration of the glossary \n&gt; function *in virtually any project*.\n\nAaah, I see we have two different ideas about &quot;sample&quot;.  To me, the \npurpose of the sample would not be to illustrate the glossary function \nbut to show what the glossary format looks like (and to help people who \nare unsure about whether their favourite text editor is the right one).\n\nSee, if there is a sample file that the user can simply open and start \nusing, he can open it directly, easily.  But if he needs to create the \nfile himself, using a text editor, he&#39;d often have to navigate to the \nright folder manually (which may not be difficult but it can be annoying \nif you have to do it each time).\n\nThat is why the sample in the RFE that I had just submitted has a grand \ntotal of *four* entries.  The Wordfast sample glossary has only three \nentries, by the way.  But the pic^H^H^Hsample is worth a thousand words.\n\nAlso, if the glossary contains a bunch of &quot;normal&quot; words, it may create \nthe impression that glossaries are meant to be used as dictionaries, \nwith common words in them, instead of as term lists, with mostly \nspecialist terms or difficult words in them.\n\n&gt; &quot;This glossary file is only a sample: it contains a selection of terms\n&gt; in several languages. Your own glossaries should only contain terms in \n&gt; one source language and one target language&quot;\n&gt; \n&gt; In my view, anyone who is translating into or from English should be \n&gt; able to understand this explanation...\n\nYes.  My sample file (on SF RFE) has a similar message.\n\nSamuel\n\n"}}