السبت، 23 أغسطس 2014

NEW Version: SDL Trados Studio 2014 SP1 Professional

SDL Trados Studio 2014 SP1 Professional 11.1.4085

الأصدار الأحدث من العملاق ترادوس

Trados SP1 v. 11.1.4085


Translation software used by over 200,000 translation professionals. Would you like to be able to deliver projects faster? Wouldn't it be great if you could work on any file type sent by your customers? Think about how much time you could save if you didn't have to translate the same sentence again and again?
SDL Trados Studio, market-leading translation software, provides a range of sophisticated features to help you not only work more easily but also up to 20% faster* than previous versions of SDL Trados. Translation memory (TM) is at the heart of SDL Trados Studio and works by recycling previously translated content so that you can complete translations projects more quickly while maintaining high quality.
* 80% of translators surveyed agree that SDL Trados Studio allows translators to work up to 20% faster than SDL Trados 2007 Suite, 2007, 2006 and prior.

Key Features:

- Unlimited languages supported at once
- Single document translation - all 25 file formats
- Unlimited TM size
- Open multiple TMs at a time
- Open unlimited termbases
- Trados Word bilingual files
- Project wizard to automatically prepare multiple files / languages projects
- Full batch task functionality
- Customizable tasks
- Create SDL Packages
- Email SDL Packages
- Open SDL Packages from Professional Version without restrictions (excluding AutoSuggest)
- Open SDL Enterprise Systems - Packages (TMS / TeamWorks / WorldServer) without restrictions (excluding AutoSuggest)
- Alignment based TM Creation
- Upgrade legacy TM formats
- RevleX TM engine
- QuickPlace
- Real-time preview
- AutoSuggest (Use)
- AutoSuggest (Create)
- PerfectMatch (Create)
- Automated translation
- TM maintenance
- Creation of termbase (add / edit terms)
- Use of server-based TMs
- Use of server-based projects
- Reports view
- And much more!
A special thanks To MPT Team

 Install Notes:
1. First, unpack and install SDLTradosStudio2014_SP1_3931 installer.
2. That's the initial SP1 release.
3. Use offline update patches or go to program's interface and use online update.
4. Run the activator to register it.


Download:


Server 1: uploaded

Server 2: Baidu pan Password: me1f

الخميس، 21 أغسطس 2014

SDL Trados Studio and memoQ: side by side

SDL Trados Studio and memoQ: side by side


memoQ_studio icons

This year, I’ve revisited memoQ. I sounded it out four years ago (memoQ 4.5) but missed so many Studio features that I didn’t persevere. Fast forward to 2014. I’ve worked with memoQ quite intensively for six months now, first because an agency has been sending me on-line projects and later because I was really rather enjoying it. My impression? memoQ is now a mature product.
Similarities
Studio 2014 and memoQ 2014 share almost all the features that can be considered essential in a CAT tool. For example, they both offer:
  • customised QA, including highlighting of typos
  • bilingual Word file export for review
  • customised shortcuts
  • placeholders / autopick
  • variables / non-translatables
  • several Translation Memories at once
  • project templates
  • multiple filetypes
  • segments filtering by status, repetitions, etc.
  • localisation of dates, numbers
  • integrated Word comments
Instead of continuing this almost endless list, I think it would be more interesting to comment on some of the differences I’ve noticed. All from my point of view, of course.
Differences
Presentation and layout
  • Studio 2014 has a ribbon presentation, giving the whole interface a familiar feel to new users, with ribbon tabs emulating Office programs (home, view, advanced, etc.).
  • Layout is highly customisable. Windows can be easily undocked and moved around (or even placed on a second monitor).
  • The Editor window only displays segments side by side, not above-below.
  • memoQ has somewhat confusing menu commands and a looong line of tiny buttons, with tooltips when you hover over them.
  • I think the Zen and “Do not press this button” icons are space wasters, but I guess it takes all sorts…
  • memoQ has two main layouts that are easy to call up by toggling F11. Windows can also be undocked, although it’s not very intuitive.
  • The active row can be displayed horizontally (source above target), but otherwise there’s no above-below display.
Word processing features
  • AutoCorrect has been repeatedly requested on the SDL Ideas site, but is still missing in Studio.
  • The spellcheck works fast, although I prefer the Xbench plug-in where you can quickly run through a full list of ‘unknown words’.
  • This is neatly implemented in memoQ. AutoCorrect makes typing much faster (nO uPPERCASE by mistake or INitial CApital problems).
  • You can also import a Word AutoCorrect list with common misspellings and add customised abbreviations for long expressions.
  • Running the spelling and grammar check can be very slow.
Filtering
  • Studio’s search engine is based on regular expressions, so you can filter wider ranges of strings, such as segments containing certain number formats, or words spelt in two different ways.
  • Studio doesn’t let you search in source and target simultaneously.
  • You can’t perform a cascading filter.
  • memoQ has a big advantage here of searching for specific strings in source and target segments at the same time.
  • You can also set up a cascading filter, by searching for another string within the filtered results.
  • You can’t use regular expressions in the search boxes.
User friendliness*
* This is very subjective. It’s almost impossible for me to compare the two tools because I’ve spent thousands of hours using Studio and probably only hundreds of hours with memoQ. But since it’s a very important aspect, here goes:
  • First-time Studio users can get help under the “Get Started” tab in the Welcome view.
  • Most settings can be found under General Options or Project Settings. I think that’s quite straightforward.
  • memoQ has a neat Startup Wizard for first-time users.
  • My first on-line projects were easy because everything was set up for me, and I found it intuitive to move around the Translation Window.
  • However, when I started creating my own projects, I did (and still do) find it hard to distinguish between the Resource Console, Options and the Operations tab.
