tag:blogger.com,1999:blog-63354600193165762812012-01-05T09:01:29.999+09:00Mac For TranslatorsA blog for translators working on Mac OSXJean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.comBlogger901100tag:blogger.com,1999:blog-6335460019316576281.post-89258818645920612352011-10-27T16:19:00.006+09:002011-11-10T09:59:00.128+09:00Oracle JDK7 for OSXYou remember when Apple said they would not maintain Java anymore ? That was just 12 months ago:<br /><br /><a href="http://mac4translators.blogspot.com/2010/10/java-is-dead-long-live-java.html">Java is dead! Long live Java? (on this blog)</a><br /><br />I just noticed that Oracle released a new preview edition of JDK7 for OSX yesterday (b215).<br /><br /><a href="http://jdk7.java.net/macportpreview/">http://jdk7.java.net/macportpreview/</a><br /><br />I installed it and after changing my Java preferences (search for "Java Preferences" in SpotLight), I tried the preview version of OmegaT.<br /><br />The result ?<br /><br /><code><br />54443: Info: OmegaT-2.5.0_1 (Thu Oct 27 15:05:55 JST 2011) Locale en_US <br />54443: Info: Java: Oracle Corporation ver. 1.7.0-ea, executed from '/Library/Java/JavaVirtualMachines/JDK 1.7.0 Developer Preview.jdk/Contents/Home/jre' (LOG_STARTUP_INFO)<br /></code><br /><br />It works !<br /><br />No crash yet so I think I'll finish the current job with that new version of Java.<br /><br />Be extra cautious though when you use preview versions of software. A bug can bite you in the middle of a job...<br /><br /><b>Update (a few hours later)</b><br />It works, but there are a few issues that make it not practical to work with this preview right now. I've reverted to Java 1.6 until Oracle delivers something closer to a release candidate :-)<br /><br />Detailed information is here:<br /><br /><a href="http://wikis.sun.com/display/OpenJDK/Mac+OS+X+Port+Project+Status">http://wikis.sun.com/display/OpenJDK/Mac+OS+X+Port+Project+Status</a><br /><br /><b>Update (a few days later)</b><br />Apple has just released a new update for Java 1.6 for Snow Leopard and Lion. Check software Update. The JDK7 port just released a new build: b217.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-8925881864592061235?l=mac4translators.blogspot.com' alt='' /></div>suzumehttp://www.blogger.com/profile/04461530003126147499noreply@blogger.com3tag:blogger.com,1999:blog-6335460019316576281.post-60171696242936128242011-10-27T15:54:00.005+09:002011-11-10T10:01:25.150+09:00New fun to come with OmegaT 2.5...OmegaT 2.5, the preview version that you can get from:<br /><br /><a href="https://sourceforge.net/projects/omegat/files/OmegaT%20-%20Latest/">https://sourceforge.net/projects/omegat/files/OmegaT%20-%20Latest/</a><br /><br />includes a really nice new feature that, unfortunately, is not yet available for Mac users...<br /><br /><b>(Nov. 10 update: </b>the latest version of the plugin works fine on Mac now<b>)</b><br /><br /><br />If it is not, then you can rightly ask why bother mentioning it here at all ? Well, the answer is simple. It is kind of available, but because of an user interface design issue, the buttons that make it run are not available on Mac... This is going to be fixed real soon. In the meanwhile, get ready for...<br /><br />A scripting interface to OmegaT's internals.<br /><br />See the announcement here:<br /><br /><a href="http://tech.groups.yahoo.com/group/OmegaT/message/22988">http://tech.groups.yahoo.com/group/OmegaT/message/22988</a><br /><br />People who know what they are doing can already check this Java documentation page:<br /><br /><a href="http://java.sun.com/developer/technicalArticles/J2SE/Desktop/scripting/">Scripting for the Java Platform</a><br /><br />According to the scripting plugin source code, the possible languages for use in OmegaT are:<br /><br /><ul><li>JavaScript</li><li>Jacl</li><li>NetRexx</li><li>Java</li><li>BML</li><li>VBScript</li><li>JScript</li><li>PerlScript</li><li>Perl</li><li>JPython</li><li>Jython</li><li>LotusScript</li><li>XSLT</li><li>Pnuts</li><li>BeanBasic</li><li>BeanShell</li><li>Ruby</li><li>JudoScript</li><li>Groovy</li><li>ObjectScript</li><li>Prolog</li><li>Rexx</li></ul><br /><br />There are already plenty of exchanges on the OmegaT mailing list regarding the scripting extension. Check this thread for example:<br /><br /><a href="http://tech.groups.yahoo.com/group/OmegaT/message/23260">http://tech.groups.yahoo.com/group/OmegaT/message/23260</a><br /><br />We'll have an announcement here when the feature works on Mac...<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-6017169624293612824?l=mac4translators.blogspot.com' alt='' /></div>suzumehttp://www.blogger.com/profile/04461530003126147499noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-13952129445202092742011-10-27T15:19:00.004+09:002011-10-27T15:54:33.936+09:00Dennis Ritchie and John McCarthy too...A few days after Jobs, Dennis Ritchie and John McCarthy passed away too, but that did not trigger international interest.<br /><br />Dennis Ritchie is called the "father of C", C as in "C language". Everyone who's done a little bit of programming knows about the importance of C in the computing world.<br /><br /><a href="http://en.wikipedia.org/wiki/C_(programming_language)">http://en.wikipedia.org/wiki/C_(programming_language)</a><br /><br />A few days after Ritchie, John McCarthy, the "father of Lisp" passed away too. Lisp is the language that was mostly used for artificial intelligence works "back then".<br /><br /><a href="http://en.wikipedia.org/wiki/Lisp_(programming_language)">http://en.wikipedia.org/wiki/Lisp_(programming_language)</a><br /><br />Lisp is 11 years older than C. Lisp was born in 1958 and C in 1969. But both languages are still commonly used in computing today...<br /><br />Of course, both languages can be used on Macs. If you install the developer's tools that come with your DVD, you have access to a C compiler. Lisp, being a family of languages, requires to make a few choices (either get an ANSI standardized Lisp, or a Scheme, or a new Lisp like Clojure, that runs in Java etc.)<br /><br />As for introductory books, "Land of Lisp" by Conrad Barski, M.D., from No Starch Press has been very well reviewed.<br /><br /><a href="http://nostarch.com/lisp.htm">http://nostarch.com/lisp.htm</a><br /><br />"Practical COmmon Lisp" by Peter Seibel from Apress is really nice too and sparked a renewed interest in the language. Plus, the PDF is freely available.<br /><br /><a href="http://www.gigamonkeys.com/book/">http://www.gigamonkeys.com/book</a><br /><br />As for C, well, there are so many books about C programming that the only one I can think of is Kerninghan and Ritchie's "The C Programming Language, Second Edition" from Prentice Hall.<br /><br /><a href="http://cm.bell-labs.com/cm/cs/cbook/">http://cm.bell-labs.com/cm/cs/cbook/</a><br /><br />Objective-C is a strict super-set of C and is mostly known for being the language behind OSX applications.<br /><br />A good introduction I found is "Programming in Objective-C" by Stephen G Kochan, from Pearson Education.<br /><br /><a href="http://www.pearsonhighered.com/educator/product/Programming-in-ObjectiveC-3E/9780321711397.page">http://www.pearsonhighered.com/educator/product/Programming-in-ObjectiveC-3E/9780321711397.page</a><br /><br />Of course, you can find plenty of free tutorial that can get you started in both languages.<br /><br /><br />Programming is fun and if it is not already the case, you should really give it a try.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-1395212944520209274?l=mac4translators.blogspot.com' alt='' /></div>suzumehttp://www.blogger.com/profile/04461530003126147499noreply@blogger.com1tag:blogger.com,1999:blog-6335460019316576281.post-20918952863586156562011-10-06T12:42:00.001+09:002011-10-06T12:44:50.844+09:00Steve Jobs passed awayIt's going to be analyzed all over the world. Daringfireball linked to Job's Commencement Address in 2005. Here it is:<br /><br /><a href="http://news.stanford.edu/news/2005/june15/jobs-061505.html">'You've got to find what you love,' Jobs says</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-2091895286358615656?l=mac4translators.blogspot.com' alt='' /></div>suzumehttp://www.blogger.com/profile/04461530003126147499noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-9029728348179982542011-05-19T09:33:00.001+09:002011-05-23T20:40:27.652+09:00Virtaal running on Mac ! Part IIAfter the previous post, it appeared that Virtaal has problems with my configuration. Some testing and a few mails later here is a new announcement from the Virtaal team:<br /><br /><br /><span class="Apple-style-span" style="font-family: monospace;"></span><br /><blockquote type="cite">From: Dwayne Bailey <dwayne@translate.org.za><br />Date: 19 mai 2011 08:40:17 UTC+09:00<br />To: translate-devel@lists.sourceforge.net<br />Subject: [Translate-devel] Mac builds for Virtaal 0.7.0 rc1<br /><br /><br />You can get Mac OS X builds for Virtaal 0.7.0 rc1 here:<br />http://translate.sourceforge.net/snapshots/virtaal-0.7.0-rc1/Virtaal-Intel-0.7.0-rc1-1.dmg<br /><br />Fixes since the beta 5 for Mac:<br />* The build uses its own Python (should solve your problem JC)<br />* Spell checking works - like Windows builds we download the spell checkers<br />* TM server is now running<br /><br />Issues:<br />* We get a solid hang with some keyboard shortcuts e.g. Ctrl-W to close<br />the translation file. Navigation seems to work<br />* The installer is massive 43M, we'll put it on diet when we've got<br />stable builds<br />* The keyboard shortcuts are still mapped to Linux/Windows and haven't<br />been remapped to Mac<br />* Doesn't seem to work at all on 10.5 (Leopard) - well it does start but<br />you can't open anything<br />* Pango is still messing up Arabic</dwayne@translate.org.za></blockquote><br /><br />Basically Virtaal launches properly now. Welcome to the world of Mac Virtaal !<br /><br />(Update: rc1-1 still had problems but rc1-2 worked fine. Check the snapshots located here to get the latest file: http://translate.sourceforge.net/snapshots/)<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-902972834817998254?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-34021806361339697252011-05-15T12:40:00.000+09:002011-05-15T12:40:20.076+09:00Virtaal running on Mac !From Dwayne Bailey, on the Translate Toolkit development list:<br /><br /><br /><span class="Apple-style-span" style="font-family: monospace;">Hi Virtaalers,<br /><br />I've just got Virtaal running on a Mac, in a bundle and in a disk image.<br /><br />It needs a testers love so please head over here and get your disk image<br /><a href="http://translate.sourceforge.net/snapshots/virtaal-0.7.0-beta5/Virtaal-Intel-0.7.0-beta5.dmg">http://translate.sourceforge.net/snapshots/virtaal-0.7.0-beta5/Virtaal-Intel-0.7.0-beta5.dmg</a><br /><br />I'd love to hear your feedback<br /><br />To install:<br />1) Download<br />2) Click on the disk image<br />3) Either drag Virtaal to your applications folder or run it directly<br />from the folder<br /><br />Testing:<br />1) Try to translate things, looking around is great but real work brings<br />out the bugs<br />2) Report any bugs at <a href="http://bugs.locamotion.org/">bugs.locamotion.org</a><br /><br />What works:<br />* The file menu is integrated like a Mac app<br />* Translating works<br />* TM and MT<br /><br />What doesn't work... yet:<br />* Spell checking - we'll probably need to use the approach we're doing<br />in Windows to download<br />* The menu appears in the application window<br />* No fancy installer<br />* Keybindings are not Cmd+ but still Ctrl+ - some don't work like<br />pasting placeables.</span><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3402180636133969725?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-13408016445024136302011-05-11T14:10:00.000+09:002011-05-11T14:10:47.112+09:00Comments on the blogApologies to the people who left comments recently. The notifications were sent to an old address and I just noticed the comments today. I've changed the notification reception address and I'll be better next time!<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-1340801644502413630?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-23885481124166375172011-04-22T01:02:00.001+09:002011-04-22T01:02:57.086+09:00Introduction to regular expressions<i>The technology that had the most impact on my workflow is definitely "regular expressions".<br /><br />I discovered them at the end of the 90' when I was working on the conversion of a database output to a set of about 6000 static HTML pages. At the time, the editor of choice on the Mac was BBEdit from Barebones Software, but its free and "lite" version "BBEdit Lite" was also immensely popular. BBedit Lite has now been replaced by Textwrangler and just like its predecessor, Textwrangler can be used without paying a user license fee*.</i><br /><br /><ol><li><h2>What are regular expressions?</h2><br />Regular expressions are a "search" function on steroïds. Regular expressions were created to find patterns in strings. They can find simple patterns like the word "pattern" in this text, or more complex patterns like "a string that starts with 'pa', followed by a letter that's repeated twice, followed by any three characters that are not 'space' or '@' or '^' and followed by a space".<br /><br />This document uses its two first paragraphs (the paragraphs in <i>italics</i>, above) as a test ground. Paste that paragraph in your favorite regular expressions supporting text editor (I use Textwrangler for all the descriptions so you might want to use it too) then call the search window, check the "grep" box at its bottom and search for:<br /><br /><b>re<span class="Apple-style-span" style="color: magenta;">[^ ]</span><span class="Apple-style-span" style="color: red;">*</span></b><br /><br />You should see colors appearing while you type the search terms.<br /><br />What that expressions means is:<br /><b>r</b> followed by <b>e</b> followed by a group of characters that are not a space, or by nothing.<br /><br />Hit <b>Next</b> and see what you get, then hit <b>Cmd+G</b> and see what you get. If you start from the top of the paragraph you should have 8 "matches".<br /><br /><br /></li><li><h2>Normal characters</h2><br />Most characters represent themselves in regular expressions (regex), like a "normal" search.<br /><br /> → <b>r</b> means <b>r</b> and <b>e</b> means <b>e</b>, " " means a <b>space</b>. In the same sequence. No magic here.<br /><br /><br /></li><li><h2>Special effects</h2><br />Some characters have special effects:<br /><br /> → <b>[</b> starts a group of characters<br /> → <b>]</b> ends that group<br /> → <b>^</b> means "not"<br /> → <b>*</b> means "zero or more of what just came"<br /><br />So, our simple regular expression means:<br /><br />"look for any string that has a <b>r</b> followed by a <b>e</b> followed by zero or more characters that are not a <b>space</b>."<br /><br />Now, what if you need to find characters like <b>^</b>, <b>[</b>, <b>]</b> or <b>*</b>?<br /><br /><br /></li><li><h2>Cancelling special effects</h2><br />When you want to find characters that have a special effect without "triggering" that special effect, you put a "<b>\</b>" in front of them:<br /><br /> → <b><span class="Apple-style-span" style="color: blue;">\*</span></b> means the character <b>*</b><br /> → <b><span class="Apple-style-span" style="color: blue;">\[</span></b> means the character <b>[</b><br /><br /><br />And since the character "<b>\</b>" has the special effect of removing the special effect of a character that has a special effect... then:<br /><br /> → <b><span class="Apple-style-span" style="color: blue;">\\</span></b> means the character <b>\</b><br /><br />etc.<br /><br />By the way, the character <b><span class="Apple-style-span" style="color: blue;">.</span></b> has the special effect of matching "any one character" so if you're looking for a period, then you really want to look for the <b><span class="Apple-style-span" style="color: blue;">\.</span></b> string...<br /><br /><h3>Examples:</h3><br />The regular expression "<b><span class="Apple-style-span" style="color: red;">. </span></b>" (<b>.</b> followed by <b>space</b>) will match any one character followed by a space. There are 78 strings that match this pattern in the paragraph.<br /><br />The regular expression "<b><span class="Apple-style-span" style="color: blue;">\. </span></b>" (<b>\</b> followed by <b>.</b> followed by <b>space</b>) will match any period followed by a <b>space</b>. There are only 2 strings that match this pattern in the paragraph.<br /><br />The regular expressions "<b>re<span class="Apple-style-span" style="color: red;">*.</span></b>" (<b>re</b> followed by <b>*</b> followed by <b>.</b>) will match any string that is composed of a <b>r</b>, followed by zero or more <b>e</b>, followed by any one character. There are 22 matches in the paragraph. Verify that you understand them all.<br /><br />The regular expression "<b><span class="Apple-style-span" style="color: red;">.</span>e<span class="Apple-style-span" style="color: blue;">\*\."</span></b> (<b>.</b> followed by <b>e</b> followed by <b>\</b> followed by <b>*</b> followed by <b>\</b> followed by <b>.</b>) will match the 4 characters string <b>ee*.</b> that you find at the end of the paragraph.<br /><br /><br /></li><li><h2>Triggering special effects</h2><br />Some characters work the other way round: by themselves they do not have a special effect but if you stick the <b>\</b> character before them, then their special effect is triggered.<br /><br /> → <b>t</b> means <b>t</b> but <b><span class="Apple-style-span" style="color: blue;">\t</span></b> means <b>tabulation</b><br /> → <b>r</b> means <b>r</b> but <b><span class="Apple-style-span" style="color: blue;">\r</span></b> means <b>line break</b> (specifically "carriage return")<br /> → <b>s</b> means <b>s</b> but <b><span class="Apple-style-span" style="color: blue;">\s</span></b> means <b>all sorts of white space</b>, which includes spaces, tabulations, line breaks etc.<br /><br />If the character does not have a special effect then using <b>\</b> has no effect.<br /><br /> → <b>i</b> means <b>i</b> and <b><span class="Apple-style-span" style="color: blue;">\i</span></b> too means <b>i</b><br /><br />Such sequences (<b>\</b> followed by a character) are usually called "escape sequences".<br /><br /><br /></li><li><h2>Remembering matches</h2><br />If you want to "memorize" a match, for later use in the expression or in the "replace" field, then you put the corresponding expressions between parenthesis:<br /><br /> → <b><span class="Apple-style-span" style="color: red;">(</span>re<span class="Apple-style-span" style="color: red;">)</span><span class="Apple-style-span" style="color: magenta;">[^ ]</span><span class="Apple-style-span" style="color: red;">+</span></b> will produce the same matches as above, but will memorize the <b>re</b> part and not the rest.<br /><br /> → <b>re<span class="Apple-style-span" style="color: red;">(</span><span class="Apple-style-span" style="color: magenta;">[^ ]</span><span class="Apple-style-span" style="color: red;">+)</span></b> will produce the same matches as above, but will not memorize the <b>re</b> part and instead will memorize the rest.<br /><br /> → <b><span class="Apple-style-span" style="color: red;">(</span>re<span class="Apple-style-span" style="color: red;">)(</span><span class="Apple-style-span" style="color: magenta;">[^ ]</span><span class="Apple-style-span" style="color: red;">+)</span></b> will produce the same matches as above and will memorize the 2 parts separately.<br /><br /><br /></li><li><h2>Using memorized matches</h2><br />Now that the matches are remembered, you can use them. Use <b><span class="Apple-style-span" style="color: blue;">\1</span></b> to refer to the first memorized string, <b><span class="Apple-style-span" style="color: blue;">\2</span></b> to refer to the second memorized string etc...<br /><br /> → <b><span class="Apple-style-span" style="color: red;">(</span>e<span class="Apple-style-span" style="color: red;">)</span><span class="Apple-style-span" style="color: blue;">\1\*\.</span></b> will produce the "<b>ee*.</b>" string that you find at the end of the text.<br /><br /> → search for <b><span class="Apple-style-span" style="color: red;">(</span>re<span class="Apple-style-span" style="color: red;">)(</span><span class="Apple-style-span" style="color: magenta;">[^ ]</span><span class="Apple-style-span" style="color: red;">+)</span></b> and put <span class="Apple-style-span" style="color: blue; font-weight: bold;">\2\1 </span>in the <b>Replace:</b> field:<br /><br /><span class="Apple-tab-span" style="white-space: pre;"> </span><b><span class="Apple-style-span" style="color: red;">(</span>re<span class="Apple-style-span" style="color: red;">)</span></b> is the <b>first group</b><br /><span class="Apple-tab-span" style="white-space: pre;"> </span><b><span class="Apple-style-span" style="color: red;">(</span><span class="Apple-style-span" style="color: magenta;">[^ ]</span><span class="Apple-style-span" style="color: red;">+)</span></b> is the <b>second group</b><br /><span class="Apple-tab-span" style="white-space: pre;"> </span><br /><span class="Apple-tab-span" style="white-space: pre;"> </span><b><span class="Apple-style-span" style="color: blue;">\2\1</span></b> will thus put the <b>second group</b> before the <b>first group</b>.<br /><span class="Apple-tab-span" style="white-space: pre;"> </span><br /><span class="Apple-tab-span" style="white-space: pre;"> </span>The term "regular" matches the pattern: <b><span class="Apple-style-span" style="color: red;">(</span>re<span class="Apple-style-span" style="color: red;">)</span></b> matches <b>re</b> and <b><span class="Apple-style-span" style="color: red;">(</span><span class="Apple-style-span" style="color: magenta;">[^ ]</span><span class="Apple-style-span" style="color: red;">+)</span></b> matches <b>gular</b>. The replaced string will thus be "<b>gularre</b>".<br /><span class="Apple-tab-span" style="white-space: pre;"> </span><br /> → search for <b><span class="Apple-style-span" style="color: red;">(</span>re<span class="Apple-style-span" style="color: red;">)(</span><span class="Apple-style-span" style="color: magenta;">[^ ]</span><span class="Apple-style-span" style="color: red;">+) </span></b>and put <b><span class="Apple-style-span" style="color: blue;">\1\1_\[\2\]</span></b><span class="Apple-style-span" style="color: blue; font-weight: bold;"> </span>in the <b>Replace:</b> field:<br /><br /><div style="margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px;"><span class="Apple-tab-span" style="white-space: pre;"> </span><b><span class="Apple-style-span" style="color: red;">(</span>re<span class="Apple-style-span" style="color: red;">)</span></b> is the first group</div><div style="margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px;"><span class="Apple-tab-span" style="white-space: pre;"> </span><b><span class="Apple-style-span" style="color: red;">(</span><span class="Apple-style-span" style="color: magenta;">[^ ]</span><span class="Apple-style-span" style="color: red;">+)</span></b> is the second group</div><span class="Apple-tab-span" style="white-space: pre;"> </span><br /><span class="Apple-tab-span" style="white-space: pre;"> </span><b><span class="Apple-style-span" style="color: blue;">\1\1_\[\2\]</span></b> will put 2 instances of the <b>first group</b>, then an <b>underbar</b>, then <b>[</b>, then the <b>second group</b>, then <b>]</b>.<br /><span class="Apple-tab-span" style="white-space: pre;"> </span><br /><span class="Apple-tab-span" style="white-space: pre;"> </span>In the case of "regular", we'd have the following replacement string:<br /><span class="Apple-tab-span" style="white-space: pre;"> </span><b>rere_[gular]</b><br /><br /><br /></li><li><h2>That's only the beginning...</h2><br />What you need to check now is the special effects of some characters. If you've used Textwrangler it is all in the user manual, page 133, Chapter 8 (Searching with Grep), or you can call the Help with Cmd+? and you'll find a relevant link right away.<br /><br />Textwrangler's regex is pretty standard so once you're used to it there, you can use it in other editors too. If what works in Textwrangler does not work there, check the idiosyncrasies of the editor you use.<br /><br />Now, take a real world document and try to transform it by using a few regular expressions. A typical use case for a translator would be to convert a TMX file into a 2 column tab separated data set, or the opposite: to convert a 2 column tab separated data set into a TMX file. If you manage to do that you've created your first alignement based TMX converter!<br /><br /></li></ol><br />* I try to use or discuss free software when possible because I think that is the way to go. People who want to use a free text editor on the Mac can use Aquamacs. It comes with all the goodness of emacs (including the same regular expressions) and looks and feels a lot like a "normal" Mac text editor.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-2388548112416637517?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com2tag:blogger.com,1999:blog-6335460019316576281.post-19298821775722356472011-02-23T11:17:00.004+09:002011-02-23T11:58:59.985+09:00When your external disks are not willing to go to bed...We've had problems with our iMacs bed time in the office pretty much since we started using them.<br /><br />At night, they seem to refuse to fall asleep.<br /><br />We've tried all the possible settings provided by the OSX interface. But nothing worked. Until I realized that the problems seemed to be related to the external back-up disks attached to them.<br /><br />We use a LaCie and a Western Digital, both with a 1TB capacity, respectively connected to a first generation 24" Intel iMac and to a before-the-latest generation 27" iMac.<br /><ol><br /><li>Sleep settings don't work for the hard disks<br /><li>Manually unmounting the disks seems to solve the issue, but mounting them back is not trivial<br /><li>OSX seems to unmount the disks when I log out from the Apple menu but when I log back in I have to restart all my applications<br /></ol><br />I have found a solution that requires the use of the "Fast user switch menu". The settings are as follows:<br /><ol><br /><li>Go to System Preferences > Accounts<br /><li>Check "Show fast user switch menu as" and choose the option you prefer<br /><li>Make sure the "Show the Restart, Sleep, and Shut Down buttons" box is checked<br /></ol><br />Now, when you want to put the whole system to sleep, the solution is:<br /><ol><br /><li>Click on the Fast user switch menu (top right of your screen)<br /><li>Call the "Login Window..."<br /><li>Press "Sleep"<br /></ol><br />Et voilà !<br /><br />My guess is that the sleep option from the login window actually unmounts the hard disks and leaves them inactive until you enter your account again.<br /><br />As a side note, those sleep problems also had a disturbing side effect: when I'd simply put the system to sleep the "old" way (either by calling "Sleep" from the Apple menu or by using the automation settings in "Energy Saver"), and tried to wake it up in the morning I'd have what looked like system freezes that sounded (yes, actually "sounded") related to the external hard disk activity. With the new system, I've had only one case of "freeze" in a few weeks of time, and it still kind of looks related to the external disk behavior.<br /><br />In any case, this system seems to be allowing our Macs to spend their whole night sleeping and not struggling with hectic external disks... I'll need to check further what is the cause of the disks' inability to sleep, and also what is the cause of my freezes (not happening on the 24"), but that's for another post...<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-1929882177572235647?l=mac4translators.blogspot.com' alt='' /></div>suzumehttp://www.blogger.com/profile/04461530003126147499noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-38053054704996575962011-02-23T11:09:00.002+09:002011-10-27T21:55:14.222+09:00Java is not so dead after all...The announcement came from Oracle, a few weeks after Apple's declaration (see <a href="http://mac4translators.blogspot.com/2010/10/java-is-dead-long-live-java.html">Java is dead! Long live Java?</a>).<br /><br />Basically all of Apple's Java efforts will be handled by Oracle, within the OpenJDK project and Oracle will release Java for Apple machines, not Apple anymore.<br /><br />If you are interested in declarations, check this link: <a href="http://blogs.sun.com/openjdk/entry/news_2010_11_12">OpenJDK News, Nov. 12</a>.<br /><br />Before OpenJDK took charge of the OSX version of Java, there were a number of projects that attempted to use the FreeBSD version of OpenJDK to create something that would run under OSX.<br /><br />Now, OSX has its <a href="http://openjdk.java.net/projects/macosx-port/">own development project</a> at OpenJDK and things are slowly progressing, which is a very good thing...<br /><br />The project goals are:<br /><ul><br /><li>Pass all appropriate certification tests for Java SE 7<br /><li>Include a complete, native Cocoa-based UI Toolkit<br /><li>Provide excellent performance<br /></ul><br />Which basically translates into: what Apple has been providing us with since the beginning of OSX, but by the people who are behind Java (and hopefully with simultaneous Windows/Linux/OSX releases).<br /><br />If you want to build Java on OSX, you can. Follow the instructions on this page: <a href="http://wikis.sun.com/display/OpenJDK/Mac+OS+X+Port">Mac OS X Port</a>. I have built Java 1.7 on my machine and it worked well with OmegaT. The only problem is that the UI toolkit still depends on X11, which means that your favorite Java application will not look like a native citizen of OSX. But that will happen!<br /><br />If you want to see how the project advances and check the discussions (and participate in case you have a problem building the thing for example) check the following links:<br /><ul><br /><li><a href="http://wikis.sun.com/display/OpenJDK/Mac+OS+X+Port+Project+Status">Mac OS X Port Project Status</a><br /><li><a href="http://mail.openjdk.java.net/mailman/listinfo/macosx-port-dev">macosx-port-dev -- Technical discussion about the Mac OS X Port Project</a><br /></ul><br />The questions that remain unanswered are the following:<br /><ol><br /><li>Will Java 1.7 on OSX be available at the time OSX 10.7 Lion is released next summer?<br /><li>If not, will OSX 10.7 Lion include the current Apple released Java 1.6 by default an all new machines?<br /><li>Once Java 1.7 is released by Oracle, will Apple include it in OSX bundles or will users have to go fetch it from Oracle's site ?<br /></ol><br />My take is that Java 1.7 will not be finished by the time Lion is released, and for the rest, I have no idea.<br />I'd like to say "yes" for a default Java 1.6 in Lion and "possible" for inclusion of Oracle's Java in further releases (after all OSX bundles plenty of third party development tools). We'll see.<br /><br />But the future is definitely much brighter than it was back in October.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3805305470499657596?l=mac4translators.blogspot.com' alt='' /></div>suzumehttp://www.blogger.com/profile/04461530003126147499noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-62238035318665230852010-10-21T19:09:00.008+09:002010-10-22T17:44:01.209+09:00Java is dead! Long live Java?Apple just released a new update for Java 1.6 (both for OSX 10.6 and OSX 10.5, available from Software Update), pretty much the same day Steve Jobs introduce us to a few features of the upcoming version of OSX, 10.7 aka Lion.<br /><br />The theme of the presentation was "Back to the Mac". Triple layered meaning...<br /><ol><li>Back to the Mac after spending so much time and energy on iOS and mobile devices<br /></li><li>Software improvements to OSX directly coming from the iOS experience<br /></li><li>Hardware improvements to the MacBook with the new incarnation of the MacBook Air, inheriting a lot of cool technology from the iPad.<br /></li></ol>The presentation is available directly from Apple's page. Skip the iLife stuff and directly go to minute 53' to see the OSX part. The App Store and Mission Control parts are really interesting.<br /><br />Then, in my inbox, came the Java update. After a good news, a bad one (well, hopefully only half bad). <br /><br />Quoting Apple: <strong>As of the release of Java for Mac OS X 10.6 Update 3, the version of Java that is ported by Apple, and that ships with Mac OS X, is deprecated.</strong><br /><br /><strong></strong>The full release note is here: <a href="http://developer.apple.com/library/mac/#releasenotes/Java/JavaSnowLeopardUpdate3LeopardUpdate8RN/NewandNoteworthy/NewandNoteworthy.html%23//apple_ref/doc/uid/TP40010380-CH4-SW1">Java for Mac OS X 10.6 Update 3 and 10.5 Update 8 Release Notes</a><br /><br /><a href="http://developer.apple.com/library/mac/#releasenotes/Java/JavaSnowLeopardUpdate3LeopardUpdate8RN/NewandNoteworthy/NewandNoteworthy.html%23//apple_ref/doc/uid/TP40010380-CH4-SW1"></a> Shocking news.<br /><br />For translators on the Mac, Java applications are the key to freedom from Windows, even though a lot of "switchers" use the Mac mostly to provide their Windows environment with a stable virtual foundation... On the top of my mind, here are the mainstream applications that depend on Java and are vital for translators who do not rely on Windows: <br /><ul><li><a href="http://www.cafetran.republika.pl/">Cafetrans</a><br /></li><li><a href="http://code.google.com/p/okapi/">Okapi Framework</a><br /></li><li><a href="http://omegat.org/">OmegaT</a><br /></li><li><a href="http://www.maxprograms.com/">Swordfish</a><br /></li><li><a href="http://www.wordfast.com/products_wordfast_60.html">Wordfast Pro</a><br /></li></ul>If you read between the lines of the release note though, you can see that what is deprecated is no Java on the Mac in general, but "<em>the version of Java that is ported by Apple, and that ships with Mac OS X</em>".<br /><br />With the recent acquisition of Sun by Oracle (Oracle makes massive use of Java), the opening of the JDK source by Sun a few years ago and the currently existing efforts to port that OpenJDK to the Mac, one can also see that move as a way for Apple to say that Mac users will not be left without Java on the Mac, because either Oracle or the OpenJDK community will eventually deliver something that Java users on Mac can still use to run their favorite applications.<br /><br />In any case, it will <strong>eventually</strong> be possible to install a foreign (compatible) JRE on Mac that runs all our applications. I've tried a few days ago with <a href="http://landonf.bikemonkey.org/static/soylatte/">Soylatte</a> but I was <strong>not</strong> able to fully run OmegaT in it, and the windowing system was X11 (with all its UI glitches).<br /><br />Still, as was mentioned today on the Java-dev list hosted by Apple, it is very unlikely that Apple will just remove Java from OSX. Java is big in education and multiplatform development and Apple has 20% of the PC share in the US as of today (cf the very first part of today's presentation). So Apple is probably thinking of something else.<br /><br />In any case, right now I don't think Mac users of Java apps have anything to fear. They can keep their Snow Leopard Mac with the latest supported Java and don't have to upgrade to anything. We have about 8 months before Lion's release, hopefully Java we'll be there too in one form or another.<br /><br />And apologies for the 10 months long blank on this blog...<br /><br />(updated on 10/22)<br /><br />New update (10/22): Steve Jobs hints at a <a href="http://news.ycombinator.com/item?id=1818550">different approach</a>, via Hacker News: <strong>"Sun (now Oracle) supplies Java for all other platforms. They have their own release schedules, which are almost always different than ours, so the Java we ship is always a version behind. This may not be the best way to do it"</strong><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-6223803531866523085?l=mac4translators.blogspot.com' alt='' /></div>suzumehttp://www.blogger.com/profile/04461530003126147499noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-72166769894933468382010-01-02T01:41:00.000+09:002010-01-02T01:41:28.251+09:00OSX + Windows hybrid systemsApple has made it very easy for Windows people to "switch" to the Mac with its adoption of Intel CPUs a few years ago.<br /><br />What people do when they switch though is not only buy a Mac because it's also a PC, they dump their Windows habits altogether and start computing on the Mac side only.<br /><br />That's good for most of what computing is about nowadays: write a document, browse the web, exchange mails, listen to music, manage pictures and edit a little bit of video.<br /><br />Now, for professionals, leaving Windows altogether is a totally different issue. The first problem is of course the fact that some of the applications they use may not have equivalents on the Mac side. We are all aware that neither Trados nor MemoQ come with a Mac version...<br /><br />The other problem is that even if you're willing to dump your Windows software, you may have to pay new licensing fees for something equivalent on the Mac side... The new software may be better integrated to the Mac ecology, but since you're still used to your Windows ways, it may take some time before you manage to be as productive with your new environment...<br /><br />On the positive side, using Windows inside Mac with a virtualization software is doubleplusgood because:<br />1) Windows is less likely to infect your whole system since it runs in a closed box<br />2) It is also less likely to be an annoyance because when there is a problem, it is always possible to go back to a previous "snapshot" of its state.<br /><br />There, you have tamed the Windows beast by putting it in a Mac box...<br /><br />But working in such a hybrid environment comes with its set of problems: keyboard shortcuts that are not similar in Windows and Mac, technology that works better in "straight" environments (printing, back up etc)...<br /><br />This is not to say that most of the existing virtualization packages have not solved most of those issues, but rather that you are bound to find glitches sometimes. Et voilà ! If you belong to the hybrid category of professionals who want to get a Mac but can't leave Windows right away then Karin Adamczyk's list is for you !<br /><br /><a href="http://tech.groups.yahoo.com/group/MacSwitch/">http://tech.groups.yahoo.com/group/MacSwitch/</a><br /><br />The list is a place where a number of "people who have there before" will explain to you all the subtleties of using your Windows environment on your Mac. Karin's experience has proved very useful on other lists and I'm sure you'll find the place comfortable.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-7216676989493346838?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-9604847763536887062009-09-09T11:51:00.003+09:002009-09-09T11:58:55.883+09:00OmegaT and Snow Leopard(anti-aliasing problem - solved)I was surprised to see a bad lack of anti-aliasing (font smoothing) when I ran OmegaT 2.0 for the first time in Snow Leopard.<br /><br />Work from English was possible, but from Japanese... Forget it !<br /><br />The problem occurred in the Editor pane of OmegaT, not in the Matches or Glossary panes, and I suspected recent developments in the Editor to be the cause of the problem since OmegaT 1.8 did not show this issue.<br /><br />After searching for information, a Java engineer at Apple who happens to monitor the Mac Java-dev list told me that the new Java 6 anti-aliasing default on OSX was probably the cause of the problem. He suggested to either add a line in the code, or to change the default value directly from the command line.<br /><br />A brief exchange with the OmegaT developers concluded that the command line was the best approach especially since command line parameters could be hard coded in the Mac bundle.<br /><br /><br />The next release of OmegaT 2.0 will happen in a few days and the Mac package will include the font-smoothing parameter.<br /><br />In the meanwhile, Mac users who work with the standard OmegaT package (the one that comes with the file OmegaT.jar) can start OmegaT from the command line with the following parameter:<br /><br /><code>$ java -Dapple.awt.graphics.UseQuartz="true" -jar OmegaT.jar</code><br /><br />Users of the Mac package (the OmegaT.app file) can modify it so that it is launched with the correct parameters:<br /><br /><ul><br /><br /><li>right-click on OmegaT.app and select Show Package Contents<br /><br /><li>find the info.plist file within the Contents folder and open it with your favorite text editor<br /><br /><li>replace the following code:<br /><br /><pre><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">key</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">Properties</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">key</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name"><span class="nxml-element-local-name">dict</span></span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">key</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">apple.laf.useScreenMenuBar</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">key</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">string</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">true</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">string</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">dict</span><span class="nxml-tag-delimiter">></span><br /></pre><br /><br /><li>with:<br /><br /><pre><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">key</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">Properties</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">key</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">dict</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">key</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">apple.laf.useScreenMenuBar</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">key</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">string</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">true</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">string</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">key</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">apple.awt.graphics.UseQuartz</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">key</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">string</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">true</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">string</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">dict</span><span class="nxml-tag-delimiter">></span><br /></pre><br /><br /><li>save the file, close the Contents folder, and relaunch OmegaT.app<br /></ul><br /><br />The two solutions are equivalent and should transmit the correct property to the system when you use OmegaT.<br />(Special thanks to Mike Swingler at Apple.)<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-960484776353688706?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-83924893925384521092009-08-30T18:41:00.001+09:002009-08-30T18:44:15.468+09:00Okapi new versionIn case that had escaped you:<br /><br /><quote><br /><br />Hello everyone,<br /><br /><p>We are happy to announce the milestone 3 of the Okapi Framework for Java.<br /><br /><p>To try to make things easier there are now two main distributions:<br /><br /><p>=== okapi-lib (for developers):<br /><br /><br>--> This distribution includes the libraries, documentation and examples you would need to use the Okapi Framework with your programs. It also include Tikal, a command-line tool to do basic task like simple extract and merge. This distribution is not UI dependent and therefore the same for all platforms.<br /><br /><p>=== okapi-apps (for users and developers): <-- The one you are likely to want<br /><br /><br>--> This distribution is the same as okapi-lib (minus the developers documentation). And in addition, it includes the UI-dependent components of the framework, as well as Rainbow (Localization Toolbox) and Ratel (SRX Editor). Because the UI depends on each platform, there are different flavors of this distribution: Windows, Linux (32-bit and 64-bit), and Macintosh (Carbon and now Cocoa).<br /><br /><br /><p>All this can be downloaded from Okapi's main Web site:<br /><a href="http://okapi.opentag.com/downloads.html">http://okapi.opentag.com/downloads.html</a>,<br /><br /><p>as well as from the Google-Code project's site:<br /><a href="http://code.google.com/p/okapi/downloads/list">http://code.google.com/p/okapi/downloads/list</a>.<br /><br /><br /><p>A large part of the work done for this milestone is not visible: We moved the build structure to Maven, so we can develop using continuous integration more efficiently. Ultimately it should make the framework more robust and better tested. <br /><br /><p>We did managed to work on a few visible changes too :) Here are some of them:<br /><br /><p>=== The first version of Tikal in Java has been implemented. This tool allows you to perform simple tasks from the command-line. For example:<br /><br />C:/Tmp>tikal -x *.docx *.html -sl EN -tl FR<br /><br />will extract to XLIFF all the DOCX and HTML files in the Tmp directory.<br /><br />C:/Tmp>tikal -m *.xlf -sl EN -tl FR<br /><br />will merge them back into their respective formats.<br /><br />For more information on Tikal, see <a href="http://okapi.opentag.com/help/applications/tikal/index.html">http://okapi.opentag.com/help/applications/tikal/index.html</a>.<br /><br /><p>=== Various bugs have been fixed in several filters (thanks for the bugs reports) and some improvements have been implemented in others.<br /><br /><p>=== There is a new filter for Qt TS files.<br /><br /><p>=== Cocoa support has been added for the Macintosh.<br /><br /><p>=== There is a new TM connector to query Translate Toolkit TM servers. You can try it using Tikal. For example, if you have a local server running on port 8080, the command:<br /><br />C:/>tikal -q "open file" -tt localhost:8080 -sl EN -tl FR<br /><br />will get the matches for "open file" in that TM.<br /><br /><p>=== As usual, a more complete list of the main changes can be seen in the changes.html document that comes with the distribution.<br /><br /><br /><p>Bug reports and enhancement or features requests can be posted here:<br /><a href="http://code.google.com/p/okapi/issues/list">http://code.google.com/p/okapi/issues/list</a><br /><br /><br /><p>Cheers,<br />-the Okapi Team<br /><br /><end quote><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-8392489392538452109?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-30485963908431739302009-08-29T14:21:00.000+09:002009-08-29T14:21:23.980+09:00Snow LeopardI've only used it for a few hours but here are the first things I found:<br /><br />1) Default Java version is Java 1.6, and OmegaT seems to have issues with that. It works but there is an issue with the font selection that is not respected in the Editor window.<br /><br />2) The input method can be set to stick to a document. For ex, you can have a TextEdit document that uses Kotoeri, another that uses US and changing of document will not change the input method. That's an improvement over the situation in Tiger where, if I remember well, the input method was "attached" to the application but not to the document.<br /><br />3) The old option "multilingual spellchecking" can use a subset of the available languages. That way, you can more efficiently check the spelling without changing the language in the spellchecker interface every time a paragraph uses a different language.<br /><br />4) The spellchecker can also automatically correct your mistakes.<br /><br />5) The services are indeed much better integrated to the workflow. A right click on an element (text, image etc) will trigger a contextual menu that shows possible services for that element.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3048596390843173930?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com1tag:blogger.com,1999:blog-6335460019316576281.post-47873481874645187152009-08-28T11:39:00.003+09:002009-08-29T09:02:56.967+09:00Calculator bug ?This bug seems to have been fixed in Snow Leopard.<br /><br />My bug report to Apple:<br /><br />Summary:<br />Calculator does not accept "." input after conversion from the "Convert" menu.<br /><br />Steps to reproduce:<br />1- enter a value with a decimal point, the decimal point can be entered either from the keyboard or from the the Calculator UI.<br />2- select any conversion from the Convert menu<br />3- the conversion result is displayed<br />4- enter a value with a decimal point again<br /><br />Expected result:<br />The new value should have a decimal point in the location where it has been input<br /><br />Actual result:<br />The decimal point cannot be input, neither from the keyboard nor from the Calculator UI. It is necessary to hit "C" on the Calculator UI to reinitialize Calculator to be able again to input a decimal point.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-4787348187464518715?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-35224859250692415002009-08-05T10:08:00.005+09:002009-08-05T10:22:01.799+09:00OmegaT Java Web StartIn previous article, I mentioned the release of <a href="http://mac4translators.blogspot.com/2009/07/omegat-small-update_29.html">OmegaT as a Java Web Start application</a>.<br /><br />Once <code>OmegaT.jnlp</code> is downloaded, a double-click should open it in Java Web Start.app.<br /><br />If that is not the case, if it opens as a text file for example, it means that .jnlp files associations to Java Web Start.app are broken.<br /><br />To fix that, right-click on the .jnlp file, Choose "Open With", select "Others..." at the bottom of the list and browse your disk to find the application.<br /><br />Java Web Start.app is located in <code>/Applications/Utilities/Java/</code> for older versions of Java and in <code>/System/Library/CoreServices/</code> for the most recent version of Java (<a href="http://support.apple.com/downloads/Java_for_Mac_OS_X_10_5_Update_4">Java update 4, released on June 15 2009</a>).<br /><br />Once you have selected the application, check the "Always open with" box at the bottom of the dialog.<br /><br />Thanks to Yves who send me the comment that triggered this "investigation" and to <a href="http://bbnews.blog.usf.edu/2009/06/20/apple-os-x-java-update-4-breaks-elluminate">this</a> blog article that clarified everything.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3522485925069241500?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-67715934772376914002009-08-04T22:23:00.013+09:002009-08-05T17:43:09.555+09:00Rainbow, XLIFF and OmegaT(I've updated the contents of the file to make things clearer for people who are not familiar with XLIFF - 08/05)<br /><br />OmegaT's support for complex XLIFF is not really optimal. I'm going to spare you the details but basically, unless you tweak the file significantly, OmegaT is likely not going to be able to leverage all the available data.<br /><br /><br />Let's say that we have a XLIFF file with the following data:<br /><br />First segment, not yet translated:<br /><strong>ba bi bu</strong><br />In OmegaT, this part should be in a supported source file located in /source/<br /><br />Reference translation from a first reference file:<br /><strong>ba bi</strong>, translated to <strong>バ ビ</strong>, matches the segment to translate at 66%<br />In OmegaT, this part should be in a TMX file located in /tm/<br /><br />Reference translation from a second reference file:<br /><strong>ba bi bu be</strong>, translated to <strong>バ ビ ブ ベ</strong>, matches the segment to translate at 75%<br />This part too should be in a TMX file located in /tm/<br /><br />Second segment, already translated in the same document:<br /><strong>ba bi</strong>, translated to <strong>バ ビ</strong><br />Since this data comes from the same document and is a validated translation, it should be in the project_save.tmx file located in /omegat/<br /><br />Such an XLIFF file would look like this:<br /><br /><pre>First segment, not yet translated(<target> is empty):<br /><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">trans-unit</span> <span class="nxml-attribute-local-name">approved</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">no</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">id</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">source_file</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">source</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi bu</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">source</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">target</span> <span class="nxml-attribute-local-name">state</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">new</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-slash">/</span><span class="nxml-tag-delimiter">></span><br /><br />First reference translation for that segment:<br /><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">alt-trans</span> <span class="nxml-attribute-local-name">match-quality</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">66</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">origin</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">first_reference_translation</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">source</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">source</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">target</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">バ ビ</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">target</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">alt-trans</span><span class="nxml-tag-delimiter">></span><br /><br />Second reference translation for that segment:<br /><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">alt-trans</span> <span class="nxml-attribute-local-name">match-quality</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">75</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">origin</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">second_reference_translation</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">source</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi bu be</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">source</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">target</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">バ ビ ブ ベ</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">target</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">alt-trans</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">trans-unit</span><span class="nxml-tag-delimiter">></span><br /><br />(↑ end of the first segment)<br /><br />Second segment, already translated in that document:<br /><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name"><span class="nxml-element-local-name">trans-unit</span></span> <span class="nxml-attribute-local-name">approved</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">yes</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">id</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">source_file</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">source</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">source</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">target</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">バ ビ</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">target</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">trans-unit</span><span class="nxml-tag-delimiter">></span></pre><br /><br /><br />If you want to know more about the XLIFF specification, look at this page: <a href="http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html">XLIFF Version 1.2</a><br /><br /><br />Now, let's see how Rainbow can help us leveraging all the data directly from within OmegaT.<br /><br /><br /><h1>Rainbow</h1><br />Here comes Rainbow. I'm mentioned Rainbow, or the Okapi Framework a number of times already.<br /><br />Rainbow is a Java software that acts as a swiss army knife for localization processes. It is a filter to/from complex formats, it is a batch search/replace tool etc.<br /><br />Don't forget to see the Okapi Webinar that was given a few weeks ago by Yves Savourel. It is about 1h long and goes into great details to show you what Rainbow/Okapi is about. OmegaT is used as an example too and the following text can be considered as a detailed explanation of what you see in the Webinar.<br /><br />Webinar: <a href="http://www.translate.com/Language_Tech_Center/Webinar_Portal.aspx?id=132">http://www.translate.com/Language_Tech_Center/Webinar_Portal.aspx?id=132</a><br /> <br />The Okapi group has decided to frequently release snapshots of the code so that users don't have to wait for milestones to get a taste of the most recent features.<br />The snapshots are available here: <a href="http://okapi.opentag.com/snapshots/">http://okapi.opentag.com/snapshots/</a>. Get the rainbow_carbon-macosx_... file.<br /><br />When you unzip the package, you will find a rainbow.sh script file. Open the Terminal where the file is located, make the file executable by typing the following command at the prompt:<br /><code>chmod +x rainbow.sh</code><br /><br />Then, call the script from Terminal to launch Rainbow.<br /><br /><br />When you launch Rainbow, you're displayed with an empty file list.<br /><br /><ol><li>drag & drop your XLIFF file on that list. It should be the list corresponding to the "Input List 1" tab.<br /><li>click on the "languages and encoding" tab and set the appropriate information. For example, an English manual translated to Japanese should be:<br /><ul><li>Source=EN (you can use a variant, like EN-US)<br /><li>Encoding=UTF-8<br /><li>Target=JA<br /><li>Encoding=UTF-8<br /></ul><li>Then go to the "Utilities > Translation Package Creation"<br /><li>Select OmegaT<br /><li>click on the Package Location tab<br /><li>Select a directory where Rainbow will create the OmegaT project<br /><li>Click OK.<br /></ol><br /><br />You're back to the main window where the status bar indicates that the XLIFF file has been processed. What has Rainbow done to your XLIFF file ?<br /><br /><h1>XLIFF</h1><br /><br />A XLIFF file is a mix of a number of things. First, it contains strings to translate in <trans-unit> sections:<br /> <br /><pre><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">trans-unit</span> <span class="nxml-attribute-local-name">approved</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">no</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">id</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">source_file</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">source</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi bu</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">source</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">target</span> <span class="nxml-attribute-local-name">state</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">new</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-slash">/</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">trans-unit</span><span class="nxml-tag-delimiter">></span></pre><br /><br />Then, it may contain reference data. The first type is, obviously, what has already been translated, in similar <trans-unit> sections:<br /><br /><pre><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name"><span class="nxml-element-local-name">trans-unit</span></span> <span class="nxml-attribute-local-name">approved</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">yes</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">id</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">source_file</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">source</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">source</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">target</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">バ ビ</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">target</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">trans-unit</span><span class="nxml-tag-delimiter">></span></pre><br /><br />The other type is what is embedded to serve as reference, it comes as <alt-trans> sections within a <trans-unit>:<br /><br /><pre><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">trans-unit</span> <span class="nxml-attribute-local-name">approved</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">no</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">id</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">source_file</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">source</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi bu</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">source</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">target</span> <span class="nxml-attribute-local-name">state</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">new</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-slash">/</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">alt-trans</span> <span class="nxml-attribute-local-name">match-quality</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">66</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">origin</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">first_reference_translation</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">source</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">source</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">target</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">バ ビ</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">target</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">alt-trans</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">alt-trans</span> <span class="nxml-attribute-local-name">match-quality</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">75</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">origin</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">second_reference_translation</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">source</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi bu be</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">source</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">target</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">バ ビ ブ ベ</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">target</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">alt-trans</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">trans-unit</span><span class="nxml-tag-delimiter">></span></pre><br /><br /><br /><br />When Rainbow is used to create OmegaT projects from XLIFF files it looks for the 3 types of information and separates them in a way that OmegaT can manage.<br /><br /><ol><br /><li>OmegaT cannot manage "empty" <target> elements in <trans-unit> sections. So, Rainbow recreates the source file so that it contains the <source> data in the <target> section. That way, OmegaT only has to overwrite that data:<br /> <br /><pre><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name"><span class="nxml-element-local-name">trans-unit</span></span> <span class="nxml-attribute-local-name">id</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">source_file</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">source</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi bu</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">source</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">target</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi bu</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">target</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">trans-unit</span><span class="nxml-tag-delimiter">></span></pre><br /><br /><li>OmegaT cannot manage already translated data in the XLIFF file. So, Rainbow creates a typical "already translated" OmegaT data file that contains the already translated segments: the project_save.tmx located in the /omegat/ folder of the project:<br /><br /><pre><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name"><span class="nxml-element-local-name">tu</span></span> <span class="nxml-attribute-local-name">tuid</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">source_file</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">tuv</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">><</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">tuv</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">tuv</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">><</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">バ ビ</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">tuv</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">tu</span><span class="nxml-tag-delimiter">></span></pre><br /><br /><li>OmegaT cannot managet reference data in the XLIFF file. So, Rainbow creates a typical "reference translation" OmegaT data file that contains all the embedded translation segments: the alternate.tmx located in the /tm/ folder of the project:<br /><br /><pre><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name"><span class="nxml-element-local-name">tu</span></span> <span class="nxml-attribute-local-name">tuid</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">first_reference_translation</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">tuv</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">><</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">tuv</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">tuv</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">><</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">バ ビ</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">tuv</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">tu</span><span class="nxml-tag-delimiter">></span></pre><br /><pre><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name"><span class="nxml-element-local-name">tu</span></span> <span class="nxml-attribute-local-name">tuid</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">second_reference_translation</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">tuv</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">><</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">ba bi bu be</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">tuv</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">tuv</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">ja</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">><</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">バ ビ ブ ベ</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">tuv</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">tu</span><span class="nxml-tag-delimiter">></span></pre><br /><br /></ol><br /><br />That way, OmegaT can seamlessly access all the data available in that complex XLIFF file. Since Rainbow creates a whole OmegaT project, the only thing necessary to proceed is to open the project with OmegaT and translate.<br /><br /><h1>Delivery</h1><br /><br />Nothing could be simpler. When you are done with your translation, create the translated files from within OmegaT.<br /><br />Then, drag and drop the manifest.xml file located at the root of the OmegaT project created by Rainbow on Rainbow's main window where the Input List 1 tab is displayed. When manifest.xml is visible on the list, use the "Utilities > Translation Package Post-Processing..." menu.<br /><br />Rainbow will use all the data it saved in the project to recreate a "proper" XLIFF file for delivery. That file contains all the data that was contained by the original XLIFF, its structure is identical. The only difference is that now it includes the data you have translated in OmegaT.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-6771593477237691400?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com1tag:blogger.com,1999:blog-6335460019316576281.post-25076935299258973662009-07-29T16:06:00.007+09:002009-07-29T17:34:40.636+09:00Excel files with colored non translatables... (2)<p>Just to show you that <a href="http://mac4translators.blogspot.com/2009/07/excel-files-with-colored-non.html">I am not lying</a>:<br /><br /><p>Here is one of the Excel cells that I have to translate:<br /><br /><span style="color:red;"><h1></span>This is ugly<span style="color:red;"><br /></span>ugly ugly ugly<span style="color:red;"></h1></span>Ugly ugly ugly ugly ugly ugly:<span style="color:red;"><br /></span><span style="color:red;"><br /></span><span style="color:red;"><a href='%%LINK_A%%' class='yellow'></span>Ugly ugly:<span style="color:red;"></a></span> Ugly ugly ugly ugly.<span style="color:red;"><br /></span><span style="color:red;"><a href='%%LINK_B%%' class='yellow'></span>Ugly ugly:<span style="color:red;"></a></span> Ugly ugly ugly ugly ugly.<span style="color:red;"><br /></span><span style="color:red;"><a href='%%LINK_C%%' class='yellow'></span>Ugly ugly:<span style="color:red;"></a></span> Ugly ugly ugly ugly ugly. <span style="color:red;"><br /></span><span style="color:red;"><a href='%%LINK_D%%' class='yellow'></span>Ugly ugly:<span style="color:red;"></a></span> Ugly ugly ugly ugly ugly.!<br /><br /><p>Putting that straight into OmegaT as an ODS file<br /><ol><li>keeps the various styles that exist in the original Excel file (fonts/colors/etc)<br /><li>keeps the HTML codes as plain text.<br /></ol><p>So, in OmegaT, you end up with segments like this (I colored in <font color="green">green</font> the formating inherited from the Excel file, and in <font color="red">red</font> the original HTML tags):<p>First segment:<p><font color="red"><h1></font><font color="green"><f0></font>This is ugly<font color="green"></f0></font><font color="green"><f1></font><font color="red"><br /></font><font color="green"></f1></font><font color="green"><f2></font>ugly ugly ugly<font color="green"></f2></font><font color="green"><f3></font><font color="red"></h1></font><font color="green"></f3></font><font color="green"><f4></font>Ugly ugly ugly ugly ugly <font color="green"></f4></font><font color="green"><f5></font>ugly<font color="green"></f5></font><font color="green"><f6></font>:<font color="green"></f6></font><font color="green"><f7></font><font color="red"><br /></font><font color="red"><br /></font><font color="red"><a href='%%LINK_A%%' class='yellow'></font><font color="green"></f7></font><font color="green"><f8></font>Ugly <font color="green"></f8></font><font color="green"><f9></font>ugly:<font color="green"></f9></font><font color="green"><f10></font><font color="red"></a></font><font color="green"></f10></font><font color="green"><f11></font> <font color="green"></f11></font><font color="green"><f12></font><font color="green"><s13/></font>Ugly ugly ugly ugly<font color="green"></f12></font><font color="green"><f14></font>.<font color="green"></f14></font><font color="green"><f15></font><font color="red"><br /></font><font color="red"><a href='%%LINK_B%%' </font><font color="green"></f15></font><font color="green"><f16></font><font color="red">class='yellow'></font><font color="green"></f16></font><font color="green"><f17></font>Ugly ugly:<font color="green"></f17></font><font color="green"><f18></font><font color="red"></a></font> <font color="green"></f18></font><font color="green"><f19></font><font color="green"><s20/></font>Ugly ugly ugly ugly ugly<font color="green"></f19></font><font color="green"><f21></font>.<font color="green"></f21></font><font color="green"><f22></font><font color="red"><br /></font><font color="red"><a </font><font color="green"></f22></font><font color="green"><f23></font><font color="red">href='%%LINK_C%%' class='yellow'></font><font color="green"></f23></font><font color="green"><f24></font>Ugly ugly:<font color="green"></f24></font><font color="green"><f25></font><font color="red"></a></font> <font color="green"></f25></font><font color="green"><f26></font>Ugly <font color="green"></f26></font><font color="green"><f27></font><font color="green"><s28/></font>ugly ugly <font color="green"></f27></font><font color="green"><f29></font>ugly ugly<font color="green"></f29></font><font color="green"><f30></font>.<p>Second segment:<p><font color="green"></f30></font><font color="green"><f31></font><font color="red"><br /></font><font color="red"><a href='%%LINK_D%%' class='yellow'></font><font color="green"></f31></font><font color="green"><f32></font>Ugly <font color="green"></f32></font><font color="green"><f33></font>ugly<font color="green"></f33></font><font color="green"><f34></font>:<font color="green"></f34></font><font color="green"><f35></font><font color="red"></a></font> <font color="green"></f35></font><font color="green"><f36></font>U<font color="green"></f36></font><font color="green"><f37></font>gly ugly ugly ugly ugly<font color="green"></f37></font><font color="green"><f38></font>.<font color="green"></f38></font><p>You see ?<p>All the original HTML is here, and all the original formatting is applied to each cell part separately... <p>This is obviously not the solution. For one thing, the inherited formatting (all the green tags) is totally irrelevant as far as the translation is concerned. Then, the HTML tags should rather be handled as HTML and not as plain text, to be able to see the translatable text better, but also to reduce the modification risks when you translate the segment.<p>Now, if you follow my earlier advice, the above segment would look like this in OmegaT (with <font color="blue">blue</font> color for emphasis), after being handled as a "normal" HTML file:<p>First segment:<p>This is ugly<font color="blue"><br0/></font>ugly ugly ugly<p>(notice that the tags <span style="color:red;"><h1></span> and <span style="color:red;"></h1></span> are not shown since they are block level tags and the whole block is the segment! You just reduced the total number of tags in the segment!)<p>Second segment:<p>Ugly ugly ugly ugly ugly ugly:<font color="blue"><br0/></font><font color="blue"><br1/></font><font color="blue"><a2></font>Ugly ugly:<font color="blue"></a2></font> Ugly ugly ugly ugly.<font color="blue"><br3/></font><font color="blue"><a4></font>Ugly ugly:<font color="blue"></a4></font> Ugly ugly ugly ugly ugly.<font color="blue"><br5/></font><font color="blue"><a6></font>Ugly ugly:<font color="blue"></a6></font> Ugly ugly ugly ugly ugly.<p>Third segment:<p><font color="blue"><br7/></font><font color="blue"><a8></font>Ugly ugly:<font color="blue"></a8></font> Ugly ugly ugly ugly ugly.!<p>Much better isn't it ? Now, how much time and energy do you think this trick will save you next time you have such a (not so uncommon) file to translate ?<p>ps: I did try to do all the heavy editing in Emacs, but I fear I am not yet familiar enough with its regex syntax. I eventually had to revert to TextWrangler, but I am not giving up...<p>ps2: If you know a CAT tool that does not require any manipulation to reach a manageable tag number, let me know !<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-2507693529925897366?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-22640548548654649092009-07-29T15:42:00.000+09:002009-07-29T15:42:49.115+09:00OmegaT small (?) updateOmegaT 2.0.3 update 2 has been released.<br /><br />From the release file:<br /><br />================================================<br />OmegaT beta version 2.0.3 update 2 has been released. For the first time, OmegaT is available as a Java Web Start application (<a href="http://en.wikipedia.org/wiki/Java_Web_Start">http://en.wikipedia.org/wiki/Java_Web_Start</a>).<br /><br />Launching OmegaT from <a href="http://omegat.sourceforge.net/webstart.html">http://omegat.sourceforge.net/webstart.html</a> requires no installation, and future updates of this version will happen automatically.<br /><br />Two bugs have been corrected. One concerns segment detection in the Editor, and the other StarDict dictionaries.<br /><br />Belarusian, Dutch and Catalan localisations have been updated.The OmegaT Project always welcomes developers, localizers and users to contribute their experience, knowledge and insights to the software we release.<br />================================================<br /><br />Regarding Webstart and privacy (quoting Tony):<br /><br />OmegaT Java Webstart does NOT save any of your information to our web servers. The application runs on YOUR machine. Your documents and translation memories remain on your computer, and the OmegaT project will have no access to your work or information.<br /><br />(end quote)<br /><br />The fact that OmegaT is now available directly from the network without any specific install procedure does not mean that OmegaT better supports network interaction between translators (data sharing etc). It only means that it is easier to distribute/use/update.<br /><br />There are still issues to iron out though: how to use the Lucene tokenizer with that WebStart version... We're investigating this right now... :)<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-2264054854865464909?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com2tag:blogger.com,1999:blog-6335460019316576281.post-67505463230666781382009-07-29T15:18:00.003+09:002009-07-29T17:06:07.876+09:00Excel files with colored non translatables...Here comes an excel file, with pseudo HTML in the cells.<br /><br /><p>The HTML tags are <font color="red">red</font> and must not be modified. If you want how the segments look check the <a href="http://mac4translators.blogspot.com/2009/07/excel-files-with-colored-non_29.html">follow up post</a>.<br /><br /><p>Translating that in OmegaT is relatively straightforward:<br /><br /><ul><li>save the file as ODS in Openffice.org (or NeoOffice)<br /><li>put that source file in the /source/ folder of your OmegaT project<br /><li>load the project and translate<br /></ul><br /><br /><p>The problem is that not only you are going to have all the HTML tags displayed for what they are within the translatable text, but you're going to have to deal with the <font color="red">red</font> color tags that will surround all the HTML...<br /><br /><p>Not user friendly at all...<br /><br /><p>Another solution is to do like this:<br /><br /><ul><li>copy-paste the column into a text file -> no more <font color="red">red</font> color, will deal with that later<br /><li>insert a visible marker like @@@ at each end of line<br /><li>save the file as .html -> no more full HTML tags in the segments<br /><li>put in /source/<br /><li>go to Options > Segmentation and add 2 rules. One where you segment before @@@ and one where you segment after @@@, that way you'll nicely isolate the marker and it will be translated only once<br /><li>load, translate<br /></ul><br /><br /><p>The resulting file should contain all the original tags, without modifications, but some characters in the original may have been converted to HTML references. Replace those with the original character if you think it is better.<br /><br /><p>Now, open your file in a text editor, remove the @@@ markers and paste the contents into a Write page in OpenOffice.<br /><br /><p>There, do a "Regular Expression" search for the string: (<[^>]*>)<br /><br /><p>The string means: a "<" followed by a number of anything but ">" followed by a ">": (basically any HTML tag). The surrounding parenthesis put the matching string into a memory for later retrieval!<br /><br /><p>and replace by "&" with the style "font color=red". "&" means "the group that was just put into memory".<br /><br /><p>All your HTML tags should be colored in <font color="red">red</font> now.<br /><br /><p>Copy-paste the contents into the original file where it needs to be, and deliver !!! Also make sure that one line corresponds to one cell (manipulating the @@@ marker should not change the overall structure but one never knows!)<br /><br /><p>(There are probably easier ways to deal with such files. Let me know!)<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-6750546323066678138?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-78253695224352652452009-07-21T22:50:00.001+09:002009-07-21T22:50:24.073+09:00Yes ! Okapi snapshots available !From Yves Savourel @ Okapi Framework:<br /><br /><quote><br />If you are interested in testing the latest build of the Java-based Okapi tools and libraries you can download them from here:<br /><a href="http://okapi.opentag.com/snapshots/">http://okapi.opentag.com/snapshots/</a><br /><br />Those are the latest development builds (more recent than the normal releases), they have all the latest features, BUT they are not tested and may be unstable. They are the versions the developers are using. Use them at you own risks.<br /><br />The times listed in the directory is date/time when the files was generated (in US Pacific Time). We will update those snapshots relatively frequently.<br /></quote><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-7825369522435265245?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-5831175405509314212009-07-09T15:09:00.000+09:002009-07-09T15:09:10.511+09:00OmegaT small updateOmegaT 2.0.3_1 was just released, it comes now with a complete Japanese/German/Slovenian UI/tutorial.<br /><br /><a href="https://sourceforge.net/projects/omegat/files/">https://sourceforge.net/projects/omegat/files/</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-583117540550931421?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com2tag:blogger.com,1999:blog-6335460019316576281.post-24394353548110236872009-07-07T10:39:00.001+09:002009-07-07T10:41:33.454+09:00Okapi webinarA message from Okapi's Yves Savourel:<br /><br /><quote><br />Just a note to let you know that I'll be giving a little introduction on using the Okapi Tools. Note that it will be focused on the new Java-based tools.<br /><br />ENLASO is hosting this free webinar on July 16th at noon Mountain Time.<br />It's free and you can register here:<br /><a href="https://enlasoevents.webex.com/enlasoevents/onstage/g.php?t=a&d=662713198">https://enlasoevents.webex.com/enlasoevents/onstage/g.php?t=a&d=662713198</a><br /></quote><br /><br />The latest version of the Java Okapi tools is here:<br /><a href="http://okapi.opentag.com/">http://okapi.opentag.com/</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-2439435354811023687?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com2tag:blogger.com,1999:blog-6335460019316576281.post-91458993175575938532009-07-02T19:03:00.002+09:002009-07-08T06:31:07.166+09:00Bored Trados users ?For bored Trados users who want to work in a free software environment, here are the latest news:<br /><br />1) OmegaT is able to translate TTX files that have source=target (output option if I am not mistaken), that requires a small utility called Toxic, to be found here:<br /><a href="http://www.omegat.org/resources/toxic.zip">http://www.omegat.org/resources/toxic.zip</a><br /><br />2) It is possible to deliver "cleaned/uncleaned" file sets by translating the file in OmegaT and processing the resulting TMX in OpenOffice.org with the Anaphraseus macro (a Wordfast equivalent for OOo). The discussion about the process is here:<br /><a href="http://tech.groups.yahoo.com/group/OmegaT/message/14705">http://tech.groups.yahoo.com/group/OmegaT/message/14705</a><br /><br />And Anaphraseus is here:<br /><a href="http://sourceforge.net/projects/anaphraseus/">http://sourceforge.net/projects/anaphraseus/</a><br /><br />(updated 7/8)<br /><br />3) Ask your Trados clients to send you TMX memories instead of Trados memories, you'll be able to use them in OmegaT without problems. Trados seems to have problems creating conforming TMX files. If OmegaT complains, use TMXValidator from Maxprograms.<br /><br />TMXValidator is here: <a href="http://www.maxprograms.com/products/tmxvalidator.html">http://www.maxprograms.com/products/tmxvalidator.html</a><br /><br />4) Some file formats are not directly supported by OmegaT. Use Rainbow to create OmegaT projects from unsupported files. Not all files supported by Trados are supported by Rainbow but Rainbow still covers a very reasonable range of "exotic" formats.<br /><br />OmegaT directly supports the following formats:<br /><br /> <ul> <li>OpenDocument/OpenOffice.org<br /> <li>Microsoft Open XML<br /> <li>DocBook XML<br /> <li>HTML, XHTML<br /> <li>TeX<br /> <li>Plain text<br /> <li>SRT subtitles<br /> <li>PO (monolingual)<br /> <li>XLIFF (Okapi generated)<br /> <li>ResX ressources<br /> <li>INI ('key=value' format)<br /> <li>Java bundle.properties<br /> <li>HTML Help Compiler<br /> <li>QuarkXPress CopyFlow Gold<br /> </ul>Rainbow has filter for the following formats: <a href="http://okapi.opentag.com/help/filters/ui/index.html">Okapi Framework - Filters</a>.Rainbow is here: <a href="http://okapi.opentag.com/downloads.html">http://okapi.opentag.com/downloads.html</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-9145899317557593853?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com2tag:blogger.com,1999:blog-6335460019316576281.post-42842799467409062022009-07-02T17:34:00.000+09:002009-07-02T17:34:34.917+09:00自由に翻訳！That is the title of an article I wrote in Japanese about OmegaT.<br /><br />The article was published in the 45th issue of the AAMT Journal. I've put a copy of the article online, here: <a href="http://doublet.jp/omegat/jiyunihonyaku_OmegaT.html">自由に翻訳！</a><br /><br />The article is not an introduction to using OmegaT, if you want the introduction, download OmegaT and start it. You'll have a tutorial in the language of your OS.<br /><br />Download link: <a href="https://sourceforge.net/projects/omegat/files/Other%20-%20Development/OmegaT_2.0.3_Beta.dmg">OmegaT_2.0.3_Beta.dmg</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-4284279946740906202?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-13415311662883802492009-07-02T17:30:00.000+09:002009-07-02T17:30:31.716+09:00OmegaT in Kyoto on July 11thI'll be making a presentation about OmegaT at the "Open Source Conference 2009 Kansai" on the 11th of July, from 11.15 to 12.00.<br /><br /><a href="http://www.ospn.jp/osc2009-kansai/modules/eventrsv/?id=2&noform=1">http://www.ospn.jp/osc2009-kansai/</a><br /><br />People who can't make it for the seminar are welcome to the OmegaT "booth" where I'll be from Friday morning.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-1341531166288380249?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-43520938989582847802009-03-30T00:38:00.003+09:002009-03-30T00:47:20.649+09:00Bash (command line) shortcutsUntil today, I only used the following shortcuts on the command line:<br /><br /><code>ctrl+a</code> → go to beginning of line<br /><code>ctrl+e</code> → go to end of line<br /><code>ctrl+k</code> → delete to end of line<br /><br />And even though I was very frustrated by the fact that I had to use <br />the mouse to select/copy/paste etc, it never really occured to me to <br />google for "bash command line shortcuts"...<br /><br />To make it short: bash uses the readline library.<br /><br />The user documentation for readline is at:<br /><a href="http://cnswww.cns.cwru.edu/php/chet/readline/rluserman.html">http://cnswww.cns.cwru.edu/php/chet/readline/rluserman.html</a><br /><br />All the shortcuts that exist on your machine can be found by using the <br />'<code>bind</code>' command:<br /><code>$ bind -P | more</code><br />You'll have more shortcuts with:<br /><code>$ bind -p | more</code><br />If you want to know how to use 'bind' to add shortcuts, check its help <br />file:<br /><code>$ help bind</code><br /><br />Select/cut/paste require to first bind a shortcut to "kill-region":<br />$ bind "\C-xx": kill-region<br />(<code>ctrl+x</code> followed by <code>x</code>)<br /><br />Now we need to select the string (create a "region").<br /><br />A region is automatically created between a "mark" and the cursor. So, we only need to put the mark at one end of the region and to move the cursor <br />to the other end.<br /><br />To create a mark use: <code>ctrl+@</code> or <code>ctrl+space</code>, <br />then move the cursor, then hit <code>ctrl+xx</code> to "kill" the <br />region.<br /><br />Pasting requires <code>ctrl+y</code>.<br /><br />But, the <code>ctrl-y</code> (Yank/paste) command works only within <br />the application from where the string was "killed". The "kill-ring" is <br />not shared by other applications (even though they may accept <br /><code>ctrl-y</code> as a Yank command).<br /><br />So, if you want to get a string from terminal and paste it outside <br />(like select a command and paste it into a mail for ex), here is <br />something that may not be the most efficient way to go, but it works:<br /><br /><code>echo string | pbcopy</code><br />or<br /><code>echo "complex string" | pbcopy</code><br /><br />For ex, to put the above line in the pastebpard, I'd do:<br /><code>echo "echo \"complex string\" | pbcopy" | pbcopy</code><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-4352093898958284780?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com2tag:blogger.com,1999:blog-6335460019316576281.post-63401262491799415632009-01-18T15:42:00.000+09:002009-01-18T15:57:23.614+09:00Static electricity and your fan...My fan started to blow like crazy yesterday. But it was not really blowing in fact. It was just making a lot of noise. A little bit like when those little model planes take off... Since my MacBook is not equipped for flying I understood something was very wrong. I was doing CPU intensive things when all this started... Like (re)install the trial version of iWork' 09 and simultaneously move 3 gb of data to my external disk...<br /><br />I did not sleep well last night. The prospect of having to complete 3 translations on my backup machine (an old Titanium) while the MacBook was sent to repairs -for the 4th time- was not making me very cheerful.<br /><br />I called Apple support this morning and they told me this fan problem could be triggered by static electricity.<br /><br />The procedure to solve that is as follows:<br /><br /><ol><li>turn the machine off<br /><li>unplug it<br /><li>remove the battery<br /><li>press the start button for more than 10 seconds<br /><li>plug the machine and put the battery back<br /><li>press <bold>Command+Option+P+R</bold> simultaneously right after pressing the start button<br /></ol><br />The machine is supposed to emit 2 long beeps after booting and then starts normally.<br /><br />I did not have 2 beeps, instead of that the MacBook entered a just as scary cycle of reboots. So I eventually stopped pressing the keys, and the machine decided to stop pedaling with my nerves and properly boot.<br /><br />Now, the fan seems to behave properly. I'll hopefully be able to complete the jobs without having to send the machine to repairs... Only 5 months left on my AppleCare !!!<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-6340126249179941563?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com1tag:blogger.com,1999:blog-6335460019316576281.post-80113392226282840662009-01-08T20:26:00.006+09:002009-01-08T20:59:31.795+09:00iWork 09, no backward compatibility...I just downloaded the <b>iWork '09</b> trial package. Reports on the net mention its enhanced Applescript support, its new looks and new functions.<br /><br /><b>Pages '09</b> opens <b>Pages '08</b> files without difficulties and can save into that format (see the new <code>Share</code> menu), but the new format cannot be opened in <b>Pages '08</b>.<br /><br />A <b>Pages '08</b> was basically a folder with a .pages extention. You could go to Terminal and do a:<br /><code><br />$ cd file_name.app<br /></code><br /><br />to find the following list of files:<br /><code><br />$ ls<br />Contents QuickLook index.xml.gz<br /></code><br /><br />where both <code>Contents</code> and <code>Quicklook</code> were folders with files in them, while the file itself was a gz-compressed XML file (<code>index.xml.gz</code>)<br /><br /><br />Now, the same file created by <b>Pages '09</b> would have a totally different structure.<br /><br />Where file_name.pages was a folder containing compressed data in <b>Pages '08</b>, the file is a compressed folder containing normal files.<br /><br />To see what it looks like, change the <code>.pages</code> extension to <code>.gz</code> and double-click that file. The result is a folder with the following files:<br /><br /><code><br />$ ls<br />QuickLook buildVersionHistory.plist index.xml<br /></code><br /><br /><code>Quicklook</code> is still a folder with a PDF (Quicklook) and a JPEG (thumbnail) preview of the file but the old <code>Contents</code> folder is not there and the index.xml contains XML code that significantly differs from the one in Pages 08.<br /><br /><br /><b>Keynote '09 </b> and <b>Numbers '09</b> show a similar internal structure for their files.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-8011339222628284066?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com2tag:blogger.com,1999:blog-6335460019316576281.post-21023501407374883812008-12-10T11:59:00.001+09:002009-01-20T10:37:45.843+09:00Copy - Paste (not Cut) filesAfter last week's post I tried using the Finder's <span class="Apple-style-span" style="font-weight: bold;">copy</span> & <span class="Apple-style-span" style="font-weight: bold;">paste</span> functions to move files around.<br /><br />One thing the struck me is that there is not <span class="Apple-style-span" style="font-weight: bold;">cut</span> function. Well, there is the <span class="Apple-style-span" style="font-weight: bold;">delete</span> function but you can't copy files and simultaneously delete them from their location.<br /><br />I discovered the reason this morning...<br /><br />When you <span class="Apple-style-span" style="font-weight: bold;">copy</span> a file in Finder, OSX does not seem to burden itself to load all the data in memory. It only seems to register the file location.<br /><br />So, if you <span class="Apple-style-span" style="font-weight: bold;">copy</span> the files, <span class="Apple-style-span" style="font-weight: bold;">delete</span> them now because you could as well do it now instead of having to come back here later, and then try to <span class="Apple-style-span" style="font-weight: bold;">paste</span> them somewhere, OSX will complain that the files are missing. Indeed, there are in the Trash...<br /><br />The correct order is thus to <span class="Apple-style-span" style="font-weight: bold;">copy</span> the files, <span class="Apple-style-span" style="font-weight: bold;">paste</span> them in their new location, go back to the original location and <span class="Apple-style-span" style="font-weight: bold;">delete</span> them...<br /><br />It would seem to me that the smarter way to implement that would be to not remember their actual path, but to put a flag on the files, similar to an alias, so as to track the files if they move or are removed, before being pasted to their new location...<br /><br /><b>Update</b><br /><br />I just found this hint on MaoOSX Hints: <a href="http://www.macosxhints.com/article.php?story=20081112153330648">Use Quicksilver for Finder cut and paste </a>.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-2102350140737488381?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com5tag:blogger.com,1999:blog-6335460019316576281.post-8015379079448831322008-12-04T19:26:00.003+09:002008-12-05T14:57:27.775+09:00Copy files to...I may have missed something but I have yet to find an easy way to copy a set of files to an arbitrary place on my disk.<br /><br />I think Windows people have this. They right-click on a file and they have a "send to" item so that they can copy the file(s) to any place they want.<br /><br />I've been playing with Automator recently so I just spent an hour or so to create a "Copy Files To..." Automator application that I also saved as a Finder plug-in.<br /><br />I've put the application into the File section of the Google group "attached" to this blog. I think you can open it in Automator (I created it on OSX 10.5.5) and use "File > Save As Plugin" to install it as a Finder contextual menu (in which case it will be saved under ~/Library/Workflows/Applications).<br /><br />The application works like this:<br /><br />1) You select items in the Finder<br />2) You call the application, either with Spotlight or with the context menu (bottom item: "More" > "Automator" > "Copy Files To...")<br />3) You select/create the destination (a folder)<br />4) The selected files are copied - and are not allowed to overwrite existing files<br />5) The destination folder opens<br /><br /><br />It looks like Automator applications are relatively slow to launch so for a small application like that I am not sure this is the best technology...<br /><br />I am reading a tutorial book to Applescript (Applescript Studioでゼンマイびゅんびゅん！！) and I'm sure I'll be able to write an equivalent thing directly in Applescript in a few days, if work allows for that...<br /><br /><b>Update</b><br /><br />Thank you for the replies on the Google Group and comments here where <a href="http://free.abracode.com/cmworkshop/on_my_command.html">OnMyCommand</a>, but also Applescript solutions and also, simply, Cmd+C/Cmd+V inside Finder were suggested.<br /><br />Automator applications, by the way they seem to be implemented, seem to be most useful when they are used a number of times in a row. WHen they are used once in a while, it seems that the time they load into memory (?) kinds of defeat the purpose of creating a simple action.<br /><br />I still have a hard time figuring out what Automator can be best used for, since obviously, most file management tricks will be executed much faster from the Terminal...<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-801537907944883132?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com5tag:blogger.com,1999:blog-6335460019316576281.post-54198771263739249332008-09-17T23:10:00.004+09:002009-01-08T20:19:40.478+09:00Backing up your data...After yesterday's "rsync update" post, I decided to do some serious reading on the subject and here are the interesting pages that I found.<br /><br />First of all, even before considering the method you'll choose, what matters is the reliability of the backed up data. In other words, how much of your data and its meta-data is saved in the process.<br /><br />I found a terrific post on the subject on the <a href="http://blog.plasticsfuture.org/">http://blog.plasticsfuture.org/</a> blog. The author tries pretty much all the existing free solutions at the time of his writing (10.4.6) and checks how the data is handled by the various tools. The result is <a href="http://blog.plasticsfuture.org/2006/03/05/the-state-of-backup-and-cloning-tools-under-mac-os-x/">"The State of Backup and Cloning Tools under Mac OS X"</a>. It is quite technical, you've been warned. The results are appalling. When seen from his perspective.<br /><br />This post and its follow-up, <a href="http://blog.plasticsfuture.org/2006/04/23/mac-backup-software-harmful/">"Mac Backup Software Harmful"</a> seem to have caused quite a stir in the OSX back up software world and it seems a number of the tools discussed have been fixed to a degree. For a more relaxing but still related read, check <a href="http://blog.plasticsfuture.org/2006/06/27/mac-os-file-creation-dates/">File Creation Dates on Mac OS X: Clash of the Cultures</a> from the same author about the conservation of the file creation date data. The post is very interesting because it shows two totally different approaches to what a "creation date" is supposed to mean depending on different ideas of what a file is.<br /><br />In reaction to the two original plasticsfuture posts comes <a href="http://www.n8gray.org/blog/2007/04/27/introducing-backup-bouncer/">"Introducing Backup Bouncer"</a>, where the author introduces a test suite to easily compare the original data to the back up.<br /><br />When you've read all this you should know quite a bit more about the issues at hand.<br /><br />For a totally different approach, but still in reaction to the plasticsfuture articles, <a href="http://inik.net/">inik.net</a> has a more pragmatic article: <a href="http://inik.net/node/148">"Ensuring trouble-free backups from your Mac to not-a-Mac"</a> followed by <a href="http://inik.net/node/151">"File copying/synchronization software and your metadata (and data!)"</a>.<br /><br />By the way, before you reach this point, you may want to know what you are actually backing up... What is a file in the OSX world and its underlying Unixy universe ? For that you may want to check Google Books and their limited preview of "<a href="http://books.google.com/books?id=o9K8KEQic5sC&printsec=frontcover&dq=A+practical+guide+to+Unix+for+Mac+OS+X+users&output=html&sig=ACfU3U1eSvs41r-JTes99PFIkxOVHkpjig">A practical guide to Unix for Mac OS X users, by Mark G. Sobell, Peter Seebach</a>. Check the Table of Contents, "The Mac OSX File System" and browse down to page 99 (if you have a better reference available on the net, leave a comment).<br /><br />Now, here are two pages that give a good summary of the situation, in terms that most of us will understand. The first is <a href="http://draft.blogger.com/post-edit.g?blogID=6335460019316576281&postID=5419877126373924933">Take Control of Mac OS X Backups: The Online Appendixes</a> from TidBits, and the second is <a href="http://www.dataexpedition.com/~sbnoble/Tips/backups.html">Mac OS X Backups</a> (can't get much simpler than that...) from "Seth's Unix Tips". You may want to read <a href="http://www.dataexpedition.com/~sbnoble/Tips/filesystems.html">his take on Unix files</a> too.<br /><br />The conclusion of all this is that, depending on your needs you'll have to make a choice. Don't forget that Leopard comes with Time Machine, which creates hourly incremental backups of the data you specify. So, if you need something different then here is my short list:<br /><br /><h3>GUI application</h3><a href="http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html">SuperDuper</a>, to "backup and clone your drives". The application is not free software but comes with a limited version that won't cost you anything.<br /><br /><h3>rsync based command line applications</h3><a href="http://www.bombich.com/mactips/rsync.html">Configuring Mac OS X for Unattended Backup Using rsync</a><br /><a href="http://www.mikerubel.org/computers/rsync_snapshots/">Easy Automated Snapshot-Style Backups with Linux and Rsync</a><br /><a href="http://www.rsnapshot.org/">rsnapshot</a> (based on the previous link)<br /><a href="http://connect.homeunix.com/lbackup/doku.php?id=about">LBackup</a> (similar to rsnapshot), check the "Alternatives to LBackup" section for more links, as well as its <a href="http://connect.homeunix.com/lbackup/doku.php?id=rsync_tips">rsync tips</a> page.<br /><a href="http://www.nongnu.org/rdiff-backup/"> rdiff-backup </a><br /><br /><h3>Others</h3><a href="http://alan.petitepomme.net/unison/index.html">Unisson</a><br /><br /><h2>Is that all there is to backing up one's data ?</h2><br />There must be a number of rules available from somewhere on the web regarding data backup...<br /><br />The few I have in mind are:<br /><br /><ul><li>Back up regularly. Time Machine does that every hour and that is a good thing. If you don't have an automated solution, do that manually every single day. But you do have an automated solution on you Mac. It is a command line utility that is called <a href="http://www.macosxhints.com/article.php?story=2001020700163714">cron</a>, and if the command line is really too much for you, check cron's GUI wrapper "<a href="http://www.abstracture.de/projects-en/cronnix">Cronnix</a>, you'll still need to understand a few things but you won't have to play with Terminal.app.<br /><br /></li><li>Check the integrity of your data regularly (like once a week), by simply taking a look at it, opening a few files at random see if they correspond to what you expect them to be etc...<br /><br /></li><li>Test the recovery process once in a while. Backed up data is useless if it can't be recovered. This test is to make sure you remember the method and to ensure that the restored data is in a useable state.<br /><br /></li><li>Do your back up on an external media, pretty obvious, a possibly a media that is physically removed from you data source (the computer). Most modern external HDs can be linked to your machine with relatively long cables. You can also use wireless connections to access that disk etc.<br /><br /></li><li>If you have extra cash, get a backup computer to make sure that you can use the restored data while your main computer is being fixed. Because it is very likely that a major computer failure will be the main reason why you'll need to restore your data. Now what if you have data to restore but no computer to restore it to ?</li></ul>I think that is pretty much everything I have to say on the subject for today. You may want to take a look at <a href="http://mac4translators.blogspot.com/search/label/Time%20Machine">this</a> old post where I discuss what happens when Time Machine saves your application folders and Spotlight indexes all that...<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-5419877126373924933?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com2tag:blogger.com,1999:blog-6335460019316576281.post-53941686906618966222008-09-16T18:24:00.002+09:002009-01-08T20:23:21.978+09:00Software updates !<h2>Free software</h2><br /><h3>NeoOffice has turned 2.2.5</h3><br />NeoOffice is a free software replacement for Microsoft Office and other similar office suites. It is based on OpenOffice.org.<br /><a href="http://www.neooffice.org/neojava/en/index.php">http://www.neooffice.org/neojava/en/index.php</a><br /><h3>VirtualBox has turned 2.0.2</h3><br />VirtualBox is a free software replacement for Parallels and VMWare and other similar virtualization software.<br /><a href="http://virtualbox.org/">http://virtualbox.org/</a><br /><h3>rsync has turned 3.0.4</h3><br />rsync is a command line utility to backup your files on a remote system. It does smart incremental backups so that you don't have to copy huge file sets when only a few files have been modified. rsync finds the modified parts and will add only the modified part to the original backup.<br />rsync 2.6.9 is installed by default on OSX 10.5.<br /><a href="http://samba.anu.edu.au/rsync/">http://samba.anu.edu.au/rsync/</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-5394168690661896622?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-45559920537857520952008-08-05T16:14:00.006+09:002008-08-05T17:45:48.264+09:00Accented letters and other symbols on the MacThis is a complement to Corinne McKay's latest blog post "<a href="http://thoughtsontranslation.com/2008/08/05/inserting-accented-characters-in-openofficeorg/">Inserting accented characters in OpenOffice.org</a>". Since Corinne focuses on Linux users I thought I'd rather add Mac specific information here.<br /><hr><br />Mac OSX comes with system wide shortcuts that work in any version of the OS. And if I remember well, the shortcuts were here well before OSX.<br /><br />It is possible to use them in <b>any</b> text editing location (a web browser field, your email, your favorite office suite, even the terminal).<br /><br />To check how to enter a character that is suspiciously missing from your keyboard, you need to display the <b>Keyboard Viewer</b> utility, a small window that will show you where is the key that will input that character on the keyboard you are using (if you have a laptop with an external keyboard like me, the viewer will adapt its display to correspond to the keyboard you are actually typing with, as you type).<br /><br />If you are used to run a strictly monolingual system (surprising for a translator), you may need to go to <b>System Preferences -> International -> Input Menu</b> and to check the little <b>Show input menu in the menu bar</b> box at the bottom of the window. Also, make sure that the <b>Keyboard Viewer</b> box is checked in the above list of displayable items.<br /><br />Once that is done, you should have a menu bar item that displays a flag that should correspond to your default keyboard setting.<br /><br />Ok. So, where are the shortcuts now ?<br /><br />For your information, I use the US standard keyboard, other keyboard layouts will allow for other shortcuts (see Paul's comment on the US Extended keyboard's available characters).<br /><br />Go to the flag menu, select <b>Show Keyboard Viewer</b> and you'll see a copy of the keyboard you are typing with displayed on your main screen.<br /><br />Now, type a few lines with your keyboard and you'll see the viewer react to each key you've used: it will display each key as depressed as you type it.<br /><br />Now, hold the <b>command</b> key and check the viewer: you'll see the viewer's command key(s) depressed but nothing more.<br /><br />Do that with the <b>alt/option</b> key. What you see should be a little more interesting. You should have a few keys that totally change of appearance. On my keyboard, <b>q</b> turns into <b>œ</b>, for example.<br /><br />Which means that if you want to type <b>œ</b> in your text, just use <b>alt+q</b>. <b>Œ</b> would then be <b>shift+alt+q</b>.<br /><br />That is for direct input. What about accents ?<br /><br />If you press <b>alt</b> you will probably see a few key that turn orange. Like <b>alt+e</b>. They turn orange and display an accent. <b>alt+e</b> displays the acute accent.<br /><br />If you type <b>alt+e</b>, OSX will insert an acute accent at the location of the cursor but the accent will be displayed with a brownish background: OSX is waiting for you to type the letter that will go under the accent. If you type <b>e</b> then you'll have a nice <b>é</b> at the location of the cursor.<br /><br />On my keyboard, the possible combinations are:<br /><br /><b>alt+_=`<br />alt+n=˜<br />alt+i=ˆ<br />alt+u=¨<br />alt+e=´</b><br /><br />You can also have direct input for pretty much all the characters in use in European languages thanks to this system. If you need more, just go back to International -> Input Menu, add the language you need (there is a huge lot of languages available directly on the Mac) and select it from the flag menu when you want to use it.<br /><br />With the US standard keyboard, I use <b>shift+alt+2</b> a lot for <b>€</b>, <b>alt+c</b> (and <b>shift+alt+c</b>) for <b>ç</b> (and <b>Ç</b>) as well as a few others.<br /><br />If you need something very exotic and you don't want to change of input system/keyboard layout (the flag menu thing), you can also access the <b>Character Palette</b> (don't forget to check its box in <b>Input Menu</b> above).<br /><br />Here, the system provides you with a way to access all the characters available from all the fonts present on your system. Select an appropriate drop down menu from the top left, then a category from the section below, browse the space on the right side of the window. You can search a character by name in the search field at the bottom right. Enter <b>note</b> and look at the possibility offered by your fonts.<br /><br />The <b>action</b> drop down menu at the bottom left allows you to search for the character that is selected in the front application.<br /><br /><br />Of course, the whole input system is available system-wide and works in pretty much all the applications that run on OSX.<br /><br />Caveat: applications that depend on the X11 windowing environment may not respect the OSX conventions and will sometimes not accept such input.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-4555992053785752095?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com5tag:blogger.com,1999:blog-6335460019316576281.post-40662913614925219562008-08-05T14:56:00.001+09:002008-08-05T14:57:36.151+09:00OOXML on the Mac (update)I have edited and updated the "Office 2007 files on Mac" post to reflect the release of the recent Office 2004 update and the beta version of StarOffice: <br /><br /><a href="http://mac4translators.blogspot.com/2007/11/office-2007-files-doc-xlsx-pptx-on-mac.html">Office 2007 files (.docx, .xlsx, .pptx) on Mac</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-4066291361492521956?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-80121022237512790332008-08-05T14:05:00.007+09:002008-08-05T14:15:41.960+09:00StarOffice 9 beta for MacIt looks like Sun Microsystems is making good use of the work of all the volunteers who made OpenOffice.org run on OSX without X11 (i.e. in OSX speak: like a normal OSX application...)<br /><br />The beta version is available, with the StarOffice logo instead of the OpenOffice.org one.<br /><br />I have downloaded the beast but if everything is business as usual, we should not see much differences between the 2 suites, except for a few proprietary things added to the StarOffice version.<br /><br />StarOffice:<br /><a href="http://www.sun.com/software/staroffice/get_beta.jsp">http://www.sun.com/software/staroffice/get_beta.jsp</a> (185 mb)<br />What's new:<br /><a href="http://www.sun.com/software/staroffice/docs/StarOffice9_WhatsNew.pdf">http://www.sun.com/software/staroffice/docs/StarOffice9_WhatsNew.pdf</a><br /><br /><br />OpenOffice.org:<br /><a href="http://download.openoffice.org/3.0beta/">http://download.openoffice.org/3.0beta/</a> (157 mb)<br />What's new:<br /><a href="http://marketing.openoffice.org/3.0/featurelistbeta.html">http://marketing.openoffice.org/3.0/featurelistbeta.html</a><br /><br />Also, NeoOffice is still running behind in term of code base but has recently released a patch for its 2.2.4 version:<br /><a href="http://www.neooffice.org/neojava/en/patch.php">http://www.neooffice.org/neojava/en/patch.php</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-8012102223751279033?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-51243342012066386262008-05-31T10:35:00.004+09:002008-05-31T10:40:07.255+09:00Spaces in 10.5.3You must be aware that Leopard's latest update, 10.5.3, has been released a few days ago. There are many comments and analysis on the web among which you can find how the bug fixes amount to new features implementation... One of the apps that greatly benefited from such bugfixes is Spaces.<br /><br />In terms of productivity, Space was one of the features from which power users expected a lot. But it was not fully useable until the 10.5.3 release as John Gruber of DaringFireball <a href="http://daringfireball.net/2008/05/spaces">writes</a>.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-5124334201206638626?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com6tag:blogger.com,1999:blog-6335460019316576281.post-17860241536967237822008-05-07T17:55:00.003+09:002008-05-07T18:08:50.463+09:00OpenOffice.org 3.0 Beta available !It is official, OpenOffice.org 3.0 Beta version is available for download.<br /><br />The feature list is <a href="http://marketing.openoffice.org/3.0/featurelistbeta.html">here</a> and you'll be glad to know that support for Microsoft 2007 file format (OOXML) is now a reality !<br /><br />Also, OpenOffice.org for Mac is now an Aqua application that does not require the X11 windowing environment. Those of you who don't know what that means are blessed !<br /><br />The stable version is planned for release in September. Although the free office suite is still not considered stable, it is stable enough for most of your non-mission critical work. I've been using test versions of 3.0 for a while now and I have been very pleased with it. I've noticed that it is significantly faster than NeoOffice at launch too.<br /><br />Feel free to download it from <a href="http://download.openoffice.org/3.0beta/">here</a>.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-1786024153696723782?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com2tag:blogger.com,1999:blog-6335460019316576281.post-37207666826780202752008-04-27T21:59:00.009+09:002008-04-28T18:45:01.883+09:00Text alignment on MacWhen you start a translation, it is important to prepare your reference materials so that you can use them in the most efficient way possible.<br /><br />Computer Aided Translation (CAT) tools have a special way to do that. They can use translation memories (TM) that contain source and target language information that will be matched against the source text to provide translation suggestions.<br /><br />Using translation memories has two major benefits. The first is that any text present in the memory and also in a similar form in the file to translate can see its TM translation be recycled in your work. The other benefit is that the translation memory, if properly used will increase the style consistency of your final work.<br /><br />Creating TMs is also called <i>aligning</i> bilingual texts. The end format will depend on your CAT flavor but the standard today is TMX (Translation Memory eXchange), an XML dialect maintained by LISA <a href="#links">☞</a>.<br /><hr><br />There are 3 ways to align text.<br /><ol><br /><li> by hand<br /><li> with a-free software<br /><li> with free software (including free of charge)<br /></ol><br />I used to do it by hand (copy the texts in 2 text editors windows with line numbers displayed, hack the contents so that strings on the same line number correspond, paste TMX code all over this).<br /><br />In a good text editor, you can do all the work with the keyboard using only shortcuts. The <i>paste TMX code all over this</i> part is a little tricky but some smart people have created simple scripts in Perl or Python to ease the pain <a href="#links">☞</a>.<br /><br />Then, I bought Heartsome's Translation Suite, a set of Java applications for translators. The set includes TMXEditor, a TMX file editor as its name says, and I did most of my alignment there for a while. I've always had mixed feelings about TMXEditor. There are display glitches, it does not seem easy to work only with the keyboard, it uses a lot of memory... TMXEditor does a few things very well (TMX merging and various checks), but on Mac, it is not the best tool for aligning texts <a href="#links">☞</a>.<br /><br />The best tool (for now) on Mac is a native application called Appletrans, previously known as Alair. Appletrans had been on my hard disk for so long that I had almost forgotten about it, always promising myself that I'd test it to write a blog entry about it.<br /><br />Appletrans is a text editor for translators. It is available free of charge directly from Apple, from their localization page, and besides for being a very nice aligner, it also is a full fledged CAT tool that a number of people have adopted as their tool of choice <a href="#links">☞</a>.<br /><br />The following is an introduction to text alignment in Appletrans. I'd like to thank Steven DeWitt for helping me when I was lost in the shortcuts and for confirming that what follows is not merely the product of my feverish imagination.<br /><br /><h2>Aligning text in Appletrans</h2><br /><ol type="I"><h3><li>Prepare the files</h3><br /><br />(This part is very well explained in the Appletrans manual. Don't hesitate to refer to it.)<br /><br /><ol><br /><li>Appletrans does not open .doc files.<br /> <dl><dt>→ save the files to align to the RTF format in TextEdit</dt><br /><dd>Appletrans can also open a number of other file formats by default and plugins are available to add even more file formats.</dd></dl><br /></li><br /><br /><li>Open the source file and the target file from the finder or in Appletrans.<br /> <dl><dt>→ in the Finder, right click, <code>Open With</code>, Appletrans should come in the list.</dt><br /><dd>The files should be displayed with most of their styling but without any images, if any were present in the original files. Also, the files names now come with an <code>.alair</code> extension in replacement for the <code>.rtf</code> extension (see the title bar).</dd></dl><br /></li><br /><br /><li>Segment the two files (repeat the procedure for both files)<br /> <dl><dt>→ Do not select any contents in the opened files<br /> → <code>Tool</code> menu, <code>Segment</code> submenu, <code>Segment</code></dt><br /><dd>A dialog shows, select the segmentation type you want in the drop down menu, press <code>segment all</code>, you'll see small orange markers at the beginning and end of each segment Appletrans has created for you.</dd></dl><br /></li><br /><br /><li>Let Appletrans know that the two files are to be synchronized, do that for the two files.<br /> <dl><dt>→ <code>Tool</code> menu, <code>Synchronize</code></dt><br /><dd>A dialog shows, enter the language of the file.</dd></dl><br /><br />The synchronization causes the display to change a little bit. Use <code>Cmd+1</code> (or <code>Cmd+2</code>) on the frontmost text and you'll see that the segments defined in that window are somehow <i>linked</i> to segments in the other window.<br /><br />By doing that, you can already see that some source segments are not associated to the correct target segment. The alignment process is about correcting such association mistakes.<br /></li><br /></ol><br /><h3><li>Correct the default segment associations</h3><br /><br />(This part is not as clear in the user manual and required a bit of guessing.)<br /><br />You have now 2 windows open:<br /><ol><br /><li>The segmented source file<br /><li>The segmented target file<br /></ol><br /><br />Here are the Appletrans specific shortcuts that you will need to modify the alignment:<br /><br /><dl><dt><code>Cmd+1</code> (<code>Tool</code> menu, <code>Segment</code> submenu)</dt><br /> <dd>→ selects the next segment and shows the associated segment in the other window</dd><br /><dt><code>Cmd+2</code> (<code>Tool</code> menu, <code>Segment</code> submenu)</dt><br /> <dd>→ selects the previous segment and shows the associated segment in the other window</dd><br />It is also possible to select any segment in the text by clicking on one of its orange segment marker.<br /><br /><dt><code>Opt+Cmd+R</code> (<code>Tool</code> menu, <code>Segment</code> submenu)</dt><br /> <dd>→ <code>Restore</code>, removes the segmentation for the selected segments, at least one full segment must be selected for the action to work</dd><br /><dt><code>Opt+Cmd+S</code> (<code>Tool</code> menu, <code>Segment</code> submenu)</dt><br /> <dd>→ <code>Segment Selection</code>, no need to go through the <code>Segment</code> dialog again !</dd><br /></dl><br /><br />Now, here are some practical standard shortcuts that will make your life easier.<br /><br /><dl><dt><code>Arrows</code></dt><br /> <dd>→ moves the cursor around the window</dd><br /><dt><code>Shift+arrows</code></dt><br /> <dd>→ selects while the cursor is moving</dd><br /><dt><code>Delete</code></dt><br /> <dd>→ deletes the selected part (segment or text)</dd><br /><dt><code>Cmd+X</code>, <code>Cmd+V</code></dt><br /> <dd>→ standard <i>cut</i>, <i>paste</i> that you can use to move segments or text around</dd><br /></dl><br /><br /><h4>Merge segments</h4><br /><ul><li>Select the segments to merge.<br /><li>Press <code>Opt+Cmd+R</code> (<code>Restore</code>) to remove their original segmentation.<br /><li>Press <code>Opt+Cmd+S</code> (<code>Segment Selection</code>) to make a segment from the selection.<br /></ul><br /><br /><br /><h4>Split a segment</h4><br /><ul><li>Select the segment to split.<br /><li>Press <code>Opt+Cmd+R</code> (<code>Restore</code>) to remove its original segmentation.<br /><li>Select the part you want to make a segment out of.<br /><li>Press <code>Opt+Cmd+S</code> (<code>Segment Selection</code>) to make a segment from the selection.<br /><li>Proceed similarly with the remaining of the original segment until every part is a segment.</ul><br /><br />It is also possible to cut and paste segment contents around to achieve the same result. You may end up with empty segments that will have to be deleted. Do what fits best your workflow.<br /><br />In the system shortcuts (see System Preferences, Keyboard Shortcuts), you should have a <i>Move focus to next window in active application</i>. <br /><br />I have set this shortcut to <code>Cmd+Esc</code>, so that I can <code>Cmd+Tab</code> to navigate the running applications and <code>Cmd+Esc</code> to navigate the open windows of the frontmost one.<br /><br />Imagine the following scenario:<br /><br /><code>Cmd+1</code>, you select the next coming segment, you notice that it is not associated with the right segment in the other window.<br /><br /><code>Cmd+Esc</code>, you go to that window, you do what you have to do there, and when the segments are properly aligned, you don't need to go back to the first window, just proceed with <code>Cmd+1</code>.<br /><br />Anyway, with the above indications, you should be able to correct all the segments association in the files by using only the keyboard and by thus saving a huge amount of time.<br /><br /><h3><li>Create the alignment file</h3><br /><br />The purpose of all this is of course to create an aligned file that you will later use for reference in your favorite CAT tool.<br /><br />Appletrans allows you to save such corpus in the familiar TMX format that most CAT tools support.<br /><br /><dl><dt>First, you need to create a new corpus that will contain the data you just aligned.</dt><br /> <dd>→ <code>File</code> menu, <code>New Corpus</code></dd><br /><br />A new dialog should be displayed but you don't have to worry about it. Click on any of the two text window that you have just aligned. <br /><br /><dt>Now, to save your data:</dt><br /> <dd>→ <code>Tools</code> menu, <code>Build Corpus</code></dd><br /><br />Appletrans will be busy for a few seconds and then will release the focus.<br /><br />If you go back to the Corpus dialog, you will notice that the upper left red light now has a black dot in it, which indicates that the corpus has been modified.<br /><br /><dt>To create the final TMX:</dt><br /> <dd>→ <code>File</code> menu, <code>Save As</code></dd><br /></dl><br />Put a relevant file name and select <code>TMX Format</code> from the <code>File Format</code> drop down menu. Then save.<br /><br />The TMX that you have just created is a TMX 1.4 file that contains only textual information. All the style that was present in the RTF files has been removed. It is thus a TMX 1.4 level 1 file.<br /><br />A typical Appletrans created TMX file will look like this:<br /><pre><br /><span class="nxml-processing-instruction-delimiter"><?</span><span class="nxml-processing-instruction-target">xml</span> <span class="nxml-attribute-local-name">version</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">1.0</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">encoding</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">UTF-8</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-processing-instruction-delimiter">?></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">tmx</span> <span class="nxml-attribute-local-name">version</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">1.4</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">header</span> <span class="nxml-attribute-local-name">creationtool</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">AppleTrans</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">creationtoolversion</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">38</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">datatype</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">unknown</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">segtype</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">sentence</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">adminlang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">srclang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">o-tmf</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">AlairCorpus</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">header</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">body</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">tu</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">tuv</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">><</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">sentence</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">tuv</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">tuv</span> <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">fr</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">><</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">phrase</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">seg</span><span class="nxml-tag-delimiter">><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">tuv</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">tu</span><span class="nxml-tag-delimiter">></span><span class="rng-error"><br /></span></pre><br /><br />You may want to change the <span class="nxml-attribute-local-name">srclang</span> argument since Appletrans defaults to <span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">en</span><span class="nxml-attribute-value-delimiter">"</span>. If you use this TMX in OmegaT, the change won't be necessary as long as the <span class="nxml-attribute-prefix">xml</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">lang</span> argument for the two <span class="nxml-element-local-name">tuv</span>s corresponds to language variants of the languages you have set at the time of the project creation.<br /><br /><h3><li>Validate the TMX contents</h3><br />Appletrans (and a number of other tools) do not ensure that the TMX contents perfectly follows the TMX standard. In some cases, the textual contents that you have just aligned and converted will contain characters that should not be included in a TMX file. To ensure that the TMX you have just created does not contain such characters, you are going to need another utility.<br /><br />Maxprograms, the creator of a number of translation related tools, has released a free TMX validation utility that will be put at use here <a href="#links">☞</a>.<br /><br />Launch TMXValidator, and instead of using the <code>Validate File</code> in the <code>File</code> menu, use the <code>Clean Invalid Characters</code> from the same menu.<br /><br />TMXValidator will ask you to select your TMX file. After a very short time, the main window should display "File cleaned". No need to save, the file has already been modified.<br /><br />You can now use the TMX file in any CAT tool that support TMX files.</ol><br /><br /><hr><br /><br /><a name="links"></a><br /><h2>Links</h2><br /><br />About LISA:<br /><a href="http://mac4translators.blogspot.com/2007/12/tmx-xliff-etc.html">TMX, XLIFF, etc...</a><br /><br />Perl and Python scripts to create TMX files are available from the <a href="http://omegat.org/en/resources.html">OmegaT official page</a>.<br /><br />Heartsome's page is <a href="http://www.heartsome.net/EN/home.html">here</a>. You can download the software set and use it without limitations for 30 days.<br /><br />Appletrans can be found from Apple's <i>Localization Tools</i> page, <a href="http://developer.apple.com/internationalization/localization/tools.html">here</a>.<br />There is a very active <a href="http://tech.groups.yahoo.com/group/appletrans_sig/">support group</a> hosted by Yahoo Groups.<br /><br /><a href="http://www.maxprograms.com/">Maxprograms</a> has been around for a while but limited itself to deliver free utilities eventually distributed with the Heartsome tool set. Now it has a full fledged XLIFF editor, Swordfish, along with all the smaller utilities that are all very useful.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3720766682678020275?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com4tag:blogger.com,1999:blog-6335460019316576281.post-16680268124138286612008-04-20T02:04:00.002+09:002008-04-20T02:09:56.575+09:00Office 2008 and OOXML on the Mac (update)I have edited and updated the Office 2008 related posts: <br /><br /><a href="http://mac4translators.blogspot.com/2007/11/office-2007-files-doc-xlsx-pptx-on-mac.html">Office 2007 files (.docx, .xlsx, .pptx) on Mac</a><br />and <br /><a href="http://mac4translators.blogspot.com/2008/01/office-2008-review.html ">Office 2008 review</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-1668026812413828661?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-16072582523003931232008-04-10T11:12:00.003+09:002008-04-10T11:30:17.219+09:00OSX in Arabic !I was wondering how much news I'd get from reading the Mac related French sites and until now I've only been disappointed by seeing only translation of the English news.<br /><br />This morning, something that was not reported in the English sites made its way to my RSS page... The Arabic localization of OSX ! The site is Mac Génération and reported on the <a href="http://www.macgeneration.com/news/voir/129630/mac-os-x-traduit-en-arabe/">release of an Arabic kit for OSX</a>.<br /><br />The release is available for OSX 10.5.2 as a .dmg package. Looking at the <a href="http://www.appleme.ae/ara/support/arabicreleases/arabicreleases.html">release page</a>, one can see an Intel 10.4.10 localization package is also available.<br /><br />Very good news for the Arabic OSX users!<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-1607258252300393123?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-38183565235317608942008-03-03T01:43:00.005+09:002008-04-28T09:33:12.974+09:00Spellchecking in OmegaT 1.8This (or something similar) will eventually make its way into the user manual. Meanwhile...<br /><br /><ol><br /><li>Click on Options > Spell checking...</li><br /><li>Indicate where you want OmegaT to look for dictionaries.</li><br />This can of course be the directory where OpenOffice.org keeps his.<br /><li>If there are valid dictionaries in that location, OmegaT will recognize them and will display them. If the dictionary you want to use is already there and visible to OmegaT, you're done. If that is not the case, proceed with the following:</li><br /><li>Click on "Install". This takes a while because OmegaT gets a list of dictionaries from the internet.</li><br /><li>OmegaT will display a list of dictionaries, click on the dictionaries you want to install (Cmd+click will do multiple selections on Mac, maybe Ctrl+click will do on other platforms).</li><br /><li>After you have clicked "Install", the button will change of color and OmegaT will get the files from the internet and nothing noticeable will happen for a while. Just wait until the button reverts to its "normal" state.</li><br /><li>Close.</li><br /><li>The new dictionaries will be displayed in the dictionary list.</li><br /><li>To use the dictionaries, <b>make sure the language code of the target files corresponds to the dictionary's language code</b>: an FR-FR dictionary will not work with an FR target setting. You need to change the setting to FR-FR to have the spellchecker recognize the correct dictionary for your target.</li><br /></ol><br /><br />You don't have to use that interface to install new dictionaries.<br /><br />Go to OpenOffice.org's <a href="http://wiki.services.openoffice.org/wiki/Dictionaries">dictionary download page</a> and get the files you want.<br /><br />Uncompress them in the directory specified in step 2) above.<br /><br />If OmegaT does not notice them after that install, you can try reloading the project or restarting OmegaT.<br /><br /><br />Once you have started translating, OmegaT will produce a familiar red wavy underlining for words that are not included in the applied dictionary. A right-click on the word should produce a contextual menu that will display a number of candidates as well as a few options.<br /><br />People who can't "right-click" because they only have one mouse button can use Command+Click to display the contextual menu. Those of you who have a recent Mighty Mouse from Apple should know that it is quite configurable. Check the System Preferences.<br /><br />It is also possible to configure some touchpads to simulate a right-click when hitting them with 2 fingers at once. Check your preferences...<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3818356523531760894?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com9tag:blogger.com,1999:blog-6335460019316576281.post-32201841386566635302008-03-02T23:07:00.007+09:002008-03-03T01:51:51.758+09:00OmegaT 1.7.3, 1.8, 1.9...February was a <a href="http://sourceforge.net/project/stats/?group_id=68187&ugn=omegat&type=&mode=alltime">good month</a> for OmegaT.<br /><br /><b>Rank</b> is second best with 187 out of 100,000+, after October 2007 (see <a href="http://mac4translators.blogspot.com/2007/11/omegat-development-status-for-october.html">this post</a>) where it was at 137.<br /><br /><b>Downloads</b> is also second best with 3,883 packages (everything included), after November 2006 where it was at 4,127.<br /><br />A few days ago, the latest stable version was released (<a href="http://sourceforge.net/forum/forum.php?forum_id=786665">OmegaT 1.7.3_01</a>). It had been existing as a test version for a while and since there were no major issues with it, it was eventually considered stable.<br /><br />Making 1.7.3 stable also meant creating a whole new test version. While the developers were busy fixing the most important glitches and adding localizations, work was also done on the last version of OmegaT that will work with Java 1.4: OmegaT 1.8.<br /><br />OmegaT 1.8 test <a href="http://sourceforge.net/forum/forum.php?forum_id=792821">has been released</a> a few minutes ago ! In fact, Didier had been waiting all this week for the OSX bundled that I had totally forgotten about. Apologies everybody !!!<br /><br /><h2>OmegaT 1.8</h2><br /><br /><a href="http://downloads.sourceforge.net/omegat/OmegaT_1.8.0_MacOSX.zip">Donwload OmegaT 1.8 test for OSX !</a><br /><br />Java 1.4 is a thing of the past for most Windows and Linux users. For them, Java 1.6 has been available for a while already. But for Mac, Java 1.5 is still the default in Leopard (10.5) and Tiger (10.4), and Panther (10.3) users are still limited to Java 1.4.<br /><br />OmegaT 1.8 is bringing quite a few major new features to OmegaT.<br /><br />First of all, a <b>spellchecker</b>. OmegaT uses the same spellchecker as OpenOffice.org: hunspell. Which also means that it can use all the dictionaries available for OpenOffice.org, and that means quite a lot. Since the manual has not been updated yet to cover this aspect of the setup, you'll have to proceed by trial and error to install your dictionaries, but it is relatively trivial so you should be alright. Don't forget to make sure that the dictionary language code and the project target language code match, otherwise the spellchecker will not realize it is called...<br /><br /><b>Update!</b> It looks like some OmegaT users have a hard time with the spellchecking setup, so I just wrote a page about that: <a href="http://mac4translators.blogspot.com/2008/03/spellchecking-in-omegat-18.html">Spellchecking in OmegaT 1.8</a>.<br /><br />After the spellchecking, there are quite a few other features that will surely ease your work. Here is a list from the changes.txt file:<br /><br /><ul><br /> <li>Letter case change in editing field </li><br /> <li>Display (all) source segments, so that you don't have to navigate to a segment to see its source, you can have all the source segments displayed at once </li><br /> <li>Mark translated segments with a distinguishable background color </li><br /> <li>Mark untranslated segments with a distinguishable background color </li><br /> <li>Navigation history, so that you can change of segment and come back to the one where you left </li><br /> <li>HTML, skip extraction of messages matching regxep</li><br /> <li>Select elements to translate in office documents</li><br /> <li>Clickable match window, so that you can navigate to a match </li><br /> <li>Compare source segment and translated segment lengths</li><br /> <li>Indicate translation progress in status bar, mostly the data in the project file window, but available without having to change of window</li><br /></ul><br /><br /><br />OmegaT 1.8 does have a few glitches though, some of them I gather, due to the spellchecker interaction with the editing interface. So it should really be considered as a test version. But I have been working with it since the very first days of the spellchecker implementation and I have yet to loose data with it (not that I am particularly anxious to prove the fact that a test version should not be used for real jobs though...)<br /><br /><br /><br /><h2>OmegaT 1.7.3_02</h2><br /><br />If you check the <a href="http://sourceforge.net/project/shownotes.php?release_id=581097&group_id=68187">release notes</a> available in OmegaT 1.8 you'll find that a 1.7.3 release 2 is in the making.<br /><br />Currently, 1.7.3_02 includes the following:<br />Enhancements:<br /><ul><br /><li>Command line parameters for OmegaT.exe</li><br /><li>Windows installer</li><br /><li>New Arabic localisation (readme, instant start)</li><br /></ul><br /> Bug fixes:<br /><ul><br /><li>PO: Bad handling of plural messages on multiple lines</li><br /></ul><br /><br />OmegaT 1.7.3 release 2 is not yet ready. It is still waiting for more localizations and eventual bug fixes. I'll update this page when information comes in.<br /><br />Regarding OmegaT's first Arabic localization, I would like to express my sincere thanks to Mr. Faycal Alami who considered my request for help and gladly contributed his work to the OmegaT Project. I hope we will be able to have a fully localized version of OmegaT in Arabic thanks to his work.<br /><br /><b>The Arabic localization will only be available in OmegaT 1.8 test for a while, until OmegaT 1.7.3_02 is released.</b><br /><br /><br /><h2>OmegaT 1.9</h2><br /><br />Now that OmegaT 1.8 is in testing as the last version of OmegaT that will work in Java 1.4, a lot of work is being accomplished on the <b>next</b> version of OmegaT. Targetting Java 1.5 and probably modifying quite a few important things that we've been used to... OmegaT 1.9 code is now mostly OmegaT 1.8 with a lot of refactoring, to prepare the code for core changes.<br /><br />I am currently using the new code and am updating it as soon as something seemingly big comes in so I'll let you know what goes on. For people who like to be on the bleeding edge, check the OmegaT Project new SVN repository by typing the following at your command line:<br /><br /><code>svn co https://omegat.svn.sourceforge.net/svnroot/omegat omegat</code><br /><br />You'll need <b>ant</b> to build the code. There won't be an OSX bundle for 1.9 before a while, so you'll have to do as we used to before the bundle: either double-click on the OmegaT.jar file, or start from the command line.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3220184138656663530?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-22445257294326967862008-02-29T11:06:00.004+09:002008-02-29T14:13:55.655+09:00Mac for Translators, mailing list ?I am starting to think that this blog could benefit from a proper mailing list...<br /><br />So here it is: <a href="http://groups.google.com/group/mac-for-translators">http://groups.google.com/group/mac-for-translators</a>...<br /><br />Feel free to join. The archives are set to be publicly available, and the group will be multilingual.<br /><br />To subscribe, send a message to <a href="mailto:mac-for-translators-subscribe@googlegroups.com">mac-for-translators-subscribe@googlegroups.com</a>. Google will send you a confirmation mail.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-2244525729432696786?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-7522898057224089602008-02-20T21:54:00.004+09:002008-02-20T22:35:53.457+09:00Okapi tools on OSX...In my "<a href="http://mac4translators.blogspot.com/2007/11/okapi-tools-for-mono.html">Okapi tools for Mono</a>" post, last November, I discussed the possibility to use Okapi on OSX <strong>without</strong> installing Parallels/VMWare/WhateverVirtualSolutionYouPrefer <strong>and</strong> Windows <strong>and</strong> .NET... Which in the end makes Okapi a very expensive free tool...<br /><br />Okapi has recently been released to work on Mono, the <strong>free</strong> (as a bird) version of .NET and I've promised myself to install everything and try the package as soon as I'd have a job requiring it.<br /><br />This job has come. At last. It is a small set of InDesign files (that will eventually end up being Illustrator files) that are part of a much bigger translation package...<br /><br />So, at the time of writing, here is the procedure you need to follow to get everything to work:<br /><br /><em>(Beware, Okapi for mono does not come with a graphical interface and everything must be done in the Terminal, at the command line. It is not terribly hard but not super trivial either for the translator who is not used to that. For people who need an introduction to working with the Terminal on OSX, check <a href="http://www.macdevcenter.com/pub/a/mac/2001/12/14/terminal_one.html">this</a> link.)</em><br /><br /><ol><br /><li>Download Mono (1.2.6 at the time of the post):<br /><br /><a href="http://www.go-mono.com/mono-downloads/download.html">http://www.go-mono.com/mono-downloads/download.html</a></li><br /><li>Install it by clicking on the package file and following the instructions.</li><br /><li>Download Okapi for Mono (R00020 at the time of the post):<br /><br /><a href="http://sourceforge.net/project/showfiles.php?group_id=42949">http://sourceforge.net/project/showfiles.php?group_id=42949</a><br /></li><br /><li>Unzip/untar the package and read the ReadMe_ForMono.htm file found in the <code>Tikal</code> folder</li><br /><li>Do what the file says under "Using the Okapi tools"<br /><br />(for some reason, I am yet unable to properly set the path to Okapi...)</li><br /></ol><br /><br />When this is done, you'll need to take a look at the <a href="http://www.mono-project.com/Mono:OSX">Mono for OSX</a> page to know how to use the beast.<br /><br />Basically, it comes down to opening the Terminal and typing:<br /><br /><code>$ mono ~/bin/OkapiMono/Tikal/Tikal.exe</code><br /><br />Here, I've left my path to Tikal because I could not set it properly in the install step. But a proper install should accept:<br /><br /><code>$ mono Tikal.exe</code><br /><br />Running only Tikal.exe without any arguments will have the application display its basic help where you'll see what you need to type to do a few basic things, like:<br /><br /><code>$ mono Tikal.exe -<strong>lf</strong></code><br />to <strong>l</strong>ist the available <strong>f</strong>ilters.<br /><br />Just for your information, since you can find that on the Okapi help pages too, here are the filters that are directly available from the Mono command line:<br /><ul><br /><li>okf_po (Okapi PO Filter)</li><br /><li>okf_properties (Okapi Properties Filter)</li><br /><li>okf_script (Okapi Script Filter)</li><br /><li>okf_netres (Okapi NETRes Filter)</li><br /><li>okf_rc (Okapi RC Filter)</li><br /><li>okf_xml (Okapi XML Filter)</li><br /><li>okf_wordfast (Okapi Wordfast Filter)</li><br /><li>okf_tradostext (Okapi Trados Text Filter)</li><br /><li>okf_illustrator (Okapi Illustrator Filter)</li><br /><li>okf_table (Okapi Table Filter)</li><br /><li>okf_inx (Okapi INX Filter)</li><br /><li>okf_html (Okapi HTML Filter (ALPHA TEST ONLY)</li>)<br /><li>okf_json (Okapi JSON Filter)</li><br /></ul><br /><br />If you use the parameter -<strong>lu</strong> you'll get a <strong>l</strong>ist of available <strong>u</strong>tilities:<br /><ul><br /><li>oku_set01:extraction</li><br /><li>oku_set01:merging</li><br /><li>oku_set01:rewriting</li><br /><li>oku_set01:encodingconversion</li><br /><li>oku_set01:lbconversion</li><br /><li>oku_set01:bomconversion</li><br /><li>oku_set02:qualitycheck</li><br /><li>oku_set02:update</li><br /><li>oku_set02:rtfconversion</li><br /><li>oku_set02:xsltransformation</li><br /><li>oku_set02:twbanalysis</li><br /><li>oku_set02:rtfsplitting</li><br /><li>oku_set02:alignment</li><br /><li>oku_set02:rtftotmx</li><br /><li>oku_set03:alignment</li><br /><li>oku_set04:dnllistedit</li><br /><li>oku_set04:xliffsplitting</li><br /><li>oku_set04:xliffconcatenation</li><br /><li>oku_set04:tmxsplittingdup</li><br /><li>oku_set04:xliffconversion</li><br /><li>oku_set04:proofreading</li><br /><li>oku_set04:searchandreplace</li><br /><li>oku_set04:uriconversion</li><br /><li>oku_set04:cdataconversion</li><br /><li>oku_set04:xmlpruning</li><br /><li>oku_set04:ttx2tmx</li><br /><li>oku_set04:xmlpartitioning</li><br /></ul><br />All the filters and utilities etc require specific parameters to run. Check the Okapi for Mono manual that comes with the download to know how to use all that.<br /><br />Don't forget that Okapi has a very nice <a href="http://tech.groups.yahoo.com/group/okapitools/">user group</a> managed by Yves Savourel, the developer. It is possible to access the archives without having to subscribe to it.</string><br /><br />Et voilà ! That is pretty much everything you need to know to get started... I hope that helped !<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-752289805722408960?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-69784460669570358612008-01-13T00:36:00.002+09:002008-03-17T18:38:47.754+09:00ZFS for OSX<h3>Update</h3><br /><br />A very interesting article at Ars Technica tells us why file systems matter. And it tells us a lot about Macs too !<br /><br /><a href="http://arstechnica.com/articles/paedia/past-present-future-file-systems.ars/">From BFS to ZFS: past, present, and future of file systems</a><br /><br /><hr><br /><br />ZFS was the new file system that was rummored to be behind Leopard's Time Machine. ZFS has been developped by SUN Microsystem for their Solaris operating system.<br /><br />Quote from the ZFS Open Solaris Page:<br /><br /><i>ZFS is a new kind of filesystem that provides simple administration, transactional semantics, end-to-end data integrity, and immense scalability. ZFS is not an incremental improvement to existing technology; it is a fundamentally new approach to data management. We've blown away 20 years of obsolete assumptions, eliminated complexity at the source, and created a storage system that's actually a pleasure to use. <br /><br />ZFS presents a pooled storage model that completely eliminates the concept of volumes and the associated problems of partitions, provisioning, wasted bandwidth and stranded storage. Thousands of filesystems can draw from a common storage pool, each one consuming only as much space as it actually needs. The combined I/O bandwidth of all devices in the pool is available to all filesystems at all times.</i><br /><br />Key word here: <b>data integrity</b>... For flawless backups etc...<br /><br />Well, to tell you the truth, the above quote was from the ZFS Open Solaris Page <i>via</i> the <b>ZFS on OS X</b> page on MacForge, the provider of many a Free Software project for the Mac.<br /><br />Which also means that <b>YES!</b> ZFS is available for the Mac !!!<br /><br />To know more about it, go to <a href="http://trac.macosforge.org/projects/zfs/wiki">Welcome to ZFS on OS X</a>.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-6978446066957035861?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-20387179283605334202008-01-04T14:22:00.003+09:002008-04-20T01:40:15.960+09:00Office 2008 review<h3>Ars Technica's word</h3><br /><br />Ars Technica has released a brief review of Office 2008, a few days before the suite's release at MacWorld 2008 <a href="#links">☞</a>.<br /><br /><h3>The new file format</h3><br /><br />For translators, the main appeal of the suite is the access it provides to the new Office 2007 format. There are plenty of things to say about this new format, and the first is that power users or developers who rely on the OOXML standard to create files that Office 2007/2008 should support are going to be a little surprised <a href="#links">☞</a>...<br /><br /><h3>Native !</h3><br /><br />Another important feature of the suite is that the new Office for Mac is now a Universal Binary, which means that it will run natively and equally well on both PPC and Intel machines. No more Rosetta between the machine and Office!<br /><br />MacTech has run a few tests (2500) to compare Office 2008 to Office 2004 on G4 and Intel /Tiger and Leopard machines.<br /><br />The conclusion is that Office 2008 is about 30% faster than Office 2004 on Intel machines and that it is "marginally" slower on G4 machines. Also, Office 2008 looks faster on Leopard than on Tiger.<br /><br />Besides for the raw performance, the article points at the fact that the suite having been rewritten, a number of features are either more quickly accessed or provide a faster ergonomic experience than their 2004 counterparts. Which means that even users of a G4 could see some benefits using it <a href="#links">☞</a>. <br /><br /><br /><h3>No more Wordfast ! Scripting options ?</h3><br /><br />The major problem for Mac translators is that since Office 2008 drops VBA support they won't be able to use WordFast anymore, at least the current versions that are basically a Word macro written in VBA.<br /><br />Office 2008 supposedly adds better AppleScript support and OSX integration but it is unlikely that such features will be of much use for tool developers who relied on the relative compatibility with Office for Windows to deliver their "mutliplatform" tools. Still, people who want to start converting their VBA work to AppleScript should take a look at MacTech's transition guide. <br /><br />According to Nadyne, MBU member and Ars Technica's Jacqui Cheng, Office 2008's Automator support does not come as a default option: it is not in the "Home/Student" edition, only in the "Standard" and "Special".<br /><br />Automator support comes along with "full Exchange support" for an extra cost of $250 ("Home/Student" at $150, "Standard" at $400)... <a href="#links">☞</a><br /><br /><h3>Pricing ?</h3><br /><br />Also, it looks like MS is sticking to its funky Vista-like pricing options (or maybe Vista only made that worse)... Why is it so hard to simply have a 1 license vs 3+ licenses pricing pattern?<br /><br />No multi-license scheme for "Standard" and 3 "non-commercial" installs for "Home/Student"...<br /><br /><br /><h3>Last but not least ?</h3><br /><br />Here is a good reason to wait until a few updates are released... Microsoft has published a list of know issues with the new software. MacOSXHints makes a short summary and has links to the relevant page at Microsoft. You wonder what they've done of their time in 4 years of development... Another case of the Vista syndrome? Some issues seem to have been addressed in the first update of the suite though. <a href="#links">☞</a><br /><br /><hr><br /><br /><br /><a name="links"></a><br /><h2>Links</h2><br /><br />Ars Technica's Office 2008 review:<br /><a href="http://arstechnica.com/reviews/apps/mac-office-2008-review.ars/1">First Look: Microsoft Office for Mac 2008</a><br />By Jonathan M. Gitlin, January 2008<br /><br />MS does not respect its own format:<br /><a href="http://ooxmlisdefectivebydesign.blogspot.com/2007/08/microsoft-office-xml-formats-defective.html">Microsoft Office XML formats? Defective by design</a><br />By Stéphane Rodriguez, August 2007<br /><br />MacTech's VBA to AppleScript transition guide:<br /><a href="http://www.mactech.com/vba-transition-guide/">Moving from Microsoft Office VBA to AppleScript: MacTech's Guide to Making the Transition</a><br />By Paul Berkowitz, April 2007.<br /><br />MacTech's Office 2008 Benchmarks Preview:<br /><a href="http://www.mactech.com/articles/mactech/Vol.24/24.03/Office2008Benchmark/">How well does Office 2008 run compared to Office 2004?</a><br />By Neil Ticktin, Editor-in-Chief, January 2008.<br /><br />Mac My Day, Nadyne's blog at MBU:<br /><a href="http://blogs.msdn.com/nadyne/archive/2008/01/16/today-s-top-five-questions-in-the-office-2008-booth.aspx">today's top five questions in the Office 2008 booth</a><br />By Nadyne, MBU member, January 2008.<br /><br />Ars Technica's Infite Loop<br /><a href="http://arstechnica.com/journals/apple.ars/2007/09/24/microsoft-announces-mac-office-2008-pricing-upgrade-details">Microsoft announces Mac Office 2008 pricing, upgrade details</a><br />By Jacqui Cheng, September 2007.<br /><br />MacOSXHints' summary of known issues<br /><a href="http://www.macosxhints.com/article.php?story=20080117144249295">A list of known issues with Microsoft Office 2008</a><br />By user davidfoster with addendum by manager robg, January 2008.<br /><br />Microsoft's first update details<br /><a href="http://support.microsoft.com/kb/948057">Description of the Office 2008 for Mac 12.0.1 Update</a><br />By Microsoft, March 2008<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-2038717928360533420?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-52209508803430255992008-01-02T19:02:00.000+09:002008-01-02T19:10:05.730+09:00Will the Real T(ranslator|echie) Please Stand Up?I think I need to change my working habits too.<br /><br /><a href="http://www.potionfactory.com/blog/2008/01/01/will-real-techie-please-stand">Here</a> is Andy Kim's story about workplace ergonomics.<br /><br />And here is Bill Clementson's older story:<br /><a href="http://bc.tech.coop/blog/041024.html">part 1</a><br /><a href="http://bc.tech.coop/blog/041029.html">part 2</a><br /><a href="http://bc.tech.coop/blog/060116.html">part 3</a><br /><a href="http://bc.tech.coop/blog/060131.html">part 4</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-5220950880343025599?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-68894778193152594972008-01-01T17:09:00.001+09:002008-03-27T15:54:37.279+09:00RAM cost on Apple machines<h3>Update</h3><br /><br />With the latest hardware updates, RAM price has considerably dropped.<br /><br />The iMac 2gb->4gb update drops from ¥89,000 to ¥47,000, same drop on the laptops. Only the Mac Pro does not seem to benefit from the drop (at ¥63,000).<br /><br /><hr><br /><br />I've seen a number of blog articles here and there complaining about Apple's RAM prices but each and every single one of them missed something: a comparison of the actual chips that were being installed on the updated machines and a comparison with other makers' practices.<br /><br />I have no doubt that one can find cheap memory anywhere but what is the cost of the high end stuff, and why not assume that it is what Apple puts in our machines ? Is there a study out their that proves Apple is such a crook as far as RAM quality/cost ratio is concerned ?<br /><br />What is the performance difference between components of various prices and origins ?<br /><br />Just to make sure I am not misunderstood. I have no doubt whatsoever that Apple is making a very fat margin on a number of items.<br /><br />The update from 2gb to 4gb on the iMac line is ¥89,000 on the Japanese store (~$615 - too bad for the US customers who are penalized by the exchange rate: $700 on the US Apple Store).<br /><br />When I check similar updates (from 2gb to 4gb) for various makers' online stores I find (after a huge lot of painful browsing through ugly online stores):<br /><br /><h3>Below $400</h3><br /><ul><li>Dell (desktop) charges $270.<br /></li><li>HP (desktop) charges $170+$100=$270<br /></li><li>Lenovo (desktop) charges $340-$60=$280<br /></li><li>Everex (?) charges $135x2=$270 for memory chips but it is not specified if the chips come installed or not.<br /></li><li>HP (laptop) charges $300<br /></li><li>AlienWare (desktop) charges $450-$100=$350<br /></li><li>Dell (laptop) charges $375.<br /></li></ul><br /><br /><h3>Above $400</h3><br /><ul><li>Apple charges less on the Mac Pro series: from 2gb to 4 gb only costs $400.<br /></li><li>Lenovo (laptop) charges $520-$80=$440<br /></li><li>NEC (desktop) charges ¥110,000-¥50,000=¥60,000 (~$460)<br /></li><li>Fujitsu (laptop) charges $480.<br /></li><li>Sony (laptop) charges $660-$110=$550 (I could not find relevant information for Sony desktops but since the Apple RAM tax applies equally to notebooks I also checked the Sony laptops)<br /></li><li>Toshiba laptops did not seem to include a 4gb options but the upgrade from 512mbx2 to 2gbx1 is $280<br /></li></ul><br /><br />Also, Apple's line is made of compact machines (obvious for the laptops) at the exception of the Mac Pro. All the compact machines' upgrades from 2gb to 4gb cost the same at Apple and the non-compact Mac Pro's upgrade costs much less. Similarly for other makers, all the compact machines' upgrades cost more than the non-compact machines'.<br /><br /><h3>So, what does all that mean ?</h3><br /><ol><li>One can find extra cheap uninstalled RAM in the wild, just check for low prices in your area.<br /></li><li>All the makers I checked charge <b>much</b> more for the update than for the price of the individual chip<br /></li><li>Makers that also compete in the low end (Dell, Lenovo, HP, Everex) charge similar prices <$400 </li><li>Other makers (Sony, Fujitsu, NEC) all charge more than Apple's upgrade for the Mac Pro's $400, and Sony is actually quite close to Apple's compact machines ($550 - $700). Toshiba would no doubt charge similar prices if its laptops accepted 4gb or RAM (I could not find any on the online store, but that does not mean they don't exist).<br /></li></ol><br /><br />Now, I have still no idea what chips are in the machines, what is their relative quality and how much margin all the other makers actually get from their RAM upgrade prices. But considering the prices, it does not seem that what Apple does is so outrageous after all. After all, as John Gruber put it in a <a href="http://daringfireball.net/linked/2007/december#mon-24-market_share">recent</a> post, Apple is after profit, not market shares.<br /><br />And just in case that would have escaped people who write blogs, the actual act of shopping is made <b>very</b> easy by Apple. I live in the Japanese country side and being able to have flawless support after getting my machine from the online store is definitely worth the $100 difference with a Sony machine, or the $350 with a Dell machine. Plus, those don't run Leopard. When I call the support center and talk to super polite people who are able to answer complex questions without hesitation, I say that is worth the Apple tax on my RAM (and yes, I did get 4GB on my wife's recent 24" iMac).<br /><br />Regarding the recent iMac's memory specifications, see this <a href="http://docs.info.apple.com/article.html?artnum=306205">document</a>. Earlier iMacs did not support the full 4GB it <a href="http://docs.info.apple.com/article.html?artnum=304284">seems</a>.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-6889477819315259497?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com3tag:blogger.com,1999:blog-6335460019316576281.post-74359602894611219292007-12-25T12:18:00.001+09:002007-12-25T13:59:31.647+09:00Fink, Mac Ports...<h2>Fink</h2><br /><br />If you want to install <a href="http://www.finkproject.org/">Fink</a> on Leopard, you'll need to go to <a href="http://www.finkproject.org/download/srcdist.php">the source release page</a> because <i>There is not currently a binary release for you.</i> (Quote from the <a href="http://www.finkproject.org/download/index.php?phpLang=en">download page</a>).<br /><br />Download the package and follow the instructions found in <b>INSTALL.html</b>.<br /><br /><b>If</b> you get a message like:<br /><br /><code>Use of uninitialized value in string ne at /sw/lib/perl5/Fink/Engine.pm line 1579.</code><br /><br />like that happened to me after I wanted to install a package, run:<br /><br /><code>fink selfupdate-rsync</code><br /><br />and that will fix it. It looks like somebody run into the same problem on the Fink user <a href="http://www.mail-archive.com/fink-users@lists.sourceforge.net/msg25887.html">list</a>.<br /><br />The list of packages can be found <a href="http://pdb.finkproject.org/pdb/index.php?phpLang=en">here</a>.<br /><br /><h2>Mac Ports</h2><br /><br /><a href="http://www.macports.org/">MacPorts</a> has been updated to version 1.6 recently and the web site also looks like it has been updated. The install procedure for Leopart users is straightforward. Just click on the "Installing Mac Ports" and follow the instructions.<br /><br />The list of available ports is <a href="http://www.macports.org/ports.php">here</a>.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-7435960289461121929?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-31880320970488854432007-12-25T11:47:00.000+09:002008-01-03T19:06:12.197+09:00Learn Cocoa !For the readers who have too much free time during the holiday, what about starting to learn programming applications the easy way ?<br /><br />And I <b>do</b> mean easy, like <i>not a single line of code written</i> ! Yes, creating applications for your favorite machine can be <b>that</b> easy.<br /><br />Scott Stevenson, the writer behind <a href="http://theocacao.com">theocacao.com</a> has updated his "<a href="http://cocoadevcentral.com/d/learn_cocoa/">Learn Cocoa</a>" tutorial for Leopard. The old Tiger version is still <a href="http://cocoadevcentral.com/d/learn_cocoa/tiger/">available</a> for those of you who have not updated your OS yet.<br /><br />You'll need to install the developer tools that come with your OSX DVD and for the rest, just follow the tutorial. It is not only amazingly well written, it is also beautiful.<br /><br />The Tiger version has a sequel (<a href="http://cocoadevcentral.com/d/learn_cocoa_two/">Learn Cocoa II</a>) that is not yet updated for Leopard, but you should be able to make sense of most of it since it is mostly an introduction to Objective-C in the context of Cocoa applications.<br /><br />Comments regarding the updated contents and Scott's <a href="http://theocacao.com/document.page/537">replies</a> are very useful too, in case you run into problems.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3188032097048885443?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-68945721718264935422007-12-22T22:25:00.001+09:002007-12-22T22:52:20.355+09:00"Open With" too many applications...All this started a few weeks ago, and it is most probably related to Leopard's Time Machine. It may be related to other things too but then I have no idea what they are. The result is that you end up with duplicates of all your applications popping up here and there, first in the SpotLight result window, then in Mail, when you right-click on an attachment, in Finder too...<br /><br />Sometimes you launch the backup instead of the original, and you realize when the backup disks starts to scramble like crazy...<br /><br />Eventually, I found a solution. A little drastic, and maybe it was not all necessary, but it also contributed to rationalize my backup procedures.<br /><br /><b>Before:</b><br /><br />1) Time Machine copied _all_ my disk to an external backup disk<br />2) I had Sync!Sync!Sync! do an extra daily backup of my whole home hierarchy (including all the "user space" applications)<br />3) I had Spotlight index everything<br /><br />What I wanted was Spotlight indexing everything _but_ the applications.<br /><br />The problem was that the Privacy setting of SpotLight did not allow for the selection of a subfolder in the Time Machine backup (like Applications, for ex).<br /><br /><b>Now:</b><br /><br />1) Time Machine copies everything <b>but</b> the system Application folder, the user Application folder, the whole Developer folder and the Download folder.<br />2) Sync!Sync!Sync! does an extra daily backup of my whole home hierarchy, including the user space Application folder<br />3) Sync!Sync!Sync! does also a daily backup of the system's Application folder<br />4) I have Spotlight index everything (including the TimeMachine backup, of course) <b>but</b> the Sync!Sync!Sync! backups where all the Application duplicates are now.<br /><br />I have also reindexed Spotlight using the following command in Terminal:<br /><br /><pre> $ sudo mdutil -Es / /Volumes/backup_disk_name/</pre><br /><br />And I have rebuilt the LaunchServices database, the one that contains all the "knowledge" about which application is supposed to launch which file, with the following command, also in Terminal:<br /><br /><pre> $ /System/Library/Frameworks/CoreServices.framework/\<br />Versions/A/Frameworks/LaunchServices.framework/\<br />Versions/A/Support/lsregister\<br /> -kill -r -domain local -domain system -domain user</pre><br /><br />SInce the whole "recipe" is based on saving applications outside Time Machine, I also had to erase <b>all</b> the data Time Machine had accumulated for a month... Setting Time Machine to not save /Applications from any day does not remove /Applications from the previous days backup sets... There may be smarter ways to do that, but I thought that with my already existing extra daily backup I was on the safe side.<br /><br />Now, I have much saner "Open With" drop down lists when I right-click a file with my mouse...<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-6894572171826493542?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-85520148163315126522007-12-18T10:05:00.000+09:002008-01-03T19:10:23.666+09:00NeoOffice 2.2.2 Patch 5 and 6, OSX Security Update (and its own update), more QuickLook sites<h2>NeoOffice 2.2.2 patch 5, then 6</h2><br />The <a href="http://www.neooffice.org/neojava/en/patch.php">patch</a> fixes a regression introduced in the previous patch and expands <i>Asian text input and layout enhancements to include Chinese, Japanese, and Korean punctuation</i>.<br /><br /><b>Update</b><br><br />It seems patch 5 introduced regressions in the layout enhancements for CJK punctuation and path 6 specifically removed all the new code introduced by patch 5.<br /><br /><h2>OSX Security Update 2007-009</h2><br />For OSX 10.5.1 and 10.4.11.<br />Available from Software Update (under the Apple menu) or from the Apple Donwload <a href="http://www.apple.com/support/downloads/">page</a>.<br /><br />Details are <a href="http://docs.info.apple.com/article.html?artnum=307179">here</a>.<br /><br /><b>Update</b><br><br />Apple released an update to that security update a few days later. It seems the first update introduced a number of new crashes in Safari...<br /><br /><h2>QuickLook</h2><br />Two sites dedicated to QuickLook plugins.<br /><br />It looks like the number of domain names that include "quick", "look", and "plugin" is decreasing...<br /><br /><a href="http://www.quicklookplugins.com/">http://www.quicklookplugins.com/</a> and <a href="http://www.qlplugins.com/">http://www.qlplugins.com/</a>.<br /><br />I have a preference for the second in terms of visibility and design.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-8552014816331512652?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-62856481247381488772007-12-16T15:38:00.000+09:002007-12-16T16:48:13.826+09:00Paperless office, PDF, XML, Zip...From the <a href="http://www.macdevcenter.com/">Mac Dev Center</a>, "<a href="http://www.oreillynet.com/mac/blog/2007/11/my_paperless_office.html">My paperless office</a>" by <a href="http://www.oreillynet.com/pub/au/1843">Gordon Meyer</a>.<br /><br />Gordon writes about how he used a <a href="http://www.fujitsu.com/global/services/computing/peripheral/scanners/product/s510m/">Fujitsu ScanSnap scanner</a> to archive all his paper documents to digital form. He also mentions <a href="http://www.devon-technologies.com/products/devonthink/index.html">DevonThink</a>, a digital document managing system, and 2 PDF utilities: <a href="http://skim-app.sourceforge.net/index.html">Skim</a>, a <i>PDF reader and note taker for OSX</i> released under the Modified BSD License, and hence Free software, and <a href="http://www.smileonmymac.com/PDFpen/">PDFPen</a>, a tool to organize and overwrite PDFs.<br /><br />Considering the <a href="http://www.apple.com/macosx/features/300.html#preview">Leopard version of Preview</a>, it looks like Skim as well as PDFPen are becoming obsolete, as some comments seem to confirm...<br /><br />The other day there was a link on Slashdot pointing to Jim King's "Inside PDF" blog, about the fact that <a href="http://blogs.adobe.com/insidepdf/2007/12/iso_ballot_for_pdf_17_passed.html">PDF 1.7 was becoming an ISO standard</a>.<br /><br />I've been reading a number of Jim's posts and here are a few that may interest some of you. They are all a little theoretical but give very interesting insights on a number of existing major documentation formats.<br /><br />Quotes from the respective pages.<br /><br /><a href="http://blogs.adobe.com/insidepdf/2007/10/pdf_by_design.html">PDF by Design</a><br /><br /><i>I named this blog "Inside PDF" because I anticipated telling you a lot about PDF technology – what is inside of a PDF file and why. I have spent most of the time so far talking about PDF and standards. So, I thought it was about time to do an entry about PDF itself. I believe that PDF has been so successful because of the caldron out of which it was brewed. By 1990 Adobe was quite successful with <a href="http://en.wikipedia.org/wiki/PostScript">PostScript</a>. By then we had helped over 60 other companies make printers, image setters, and other imaging devices that used PostScript. We had also shipped <a href="http://en.wikipedia.org/wiki/Display_PostScript">Display PostScript</a> and the Steve Jobs <a href="http://www.time.com/time/magazine/article/0,9171,968761-1,00.html">NeXT machine</a> was a computer whose operating system's imaging model was Display PostScript. So Adobe had had considerable experience in displaying documents on a screen...</i><br /><br /><a href="http://blogs.adobe.com/insidepdf/2007/09/xml_documents.html">XML Documents</a><br /><br /><i>Today I hope to tie together two previous blogs about <a href="http://blogs.adobe.com/insidepdf/2007/09/high_drama.html">OOXML</a> and about <a href="http://blogs.adobe.com/insidepdf/2007/09/xml_for.html">XML For ...</a>.<br /><br />I am sure you have often heard the term “XML Document.”  I hope you realized that that term is nearly meaningless just like the term “XML.”  We should never use either in polite conversation. Let me tell you some of the totally different uses for the term “XML Document” which render it a useless term, and maybe you will agree with me to banish it from our vocabularies...</i><br /><br /><a href="http://blogs.adobe.com/insidepdf/2007/10/archiving_documents.html">Archiving Documents</a><br /><br /><i>Archiving is a rather loaded word since doing it can be a widely varying activity. In many situations, archiving PDF files is a very good solution. In fact it was so attractive to some US Government agencies that they encouraged their personnel to work on an ISO committee/working group to define a special subset of PDF called PDF/A that meets their needs better than plain old PDF might...</i><br /><br /><br /><a href="http://blogs.adobe.com/insidepdf/2007/12/zip_archives_and_portable_dire.html">ZIP Archives and Portable Directories</a><br /><br /><i>This is a topic that is dear to my heart and I would love to spur some interest in creating an open source project or something like that. Since about 1999 I have been talking to my colleagues about a concept that I call "portable directories." It is a simple idea once you "get it." <br /><br />File systems, organized around the notion of directories or folders in which to collect files and other directories, have been the staple for how we save computer material on our hard drives, data CDs and DVDs, etc. I suppose it had its invention from an analogy with a file cabinet, but on the computer we can nest folders inside folders to any depth, something hard to do with real physical folders...</i><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-6285648124738148877?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-64775869784624805822007-12-15T19:17:00.000+09:002007-12-15T19:38:31.703+09:00Automation on the Mac ! - PythonAn Automator action "Run Python script" is <a href="http://toxicsoftware.com/run-python-script/">provided</a> by toxicsoftware.com.<br /><br />That comes in addition to the already existing "Run AplleScript" and "Run Shell Script" provided by Apple.<br /><br />This Automator action is Free Software, released under the <a href="http://www.gnu.org/licenses/license-list.html#ModifiedBSD">Modified BSD License</a>.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-6477586978462480582?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-49130753953668510032007-12-14T20:16:00.000+09:002007-12-16T23:00:59.815+09:00Apple Java 1.4 and 1.5 Update for OSX 10.4.10 and later...Released yesterday: <a href="http://www.apple.com/downloads/macosx/apple/macosx_updates/javaformacosx104release6.html">Java for Mac OS X 10.4, Release 6</a>.<br /><br />Make sure you don't get a version number wrong...<br /><br />From the page:<br /><i>Java for Mac OS X 10.4, Release 6 delivers improved reliability and compatibility for Java SE 5.0 and Java 1.4 on Mac OS X 10.4.10 and later. This release updates J2SE 5.0 to version 1.5.0_13 and Java 1.4 to version 1.4.2_16.</i><br /><br />The release notes are <a href="http://developer.apple.com/releasenotes/Java/Java104R6RN/Introduction/chapter_1_section_1.html">here</a>.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-4913075395366851003?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-88095928098442375582007-12-14T11:18:00.000+09:002007-12-14T11:19:43.908+09:00Happy Holiday season !<a href="http://movies.apple.com/movies/us/apple/getamac/apple_getamac_holiday_480x272.mov">Santa Claus is coming to town !</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-8809592809844237558?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-76146073224109758762007-12-14T10:31:00.000+09:002007-12-14T11:29:29.719+09:00TRANSLATION QUALITY ASSURANCE TOOLS: CURRENT STATEThanks to Jost Zetzsche and his <a href="">Tool Kit Newsletter</a> where a link to <a href="http://www.palex.ru/getCommonFile.php?fileId=98">this study</a> (441 kb PDF) was made available.<br /><br />The 1.6 mb <a href="http://www.palex.ru/getCommonFile.php?fileId=99">presentation file</a> that comes with it is also very interesting.<br /><br />A very thorough study on current QA tools that, of course, focuses on Windows tools and for good reason.<br /><br />Excerpts from the document:<br /><br /><i>As expected, most of the respondents (141 or 86.5%) represented translation/localisation service provider companies while a few (more specifically, 11 people) were from service buyer side and 2 were software developer representatives. 3.07% of other organisations were consulting and academic institutions, and one respondent reported his organisation to be multilingual quality assurance service provider.<br /><br /><...><br /><br />The most popular operating system is Microsoft Windows, and 62.58% of respondents confirm their companies work only in MS Windows with no other OS11’s. Users of both Windows and MacOS who follow Windows users comprise only 19.35%. Users of three OS’s (Windows, MacOS and Unix/Linux) account for approx. 9%, and those who work under Windows and Linux comprise 7.1% of all respondents. 0.65% (1 respondent per each category) work only in MacOS, Unix/Linux and other (medical hardware) OS. So, the amount of translation professionals who never uses Windows was below 2%. <br /><br /><...><br /><br />After SDL/Trados merger, SDL translation memory tools are indeed prevailing. Almost 60% of respondents use Trados and/or SDLX as their translation memory solution. Star Tranist (11.11%) is the third popular TM according to the feedback, and Wordfast and Déjà Vu account for 9.8% and 7.84% respectively. Other tools mentioned were across, Idiom, Logoport, MemoQ, Lingotek, Heartsome, MulitTrans, OmegaT, WordFischer and proprietary tools. Many respondents also named Passolo, Catalyst, RC-WinTrans, Helium, LocStudio and other localisation tools which, however, are beyond the scope of the paper. 4.9% of the respondents stated they don’t use any translation memory tool at all.</i><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-7614607322410975876?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-16480041806966999442007-12-14T10:04:00.001+09:002007-12-14T10:04:59.435+09:00NeoOffice 2.2.2 Patch 4NeoOffice 2.2.2 Patch 4 has just been released.<br /><br />It comes with (from the announcement):<br /><i><ul><br /><li>Improved Microsoft 2007 file handling<br /><li>Improved Asian text input and layout<br /><li>Closed a security hole in NeoOffice Base's underlying HSQLDB database engine<br /></ul><br />Patch 4 can be downloaded from the following URL:<br /><a href="http://www.neooffice.org/neojava/patch.php">http://www.neooffice.org/neojava/patch.php</a><br /></i><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-1648004180696699944?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-36871915279322979252007-12-13T15:56:00.000+09:002007-12-24T22:52:36.843+09:00OpenOffice.org localization: an easy way to deal with .sdf files<h2>What are .sdf files ?</h2><br /><br />A few days ago I <a href="http://mac4translators.blogspot.com/2007/11/openofficeorg-24-localization.html">wrote</a> about OpenOffice.org 2.4 localization update.<br /><br />For some reason related to the way SUN manages the UI/Help strings, the translation source file comes in a weird format: all the XML "<" and ">" etc are escaped with "\" and the file structure comes as a set of 2 lines pairs, the first line being the en-US original and the second line a placeholder for the target string.<br /><br />This placeholder contains sometimes the en-US string and sometimes a close approximate of what would be the translation of the source string in the target language. All this is nicely embedded into a lot of meta information that makes the file impossible to parse with normal human senses...<br /><br />Here is an example (without the meta information):<br /><br />String in the .sdf:<br /><pre>\<ahelp hid=\".\" visibility=\"hidden\"\>something in the .sdf\</ahelp\></pre><br />(.sdf is the extension SUN has created to name the format)<br /><br />SUN also provides translators with <a href="http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx21/">TMX files</a> of the whole UI/Help for a number of languages (de, es, fr, hu, it, ja, ko, nl, pl, pt-BR, pt, ru, sv, zh-CN, zh-TW, at the time of this writting).<br /><br />The TMX seem to have been created not from the original XML (with nicely encapsulating TMX 1.4 level2 tags) but from the funky .sdf file. Which means that all the original XML tags are found escaped as per the .sdf, alongside the translatable contents...<br /><br />So the above string would be exactly the same in the TMX:<br /><pre>\<ahelp hid=\".\" visibility=\"hidden\"\>something in the .tmx\</ahelp\></pre><br /><br /><h2>How to translate that ?</h2><br /><br />So, how to practically translate such files <b>while</b> making use of the TMX data ?<br /><br /><h3>The no brainer way...</h3><br /><br />Edit the .sdf file directly, possibly after renaming it to .csv and importing it into OpenOffice.org, where all the {tab} separated meta information fields will nicely fill their own column and leave the translatable contents on its own...<br /><br />It is not exactly translator friendly... But with a little playing with the column width you'll manage to have only the translatable parts displayed... <br /><br />This procedure allows translators to separately (and manually) do searches in the TMX or the glossary (<a href="http://g11nportal.sun.com/sungloss/login.jsp;jsessionid=7DC9D167D34BE1652EEC520004BDA7B2">Sun Gloss</a>) and to use the matched contents directly without having to play with the "\" too much.<br /><br />It is not very practical because the TMX data is embedded in plenty of XML tags and the result is thus not exactly pretty...<br /><br /><h3>The PO way</h3><br /><br />The <a href="http://en.wikipedia.org/wiki/Gettext">PO</a> way is not the best way to leverage the TMX contents. It also requires translators quite some editing when wanting to use TMX matches... Still, it seems to be the most common way to localize OpenOffice.org...<br /><br />PO files are provided by the team coordinators, they are created with the <a href="http://en.wikipedia.org/wiki/Translate_Toolkit">Translator's Toolkit</a>'s <a href="http://translate.sourceforge.net/wiki/toolkit/using_oo2po?DokuWiki=507cd1c5404c9fcafc3a273d3cc79314">oo2po</a> tool.<br /><br />The above .sdf contents would be converted like this:<br /><br /><pre>\\<ahelp hid=\\\".\\\" visibility=\\"hidden\\\"\\>something in the .po\\</ahelp\\></pre><br /><br />The reason is that oo2po wants to be smart and adds an extra layer of escape characters (the ugly and ubiquitous "\"). And as you see above, the number of added "\" depends on what has been escaped: a simple [\] will become [\\], but [\"] will become [\\\"] because PO wants to escape both [\] and ["] with another [\]...<br /><br />Now, it does not take much to see that matching that against the TMX data <b>will</b> be a problem. Even if the translator uses a smart PO editor to refer to the TMX there will still be a need to <b>add</b> all the ugly extra "\" that oo2po has added to the .sdf contents.<br /><br />Basically, oo2po adds a useless extra layer of complexity to an already complex process that also happens to render TMX matching pretty much useless.<br /><br /><br /><h3>The smart way that also happens to really ease the translator's work</h3><br /><br />Here we are. Now, to keep the post to a reasonable length, let me refer you to <a href="http://l10n.openoffice.org/servlets/ReadMsg?list=dev&msgNo=8394">the mail</a> I just wrote to the OOo-l10n-dev list where everything is explained.<br /><br />The idea is basically that, since the TMX matches the structure of the .sdf, then it is easier to work from the .sdf. But to make the TMX really useful it is necessary to make the .sdf contents easily handled by a tool that will also make full use of the TMX contents.<br /><br /><a href="http://sourceforge.net/project/showfiles.php?group_id=68187&package_id=214253">OmegaT</a> for example...<br /><br />Within OmegaT you can have automatic TMX and glossary (Sun Gloss export) matching, automatic file encoding handling, automatic file naming handling etc...<br /><br />So, there is a very small Java utility <a href="http://alex73.zaval.org/snapshots/OpenOffice/sdf2txt.jar">sdf2txt.jar</a> that basically extracts all the translatable contents of the .sdf file and outputs it as a "key=value" format that OmegaT can parse natively.<br /><br />From there you see what needs to be done...<br /><br />Basically:<br /><ul><br /><li>put the extracted files in the <b>/source/</b> folder of your newly created OmegaT translation project,</li><br /><li>put the TMXs in <b>/tm/</b>,</li><br /><li>put the glossary files (if any) in <b>/glossary/</b>,</li><br /><li>load the project...</li><br /></ul><br /> and enjoy translating in a Nice and Friendly to the translator Professional yet Free Computer Aided Translation tool....<br /><br /><h3>Another smart but regexpy way...</h3><br /><br />Before using the CSV trick above ensure that the line pairs are converted so that the 2 lines are put on one line.<br /><br />To do that in a text editor that supports regular expressions, search for:<br /><pre>^(.*)(en-US)(.*)\r^(.*)(fr)(.*)</pre><br />replace with:<br /><pre>\1\2\3\t\4\5\6</pre><br /><br />Now that your .sdf is "linearized", change its name to .csv and open it in OpenOffice by using "tab" as field separator and "nothing" as text delimiter.<br /><br />The tabs in the original .sdf create a number of columns from where you just need to copy the column with the en-US translatable contents.<br /><br />Paste that into a text file with the ".utf8" extension, load into OmegaT... Et voilà !<br /><br />You'll have to paste the contents of the translated file into the target part of the CSV file, convert back to a 2 lines pair set.<br /><br />The pattern we need to find to revert the 1 line blocks to 2 line blocks is something like:<br /><br />(something)(followed by lots of en-US stuff)a tab(the same something)(followed by lots of translated stuff)<br /><br /><pre>^([^\t])(.*)\t\1(.*)$</pre><br />and we need to replace it with:<br /><pre>\1\2\r\1\4</pre><br /><br />Make sure there are no mistakes (if there are any they are likely to appear right in the first lines).<br /><br />Now you should have your 2 lines block.<br /><br />Rename the file to .sdf and deliver...<br /><br /><h2>Conclusion</h2><br /><br />There are plenty of ways to deal with OpenOffice.org's localization files. But to make sure that the contents of the TMX can be fully leveraged (and with close to 70,000 segments, it would be a waste if it were not) there is a real need to <b>avoid</b> the PO files created by oo2po. Problem is, anything that involves the .sdf files directly requires a little bit of massaging...<br /><br />Ideally, SUN would provide XLIFF files that are created directly from the original XML files (and with empty targets), as well as properly encapsulating TMX files...<br /><br /><h3>Credits</h3><br /><br /><a href="http://alex73.zaval.org/snapshots/OpenOffice/sdf2txt.jar">sdf2txt.jar</a> has been created by Alex Buloichik. The word count included in the output may not be 100% exact but the extraction/merge works, which is what matters for now. The code is within the Jar file and the whole thing is GPLed. Thank you <b>very</b> much Alex.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3687191527932297925?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-43215905981280852472007-12-13T00:42:00.000+09:002007-12-13T15:38:05.271+09:00TMX, XLIFF, etc...Just to make sure you have them right at hand:<br /><br /><h2>LISA</h2><br /><br /><a href="http://www.lisa.org/">Localization Industry Standards Association</a><br /><br />LISA's <a href="http://www.lisa.org/standards/tmx/">TMX page</a><br /><br />LISA's <a href="http://www.lisa.org/sigs/oscar/">standards page</a><br /><br />LISA's <a href="http://www.lisa.org/globalizationinsider/">Globalization Insider</a><br /><br />LISA is also working on SRX, the segmentation exchange standard and TBX, the terminology exchange standard.<br /><br /><h2>OASIS</h2><br /><br /><a href="http://www.oasis-open.org/home/index.php">Organization for the Advancement of Structured Information Standards</a><br /><br />OASIS' <a href="http://wiki.oasis-open.org/xliff/FrontPage">XLIFF page</a><br /><br />OASIS' <a href="http://xml.coverpages.org/newsletter.html">XML Daily Newslink</a><br /><br />OASIS' <a href="http://www.oasis-open.org/specs/index.php">Standards page</a> (you may want to take a look at <a href="http://www.oasis-open.org/specs/index.php#dbv4.5">DocBook</a> and <a href="http://www.oasis-open.org/specs/index.php#opendocumentv1.1">OpenDocument</a>)<br /><br /><h2>W3C</h2><br /><br /><a href="http://www.w3.org/">World Wide Web Consortium</a><br /><br />W3C's <a href="http://www.w3.org/International/">Internationalization activity page</a><br /><br />W3C's <a href="http://www.w3.org/International/its/">Internationalization Tag Set page</a><br /><br />W3C's <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=i18n-tutorials">Translated articles page</a><br /><br /><h2>WHATWG</h2><br /><br /><a href="http://www.whatwg.org/">Web Hypertext Application Technology Working Group</a><br /><br />And while we are at it, something that is likely to appear on your desktops earlier than you think, <a href="http://www.whatwg.org/specs/web-apps/current-work/">HTML 5.0</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-4321590598128085247?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-76825785140872057602007-12-12T23:58:00.000+09:002007-12-13T15:38:38.395+09:00La traducción del software libre. Por Juan Rafael Fernández García.A series of 5 articles, in Spanish, that describe everything you need to know to localize Free Software, and software with free tools too. Most of the tools described in the paper are available for the Mac.<br /><br />From <a href="http://people.ofset.org/jrfernandez/">Juan Rafael Fernández García</a>.<br /><br /><ol><br /><li><a href="http://people.ofset.org/jrfernandez/edu/n-c/traducc_1/">Una oPOrtunidad de colaborar</a> <br />Aunque no seamos programadores, hay una gran oportunidad de contribuir en los campos de la documentación y de la traducción. Por una vez querer es poder, ¿queremos ser miembros activos de la comunidad?</li><br /><li><a href="http://people.ofset.org/jrfernandez/edu/n-c/traducc_2/">Los problemas de PO y el abrazo fuerte</a> En la primera entrega de esta serie hemos hablado de la tecnología gettext; ahora es el momento de resumir sus ventajas pero también de señalar sus defectos. Qué triste sería el artículo si no pudiéramos hablar también de las soluciones, de las alternativas...</li><br /><li><a href="http://people.ofset.org/jrfernandez/edu/n-c/traducc_3/">Memorias compartidas</a> Hablábamos en la segunda entrega del momento fácil de la enumeración destructiva de problemas. Es el momento de enfrentarnos a los que tenían con ver con la necesidad de compartir esfuerzos, herramientas y resultados. Vamos a examinar las respuestas.</li><br /><li><a href="http://people.ofset.org/jrfernandez/edu/n-c/traducc_4/">¿El momento de cambiar de herramientas?</a> No podemos cerrar el estudio sin examinar las propuestas de la industria de la traducción: la especificación XLIFF y sus herramientas. ¿Está el software libre a la altura?</li><br /><li><a href="http://people.ofset.org/jrfernandez/edu/n-c/traducc_5/">Cerrando el ciclo</a> El objetivo inmediato de esta serie de artículos es lograr la incorporación de voluntarios a los equipos de traducción, vamos a conocer estos equipos un poquito más de cerca.</li><br /></ol><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-7682578514087205760?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com3tag:blogger.com,1999:blog-6335460019316576281.post-62706453547485530652007-12-12T22:47:00.000+09:002007-12-13T15:37:34.781+09:00TMX Editor, locale4j, File2XLIFF4jA bunch of new exotic names for Mac...<br /><br /><h2>TMX Editor</h2><br /><br /><a href="http://tmx-editor.sourceforge.net/">TMX Editor</a> is <i>a Java Swing GUI built for working with files supporting the TMX localization standard.</i><br />I found the application yesterday and tried to open an OmegaT tmx file just to see what the tool was able to do and, well, nothing happened. I sent a mail to Matthew Gagne, the project manager and received this answer a few minutes ago:<br /><br /><i>It seems as if this problem relates to the version of the TMX standard that is implemented currently.<br /><a href="http://www.lisa.org/standards/tmx/">http://www.lisa.org/standards/tmx/</a> lists 1.4b as being the official revision level. The editor, however implements the newest <a href="http://www.lisa.org/standards/tmx/tmx2/">TMX 2.0 draft</a> standard using the <a href="http://locale4j.sourceforge.net/">locale4j</a> library. This was a decision made when we began localization of our other projects here. Unfortunately there seems to be compatibility issues between the two TMX formats (1.4b vs 2.0).</i><br /><br />Since TMX 2.0 is unlikely to be in widespread use before a while, Matthew also mentioned that he'd love if Java developers could join the project to work on backward compatibility with the current TMX version.<br /><br /><b>locale4j</b> is the library that is at the core of TMX Editor. It currently works only with TMX 2.0 data.<br /><br /><h3>License</h3><br /><br />Both TMX Editor and locale4j are licensed under the <a href="http://www.mozilla.org/MPL/MPL-1.1.html">Mozilla 1.1 License</a>, which is a <a href="http://www.gnu.org/licenses/license-list.html">Free Software License</a> not <a href="http://www.gnu.org/licenses/gpl-faq.html#WhatDoesCompatMean">compatible</a> with the <a href="http://www.gnu.org/licenses/license-list.html#GNUGPL">GPL</a>.<br /><br /><h2>File2XLIFF4j</h2><br /><br /><a href="http://file2xliff4j.sourceforge.net/">File2XLIFF4j</a> is quite another beast: <i>File2XLIFF4j is a java based library for converting files to the XLIFF standard.</i> The <a href="http://file2xliff4j.sourceforge.net/file2xliff4j_intro.html">overview</a> shows that the library is not exactly for the normal translator, but it is still important to know that such conversion libraries exist.<br /><br />Interesting to see that the overview author, Weldon Whipple, has a "<a href="http://www.lingotek.com/">lingotek</a>" email.<br /><br /><h3>License</h3><br /><br />File2XLIFF4j is licensed under the GPL.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-6270645354748553065?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-566472903712303332007-12-12T18:13:00.000+09:002007-12-13T15:38:55.208+09:00CEDICT for Apple Dictionary 1.0<a href="http://www.apple.com/downloads/macosx/home_learning/cedictforappledictionary.html">One</a> more dictionary for Dictionary.app<br /><br />Regarding the attempts at converting <a href="http://www.csse.monash.edu.au/~jwb/j_edict.html">edict</a> to the Dictionary.app format (see <a href="http://mac4translators.blogspot.com/search/label/Dictionary">previous</a> posts), well they have been successful, but the issue is how to distribute the data ? The solution Prof. Breen has chosen is to make the XML data available from the site, along with a how-to that explains how to build the data. This how-to is currently being written and hopefully, everything will be ready around Christmas...<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-56647290371230333?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com6tag:blogger.com,1999:blog-6335460019316576281.post-89034269026215160102007-12-09T19:03:00.000+09:002007-12-13T00:10:44.195+09:00Looking for a QuickLook plugin ?<h2>OSX Network</h2><br /><br /><a href="http://osx.hyperjeff.net/">OSX Network</a> is provided by Jeff Biggus and has a wonderful list of applications for OSX. OSX Network is also known for its extensive OSX development articles listing, to be found <a href="http://osx.hyperjeff.net/reference/CocoaArticles.php">here</a>.<br /><a href="http://osx.hyperjeff.net/Apps/apps?f=QuickLook&w=1">Here</a> is the page that lists all the registered QuickLook plugins. At the time of this writing, you can find plugins for the following file formats:<br /><br /><ul><br /><li>Brainsight QuickLook Generator - Supports medical image file formats</li><br /><li>Colorxml-QuickLook - XML QuickLook</li><br /><li>EPSQLPlugIn - EPS files</li><br /><li>flv.qlgenerateo - Flash FLV files</li><br /><li>Folder.qlgenerator - folder contents</li><br /><li>illust.qlgenerator - Illustrator files</li><br /><li>Mac2SpecQLPlugin - Spectrum SCR file</li><br /><li>QLEnscript - Programming code</li><br /><li>Quickcomic - Zip/cbz file</li><br /><li>QuickLook Script - AppleScript source</li><br /><li>TextMate in QuickLook - Renders QuickLook previews using TextMate highlighting</li><br /><li>Zip.qlgenerator - zip file contents</li><br /><li>ZipQuickLook - Zip file</li><br /></ul><br /><br />Keep the URL in your bookmarks to check the updates.<br /><br /><h2> hrmpf.com</h2><br /><br />Another site that has a list of QuickLook plugins (the two overlap a lot) is <a href="http://hrmpf.com">hrmpf.com</a>. The <a href="http://hrmpf.com/wordpress/218/quick-look-plugins-for-leopard">page</a> also has screenshots. Here again, the list seems to be updated quite often.<br /><br /><h2>Apple</h2><br /><br />And if you want to create you own plugin, <a href="http://developer.apple.com/documentation/UserExperience/Conceptual/Quicklook_Programming_Guide/Introduction/chapter_1_section_1.html#//apple_ref/doc/uid/TP40005020-CH1-DontLinkElementID_14">here</a> is Apple's developer docs.<br /><br />Apple does not seem to have a section dedicated to QL plugins on its download page...<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-8903426902621516010?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-81714856418378662902007-12-06T10:39:00.000+09:002007-12-06T11:06:24.033+09:00Nice Xmas present...It is not a Mac, but the machine has generated a huge lot of buzz since its inception.<br /><br />The <a href="http://laptop.org/">XO</a>, also known as the OLPC is there for you to <a href="http://www.laptopgiving.org/en/index.php">get</a> !<br /><br />Here are various links that actually tell something about the machine and the concept...<br /><br /><a href="http://dlweinreb.wordpress.com/2007/11/20/xo-the-next-lisp-machine/">XO, the next lisp machine ?</a><br /><br /><a href="http://video.google.com/videoplay?docid=-4285568518538296189">Ivan Krstic's Google Tech Talk</a><br /><br /><a href="http://www.freedom-to-tinker.com/?p=1206">One Laptop Per Child (New Version), Reviewed by 12-Year-Old</a><br /><br />And of course, <a href="http://en.wikipedia.org/wiki/Alan_Kay">Alan Kay</a>'s keynote at EuroPython 2006 <a href="http://mrtopf.tv/vlog/2006/07/europython-2006-keynote-by-alan-kay.html">part 1</a>, <a href="http://mrtopf.tv/vlog/2006/07/europython-2006-keynote-by-alan-kay_19.htmll">part 2</a> and <a href="http://mrtopf.tv/vlog/2006/07/europython-2006-keynote-by_115334573228249388.html">part 3</a>, with a <a href="http://www.artima.com/weblogs/viewpost.jsp?thread=167318">summary</a> by <a href="http://en.wikipedia.org/wiki/Guido_van_Rossum">Guido van Rossum</a><br /><br />Computing does not have to be dumb !<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-8171485641837866290?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-41227826863545713352007-12-04T23:29:00.002+09:002007-12-04T23:32:48.191+09:00References to emails in other applicationsDaringFireball has an <a href="http://daringfireball.net/2007/12/message_urls_leopard_mail">article</a> on how emails can be linked to in other applications.<br /><br />Interesting if you need to keep track of clients' mails for a given project. John Gruber even published an Applescript that makes this feature even easier to use.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-4122782686354571335?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-18521547001157765962007-12-02T14:40:00.000+09:002007-12-02T15:51:44.482+09:00Maxprograms is back !<h2>About Maxprograms</h2><br /><br /><a href="http://www.maxprograms.com/">Maxprograms</a> is manned by Rodolfo Raya, of Heartsome and XLIFF fame. Maxprograms used to provide a few free Java utilites that were later included in Heartsome's Translation suite. Rodolfo quit Hearstome a few weeks ago and decided to put all his utilities back on Maxprograms' site.<br /><br /><h2>The tools</h2><br />The <a href="http://www.maxprograms.com/freetools.html">free tools</a> that are now distributed directly from his site are:<br /><br /><dl><br /><dt>TMXValidator</dt><br /> <dd>TMXValidator checks your documents against TMX DTD and also verifies if they follow the requiremenst described in TMX specifications.</dd><br /><dt>TBXMaker</dt><br /> <dd>TBXMaker converts glossaries stored in CSV (Comma Separated Values) to TBX (TermBase eXchange) format.</dd><br /><dt>CSVConverter</dt><br /> <dd>CSVConverter converts glossaries stored in CSV (Comma Separated Values) to TMX (Translation Memory eXchange) standard.</dd><br /><dt>Java Properties Viewer</dt><br /> <dd>A tool specially created for viewing translated Java .properties files comprising languages not supported by the ISO 8859-1 character encoding.</dd><br /><dt>MARTIF to TBX Converter</dt><br /> <dd>A program designed to convert glossaries in MARTIF format, also known as ISO 12200, to TBX format.</dd><br /><dt>RTFCleaner<dt><br /> <dd>RTFCleaner removes hidden text and Trados/Wordfast markup from translated Tagged RTF files.</dd><br /></dl><br /><br />It is very nice to see that they are now available without having to download the full HTS package.<br /><br /><h2>Dependancies</h2><br />The utilities require Java 1.5 or better. Which means that for the time being they can be used only on OSX 10.4.8 or better. See Apple's <a href="http://www.apple.com/support/downloads/javaformacosx104release5.html">download page</a> if you only have Java 1.4. Java 1.5 is the default version on Leopard.<br /><br />Since the utilities were included with Heartsome's Translation Suite they can be put to even better use in a workflow that involves HTS.<br /><br /><h2>Free software ?</h2><br />Currently, only <b>TMXValidator</b> has been released as a free to use source package. The license Maxprograms used is the <a href="http://www.eclipse.org/legal/epl-v10.html">Eclipse Plugin License v. 1.0</a>. This makes TMXValidator free (as in free speech) software, but the EPL v. 1.0 not being compatible with the GPL it <a href="http://www.gnu.org/licenses/gpl-faq.html#WhatIsCompatible">won't be possible</a> to use the source code for inclusion in GPLed products.<br /><br />All the other utilities are not (yet ?) available as free software, they are just free as in "free beer".<br /><br /><br />Anyway, thank you very much for your work Rodolfo ! And good luck to Maxprograms !<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-1852154700115776596?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-18468668772207388352007-12-02T11:02:00.000+09:002007-12-15T19:03:27.633+09:00Kazunari Hirano interviewKazunari Hirano is a long time contributor to the OpenOffice.org Japanese community and has recently been involved with Open Solaris and its localization community.<br /><br />He was recently interviewed by both Reiko Saito, Japanese Language lead at SUN for Solaris, Java and Sun Java Enterprise System and by Jim Grisanzio, Sr. Program Manager, OpenSolaris Engineering at Sun.<br /><br />Reiko is also very active in the OpenOffice.org Japanese localization community where she helps us a lot.<br /><br />The interview has been conducted in Japanese and English and is available on both <a href="http://blogs.sun.com/reiko/entry/インタビュー_interview_with_khirano">Reiko's blog</a> and <a href="http://blogs.sun.com/jimgris/entry/contributor_interview_kazunari_hirano">Jim's</a>.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-1846866877220738835?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-53548950545743474052007-12-02T10:41:00.000+09:002007-12-02T14:19:06.978+09:00Apples and Windows...Just like with oranges, apples and windows do not compare.<br /><br />Still, if you really need to have both on the same machine, there are ways to do that.<br /><br />As a minimal introduction, check Bill Clementson's <a href="http://bc.tech.coop/blog/071129.html">article</a> on the subject.<br /><br />Then, if you really need to stay on the Mac with the occasional Windows application, you may want to take a look at a few recent threads on the <a href="http://tech.groups.yahoo.com/group/MacLingua/messages/1969?xm=1&m=p&tidx=1">MacLingua</a> forum (subscription required), where a few CAT tools are discussed in the context of Windows on Mac.<br /><br />Now, if you want to dream a little, check this <a href="http://arstechnica.com/journals/apple.ars/2007/11/30/uncovered-evidence-that-mac-os-x-could-run-windows-apps-soon">article</a> on Ars Technica or this <a href="http://www.winehq.org/pipermail/wine-devel/2007-November/060846.html">thread</a> (for geeks) on the Wine HQ mailing lists...<br /><br />By the way, Wine is yet another means to get Windows on your Mac. From the site:<br /><br /><i>Wine is an Open Source implementation of the Windows API on top of X, OpenGL, and Unix.<br /><br />Think of Wine as a compatibility layer for running Windows programs. Wine does not require Microsoft Windows, as it is a completely free alternative implementation of the Windows API consisting of 100% non-Microsoft code, however Wine can optionally use native Windows DLLs if they are available. Wine provides both a development toolkit for porting Windows source code to Unix as well as a program loader, allowing many unmodified Windows programs to run on x86-based Unixes, including Linux, FreeBSD, Mac OS X, and Solaris.</i><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-5354895054574347405?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-4908975225136014342007-12-01T12:05:00.000+09:002007-12-13T15:41:40.513+09:00BetterZip Quick Look GeneratorAnother developer has created a <a href="http://macitbetter.com/BetterZipQL-1.0">Quick Look plugin</a> that accesses the contents of all types of archives:<br /><br />From the site:<br /><i>The currently supported archive formats are: ZIP, TAR, GZip, BZip2, ARJ, LZH, ISO, CHM, CAB, CPIO, RAR, 7-Zip, DEB, RPM, StuffIt's SIT, DiskDoubler, BinHex, and MacBinary.</i><br /><br />The software costs $19.95 and comes with a one month free trial.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-490897522513601434?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-24919516969438202092007-11-28T22:08:00.000+09:002007-12-13T15:42:27.296+09:00Quick Look for zip files, foldersCurrently, Quick Look does not display anything interesting when you hit a folder or a zip file.<br /><br />With 2 free utilities you can hit the space bar and see a listing of the contents of a folder or of a zipped file...<br /><br />- <a href="http://d.hatena.ne.jp/t_trace/20071124/p3">Folder Quick Look Plugin</a><br />- <a href="http://d.hatena.ne.jp/t_trace/20071125/p3">Zip Quick Look Plugin</a><br /><br />Keep the pages in your bookmarks to see updates when they are released.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-2491951696943820209?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-56759794961329817522007-11-28T21:09:00.000+09:002007-12-13T15:45:36.406+09:00OmegaT 1.7.3 (with Mac bundle) released !First of all I'd like to thank all the people who have tested my Mac bundles for OmegaT.<br /><br />I used your comment to create the <a href="http://downloads.sourceforge.net/omegat/OmegaT_1.7.3_MacOSX.zip">official version</a> that is <a href="http://sourceforge.net/forum/forum.php?forum_id=759243">released</a> today.<br /><br />As you probably know, the OmegaT project puts the "<b>test</b>" label on versions that do not have up to date manuals but that are at least as stable as the stable version... Basically, <b>test</b> version have been thoroughly tested already by a number of power users and all the problems are supposed to have been ironed out.<br /><br />So go ahead, it won't bite you !<br /><br />The <a hef="http://downloads.sourceforge.net/omegat/OmegaT_1.7.3_MacOSX.zip">file</a>, once unzipped, becomes OmegaT.dmg and opens with 2 files:<br /><br />- documentation.html<br />- OmegaT.app<br /><br />The documentation.html file is exclusive (now) to the Mac package, and groups all the information per available language. I put the up to date manuals in <b>bold</b> so that you can see them right away. This is the case for the <b>English</b> manual exclusively as of today.<br /><br />The manual has been fully updated thanks to the work of the current documentation manager to reflect all the new features (check the <a href="http://omegat.cvs.sourceforge.net/omegat/omegat/release/changes.txt?view=markup&pathrev=release-1-7-3">changes.txt</a> file) and extra information like bidi languages handling and command line arguments.<br /><br />It's been a long time since OmegaT was released with a Mac bundle (1.4.4 was the last one if I remember well) and the current release manager and I are working on automating this process (instead of having to do everything by hand here).<br /><br />People who still want the rough edges of the "pure Java" version can still use the "<a href="http://downloads.sourceforge.net/omegat/OmegaT_1.7.3_Without_JRE.zip">OmegaT_1.7.3_Without_JRE.zip</a> file. It will behave exactly like previous OmegaT versions (as far as integration with OSX is concerned) and will allow for all sorts of command line arguments passing. The bundle is a little bit trickier to modify, you need to edit the .plist file inside the package to obtain the same results.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-5675979496132981752?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com1tag:blogger.com,1999:blog-6335460019316576281.post-37389282329017312052007-11-28T12:11:00.002+09:002008-04-21T00:33:54.070+09:00Java 1.6 for Mac !Apple has been criticized for not including Java 1.6 into Leopard. The current default is Java 1.5 when all the other platforms (Windows, Linux, Solaris etc) have access to Java 1.6...<br /><br />Since SUN opened the code of Java it is freely available for porting and modifications. What should happen eventually happened: somebody took the source code and ported it to Mac.<br /><br />The result is "<a href="http://landonf.bikemonkey.org/static/soylatte/">SoyLatte: Java 6 Port for Mac OS X 10.4 and 10.5 (Intel)</a>" by Landon Fuller. The performance seems to be pretty good too. See the <a href="http://headius.blogspot.com/2007/11/java-6-port-for-os-x-tiger-and-leopard.html">benchmark comparing Ruby on OSX and JRuby on Java 1.6/OSX</a> by Charles Nutter.<br /><br />With this release, OSX users are getting closer and closer to a stable release of Java 1.6 for their machine (only Tiger or Leopard).<br /><br />There is a <a href="http://docs.info.apple.com/article.html?artnum=307208">developer preview from Apple</a>, but it only works under Leopard and you need to be registered as a developer to access it (registration is free).<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3738928232901731205?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-31624313415615035382007-11-28T11:07:00.001+09:002007-11-28T11:30:04.471+09:00OpenOffice.org 2.4 localizationAlmost two weeks since the last post. Amazing how 3 kids can suck your energy into nether...<br /><br />Today's first post is an announcement.<br /><br /><a href="http://www.openoffice.org/">OpenOffice.org</a> is a free office suite that a lot of translators already use for its compatibility with MS Office and the fact that, well, it is a free download and a free use application. OpenOffice.org is developped in part by SUN Microsystem, contributions come from IBM and other major players in the software industry and there is a very strong community of users and volunteers that exchange in a variety of languages. The "<a href="http://projects.openoffice.org/native-lang.html">Native Language Confederation</a>" is where all the non-English things take place.<br /><br />OpenOffice.org is thus localized by this community of communities under a separate project called, obviously, the "<a href="http://l10n.openoffice.org/">Localization Project</a>".<br /><br />The current available version of OpenOffice.org is version 2.3. Version 2.4 is expected to be <a href="http://wiki.services.openoffice.org/wiki/OOoRelease24">released</a> sometimes at the beginning of March and the localization efforts will thus start very soon.<br /><br />Translators on Mac who do not use OpenOffice.org but prefer NeoOffice should be aware that all the localization work that goes into OpenOffice.org is automatically "recycled" into NeoOffice.<br /><br />So, the deal is: you're enjoying a wonderful free office suite, and somehow you feel guilty for not having had to pay for it, or you feel that you'd love to "pay something back" but not being a programer you are not sure where to start...<br /><br />Well, you are a translator by trade, aren't you ? Localization is where your skills can be used the best. <a href="http://wiki.services.openoffice.org/wiki/Translation_for_2.4">Here</a> is where you'll be able to find all the necessary informations for this version's translation.<br /><br />There are TMX files <a href="http://ooo.services.openoffice.org/pub/OpenOffice.org/cws/upload/localization/tmx21/">available</a> for some language communities and since the source files are in the PO format you can translate them in your favorite CAT tool.<br /><br />First, get in touch with the translation group within your language community (from the Native Project <a href="http://projects.openoffice.org/native-lang.html">page</a>: click on your language community, go to the relevant page from there, either "contributions" or "participation" or "projects" etc. and propose your help !<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3162431341561503538?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-53982095511304802592007-11-16T11:14:00.000+09:002007-11-17T16:59:24.162+09:00OSX 10.5.1, Safari 3.0, TextEdit...It took Apple three weeks to <a href="http://docs.info.apple.com/article.html?artnum=306907">address</a> the most problematic bugs in Leopard. Good job ! The security contents of the update are detailed <a href="http://docs.info.apple.com/article.html?artnum=307004">here</a>. See also the relevant TidBits link in the feed box below.<br /><br /><strong>Update</strong>: Heise Security's <a href="http://www.heise-security.co.uk/news/99104">opinion</a> on the fixes.<br /><br />Safari 3.0, shipped in 10.5, includes a WebKit update that will certainly improve our Web experience. The <a href="">Ars Technica</a> article gives an interesting perspective on the WebKit market and <a href="http://webkit.org/blog/122/webkit-3-10-new-things/">WebKit.org</a> gives a technical review that highlights the main new features. This new version of the WebKit is available in Leopard and in the latest Tiger update (10.4.11) released yesterday.<br /><br />If you make a search in TextEdit now, you'll see that the search results are highlighted as they are in Safari. Much easier to see the searched string !<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-5398209551130480259?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-24578878806395446462007-11-15T17:44:00.000+09:002007-11-15T17:58:32.199+09:00Bento, NeoOffice, OSX 10.4.11<a href="http://www.filemaker.com/products/bento/features.html">Bento</a> is "<i>the new personal database from FileMaker that's as easy to use as a Mac</i>".<br /><br />Daringfireball's <a href="http://daringfireball.net/2007/11/bento">analysis</a> is quite interesting and convinced me to take a new look at Numbers for my simple database needs...<br /><br />NeoOffice has just release the <a href="http://www.neooffice.org/neojava/en/patch.php">second patch</a> for NeoOffice 2.2.<br /><br />And Apple has also released a point update: <a href="http://docs.info.apple.com/article.html?artnum=306297">OSX 10.4.11</a>, that contains Safari 3.0 and ships a number of other items and fixes.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-2457887880639544646?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-49203989151972670002007-11-14T00:34:00.001+09:002007-11-14T18:12:34.254+09:00XLIFF 1.2, TMX 2.0, etc.For some reason, my <a href="http://www.google.com/alerts">Google Alert</a> for XLIFF decided to inform me today of the existence of the <a href="http://docs.oasis-open.org/xliff/v1.2/cs02/xliff-core.html">XLIFF 1.2</a> specification on the <a href="http://www.oasis-open.org/home/index.php">OASIS</a> site...<br /><br />Since we're at it, the other relevant standard body, <a href="">LISA</a>, is also working very hard, to produce the next version of TMX: <a href="http://www.lisa.org/standards/tmx/tmx2/">TMX 2.0</a>. With Heartsome's Rodolfo Raya as the standard editor, we can be sure that HTS will be one of the first application suite to support the standard.<br /><br />Meanwhile, the <a href="http://www.w3.org/International/">Internationalization Activity</a> of the <a href="http://www.w3.org/">World Wide Web Consortium</a> has not ceased to produce very interesting documents, like an Updated Working Draft about the <a href="http://www.w3.org/blog/International/2007/11/05/updated_working_draft_best_practices_for_2">Best Practices for XML Internationalization</a>.<br /><br />The W3C's i18n group is also working on the <a href="http://www.w3.org/International/its/">Internationalization Tag Set</a>. Yves Savourel of Okapi Framework fame being the chair of that Working Group, you've already guessed that the framework already supports <a href="http://www.w3.org/International/its/links.html">a part</a> of this tag set...<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-4920398915197267000?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-85917749205923806632007-11-13T18:25:00.001+09:002008-03-01T17:52:43.009+09:00OpenWordFastChristmas in November !!!<br /><br />After the Okapi for Mono package 2 days ago, another package useable on the Mac has just been released: <a href="http://sourceforge.net/projects/openwordfast/">OpenWordFast</a>, a macro for OpenOffice.org that accepts WordFast translation memories.<br /><br />The project was registered on October 8th, which means that it is yet a little early to expect function parity with WordFast, currently it only accept 100% matches from the TM... But since the project is free software (GPL) I have no doubts that it will find a lot of contributors.<br /><br /><strong>Update</strong>:<br /><br />I received a mail from Oleg, OpenWordFast's developer after congratulating him for his work:<br /><br /><pre><br />Hi, Jean-Christophe.<br /><br />Thanks for your post. But OpenWordFast in the raw Beta stage. I'm not tested it on Mac yet.<br />Its lacks of vital functionality - Glossary, Terminology Recognition, search of not full match TU. <br /><br />But I plan to work on this list in the future releases.<br /><br />Best regards, Oleg Tsygany.<br /></pre><br /><br />Here we go !<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-8591774920592380663?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-37771841616801102622007-11-12T22:27:00.000+09:002007-11-12T22:42:44.186+09:00Transmug !Yves, apologies !<br /><br />Jost Zetzsche of <a href="http://www.internationalwriters.com/toolkit/">The Tool Kit</a>, <i>the</i> newsletter to read, even if Mac news are scarce, just reminded me of the existence of <a href="http://transmug.wordpress.com/">Transmug</a>, your group of Mac using translators...<br /><br />I found the <a href="http://transmug.wordpress.com/2007/11/02/preaching-to-a-big-choir/">Preaching to a Choir</a> post and liked the <a href="http://transmug.files.wordpress.com/2007/11/the-merits-of-using-a-mac.pdf">PDF (10 mb)</a> presentation attached to it.<br /><br /><b>ps</b>: Amazing the number of Yves related to Mac and translation. Yves Averous of Transmug, Yves Savourel of the <a href="http://okapi.sourceforge.net/">Okapi Framework</a>, Yves Champollion of <a href="http://www.wordfast.net/">WordFast</a>...<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3777184161680110262?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-41502507754435499562007-11-12T18:12:00.000+09:002007-11-12T19:39:08.343+09:00Okapi tools for Mono !The <a href="http://okapi.sourceforge.net/">Okapi framework</a> is a set of applications designed to ease the work of the translator:<br /><br /><i>"The Okapi Framework is a set of interface specifications, format definitions, components and applications that provides an environment to build interoperable tools for the different steps of the translation and localization process.<br /><br />The goal of the Okapi Framework is to allow tools developers and localizers to build new localization processes or enhance existing ones to best meet their needs, while preserving a level of compatibility and interoperability. It also provides them with a way to share (and re-use) components across different solutions. The project uses and promotes open standards, where they exist. For the aspects where open standards are not defined yet, the framework offers its own. The ultimate goal is to adopt the industry standards when they are defined and useable.<br /><br />In short, the Okapi Framework aims at being a crucible where we forge common components that can be used in any localization and translation application, providing faster development time and better interoperability, but still allowing for the diversity of solutions."</i><br /><br />(quote from <a href="http://okapi.sourceforge.net/">http://okapi.sourceforge.net/</a>)<br /><br />Problem is, Okapi is developed on the <a href="http://en.wikipedia.org/wiki/.NET_Framework">.NET</a> platform, basically a Windows only platform.<br /><br />A few years ago, people on the Linux side have decided that .NET was a valuable platform and decided to create an implementation of .NET for Linux, that could run .NET applications out of the box. <a href="http://www.mono-project.com/Main_Page">Mono</a> was born.<br /><br />Mono was also made to run on OSX... The problem was that until recently Mono's support for .NET was not sufficient to run the Okapi tools and that the Okapi tools had not been written with the lowest common denominator in mind to run on Mono.<br /><br />Yesterday, Yves Savourel, lead developer of the Okapi Framework Project, released a first <a href="http://okapi.sourceforge.net/Release/Tikal/ReadMe_ForMono.htm">Okapi for Mono</a> package for testing on existing Mono environments (including OSX and Linux). The totality of the tools is not yet available but command line tools are said to work.<br /><br />As far as OSX workflows are concerned, Okapi can produce <a href="http://www.google.com/search?&rls=en&q=xliff&ie=UTF-8&oe=UTF-8">XLIFF</a> files (or OmegaT projects, or XLIFF files for OmegaT) from a number of localization/translation formats. It is now relatively trivial for OSX translators to deal with inDesign files, for example, as long as they are saved in the inDesign XML format (<code>.inx</code>). Okapi will convert the <code>.inx</code> files to XLIFF for translation in OmegaT and will convert the target files back to <code>.inx</code> for delivery....<br /><br />Very good news for translators on OSX and warm thanks to the Okapi team !<br /><br /><b>ps</b>: I'll post a detailed description of how to install Mono and Okapi on OSX in a few days for the readers who don't feel too adventurous. Meanwhile, here are the respective download pages:<br /><ul><br /><li><a href="ftp://www.go-mono.com/archive/1.2.5.1/macos-10-universal/0/MonoFramework-1.2.5.1_0.macos10.novell.universal.dmg">MonoFramework-1.2.5.1_0.macos10.novell.universal.dmg</a></li><br /><li><a href="http://sourceforge.net/project/showfiles.php?group_id=42949&package_id=251957">OkapiMono (Test Only)</a></li><br /></ul><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-4150250775443549956?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com2tag:blogger.com,1999:blog-6335460019316576281.post-36746365892723770692007-11-09T00:05:00.001+09:002007-11-12T21:32:28.132+09:00Dictionary.app development kitDictonary.app comes with a few dictionaries already, but limited to 2 languages: English and Japanese.<br /><br />What if you want to use other data sets there ?<br /><br />Apple has released a Dictionary Development Kit that you will find in <code>/Developer/Extras/Dictionary Development Kit/</code>, if you have installed the XCode tools.<br /><br />From a first glance, a dictionary file is basically a twisted XHTML file that gets massaged with perl scripts and a few command line applications, for use in the dictionary application.<br /><br />Here is the first part of the abstract from the file <i>Dictionary Format.rtf</i> located in <code>./documents</code><br /><br />"This document explains an XML schema that enables developing dictionaries / references that are compatible with Dictionary.app and other Dictionary Services. The schema defines the source code format for the dictionary. The dictionary source needs to be validated to make sure it is in the correct format. It is then processed by the Dictionary Build tool together with css and other auxiliary files, and packaged into a dictionary bundle. The dictionary bundle can be installed into one of the Library/Dictionaries folders to make it accessible from Dictionary.app."<br /><br />And here is the first entry in one of the sample provided (<code>./samples/JapaneseDictionarySample.xml</code>):<br /><br /> <pre><br /><span class="nxml-processing-instruction-delimiter"><?</span><span class="nxml-processing-instruction-target">xml</span> <span class="nxml-attribute-local-name">version</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">1.0</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-local-name">encoding</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">UTF-8</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-processing-instruction-delimiter">?></span><br /><span class="nxml-comment-delimiter"><!--</span><span class="nxml-comment-content"><br /> This is a sample dictionary source file.<br /> It can be built using Dictionary Development Kit.<br /><br /> Entry examples for Japanese dictionary, English-Japanese dictionary, and Japanese-English dictionary.<br /></span><span class="nxml-comment-delimiter">--></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-prefix">d</span><span class="nxml-element-colon">:</span><span class="nxml-element-local-name">dictionary</span> <span class="nxml-namespace-attribute-xmlns">xmlns</span>=<span class="nxml-namespace-attribute-value-delimiter">"</span><span class="nxml-namespace-attribute-value">http://www.w3.org/1999/xhtml</span><span class="nxml-namespace-attribute-value-delimiter">"</span> <span class="nxml-namespace-attribute-xmlns">xmlns</span><span class="nxml-namespace-attribute-colon">:</span><span class="nxml-namespace-attribute-prefix">d</span>=<span class="nxml-namespace-attribute-value-delimiter">"</span><span class="nxml-namespace-attribute-value">http://www.apple.com/DTDs/DictionaryService-1.0.rng</span><span class="nxml-namespace-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-element-prefix">d</span><span class="nxml-element-colon">:</span><span class="nxml-element-local-name">entry</span> <span class="nxml-attribute-local-name">id</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">annojou_j</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-prefix">d</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">title</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">案の定</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-prefix">d</span><span class="nxml-element-colon">:</span><span class="nxml-element-local-name">index</span> <span class="nxml-attribute-prefix">d</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">value</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">アンノジョウ</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-prefix">d</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">title</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">案の定</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-prefix">d</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">yomi</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">あんのじょう</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-tag-slash">/</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-prefix">d</span><span class="nxml-element-colon">:</span><span class="nxml-element-local-name">index</span> <span class="nxml-attribute-prefix">d</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">value</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">あんのじょう</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-prefix">d</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">title</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">案の定</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-prefix">d</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">yomi</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">あんのじょう</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-tag-slash">/</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-prefix">d</span><span class="nxml-element-colon">:</span><span class="nxml-element-local-name">index</span> <span class="nxml-attribute-prefix">d</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">value</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">案の定</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-prefix">d</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">title</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">案の定</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-attribute-prefix">d</span><span class="nxml-attribute-colon">:</span><span class="nxml-attribute-local-name">yomi</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">あんのじょう</span><span class="nxml-attribute-value-delimiter">"</span> <span class="nxml-tag-slash">/</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">h1</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">span</span> <span class="nxml-attribute-local-name">class</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">headword</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">あん‐の‐じょう</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">span</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">span</span> <span class="nxml-attribute-local-name">class</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">hyouki</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">【案の定】</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">span</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">h1</span><span class="nxml-tag-delimiter">></span><br /> <span class="nxml-tag-delimiter"><</span><span class="nxml-element-local-name">span</span> <span class="nxml-attribute-local-name">class</span>=<span class="nxml-attribute-value-delimiter">"</span><span class="nxml-attribute-value">meaning</span><span class="nxml-attribute-value-delimiter">"</span><span class="nxml-tag-delimiter">></span><span class="nxml-text">予想通りに事が運ぶさま。</span><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-local-name">span</span><span class="nxml-tag-delimiter">></span><br /><span class="nxml-tag-delimiter"><</span><span class="nxml-tag-slash">/</span><span class="nxml-element-prefix">d</span><span class="nxml-element-colon">:</span><span class="nxml-element-local-name">entry</span><span class="nxml-tag-delimiter">></span></pre><br /><br /><br />(Side note: interesting to see that <code>.xml</code> files open in Dashcode by default.)<br /><br /><b>Update:</b> Apple has a full "Dictionary Services Programming Guide" available <a href="http://developer.apple.com/documentation/UserExperience/Conceptual/DictionaryServicesProgGuide/">here</a>. It also comes as a downloadable 1.3mb PDF <a href="http://developer.apple.com/documentation/UserExperience/Conceptual/DictionaryServicesProgGuide/DictionaryServicesProgGuide.pdf">file</a>.<br /><br />I have been trying to build a sample of <a href="http://www.csse.monash.edu.au/~jwb/j_edict.html">EDICT</a> provided for this purpose by Prof. Breen but even though the build process seems to be successful, Dictionary.app only displays that is finds an entry without actually displaying it... More later...<br /><br /><b>Update 2:</b> I have spent a good part of the week end testing Prof. Breen's sample. The documentation provided by Apple is really minimal so we had to try a lot of different things.<br /><b>hints</b>:<br /><ul><li>The IDs that are meant to be unique are not validated if they are entirely numerical, but it seems numerical values are handled without problems by the build process.</li><br /><li>The build process seems to have difficulties to properly build the dictionary if the project is not in the <code>/Developer/Extras/Dictionary Development Kit/</code> directory.</li></ul><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-3674636589272377069?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-55521747769121565592007-11-04T23:15:00.001+09:002007-11-04T23:38:06.470+09:00Regular expressions and text editing<h3>Regular expressions</h3><br /><br />When you edit glossaries or translation memories a few <a href="http://en.wikipedia.org/wiki/Regular_expression">regular expressions</a> always come in handy.<br /><br />Regular expressions are pattern matching expressions. You create a pattern in the search field of a text editor and the text editor will look for anything that matches the pattern. Similarly, once you have found the pattern, you can replace it with a second pattern. That way, you end up with super powerful search-replace routines that can save you hours of stress on thorny texts...<br /><br />Here are two articles that you can use to get up to speed on the topic:<br /><br />• <a href="http://www.cs.princeton.edu/introcs/72regular/">Regular Expressions</a> from Princeton University<br />• <a href="http://developer.apple.com/documentation/OpenSource/Conceptual/ShellScripting/index.html?http://developer.apple.com/documentation/OpenSource/Conceptual/ShellScripting/PortingScriptstoMacOSX/chapter_8_section_1.html">Regular Expressions Unfettered</a> from Apple Developer Connection<br /><br />As you can see, regular expression creation is not always an easy task and a helper application can sometimes save you a lot of time.<br /><br />There are a few <a href="http://www.fsf.org/">free</a> regexp testers for OSX but they basically all work from outside your text editor.<br /><br />The one that seems to be the easiest to use is <a href="http://reggyapp.com/">reggy</a>, a nice piece of software licensed under the <a href="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html">GNU General Public License v2</a>.<br /><br />On his blog, <a href="http://bc.tech.coop/blog/071103.html">Bill Clementson</a> talks about <a href="http://www.newartisans.com/downloads_files/regex-tool.el">regex-tool.el</a>. As the name indicates, regex-tool.el is an <a href="http://www.gnu.org/software/emacs/emacs-lisp-intro/html_node/index.html">elisp</a> library for Emacs<br /><br />Besides for text editors, regular expressions are supported by all kinds of software. Including, of course, the major Office applications on the market. Look at their user manuals to find more information about regexp handling there.<br /><br /><h3>Text editing</h3><br /><br />A number of very good text editors are available for the Mac. <a href="http://www.google.com/search?client=safari&rls=en-us&q=Apple+TextEdit&ie=UTF-8&oe=UTF-8">TextEdit</a>, OSX's default text editing application, is fine but lacks even basic regular expressions support. It does plenty of other things though, and can be considered as a simple word processor with most of what is needed in that field (read and write Word files etc).<br /><br />Others major text editors on Mac include:<br />• <a href="http://smultron.sourceforge.net/">Smultron</a> (free as in "speech"),<br />• <a href="http://www.barebones.com/products/textwrangler/">TextWrangler</a> (free as in "beer"),<br />• <a href="http://www.codingmonkeys.de/subethaedit/">SubEthaEdit</a> (not free, except for the old version),<br />• <a href="http://www.barebones.com/products/bbedit/">BBEdit</a> (not free at all) and<br />• <a href="http://macromates.com/">TextMate</a> (not free either and with very bad multibyte characters support).<br /><br />There are also the "ancestors" that are <a href="http://www.vim.org/">VI (VIM)</a> and <a href="http://www.gnu.org/software/emacs/">Emacs</a>. Both are available from the Terminal application but require some time to get used to. Still, they are definitely some of the most powerful application OSX hosts...<br /><br />Emacs is not exactly the text editor that I'd recommend to my wife. But <a href="http://aquamacs.org/">Aquamacs</a>, a "Mac" version in terms of interface is much friendlier and can <i>almost</i> right away be used as a replacement for TextEdit as far as, well, text editing is concerned. Being an adaptation of Emacs, it is just as free and also distributed under the GNU General Public License...<br /><br />Emacs is written in Elisp. So anything you write in Elisp within Emacs can de-facto extend the functionality of Emacs. In other words, Emacs is just a huge macro editing environment...<br /><br />Whichever text editor you decide to use, don't forget to read the user manual and especially the "searches" and "regular expressions" chapters.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-5552174776912156559?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-9849376001407311042007-11-02T18:38:00.001+09:002007-11-02T18:46:19.894+09:00Automation on the Mac !<h3>AppleScript</h3><br /><br />Apple just updated the <a href="http://www.apple.com/applescript/index.html">AppleScript section</a> of its site.<br /><br />I have never found a practical way to use AppleScript in my workflows... Hopefully the new version and better integration between applications and OS will make that a no-brainer now...<br /><br /><h3>Automator</h3><br /><br />I have more hopes for Automator, especially the new version that has full access to the user interface (see <a href="http://mac4translators.blogspot.com/2007/10/what-i-like-in-osx-105.html">here</a>).<br /><br />Here is the state of the documentation about <a href="http://developer.apple.com/macosx/automator.html">Automator</a> on Apple's developer's site. It is not updated yet for Leopard but is a very good start (after the Help files themselves) for people who want to take a serious look at this technology.<br /><br />It is also possible to create actions with AppleScript or other easy to learn languages.<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-984937600140731104?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-45830913437714231542007-11-02T14:34:00.001+09:002007-11-04T15:19:54.604+09:00OmegaT development status for OctoberIt is nice to see on OmegaT's <a href="http://sourceforge.net/projects/omegat/">development site</a> that October has been quite an <a href="http://sourceforge.net/project/stats/?group_id=68187&ugn=omegat&type=&mode=alltime">active month</a>.<br /><br />For those who don't know what OmegaT looks like, take a look at the <a href="http://sourceforge.net/project/screenshots.php?group_id=68187&ssid=47042">screenshots</a>, and read the online <a href="http://sourceforge.net/docman/display_doc.php?docid=61937&group_id=68187">documentation</a>.<br /><br />Back to the stats.<br /><br />Project rank was <b>137</b>, which is the highest ever in the project's history (out of more than a 100,000 projects). The Downloads figure was <b>3,466</b>, which is second best, after November 2006 (4,127), when the first build in the 1.6 series was released. Of course, the downloads figure includes the current stable and test versions as well as a few other packages.<br /><br />This 3,466 figure comes right after the latest test version (<a href="http://sourceforge.net/project/showfiles.php?group_id=68187&package_id=214253">OmegaT 1.7.2</a>) was released, at the end of September.<br /><br />The <b>Mac OSX</b> zip packages that are available for the stable version (<a href="http://downloads.sourceforge.net/omegat/OmegaT_1.6.1_04_MacOSX.zip?use_mirror=nchc">1.6.1_04</a>) and for the test version (<a href="http://downloads.sourceforge.net/omegat/OmegaT_1.7.2_MacOSX.zip?use_mirror=nchc">1.7.2</a>) are soon going to be replaced with a real MacOSX application bundle that will make OmegaT even easier to use on the Mac.<br /><br />The development code is available through the Terminal application, or any CVS interface.<br /><br />Here is a rudimentary shell script that I use to update the sources and build them (you will need the OSX developer's tools installed, available from the install DVD):<br /><br /><pre><br />#!/bin/sh<br />cd ~/Documents/OmegaT/application/current_cvs/<br />cvs -z3 -d:pserver:anonymous@omegat.cvs.sourceforge.net:/cvsroot/omegat co -P omegat<br />cd omegat<br />ant<br />cd dist<br />open -e readme.txt &<br />open -e changes.txt &<br />java -jar OmegaT.jar &<br /></pre><br /><br />I am sure there are things to improve here, but it works for me :).<br /><br />The current code in CVS is labelled OmegaT 1.8 and includes the OpenOffice.org spellchecking engine etc.<br /><br />The <a href="http://omegat.cvs.sourceforge.net/omegat/omegat/release/changes.txt?view=markup">changes.txt</a> file indicates the features that have been implemented, the bugs that have been fixed and the localizations that have been added.<br /><br />Feel free to test and look for bugs !<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-4583091343771423154?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com2tag:blogger.com,1999:blog-6335460019316576281.post-79890510377603170072007-11-02T11:52:00.009+09:002008-08-10T19:30:38.091+09:00Office 2007 files (.docx, .xlsx, .pptx) on Mac(updated to reflect the release of StarOffice 9 for Mac and the OOXML conversion software for Office 2004)<br /><br />Microsoft Office 2007 for Windows (and its Mac counterpart: Microsoft Office 2008) uses a new file format that has been available for a while now as .docx, .xlsx or .pptx ("x" to distinguish them from the standard MS formats).<br /><br />The file format is commonly known as <a href="http://en.wikipedia.org/wiki/Office_Open_XML">OOXML</a> or OpenXML, or more simply as Microsoft Office 2007 format.<br /><br />Even if the new files don't seem to be very widely used, they sometimes end up on a Mac user's desktop, especially since they are the default file format of the two suites (i.e., you need to go through a number of loops to save to a different format)...<br /><br />What to do when you encounter such files ?<br /><br />Since I do not own Office 2008 and I did not have the OOXML update for Office 2004 at the time of the writing, I had to test access with OOXML files created with NeoOffice, from "real" Microsoft .doc, .ppt and .xls. All of the test files were pretty complex and quite heavy and had all been created originally on various versions of Microsoft for Windows.<br /><br /><h2>Access through proprietary applications</h2><br /><br /><h3>The iWorks '08 way</h3><br /><br /><b>iWorks: $79</b> from Apple<br /><br />As far as I can tell, iWorks '08 applications Pages and Keynotes opened the .docx and .pptx files I had created without any problems.<br /><br />And the result was as good looking as the original files. Very impressive.<br /><br />When I tried to open the .xlsx file, Numbers was considered as the default application (even the converter was not listed) but it was unable to open it correctly. I'll need to have a "genuine" .xlsx file to test Numbers' capacities.<br /><br />The problem with iWorks it that it cannot save a file to the new format. It can save it to the iWords default format or to the old Microsoft format, along with a few other more classical formats.<br /><br /><br /><h3>The Microsoft way</h3><br /><b>Microsoft Office 2008: $399.95 retail, $284.99 online, $239.95 retail upgrade version, $194.99 online upgrade version</b> from Microsoft.<br />(The prices given correspond to the cheapest available version for professionals, the "Home & Student" package is not available for commercial activity.)<br /><br />The Mac equivalent of Office 2007, Office 2008, has been available for a few months already. Office 2008 is the quickest way to access the new file format in a relatively smooth and painless way.<br /><br />If you don't want to acquire Office 2008, you can download Microsoft's "Open XML File Format Converter for Mac". The application is available from <a href="http://www.microsoft.com/mac/downloads.mspx?pid=Mactopia_AddTools&fid=6B9238E1-CF69-48C4-BF2D-C4A8ACEEE520#viewer">here</a>. It is at the bottom of the page, if the URL has not changed...<br /><br />The converter requires OSX 10.4.8 or later. Microsoft also says that to view the files, you need either Microsoft Office 2004 11.3.4 or later, or Microsoft Office v.X 10.1.9 or later.<br /><br />If you also install "Microsoft Office 2004 for Mac 11.5.0 Update" (description available here: <a href="http://support.microsoft.com/kb/953824">http://support.microsoft.com/kb/953824</a>) you'll also enable "Office 2004 for Mac to read and to write Office documents that are in Open XML Format".<br /><br /><h3> The StarOffice 9 (beta) way</h3><br /><b>StarOffice: $69.95</b> (StarOffice 8 price, 9 is still beta), from Sun Microsystems.<br /><br />StarOffice 9 beta is available from here:<br /><a href="http://www.sun.com/software/staroffice/get_beta.jsp">http://www.sun.com/software/staroffice/get_beta.jsp</a><br /><br />It should work pretty much as OpenOffice.org 3.0 beta. See below.<br /><br /><h3>System wide support on Leopard (OSX 10.5)</h3><br />Leopard: $129, from Apple.<br /><br />If you don't (plan to) own any recent version of Office for Mac what can you do ?<br /><br />Leopard users have the free option of using the new TextEdit. It can open and save the new file format.<br /><br />OOXML support is system wide, which means that the Finder and other applications will also give you a "<a href="http://www.apple.com/macosx/features/quicklook.html">quicklook</a>" of such files. Although not all files are equal under Quicklook. Some are displayed properly, some are displayed as a white icon and no contents is shown... The test .pptx worked, the .docx and xlsx did not.<br /><br />So, support is not extremely good and I would not rely on it to check the translatable contents of a client file...<br /><br /><h2>Access through free applications</h2><br /><br /><h3>OpenOffice.org and NeoOffice anyone?</h3><br /><br />Users on Panther (10.3) and above can use <a href="http://www.neooffice.org/neojava/en/download.php">NeoOffice</a> 2.2. NeoOffice is a sister application of <a href="http://porting.openoffice.org/mac/download/index.html">OpenOffice.org</a>.<br /><br />The current available version of the standard OpenOffice.org (2.4) does <b>not</b> include OOXML support but NeoOffice includes special goodies, like OOXML support, that are found in Novell's version of <a href="http://go-oo.org/">OpenOffice.org</a>, which is, sadly, not available for the Mac...<br /><br />As of May 7th, the beta version of OpenOffice.org 3.0 is <a href="http://download.openoffice.org/3.0beta/">available</a>. This version does include support for OOXML.<br /><br />As written above, I used NeoOffice to create Office 2007/OOXML files with various degrees of success in terms of interoperability. I am pretty sure NeoOffice could open relatively complex files since the files I fed it for OOXML output were fairly complex, although I'd need to test that.<br /><br /><h3>As text ?</h3><br /><br />An extreme way to access the contents of such files it to handle them as if they were zipped, unzip them and find the <b>document.xml</b> located somewhere in the folder hierarchy that appears (it would be under /word/ for a Word document). This file is standard XML and can be opened in any text editor.<br /><br />To properly access the contents of the file, you'd need to use Okapi's Tikal utility, available for the Mono (free) running environment. Tikal should be able to extract the contents of the XML into an XLIFF file that you can later load into a translation tool...<br /><br /><br /><h2>Translation</h2><br /><br />Once you have access to the file, you can translate it by overwriting it in the application of your choice. Saving the resulting file to .docx will produce results that vary with the application you used. A best bet would be to save the result to .rtf for delivery.<br /><br /><h3>OmegaT and other Java based applications</h3><br /><br />If you want to use a translation memory tool, the few I know that directly handle OOXML are <a href="http://omegat.org/">OmegaT</a>, <a href="http://www.maxprograms.com/products/swordfish.html">Swordfish</a>, the newborn from Maxprograms, and <a href="http://heartsome.net/">Heartsome's Translation Suite</a>.<br /><br /><h3>Appletrans</h3><br /><br />If you have converted the file to .rtf or HTML before translation, <a href="http://developer.apple.com/internationalization/localization/tools.html">AppleTrans</a> should be able to handle it directly.<br /><br /><h3>Okapi's Tikal for conversion to XLIFF</h3><br /><br />Or, as written above, you can use Okapi's Tikal command line utility to convert its contents to XLIFF and translate it in any of the above mentioned applications.<br /><br /><h3>Wordfast</h3><br /><br />The Microsoft converter opens the file in Word in the RTF format and you can then use <a href="http://www.wordfast.net/index.php?whichpage=products&lang=engb">WordFast</a> to translate it directly (from within Word 2004 / Word v.X).<br /><br /><h3>OpenLanguageTools</h3><br /><br />With hacks, you can also translate the document.xml file in <a href="https://open-language-tools.dev.java.net/">OpenLanguageTools</a>.<br /><br />Have I forgotten your favorite tool ?<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-7989051037760317007?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com4tag:blogger.com,1999:blog-6335460019316576281.post-69568070553630888722007-10-31T16:15:00.001+09:002007-10-31T22:46:15.206+09:00Java applications on LeopardIt seems Java developers are very disappointed by the fact that not only does Leopard not ship with Java 1.6 but that the Java 1.6 preview available from the Apple Developer Connection is simply gone.<br /><br />Does that mean that Java applications will stop working on Leopard ? No.<br /><br />Leopard comes with Java 1.5. Quote from <a href="http://developer.apple.com/java/">Apple</a>: "<i>Mac OS X includes the full version of J2SE 1.5, pre-installed with the Java Development Kit (JDK) and the HotSpot virtual machine (VM), so you don't have to download, install, or configure anything."</i><br /><br />So, you can still run <a href="http://omegat.org/">OmegaT</a>, <a href="https://open-language-tools.dev.java.net/">OpenLanguageTools</a>, <a href="http://heartsome.net/">Heartsome's Translation Suite</a> and any other software <b>that does not depend on Java 1.6</b> without a glitch, as far as I've tested.<br /><br />Some developers have reported that the Java 1.6 preview totally broke Java on Leopard but it is not the case for me... [see the update at the bottom]<br /><br /><br />Anyway, it is likely that Java 1.6 will be released soon as seems to believe Eric Burke of "<a href="http://stuffthathappens.com/blog/2007/10/28/os-x-java-definitive-timeline/">It's just a bunch of Stuff That Happens</a>"...<br /><br />Check this Apple Developer Connection <a href="http://developer.apple.com/java/download/">page</a> to see if you miss a Java 1.5 update on Tiger.<br /><br /><hr><br /><br /><i>ps1: OpenLanguageTools is not advertised as a Mac application but the UNIX version runs very well on Mac.</i><br /><br /><i>ps2: Heartsome will soon release version 7 of its suite.</i><br /><br /><b>update:</b> Java 1.6 did indeed break a few things. When Leopard is installed the Java preferences in /Applications/Utilities/Java allow you to change the default JVM to Java 1.6. <b>Don't do that!</b> If you do, a number of processes that are meant to run with an unspecified version of Java will try to run with Java 1.6 and won't work. Since the Java Preferences also seems to call that unspecified version of Java, you will be stuck without being able to get back to a default Java 1.5.<br /><br />Well, there may be tricks to do get back there quickly, be the safest route seems definitely to remove Java 1.6. <a href="http://javablog.co.uk/">Javablog</a> indicates a straightforward <a href="http://javablog.co.uk/2007/10/26/apple-os-x-leopard-doesnt-have-java-6/">procedure</a> to do so. Not for the faint of heart! But that is the cost of using developer preview beta software...<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-6956807055363088872?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-14549348757934969702007-10-30T17:50:00.001+09:002007-10-31T16:29:13.401+09:00What I like in OSX 10.5Apple advertises over 300 new features in OSX 10.5. A lot of them have no immediate use for the translator but some of them really rock. <a href="http://www.apple.com/macosx/features/300.html">300+ New Features</a><br /><br />Here is my current and most immediate pick. The list will grow as I use them in real life.<br /><br /><h3>Spotlight</h3><br /><br />I never really used Spotlight, even on my relatively fast MacBook. Instead I had <a href="http://www.manytricks.com/butler/">Butler</a> as an application launcher and the standard Finder for file searches (even though the Finder used Spotlight technology).<br /><br />Now, Spotlight is all this and more.<br /><br /><ul><br /><li>it displays applications first, so that you can really use it as an application launcher. Even though it is not as sophisticated as Butler, it does the job very properly.<br /><li>searches are faster than on Tiger.<br /><li>it calculates as you type a formula. I used <a href="http://www.jwwalker.com/pages/plaincalc.html">PlainCalc</a> for that before, and even though PlainCalc is much more powerful than Spotlight, the later is currently just what I need most of the time.<br /><li>it acts as a (English) dictionary by showing you the first line of the definition of the word you type, clicking on the result will bring you to the Dictionary application.<br /></ul><br /><br /><a href="http://www.apple.com/macosx/features/300.html#spotlight">Spotlight on Apple's "New features" page.</a><br /><br /><h3>Dictionary</h3><br /><br />Dictionary now has a set of 3 Japanese dictionaries (Shogakukan) and also accesses Wikipedia in the main available languages. It is faster than launching Safari to find a reference online. The only drawback, when compared to Safari, is that Dictionary does not display the language versions links of the article you are reading which does not allow the user to jump to the target language in which the reference is sought.<br /><br /><a href="http://www.apple.com/macosx/features/300.html#dictionary">Dictionary on Apple's "New features" page.</a><br /><br /><h3>Automator</h3><br /><br />Automator now has a "Record" function that allows it to remember mouse activity on any application's menus. That allows for quick "macro" recording in applications that are not well integrated with OSX and/or that do not support AppleScript. Java applications for translators come to mind !<br /><br /><a href="http://www.apple.com/macosx/features/300.html#automator">Automator on Apple's New features" page.</a><div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-1454934875793496970?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com0tag:blogger.com,1999:blog-6335460019316576281.post-76122640563358348422007-10-30T17:08:00.000+09:002007-10-31T16:29:02.807+09:00What I miss in OSX 10.5<h3>The ability to have a different input system per window</h3><br /><br />This setting was present in Tiger under "International > Input Menu" at the bottom of the window, the same location in Leopard only indicates the keyboard shortcut to change of input method.<br /><br /><b>Use case:</b> you translate from a language that requests a different input system from the language you translate to. When you need to type a word in a dictionary to check its meaning, you change of window, change of input system, type, get the results, go back to the original window, go back to the original input system and type. Having the OS remember which input systems goes with which application is quite a time an annoyance saver...<br /><br /><h3>Clear visual clues to identify folders in the Dock</h3><br /><br />John Siracusa has a full page about that on <a href="http://arstechnica.com">Ars Technica</a>, with plenty of nice screenshots:<br /><br /><a href="http://arstechnica.com/reviews/os/mac-os-x-10-5.ars/13">Mac OS X 10.5 Leopard: the Ars Technica review: The Dock</a> By John Siracusa | Published: October 28, 2007 - 11:36PM CT<div class="blogger-post-footer"><hr/>
<a href="http://mac4translators.blogspot.com/2008/02/mac-for-translators-mailing-list.html">Mac for Translators, the mailing list...</a>
<hr/><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/6335460019316576281-7612264056335834842?l=mac4translators.blogspot.com' alt='' /></div>Jean-Christophe Helaryhttp://www.blogger.com/profile/05177466380850385765noreply@blogger.com1