{"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":212348766,"authorName":"Raymond Martin","from":"Raymond Martin &lt;biophotoray@yahoo.ca&gt;","profile":"biophotoray","replyTo":"LIST","senderId":"sgGcrxe1VMLaDjOeeAS6Oahkg0Tzs6pClNF38oB3kvLF_nyEHgkpITp14Ve_1SJxOQdPwK-TJriPGwNjoXISWNCq41BX2G-CSwIhGQ","spamInfo":{"isSpam":false,"reason":"12"},"subject":"Re: [OmT] OmegaT resource bundle upgrade comments","postDate":"1113322668","msgId":1712,"canDelete":true,"contentTrasformed":false,"systemMessage":false,"headers":{"messageIdInHeader":"PDIwMDUwNDEyMTYxNy40ODg3NC5iaW9waG90b3JheUB5YWhvby5jYT4=","inReplyToHeader":"PGZkYzhiZDMxMDE2YjczN2FkY2VkZmRkODI1Y2I2YWNhQG14ODIudGlraS5uZS5qcD4=","referencesHeader":"PDIwMDUwNDA3MTIxNC4wNDc0MS5iaW9waG90b3JheUB5YWhvby5jYT4gPDIwMDUwNDEyMTE1MC4zNzk5MC5iaW9waG90b3JheUB5YWhvby5jYT4gPGZkYzhiZDMxMDE2YjczN2FkY2VkZmRkODI1Y2I2YWNhQG14ODIudGlraS5uZS5qcD4="},"prevInTopic":1711,"nextInTopic":1714,"prevInTime":1711,"nextInTime":1713,"topicId":1682,"numMessagesInTopic":26,"msgSnippet":"JC,\n\n \n  TF_MENU_FILE_COMPILE=Create Documents\n \n As long as the menu is properly documented in the doc I suppose it is \n perfectly fine.\n \n\nAny","rawEmail":"Return-Path: &lt;biophotoray@yahoo.ca&gt;\r\nX-Sender: biophotoray@yahoo.ca\r\nX-Apparently-To: OmegaT@yahoogroups.com\r\nReceived: (qmail 21410 invoked from network); 12 Apr 2005 20:18:01 -0000\r\nReceived: from unknown (66.218.66.218)\n  by m27.grp.scd.yahoo.com with QMQP; 12 Apr 2005 20:18:01 -0000\r\nReceived: from unknown (HELO smtp202.mail.sc5.yahoo.com) (216.136.129.92)\n  by mta3.grp.scd.yahoo.com with SMTP; 12 Apr 2005 20:18:01 -0000\r\nReceived: from unknown (HELO jasper.eureka.net) (biophotoray@216.252.85.164 with plain)\n  by smtp202.mail.sc5.yahoo.com with SMTP; 12 Apr 2005 20:18:00 -0000\r\nTo: OmegaT@yahoogroups.com\r\nDate: Tue, 12 Apr 2005 16:17:48 +0000\r\nUser-Agent: KMail/1.7.2\r\nReferences: &lt;200504071214.04741.biophotoray@yahoo.ca&gt; &lt;200504121150.37990.biophotoray@yahoo.ca&gt; &lt;fdc8bd31016b737adcedfdd825cb6aca@mx82.tiki.ne.jp&gt;\r\nIn-Reply-To: &lt;fdc8bd31016b737adcedfdd825cb6aca@mx82.tiki.ne.jp&gt;\r\nMIME-Version: 1.0\r\nContent-Type: text/plain;\n  charset=&quot;iso-8859-1&quot;\r\nContent-Transfer-Encoding: 7bit\r\nContent-Disposition: inline\r\nMessage-Id: &lt;200504121617.48874.biophotoray@yahoo.ca&gt;\r\nX-Originating-IP: 216.136.129.92\r\nX-eGroups-Msg-Info: 1:12:0\r\nFrom: Raymond Martin &lt;biophotoray@yahoo.ca&gt;\r\nSubject: Re: [OmT] OmegaT resource bundle upgrade comments\r\nX-Yahoo-Group-Post: member; u=212348766\r\nX-Yahoo-Profile: biophotoray\r\n\r\nJC,\n\n&gt; &gt;\n&gt; &gt; TF_MENU_FILE_COMPILE=Create Documents\n&gt; \n&gt; As long as the menu is properly documented in the doc I suppose it is \n&gt; perfectly fine.\n&gt; \n\nAny changes here are going to have to be rectified in the documention.\n\n&gt; \n&gt; You are right, if we have a project menu and if the app follows, then \n&gt; it is necessary to have all things related together under one menu.\n&gt; \n&gt; But right now, Maxym being away, I don&#39;t see that we&#39;re going to see \n&gt; any big changes in the app for a while.\n&gt; \n\nMyself, I want to try to get some of the GUI aspects more in line with other well\nknown CAT apps available to start. After that is out of the way I can look at some \nmore serious tasks like file filters.\n\n\n&gt; Besides for that I see your point. But do we address the (far) future \n&gt; users or the immediate users ? Up to the coders !\n\nMy perspective would be to try to see both at the same time and keep a balance.\nIt is inevitable that somewhere down the line new changes brought in are going \nto require the user to adjust somewhat. Hopefully when the changes come people\nwill not be too upset. As long as good reasons are given for changes then most\npeople will get past it and the project can move forward.\n\nThe Lion&#39;s share of decision making power for the code falls on the coders, but\nin the long run that will not necessarily land the software in the right place if the\nend user&#39;s perspective is not carefully considered. Coders might add in things\nwhich are not needed or exclude something necessary because they do not have\na sufficient understanding of the problem domain. On the other hand, users\nmight not understand what exactly is possible in software and have unrealistic\nexpectations about what can be accomplished and in how much time. The only\nway to move forward is in consultation with each other and through the realization\nof each others strengths and areas of expertise.\n\n\n&gt; I am the one who requested such a menu to disable the default mnemonics \n&gt; on Mac. Mnemonics are _never_ used on the OSX gui and are confusing \n&gt; since calling them uses keys that also call special characters on some \n&gt; keyboards. That is when one uses the .jar file on Mac.\n&gt; \n&gt; Now that the OSX bundle exists there is no need for the menu since OSX \n&gt; users are very likely to use the bundles, which does not give them \n&gt; access to mnemonics anyway.\n&gt; \n\nI see. I&#39;m going to take it out of my RPM version, but if anybody uses another\nversion on Mac other than the bundle they will still need it. No?\n\n&gt; \n&gt; But the two strings are what is reinjected in the code to have the \n&gt; &lt;segment 0001&gt; and &lt;end segment&gt; displayed right ?\n\nYes. But they are inserted verbatim. There is no code at present for their localization.\n\n&gt; \n&gt; Besides, since OmegaT supports utf-8 etc, I suggested that project \n&gt; folder names be localizable too (not /glossary in French but /glossaire \n&gt; etc). I know that&#39;s a feature request, but keep it in mind if you look \n&gt; for potential localizable strings.\n&gt; \n\nJust need the localized strings and the rest should be easy to put in.\n\n\n&gt; &gt; More detail on allowable language codes or links to them is need in the \n&gt; &gt; documentation. A complete list of the codes or where to find them is the \n&gt; &gt; best idea.   Then this message can be fixed.\n&gt; \n&gt;  From the TMX 1.4b specification:\n&gt; \n&gt; [ISO 639]\n&gt; Codes for the Representation of Names of Languages. ISO (International \n&gt; Standards Organization), Nov 2001.\n&gt; [ISO 3166]\n&gt;   Codes for the representation of names of countries and their \n&gt; subdivisions. ISO (International Organization for Standardization), Jun \n&gt; 2000.\n\nOkay. Maybe a page with the codes in the docs or a link to the codes too.\n\n&gt; ## What about something like:\n&gt; ST_NOTHING_FOUND=The string you searched was not found in any specified\n&gt; document\n\n&gt; &gt; Have to look at the search for relevance of your string. Is the user really \n&gt; &gt; attempting to search in a &#39;specified&#39; document?\n&gt; \n&gt; Well, the doc says what documents are searched for each type of search, \n&gt; so I suppose that fits the definition of &quot;specified&quot;. But there must be \n&gt; either a way to explicit what the specified documents are, or a way to \n&gt; rephrase this part to fit what the search actually does.\n&gt; \n\nThe user is not specifying any particular documents by their choice of options.\nThe search is restricted to certain subsets of the available documents/files for\nthe options or type of search performed.\n\nThe search function at present doesn&#39;t seem to warrant too much extra being added \nto it. \n\nI see that only the segment number is given along with the results.\n\nThe user can look at the project files list and do the math to see which files are\ninvolved (a little tedious perhaps), the filename could be added next to the segment \nnumber returned by the search, or the range of segments could be given as a new\ncolumn in the project files list next to the segment count ( e.g.\n\n-------------------------------------------------\nFilenames  Segments       Range\nfile-a.txt          25              1 -   25\nfile-b.sxw       50\t      26 -   50\nfile-c.html      200            51 - 250 \n...\n-------------------------------------------------\n\nRaymond\n\n\n\n\n\r\n\n"}}