Merging
  • Out of the box, Studio 2014 lets you merge files on the fly, in a customised order, but you need to install the SDLXLIFF Toolkit app to create other views. Even so, the choices are more limited than in memoQ.
  • memoQ has a very rich views feature, where you can combine files, split individual files, or create views with certain elements (comments, changes, errors, status).
  • memoQ 2014 now even has a preview for these views, and lets you split/join rows too.
  • One drawback: you can’t use track changes in merged file views.
Working with projects
  • The Editor window in Studio lets you open several projects at once, under different tabs. This is useful if you’re working on one project, and have to make a quick change to another.
  • It’s easy to switch to the project list: just one click away.
  • In memoQ you can open multiple tabs (files and views), but they have to belong to the same project.
  • It’s a nuisance to have to close a project to view your project list on the dashboard.
  • Working/Master TMs have been introduced in memoQ 2014. Considering the confusion that separate project TMs caused in Studio (default project TMs were actually removed in Studio 2011), I was surprised to see this new feature in memoQ. Time will tell whether this has been a good move.
Terminology*
Translation England has recently published a blog post called Comparing Trados and memoQ in terms of terms.
  • SDL Multiterm is a standalone terminology tool with rich features and it’s integrated in the Studio Editor window.
  • It takes just two clicks to add a term on the fly.
  • It’s Java-dependent, which can make it unstable when Oracle brings out Java updates. SDL is apparently moving away from Java in the not too distant future. We all look forward to that.
  • This behemoth can be tamed by the OpenExchange Glossary Converter. Creating and converting termbases is much easier.
  • memoQ uses a simpler approach to terminology. Marking a term as forbidden, for example, is much more straightforward in memoQ (simply check the relevant box under the Usage tab in the Term Base view).
  • It takes just one click to add a term on the fly.
  • When several TBs are used, the Translation Results window doesn’t specify which TB the term comes from unless you click on the entry.
  • memoQ has a terminology extraction tool, which is useful for creating a termbase from scratch in a big project.
Track changes
  • Studio handles source files with track changes in native Word format.
  • It saves target track changes in the final formatted Word file.
  • These two features combined make Studio compliant with regulated industry requirements.
  • memoQ tackles track changes in a unique way. It keeps a record of version changes and marks changes in the current version accordingly.
  • However, these changes can’t be saved in the final file (only in an unformatted file when you “export changes to Word”).
  • Since track changes are virtual, source files with controlled track changes in regulated industries (e.g. EMA product information) can’t be processed in memoQ.
Subsegment suggestions / autosuggest / concordance
  • Studio builds autosuggest dictionaries from translation memories (with at least 10,000 segments) and its version of Predictive Typing (AutoSuggest) is based on TBs, A/S dictionaries and AutoText lists. The combination makes typing much faster.
  • Bad news: the A/S dictionary creation tool is an optional extra in the Studio Freelance edition.
  • Automatic concordance kicks in when no matches are returned in the TM.
  • The drawback of this system is that the oldest hits are returned first in automatic concordance.
  • memoQ uses Muses to provide subsegment suggestions in predictive typing. You can throw in TMs and Live Docs corpora and train memoQ to produce meaningful results.
  • Concordance results are displayed in the form of longest substring concordance in the translation results pane.
  • The disadvantage of such a wide source of resources for predictive typing is that there can be a lag in typing while memoQ comes up with suggestions.
Minor details that make memoQ that bit better:
  1. Automatic target document opening after exporting
  2. Source segments in other languages can be recognised and locked
  3. Unlimited languages
  4. Preview pane is HTML-based (no Word version issues)
  5. Reverse direction TMs can be used as reference
  6. Small footprint in your computer, i.e., it’s quick to download and install
Minor details that make Studio that bit better:
  1. Progress bar in Editor window shows the word count as well as a percentage
  2. Jump to a specific file in a merged file view
  3. Choose target file name on the fly
  4. Xbench integration
  5. Prompting options for auto-propagation
In both tools, I’d like to see:
  • An option for above-below segment display in the Editor window, not just side by side.
  • Improved help documentation. (Ever tried looking up how to add a “forbidden” term in Studio or a “synonym” in memoQ?)
  • Ultimately, fewer proprietary formats (imagine being able to drop a Studio TM into memoQ and vice versa). 
Which should you choose?
Studio and memoQ both have a demo version (30 days for Studio, 45 days for memoQ). Test them when you have plenty of time and see which you like best.
Work with both?
CAT hopping is a big productivity killer. Exporting proprietary TMs to tmx format is time consuming, and the Studio and memoQ widgets for TM lookup are not as flexible as a fully-fledged translation memory. Most shortcuts can be customised, so you can use the same ones for both tools, but the instinctive clicks you do without thinking to set up a project, change options and complete your translation are hard to reproduce in more than one environment.
I suggest focusing on one particular tool. After all, you can process memoQ xliff files in Studio, and Studio ones in memoQ, so this is probably the best solution of all.
Nevertheless, on-going familiarity with different tools is useful, because it’s important to know the different options that are available and how they develop over the years. Also, you may get sent on-line projects that have to be processed in a particular tool. That’s the only situation where you have no choice. Otherwise, take your pick.
المقال منقول من مدونة: