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

Could you add "border line" for segments? | Totally agree

$
0
0
Forum: SDL Trados support
Topic: Could you add "border line" for segments?
Poster: Thomas T. Frost
Post title: Totally agree

I have been trying to find the same feature. Non-white backgrounds make the text more difficult to read, particularly when you reach a certain age, so I have set the background shading to close to imperceptible. But then it becomes difficult to distinguish one segment from another.

A thin line between the segments would be much better. As in MemoQ and Memsource.

Also, it would be nice to be able to move the status column from the middle to the right (or perhaps the left). It should not be the centre of attention between the source and target columns.

Studio 2017 - "move to next segment" not working anymore

$
0
0
Forum: SDL Trados support
Topic: Studio 2017 - "move to next segment" not working anymore
Poster: Francesca Siotto

Hi,
my cat jumped on my keyboard while I was translating in Studio 2017, I don't know what was pressed but all of a sudden the cursor has stopped moving to the next segment after Ctrl+Enter, and the same happens when I use the shortcut with the mouse. How do I fix this?

Could you add "border line" for segments? | SDL website?

$
0
0
Forum: SDL Trados support
Topic: Could you add "border line" for segments?
Poster: Mirko Mainardi
Post title: SDL website?

I haven't noticed SDL's representatives posts here as of late, so perhaps they stopped following threads on ProZ and "retreated" to the SDL fora?

At any rate, about feature suggestions: [url removed]

Studio 2017 - "move to next segment" not working anymore | Feline misbehaviour

$
0
0
Forum: SDL Trados support
Topic: Studio 2017 - "move to next segment" not working anymore
Poster: Thomas T. Frost
Post title: Feline misbehaviour

Well, it is a CAT tool after all.

I'd close the application and restart it. Remember to save the document first.

I have taught my cats not to walk or jump on the keyboard, so I fortunately don't have such problems.

Could you add "border line" for segments? | Yes, better as a suggestion on the SDL site

$
0
0
Forum: SDL Trados support
Topic: Could you add "border line" for segments?
Poster: Thomas T. Frost
Post title: Yes, better as a suggestion on the SDL site

The direct link to the suggestion page is [url removed] .

Let us know when you have posted it, so I can vote for it.

Could you add "border line" for segments? | Thank you for the link

$
0
0
Forum: SDL Trados support
Topic: Could you add "border line" for segments?
Poster: Regi2006
Post title: Thank you for the link

[quote]Mirko Mainardi wrote:
[url removed] [/quote]

Thanks for the link, Mirko.

[quote]Thomas T. Frost wrote:

The direct link to the suggestion page is [url removed] .

Let us know when you have posted it, so I can vote for it. [/quote]

Thanks Thomas, I already post the request here.

[url removed]

Thank you

Could you add "border line" for segments? | Status Column

$
0
0
Forum: SDL Trados support
Topic: Could you add "border line" for segments?
Poster: Regi2006
Post title: Status Column

[quote]Thomas T. Frost wrote:
Also, it would be nice to be able to move the status column from the middle to the right (or perhaps the left). It should not be the centre of attention between the source and target columns. [/quote]

I have also posted the request for this feature in a separate thread here:

[url removed]

Thanks

Could you add "border line" for segments? | Thanks

$
0
0
Forum: SDL Trados support
Topic: Could you add "border line" for segments?
Poster: Thomas T. Frost
Post title: Thanks

Excellent, thanks. I was a bit lazy. :-)

Could you add "border line" for segments? | :)

$
0
0
Forum: SDL Trados support
Topic: Could you add "border line" for segments?
Poster: Regi2006
Post title: :)

[quote]Thomas T. Frost wrote:

Excellent, thanks. I was a bit lazy. :-) [/quote]

Haha, no prob. I just received an email notification from them that the status for both requests had been changed to "Under Community Review".

Studio 2017 - "move to next segment" not working anymore | This man's dinner was unconfirmed by his cat

