From: Wayne W. <wa...@wa...> - 2007-09-16 21:27:11
|
I wasn't refering to auto compiling or machine translation. I was refering to automatic phrase matching. Like text-messaging chat I have it figured out in my head and will get it working soo. Basically, based on all the words in the current souce or phrase/segment the computer works out the total list of possible translations. Then as you type it matches your letters against the list to narrow down the combinations. If you have the sentence, "Tous the bons garcons veulent aimer une fille." There may be 3 to 5 or more possible translations in the glossary for eath word or combination. If when you type "a" and the only word in its like is "all" that starts with an a, it fill in the ll. But if you type a different letter next, it drops the assumption. It's called auto-completion. Used in select boxes on web sites, text messaging, etc. Plus if it lights up (like in Eclipse) because it has multiple words or phrases that start with that letter, I can just use the arrow keys to pick one and hit enter. Obviously, this will grow in usefulness with the robustness of the glossary used. But a tool like omega should have configurable shortcuts for most common words in a language based on word frequency. In most languages, there's less than 10 words that make up over 50 % of any text. I've been thinking what makes sense for short cuts.... Personally, I'd like to avoid using ctrl-t or alt-t or left-shift-t To type the word the. And CERTAINLY not T H E. Do you realize how much typing it would save if you can type "the" With one keystroke? It's by way THE most used word in THE english Language. It just occurred to me that holding down a key repeats it but that's useless in a translating tool. When do we ever hold down an alphabetic letter to type ttttttttt. We could so like ring tones. You press the first letter of a word. It shows the most popular word AUTOMATICALLY. But you can keep typing--it doesn't interfere. As you type letters, it narrows down the choice and if you see the word you want before you stop typing, then you pause a split second and it advances the cursor. I'd have to fiddle with it to make it smooth and get used to it. Take this sentence: The girl with the golden hair. All you would type is "tgwtgh" ideally instead of 25 keystrokes--a 500% reduction in keystrokes. Since there's a limited words that can translate from "La fille avec des cheveux d'ores" the guessing can be even more accurate than on ring tones. Trust me, I will figure out a faster typing system for translating! Wayne -----Original Message----- From: ome...@li... [mailto:ome...@li...] On Behalf Of Samuel Murray Sent: Sunday, September 16, 2007 4:52 PM To: Mailing list for OmegaT developers. Subject: Re: [OmTdev] The New KeyEventHandler Class Wayne Walter wrote: > What if you decide later down in a document that you pick a better > translation for a word or phrase that you already used 20 times in > the document? Just like in Java, the CAT should notice automatically > that you translated a phrase differently and offer you to change > it everywhere else. Etc. Etc. Etc. You have to wonder how these things will impact on workflow. Here are my thoughts: Having the ability to change a word that had been translated differently previously is nice, but when would you change it? Some translators might want to change it immediately, whereas others might want to change it at a certain interval, or only at the proofreading stage. These two approaches could both be satisfied with Wayne's multiple tabs approach. Here's how: if OmegaT realises that a word is translated differently (or if the user realises it), the user can request a report of all segments with this issue, and the report is displayed in a separate tab. The report tab displays only the segments with the issue, but is fully editable -- any changes made in it will be added to the TM. This report tab can be generated immediately or only at proofreading stage, whichever the translator prefers. Perhaps there could be a to-do tab in which the translator could make a note that he wants to create a report tab about such and such a word or phrase, so that he doesn't forget, but he isn't forced to do it immediately either. In fact, the report tab idea can be used even if automatic phrase recognition is absent. Some CAT tools do have automatic phrase recognition. Wordfast has it, but it only recognises source text phrases -- it is up to the user to check the report and decide where the target text begins or ends. > TMs and Glossaries need to all be integrated seemlessly. Relationships > need to color code and highlight on the fly. Yes, all these things will be added to OmegaT some day in future. > Words need to fill in automatically when a match is seen before you > see it yourself. No, if a CAT tool does this for me, I would uninstall it. For some languages and for some very technical texts it may be useful, but not for me in my languages (Afrikaans/English) and the types of texts I translated (all types). Having the option to autocompile is useful, but it should be an option and it should not be the default option. You're going to scare away serious translators if you have autocompile as the default behaviour because they will assume it can't be turned off. Bilingual phrase recognition is nice, but who's going to write it? I know of no CAT tool (even the very expensive ones) that can currently do it. Bilingual phrase extraction is possible in one or two cases (again, expensive closedsource tools with backing from multinational companies), so I guess it must be more difficult to write than other things. > Interestingly, TRADOS sells a lot for $900, why? People who make a living > doing translating (just like software developers) make great money > and need to reduce the repetitive work so they can be more productive. > > I rest my case. In my humble opinion, Trados sells because it markets aggressively and uses FUD a lot. And because it has some useful features. Samuel ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Omegat-development mailing list Ome...@li... https://lists.sourceforge.net/lists/listinfo/omegat-development |