Quantcast
Channel: ProZ.com Translation Forums
Viewing all 29882 articles
Browse latest View live
↧

Studio 2017: Tracked Changes

March 14, 2018, 11:27 am
$
0
0
Forum: SDL Trados support
Topic: Studio 2017: Tracked Changes
Poster: MikeTrans

Hello,
is it possible to export tracked changes from Studio so that these changes are visible?
The "SDL XLIFF Converter for MS Office" apparently cannot do that, or yes?

Thank you,
↧
Search

Studio 2017: Tracked Changes | Problem solved...

March 14, 2018, 11:55 am
$
0
0
Forum: SDL Trados support
Topic: Studio 2017: Tracked Changes
Poster: MikeTrans
Post title: Problem solved...

When using the converter above, I have to export in MS Word, the changes are included, I just have to highlight the changes in MS Word.
↧
↧

SDL Studio: I hate it, I hate it, I hate it! | WOW!

March 14, 2018, 1:17 pm
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: Robert Rietvelt
Post title: WOW!

[quote]Michael Joseph Wdowiak Beijer wrote:

There, got that out of my system.

I have a permanent warning/reminder on my whiteboard that says "NEVER USE STUDIO AGAIN!" because every single time I use the program, something goes wrong at the very end, once I've finished translating, and I end up having to google thousands of error reports and waste a ton of my time.

I hate this program with a passion. The only reason I use it is because a lot of clients (agencies) own it and are stuck with it.

Michael [/quote]

Dear Michael,

I hardly dare to say it after reading your thread, but I am working with Studio since version 2009 (before that with Trados 2007), and I know nothing is perfect, but my Studio(s) (2014/2015) are working just fine. Sorry for the insult. :-)

Could it maybe be you are doing something wrong? (I know hard to imagine, but still....)

Isn't 'hate' a bit too far fetched here?

[Edited at 2018-03-14 20:18 GMT]
↧

SDL Studio: I hate it, I hate it, I hate it! | plug-ins

March 14, 2018, 1:26 pm
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: Mirko Mainardi
Post title: plug-ins

[quote]Michael Joseph Wdowiak Beijer wrote:

Anyone know what to do when you get told:

"Cannot validate SDL plug-in: Sdl.ProjectAutomation.AutomaticTasks.WIPReport.WIPReportTask, Sdl.ProjectAutomation.AutomaticTasks.WIPReport, Version= [IP removed] , Culture=neutral, PublicKeyToken=c28cdb26c445c888"?
[/quote]

Remove the plug-ins from Studio and use a vanilla version?
↧

How to import an excel glossary into an existing termbase? | Useful PDF that guides you step by step

March 14, 2018, 1:33 pm
$
0
0
Forum: SDL Trados support
Topic: How to import an excel glossary into an existing termbase?
Poster: Elisa Farina
Post title: Useful PDF that guides you step by step

Three years after the first entry of this string was posted I found myself facing the same issue. I bumoped into this PDF by Jayne Fox, followed the instructions and managed to carry out the task successfully:
[url removed]
(link to the page were I found it: [url removed] )

Two important notes:
1) I work with SDL MultiTerm 2015 and the process is the same.
2) The PDF is about importing the glossary in a new and empty termbase, but the process worked just as well with an existing and not at all empty termbase.
↧
↧

SDL Studio: I hate it, I hate it, I hate it! | The SDL AppStore Home = a double-edged sword

March 14, 2018, 1:44 pm
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: Michael Joseph Wdowiak Beijer
Post title: The SDL AppStore Home = a double-edged sword

[quote]Mirko Mainardi wrote:

[quote]Michael Joseph Wdowiak Beijer wrote:

Anyone know what to do when you get told:

"Cannot validate SDL plug-in: Sdl.ProjectAutomation.AutomaticTasks.WIPReport.WIPReportTask, Sdl.ProjectAutomation.AutomaticTasks.WIPReport, Version= [IP removed] , Culture=neutral, PublicKeyToken=c28cdb26c445c888"?
[/quote]

Remove the plug-ins from Studio and use a vanilla version? [/quote]

Yeah, that is indeed often the source of the problems: plugins. Although the SDL AppStore is a great idea, and has many potential benefits, it can also result in an even more unstable program, which in Studio's case means a very unstable program indeed.

As I mentioned above though, I managed to solve the problem, this time, by doing the following:

As usual, the quickest way to solve the problem was to completely uninstall the Studio (using Revo Uninstaller, which removes EVERYTHING, also the stuff in your Windows registry), reinstall it, and then recreate the project and pretranslate it using a separate TM (which I always make sure I have when working with Studio packages/projects).
↧

SDL Studio: I hate it, I hate it, I hate it! | Extirpation

March 14, 2018, 2:54 pm
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: Mirko Mainardi
Post title: Extirpation

[quote]Michael Joseph Wdowiak Beijer wrote:

[quote]Mirko Mainardi wrote:

Remove the plug-ins from Studio and use a vanilla version? [/quote]

Yeah, that is indeed often the source of the problems: plugins. Although the SDL AppStore is a great idea, and has many potential benefits, it can also result in an even more unstable program, which in Studio's case means a very unstable program indeed.

As I mentioned above though, I managed to solve the problem, this time, by doing the following:

As usual, the quickest way to solve the problem was to completely uninstall the Studio (using Revo Uninstaller, which removes EVERYTHING, also the stuff in your Windows registry), reinstall it, and then recreate the project and pretranslate it using a separate TM (which I always make sure I have when working with Studio packages/projects). [/quote]

Yes, I had read your solution (which is kind of radical, as per subject), however, like you, I too believe plug-ins might be causing added instability to an already "problematic" piece of... software, and, like you, I too don't particularly like Studio, or the fact it still (inexplicably) dominates the market... but in my case it's mostly because I find it unnecessarily complicated, bloated and cumbersome. In the past I've had my fair share of technical issues (tied to Java, Nalpeiron or whatnot), and that didn't certainly do any good to my general disposition toward it.

BTW, I'm still on 2015 with the upgrade to 2017 still pending (and I think I haven't used it in months anyway). I usually don't even bid if a client mentions Studio as THE required CAT tool, but I guess Kathryn and John have a point, although I think I'd feel very uneasy if I were to accept a "Trados-only" project and then work on it with another tool (MemoQ in my case)...
↧

SDL Studio: I hate it, I hate it, I hate it! | Who is it that blames his tools again?

March 15, 2018, 12:31 am
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: Jo Macdonald
Post title: Who is it that blames his tools again?


Micheal your "NEVER AGIN" pic made me laugh but I reckon you just need to learn how to use it mate.

My experience is quite the opposite.
I started using SDLX when that came out in the dark ages, switched to Trados, then Studio, when the companies merged.

Personally I've never had any major problems with the programs, and any minor problems were often caused by hang-ups in the original file being processed, busted tables, stuff like that.

In my case if I get a MemoQ job I'll translate the mqxliff file in Studio, never had a problem with this, and I wouldn't touch Memsource even with a long pointy stick and thick rubber gloves on. I get about 10 mails a week from one client warning everyone their MemoQ server is up the spout, so if you're working with that online you're fu......ed, but do I care with my good old trusty Studio on my own computer at home? Naaaah.
But, then again, maybe I should learn to use more tools.
;)
↧
Search

SDL Studio: I hate it, I hate it, I hate it! | Cross-compatibility - Groupshare?

March 15, 2018, 1:19 am
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: LEXpert
Post title: Cross-compatibility - Groupshare?

[quote]John Fossey wrote:

[quote]Kathryn Britton wrote:

MemoQ and Studio are compatible so when I receive a package in Trados, I simply load it into MemoQ, work as normal and then when I create the return package, MemoQ kindly puts it back into Trados for me .... [/quote]

That's what I've been doing for years as well. The client doesn't appear to even know I didn't use Studio.

[Edited at 2018-03-14 17:06 GMT] [/quote]

Can you check out Groupshare projects in MemoQ?
↧
↧

Trados Professional vs. Trados freelance | Run a new version in Trial mode...

March 14, 2018, 7:45 pm
$
0
0
Forum: SDL Trados support
Topic: Trados Professional vs. Trados freelance
Poster: MikeTrans
Post title: Run a new version in Trial mode...

Best way to know what the 'Professional' version is all about is to run for 30 days the Trial when you install a new Trados version. It will be the Professional version for 30 days, after that you need to buy the software (one of the versions) or run in Demo mode. I think if you buy with Group Buy here on Proz, you also get this 30-day-trial after installing.

The most important differences are mentioned above already, in addition it allows you to:

- Create packages (for PMs, but also convenient if you exchange between other fellow translators who work with other CATs, and you can bypass expensive networking to some degree, I suppose)
- Run custom Batch tasks instead of the pre-defined ones
- Use the included Autosuggest Dictionary feature (which you can also buy separately for Freelance Edition)
- Use improved Verify and QA functions (only useful for PMs, less useful for translators...)
- You can change the status of locked segments (oh, great...I always wanted to mess with my PM...)

As for projects, no, I don't think multi-languages are really supported because I don't think a TM can have different source languages recognized in it, so if you happen to have a mixture of languages in a file, the Pro version won't help you very much, you won't be able to load different language TMs or termbases in a single project AFAIK. The Pro version is clearly only designed for PMs when doing admin work inside Trados and all these additional features are certainly not worth the multi-thousand Euro/Dollars to spend IMO, unless you can detract them from taxes obviously...
But what really puzzles me is: How in the world would a PM need all these 'translation' functions? If a separate program was made for PMs only containing the additions of the Pro version, this would surely be enough for any admin work, and at a reduced cost also!

[Edited at 2018-03-15 04:09 GMT]
↧

SDL Studio: I hate it, I hate it, I hate it! | Problems with Termbase Search

March 15, 2018, 1:39 am
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: asr2
Post title: Problems with Termbase Search

Although I do not have any major problems with Studio, this is not the case with Termbase Search.
Although the consistent use of terminology is essential for translators, I often get the message "No results available" even though I get the message "term exists already ... in the active termbase". The suggested solution to reorganise the TB does not help.
↧

SDL Studio: I hate it, I hate it, I hate it! | Workaround for creating impossible return packages

March 15, 2018, 1:54 am
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: Angela Rimmer
Post title: Workaround for creating impossible return packages

Hey Michael,

I have never had the kind of problem you are describing, but when I install Studio I always try to avoid installing any additional plug-ins or widgets, so perhaps that is why.

BUT to get around this particular issue, you CAN just go into the project folder, go to your target language folder, and then send the SDLXLIFF files to the client. They don't HAVE to have a return package in order to receive the translation. This is actually one of the main reasons why I prefer Trados Studio to MemoQ.

For example, once you have translated a project going from en-US to de-DE, navigate to the folder where your project is located, go to the de-DE folder, and you will find your translated files there. You can simply return those to the client without having to worry about creating a return package.
↧

TM units don't seem to be updated instantly | It depends on your Fuzzy Match settings...

March 14, 2018, 9:18 pm
$
0
0
Forum: SDL Trados support
Topic: TM units don't seem to be updated instantly
Poster: MikeTrans
Post title: It depends on your Fuzzy Match settings...

First, check wether all necessary checkboxes are enabled in your Project Options for the TM: Enabled_Lookup_Concordance_Update; if the second and/or the last one is deactivated you will never see any matches proposed from new translations, but you get results when hitting Concordance searches.
Then, you have to check the Options or Project Options and look in the 'Search' settings for your language pair. Here the fuzzy match settings must be small enough in order to return a fuzzy match; if it's set to 70 (default) or higher you will hardly ever see any fuzzy match, especially with longer sentences.
You can also set the Concordance settings as low as 30% for a lot of returns, also automatic ones, and finally, be sure you have the Fragment Search and upLIFT function enabled which really helps (but for that you need to have 1000 TUs or more in your TM).

Cheers,

[Edited at 2018-03-15 04:36 GMT]
↧
↧

How to create a TMX file in SDLX (Trados 7)

March 15, 2018, 2:01 am
$
0
0
Forum: SDL Trados support
Topic: How to create a TMX file in SDLX (Trados 7)
Poster: Barbara Østergaard

Dear colleagues,

A supplier of mine has problems exporting a TM compatible with my own translation tool - MemoQ. I need either a TMX or CSV format, but apparently this is not possible with her tool.

Do you have any experience with SDLX (which is supposedly part of Trados 7), and do you have any suggestions as to how we solve this problem?

Thank you very much!

Best regards,
Barbara
↧

SDL Studio: I hate it, I hate it, I hate it! | Same thing (kinda)

March 15, 2018, 2:15 am
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: Samuel Murray
Post title: Same thing (kinda)

[quote]Michael Joseph Wdowiak Beijer wrote:
I have a permanent warning/reminder on my whiteboard that says "NEVER USE STUDIO AGAIN!"... [/quote]

We all make such promises to ourselves. Never again will I use X or Y system. But then a client comes begging, and you end up doing it again. And sometimes you get burnt again.

For example, a while ago I vowed never to use Crowdin ever again, but... a good client asked me to do it, and so I did, and got burnt again. And a few weeks ago it happened again: another client asked me to use it, I refused, there was some correspondence back and forth, and now I'm using it again. I dislike it intensely ("hate" is a strong word), but sometimes you have to bite down. I've made similar vows about Wordbee, XTM, that nameless Lionbridge tool, etc.
↧
Search

SDL Studio: I hate it, I hate it, I hate it! | "NEVER AGAIN"

March 15, 2018, 2:49 am
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: Michael Joseph Wdowiak Beijer
Post title:"NEVER AGAIN"

[quote]Jo Macdonald wrote:

Micheal your "NEVER AGIN" pic made me laugh but I reckon you just need to learn how to use it mate.

My experience is quite the opposite.
I started using SDLX when that came out in the dark ages, switched to Trados, then Studio, when the companies merged.

Personally I've never had any major problems with the programs, and any minor problems were often caused by hang-ups in the original file being processed, busted tables, stuff like that.

In my case if I get a MemoQ job I'll translate the mqxliff file in Studio, never had a problem with this, and I wouldn't touch Memsource even with a long pointy stick and thick rubber gloves on. I get about 10 mails a week from one client warning everyone their MemoQ server is up the spout, so if you're working with that online you're fu......ed, but do I care with my good old trusty Studio on my own computer at home? Naaaah.
But, then again, maybe I should learn to use more tools.
;)
[/quote]

I must be having really bad luck then, because this is probably the 4th or 5th time I have had to completely uninstall/reinstall Studio. Hell, I even had to reinstall Windows itself once, to solve a problem with Studio that SDL support couldn't fix. It wouldn't be a such an issue, if it weren't for the fact that more and more agencies are requiring it these days.

Yeah, regarding Memsource, that's exactly what I would have said a few months ago, but I actually started playing around with it a while ago, first the online editor (which I pretty quickly ditched because it was too slow), and then their desktop editor, which I soon realized was actually really good. Sure, it's missing a few features of the other big CAT tools, but I soon found that I was actually really enjoying using it, and that it had considerably speeded up my work, probably partially due to the fact that it has less features, and thus less dictractions. I also love the fact that I can finally connect ALL my large TMs to a project with no slow-downs at all, which is a benefit of using cloud-stored TMs/TBs. Another thing I really like about it is it's minimalist, logical UI, which is basically a copy of the memoQ UI. I can't stand the convoluted mess that the Studio has become. I can never tell where one little window starts and the next begins. Anyway, I'm sure you and pothers will disagree, but that's been my experience.

Michael
↧

SDL Studio: I hate it, I hate it, I hate it! | Yes, that's one of my main problems with Studio too: absolutely unreliable terminology recognition

March 15, 2018, 2:54 am
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: Michael Joseph Wdowiak Beijer
Post title: Yes, that's one of my main problems with Studio too: absolutely unreliable terminology recognition

[quote]asr2 wrote:

Although I do not have any major problems with Studio, this is not the case with Termbase Search.
Although the consistent use of terminology is essential for translators, I often get the message "No results available" even though I get the message "term exists already ... in the active termbase". The suggested solution to reorganise the TB does not help. [/quote]

… whether you're using local termbases, or their new Cloud Terminology termbases (which is very interesting but just doesn't work). There is nothing more frustrating than constantly being told that the term you are trying to enter is already present in your termbase, and yet you were not shown it.

I have been sending in support requests about this for years, and although I'm sure they are doing their best at SDL, no one has ever really managed to solve this problem. My guess is that they should completely ditch whatever underlying system they are currently using, and start from scratch again. In CafeTran, or Memsource, e.g., terminology recognition always works, period. It's ridiculous that the so-called market leader cannot offer functional terminology matching.
↧
↧

SDL Studio: I hate it, I hate it, I hate it! | Thanks for the tip!

March 15, 2018, 2:57 am
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: Michael Joseph Wdowiak Beijer
Post title: Thanks for the tip!

[quote]Angela Rimmer wrote:

Hey Michael,

I have never had the kind of problem you are describing, but when I install Studio I always try to avoid installing any additional plug-ins or widgets, so perhaps that is why.

BUT to get around this particular issue, you CAN just go into the project folder, go to your target language folder, and then send the SDLXLIFF files to the client. They don't HAVE to have a return package in order to receive the translation. This is actually one of the main reasons why I prefer Trados Studio to MemoQ.

For example, once you have translated a project going from en-US to de-DE, navigate to the folder where your project is located, go to the de-DE folder, and you will find your translated files there. You can simply return those to the client without having to worry about creating a return package.
[/quote]

Yes, I know about that trick, but I always try to return a Return package if that's what the client wants. This was an extremely large job, which their engineers created out of literally thousands of different files, and I have a feeling that they want a Return package for some kind of technical reason rather.

Michael
↧

SDL Studio: I hate it, I hate it, I hate it! | Hear hear

March 15, 2018, 2:58 am
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: Claudia Cherici
Post title: Hear hear

[quote]Jo Macdonald wrote:

Micheal your "NEVER AGIN" pic made me laugh but I reckon you just need to learn how to use it mate.

My experience is quite the opposite.
I started using SDLX when that came out in the dark ages, switched to Trados, then Studio, when the companies merged.

Personally I've never had any major problems with the programs, and any minor problems were often caused by hang-ups in the original file being processed, busted tables, stuff like that.

In my case if I get a MemoQ job I'll translate the mqxliff file in Studio, never had a problem with this, and I wouldn't touch Memsource even with a long pointy stick and thick rubber gloves on. I get about 10 mails a week from one client warning everyone their MemoQ server is up the spout, so if you're working with that online you're fu......ed, but do I care with my good old trusty Studio on my own computer at home? Naaaah.
But, then again, maybe I should learn to use more tools.
;)
[/quote]

I quote every word (except the last line ;-))
↧

SDL Studio: I hate it, I hate it, I hate it! | so true

March 15, 2018, 3:03 am
$
0
0
Forum: SDL Trados support
Topic: SDL Studio: I hate it, I hate it, I hate it!
Poster: Michael Joseph Wdowiak Beijer
Post title: so true

[quote]Samuel Murray wrote:

[quote]Michael Joseph Wdowiak Beijer wrote:
I have a permanent warning/reminder on my whiteboard that says "NEVER USE STUDIO AGAIN!"... [/quote]

We all make such promises to ourselves. Never again will I use X or Y system. But then a client comes begging, and you end up doing it again. And sometimes you get burnt again.

For example, a while ago I vowed never to use Crowdin ever again, but... a good client asked me to do it, and so I did, and got burnt again. And a few weeks ago it happened again: another client asked me to use it, I refused, there was some correspondence back and forth, and now I'm using it again. I dislike it intensely ("hate" is a strong word), but sometimes you have to bite down. I've made similar vows about Wordbee, XTM, that nameless Lionbridge tool, etc.
[/quote]

Indeed, I will write myself a little note like that, but then after not working in Studio for a couple of months, and perhaps erasing the note from my whiteboard because I need space for something else, a good client pops up and asks me whether I would like to do a very large, lucrative job in Studio, and having stupidly forgotten my past woes, I accept it. I do this over and over and over, like some kind of Greek mythological character ;-)

Another reason I am often tempted back by Studio is the fact that it does have a lot of cool features (for example, it's auto-complete system is probably the best in any CAT tool at the moment), and of course a whole bunch more are constantly being added by the SDL AppStore. However, as a few people have already mentioned, and this has been my experience too: SDL Apps are often more trouble than they're worth in terms of the added instability they cause.

PS: I'm dictating all of these posts, so please excuse any typos...
↧
Viewing all 29882 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>