$
0
0
Forum: SDL Trados support
Topic: Studio 2017 - "move to next segment" not working anymore
Poster: Thomas T. Frost
Post title: This man's dinner was unconfirmed by his cat

[url removed]

Studio 2017 - "move to next segment" not working anymore | Shortcut

$
0
0
Forum: SDL Trados support
Topic: Studio 2017 - "move to next segment" not working anymore
Poster: Silke Walter
Post title: Shortcut

Sometimes shortcuts seem to disappear or change out of the blue. Maybe this has happened here.

You can check this by going to „Start“ >„Options“ >„Keyboard shortcuts“.
„Confirm and move to next segment“ (or something like this, I am using a German version) should be „Strg+Enter“. If not, just change it this way and everything is going to work as before.

DEEPL Pro is now available for Trados | Credit card declined

$
0
0
Forum: SDL Trados support
Topic: DEEPL Pro is now available for Trados
Poster: Olly Pekelharing
Post title: Credit card declined

Anyone else get a 'credit card declined' message when trying to create a DeepLpro account? Am thinking it must be something at DeepL's end, as my card is perfectly valid.

Olly

DEEPL Pro is now available for Trados | My credit card worked

$
0
0
Forum: SDL Trados support
Topic: DEEPL Pro is now available for Trados
Poster: Gary Evans
Post title: My credit card worked

Maybe try with the full name that's on your card. It worked for me.

[quote]Olly Pekelharing wrote:

Anyone else get a 'credit card declined' message when trying to create a DeepLpro account? Am thinking it must be something at DeepL's end, as my card is perfectly valid.

Olly [/quote]

DEEPL Pro is now available for Trados | A bit too expensive for me.

$
0
0
Forum: SDL Trados support
Topic: DEEPL Pro is now available for Trados
Poster: Wojciech_
Post title: A bit too expensive for me.

20 dollars per month is a bit too steep for me, especially that even if one month you just need to translate 50,000 characters, you will be charged 20 USD anyway.
Shame they haven't applied similar policy to Google Translate where you are charged for the usage from the very beginning, not after you exceed the magical 1 million characters. Or at least they could have set the limit slightly lower, say at 200,000 for lower price.
I guess I'll try it one month and see if in combination with Trados's excellent Autosuggest it visibly boosts my performance or not.

[Edited at 2018-03-23 21:20 GMT]

DEEPL Pro is now available for Trados | You better try GT4T

$
0
0
Forum: SDL Trados support
Topic: DEEPL Pro is now available for Trados
Poster: Jorge Payan
Post title: You better try GT4T

[quote]Wojciech_ wrote:

20 dollars per month is a bit too steep for me, especially that even if one month you just need to translate 50,000 characters, you will be charged 20 USD anyway.
Shame they haven't applied similar policy to Google Translate where you are charged for the usage from the very beginning, not after you exceed the magical 1 million characters. Or at least they could have set the limit slightly lower, say at 200,000 for lower price.
I guess I'll try it one month and see if in combination with Trados's excellent Autosuggest it visibly boosts my performance or not. [/quote]

I am not linked in any sense to GT4T. I am just a satisfied user.

What I know is that GT4T gives you access not only to DeepL, but to Google Translate and Bing Translator too. It works not only with Studio but with any major CAT tool (I use it with Wordfast, DéjàVu and MemoQ). I pay USD 6 per month and have never reached any limit, although sometimes I have translated 500,000 characters per month.

They also offer a trial period.

[url removed]


Studio 2017 - "move to next segment" not working anymore | Not only the 'CAT's' fault I think...

$
0
0
Forum: SDL Trados support
Topic: Studio 2017 - "move to next segment" not working anymore
Poster: MikeTrans
Post title: Not only the 'CAT's' fault I think...

For some reason in Studio 2017, the CTRL-Down does not move to the next segment although it is defined as such in the keyboard shortcuts, also the arrow up / arrow down in the Navigation part of the ribbon don't work. And my 3 cats are definitly not the culprits!

Mike

[Edited at 2018-03-24 05:05 GMT]

Studio 2017 - "move to next segment" not working anymore | User profiles

$
0
0
Forum: SDL Trados support
Topic: Studio 2017 - "move to next segment" not working anymore
Poster: Natalie
Post title: User profiles

[quote]MikeTrans wrote:

For some reason in Studio 2017, the CTRL-Down does not move to the next segment although it is defined as such in the keyboard shortcuts, also the arrow up / arrow down in the Navigation part of the ribbon don't work. And my 3 cats are definitly not the culprits!

[/quote]

The shortcuts (and many other things) depend on the profile you are using. You may want to check this information:
[url removed]

Spectre and Meltdown & Multiterm?

$
0
0
Forum: SDL Trados support
Topic: Spectre and Meltdown & Multiterm?
Poster: Eileen Cartoon

I am using Studio 2017. Some time ago there was a Windows Update and since them my Multiterm usage on the fly with Trados has become IMPOSSIBLY slow, particularly for my longer termbases. I thought there might be something to do with my computer so I took it into the shop but it was working fine. I have an SSD hard disk and things used to just fly. The technician in the shop (who is not just the latest kid by a man with quite some experience) asked me if there might be some problem with Spectre and Meltdown as the last update to Windows tried a software patch to a hardware problem to avoid these back doors.He said that this has affected many professional programs.

I was wondering if this is part of the reaosn for my Multiterm problems. I like the new one-click way of adding but it really has become impossibly slow. And it is something I rely on a great deal. I do a lot of pharma translations and every time I encounter a new drug or chemical compound I save it to Multiterm so I never make another spellign mistake. But now, I could have done 2-3 segments if I didn't have to wait so long for the hits to appear. And I don't want to go back to an older version because I like a lot of the new features.

Any ideas

P.S. I logged this on and an SDL tech guy tried to work on it in my computer but was not able to resolve the problem.

Any ideas would be of great interest (also to my computer technician who would like to know your takes on the Spectre-Meltdown question)

Eileen

DEEPL Pro is now available for Trados | GT4T - thanks for the tip

$
0
0
Forum: SDL Trados support
Topic: DEEPL Pro is now available for Trados
Poster: Roy Oestensen
Post title: GT4T - thanks for the tip

[quote]Jorge Payan wrote:
What I know is that GT4T gives you access not only to DeepL, but to Google Translate and Bing Translator too. It works not only with Studio but with any major CAT tool (I use it with Wordfast, DéjàVu and MemoQ). I pay USD 6 per month and have never reached any limit, although sometimes I have translated 500,000 characters per month.
[url removed]
[/quote]

I am also a satisfied user of GT4T, but I have not tried linking it up to DeepL. I have no experience with DeepL, so I am curious to see how it works at least.

Update: Pity: GT4T supports DeepL, but DeepL does not support Norwegian regretably.

Roy

[Edited at 2018-03-24 15:04 GMT]

Client generated package displays source and target in editor, generates an empty return package

$
0
0
Forum: SDL Trados support
Topic: Client generated package displays source and target in editor, generates an empty return package
Poster: Catherine Earle

I'd love to have some help with this. A new client has sent me 2 client-generated Trados packages for 2 different products. I use Trados Studio 2015, and I used it to produce both projects. The first project was submitted with no problem.
For the second project, the PM came back to me and said the "target" was empty. When I open the "completed" project in editor view, I see both the source and my completed translation on the target side. But, I cannot get the project to save the target as a Word doc.
The client is telling me to use only Trados 2017, and not to use Studio. But...I produced the first translation using Trados Studio 2015, and there were no problems.
Does anyone have any ideas what the problem may be? I would appreciate your help.
Viewing all 29878 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>