Quantcast
Viewing all 3915 articles
Browse latest View live

Translation Workspace - Failed to activate plugin (Could not load Translation Workspace DLL) | Solved

Forum: CAT Tools Technical Help
Topic: Translation Workspace - Failed to activate plugin (Could not load Translation Workspace DLL)
Poster: Reindel
Post title: Solved

I actually found a solution. I got this from a client's support:

Have user do a clean install. Below is the template that can be used for this purpose:

Please uninstall Xliff Editor and Translation Workspace client/tools.

Also please remove following folders:

C:\Users\%UserAccount%\AppData\Roaming\Translation Workspace

C:\Users\%UserAccount%\AppData\Roaming\Translation Workspace XLIFF Editor

C:\ProgramData\Translation Workspace XLIFF Editor

C:\Program Files (x86)\Lionbridge\Translation Workspace XLIFF Editor or C:\Program Files\Lionbridge\Translation Workspace XLIFF Editor

C:\Users\%UserAccount%\AppData\Roaming\Microsoft\Word\STARTUP ------ Here please remove WorkspaceForWord.dot and WorkspaceForWord.dotm

C:\Program Files (x86)\Microsoft Office\Office15\STARTUP

After that please download from translate.translationworkspace.com:

- Translation Workspace Tools client

- Translation Workspace Xliff Editor

and install them in that order.

Please let us know if this helps.

NOTE: The described steps will reset any TW Plugin configuration changes back to their default settings.

[Edited at 2019-07-12 08:17 GMT]

[Edited at 2019-07-12 08:18 GMT]

A simple Google Translate translator for API users | New version of simplegoog v5

Forum: CAT Tools Technical Help
Topic: A simple Google Translate translator for API users
Poster: Samuel Murray
Post title: New version of simplegoog v5

Hello everyone

I got a new computer and had to switch from Windows 7 to Windows 10. I've discovered that traytips do not behave rationally in Windows 10. The original simplegoog script uses traytips for a progress indicator, but that is no longer feasible in Windows 10, so I created a new version that uses a tooltip in the top right corner of the screen to tell you how many segments are being translated.

[url removed]

Samuel

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: Dylan Jan Hartmann

Hi Fellow LB Vendors!

After half a year of paying for the Freelancer Subscription of Translation Workspace (TWS), I accepted that I'd never use TWS xliff editor for anything other than LB jobs, so cancelled the subscription. Then, the next job I was sent from a LB PM required me to use the the TWS xliff editor, but I couldn't log in - it required me to reactivate my TWS account. The PM sent a message to GeoWorkz, who promptly reinstated my freelancer subscription. Bye bye another monthly $14!

What I'd like to confirm, is whether everyone working with LB is also required to pay this monthly subscription, or has something gone wrong? I've sent numerous support requests asking this question to Geoworkz but the responses either make no sense or don't answer the question.

I understand that I'm paying for a personal subscription, but I don't want it for personal use, only to use it as a LB vendor.

Any advice would be super appreciated.

(If possible, I'd like to get the months and months of unused subscription $$ back too!)

DJH

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors? | The tally shop: seek other clients

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: IanDhu
Post title: The tally shop: seek other clients

Broaden your client base, and move away from this one. It doesn't make sense to have to pay a client in order to work for it.

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors? | This does not help in any way.

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: Dylan Jan Hartmann
Post title: This does not help in any way.

[quote]IanDhu wrote:

Broaden your client base, and move away from this one. It doesn't make sense to have to pay a client in order to work for it. [/quote]

Please kindly respond to the question in the post, or leave it be. Thanks.

"Move away from" LB? Look at the top performing global LSPs and you may reconsider this advice when you realise who LB is.

Thanks again, looking forward to hearing from anyone with experience with Translation Workspace.

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors? | Support

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: Jean Dimitriadis
Post title: Support

[url removed]

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors? | Thanks, but the Support Isn't Responding

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: Dylan Jan Hartmann
Post title: Thanks, but the Support Isn't Responding

[quote]Jean Dimitriadis wrote:

[url removed] [/quote]

Thanks Jean,

But as I said in the first post, the support either isn't making sense in their responses or isn't responding to my question. That's why I came here to seek other LB vendors' advice.

Thanks!

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors? | Makes perfect sense to refuse to pay to work

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: Sheila Wilson
Post title: Makes perfect sense to refuse to pay to work

[quote]Dylan Jan Hartmann wrote:

[quote]IanDhu wrote:

Broaden your client base, and move away from this one. It doesn't make sense to have to pay a client in order to work for it. [/quote]

Please kindly respond to the question in the post, or leave it be. Thanks.

"Move away from" LB? Look at the top performing global LSPs and you may reconsider this advice when you realise who LB is. [/quote]
I think it's highly likely that Ian knows who LB are, just as I do. They're a big player, sure. But there are thousands of agencies, certainly tens of thousands, maybe hundreds of thousands. IMHO it would be far more relevant to look at the career paths of the top performing freelance translators. How many rely on LB?

But to revert to 100% on-topic, I advise you to check out the ProZ.com scam centre. One of the things we are advised never to do is pay to work! It seems to me you have the means to stop -- you already did it once. I doubt you'll ever get anything back though as you entered into the agreement of your own free will.

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors? | Unfortunately this is how it works

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: Renée van Bijsterveld
Post title: Unfortunately this is how it works

Indeed, you have to have a (paid) subscription to use Translation Workspace: [url removed]

However, I once worked for an LSP who had an extra license that I could use before I had my own TW suscription. So this is something you could check out.

LB has grown to be a huge translation provider, and they can ask anything from translators. It's up to you if you want to accept.

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors? | Discussing LSPs and using specific CAT tools

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: Stephanie Busch
Post title: Discussing LSPs and using specific CAT tools

The problem when discussing a large LSP is, that a) you either will have signed an NDA in order to be able to work for them, or b) you haven’t worked for them.

In the first case, you aren’t allowed to share your knowledge about them, and in the second case, you can only speculate about them.

I confirm that the subscription is legitimate and that you do need to take it out if you want to use XLIFF Editor for LB projects.

You have to decide for yourself whether this subscription is likely to make economic sense for you.

In case XLIFF Editor turns out to be your preferred CAT tool, you can upgrade your subscription and use it for non-LB projects too.

XLIFF Editor is also used by other LSPs, and if one of these approaches you with a XLIFF Editor project, they will provide you with a license you can only use for that project.

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors? | One shouldn't be overawed...

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: IanDhu
Post title: One shouldn't be overawed...

... by a client's size.

And, in any case, it is important to diversify one's client base for the sake of avoiding economic dependence, hence vulnerability to adverse economic factors. Obviously, at the start of one's career, one may find onself doing a significant proportion of one's work with just a few clients. However, for business survival, the pattern must be made to evolve. To be exposed to a single client to the tune of 20% for any length of time should sound a warning signal.

I hope this helps.

XLIFF mixed language -- any tool/process to input into a translation workflow?

Forum: CAT Tools Technical Help
Topic: XLIFF mixed language -- any tool/process to input into a translation workflow?
Poster: SoerenB

Sorry if this has been discussed in the past (would have thougth so, but find none).

The normal process for XLIFFs is to get:
either a delta-only file - with untranlated translation units with the new/changed source
or a full, untranslated file - with all units in the source language (and then use a memory to 'translate' the unchanged stuff).

But if you get from a customer a bunch of XLIFF files with a mix of translated units (translations in the target element of the translation unit), and untranslated units (in this case English - which is populated to the target element).

In the CAT tools I know of this could never work. Because the already translated values would be considered (unknown) source. Unless there is some attribute info for those units of unchanged content.

Is it just me not knowing of a trick in this or that CAT tool for allowing such mixed language XLIFFs and still getting to easily learn of exactly what units are new/changed and have source to translate?

So far I told the customer, that this is a no-go, and requested either delta-only or full source and memory. But am I ignorant of a way to handle mixed language XLIFFs?

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors? | Thank you

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: Dylan Jan Hartmann
Post title: Thank you

[quote]Stephanie Busch wrote:

I confirm that the subscription is legitimate and that you do need to take it out if you want to use XLIFF Editor for LB projects.

You have to decide for yourself whether this subscription is likely to make economic sense for you.

In case XLIFF Editor turns out to be your preferred CAT tool, you can upgrade your subscription and use it for non-LB projects too.

XLIFF Editor is also used by other LSPs (there's a directory where they can find translators who use XLIFF Editor), and if one of these approaches you with a XLIFF Editor project, it will count against their subscription rather than your own. You do need to have the basic subscription though.[/quote]

Thanks for your confirmation.

The subscription is indeed worth it, but I wanted to see if it was necessary to be paying.

I managed to negotiate with the TWS support team to revert my subscription to the free LB vendor's subscription, even after being told that having unwillingly upgraded to the paid subscription, I couldn't revert. I replied questioning the ethics of this, and they asked for my PM to email them directly.

This might be a suitable pathway for others who don't use TWS for anything other than LB work.

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors? | Relevance

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: Dylan Jan Hartmann
Post title: Relevance

[quote]IanDhu wrote:

... by a client's size.

And, in any case, it is important to diversify one's client base for the sake of avoiding economic dependence, hence vulnerability to adverse economic factors. Obviously, at the start of one's career, one may find onself doing a significant proportion of one's work with just a few clients. However, for business survival, the pattern must be made to evolve. To be exposed to a single client to the tune of 20% for any length of time should sound a warning signal.

I hope this helps. [/quote]

Thanks for your concern. I did not post in this forum looking for new clients. You've jumped to a huge assumption that I am in dire need of this one agency, which is completely flawed.

This was only a question about the CAT tool, which you offered no insight about.

Thanks for your time and concern.

DJH

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors? | @Dylan

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: Samuel Murray
Post title: @Dylan

[quote]Dylan Jan Hartmann wrote:
What I'd like to confirm, is whether everyone working with LB is also required to pay this monthly subscription... [/quote]

I regularly get jobs that "require" TWS Xliff Editor (TWSXE) but I work for intermediary agencies (not LB directly), so perhaps they have a special type of subscription with LB that allows them to farm out jobs to freelancers who are not subscribed. Installing TWSXE can be done without a subscription, and there is no need to "log in" to use it. Well, if you want to use the client's TM, then you have to log in to the client's TM server, but the login details are always shared with me by the agencies I work for.

Ultimately, I rarely actually connect to the TM. Most of the time when I do a TWSXE job, I don't actually use it (I use e.g. OmegaT, and just open the final file in TWSXE to check if it looks okay). But I suppose that if you get jobs that absolutely require you to use the client's TM or glossary and you are unable to get your hands on it otherwise, then you'd have to use TWSXE and you have to log in. For jobs that start out as mostly untranslated, and I have to use the client's TM (and I'm given the login details), I use a little AutoIt script to extract all necessary segments from the online TM, and then proceed offline in e.g. OmegaT.

To sum up: I'm not sure if working with **LB** themselves would require a subscription. But I do do some work for agencies who in turn do work for LB, and I don't have a subscription myself.

Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors? | I go for more cooperative clients

Forum: CAT Tools Technical Help
Topic: Translation Workspace -> are we forced to pay the $14/month to GeoWorkz as LB vendors?
Poster: Christine Andersen
Post title: I go for more cooperative clients

[quote]Dylan Jan Hartmann wrote:

[quote]IanDhu wrote:

Broaden your client base, and move away from this one. It doesn't make sense to have to pay a client in order to work for it. [/quote]

Please kindly respond to the question in the post, or leave it be. Thanks.

"Move away from" LB? Look at the top performing global LSPs and you may reconsider this advice when you realise who LB is.

Thanks again, looking forward to hearing from anyone with experience with Translation Workspace.

[/quote]

I was expected to pay for the privilege of using GeoWorks - after spending time installing it, and more time trying to get it to work, all unpaid. I lost patience with LB before I ever earned a penny from them.
That was some years ago, but my approach to the big clients has always been the same. I look at who they are, and if they are big and inflexible, they are not for me.

I have practically always been offered more work than I could take on by clients who let me choose my CAT tool - so I strongly prefer my own CAT, having fine-tuned it and collected all my databases and TMs on it, quite a part from the simple, subconscious routines. OK, I pay for that, but then the online support is excellent when I need it. (I rarely do!)

My preferred clients are small to medium-sized agencies - ´Big enough to cope, small enough to care´ - as one of them said in its tagline.
They often pay better rates, or else they are more helpful and save me time. I hope the big companies never crowd that type of agency out. I have simply stopped working with several big names.
Two started as small, sensible agencies, and ended up as big bullies, one in the UK and one in Denmark, whom colleagues are boycotting. Others expect me to spend too much (unpaid) time on portals and ticking boxes, or they are inflexible one way or another - often with tight deadlines and work outside my scope.

I regretfully dropped one originally very nice agency that started collaborating with LB - and I could no longer just use my own CAT. They did not pay particularly well when the pound was low, so the extra hassle was the deal-breaker.

I know a lot of people work more or less happily for LB, but I hope they never succeed in crowding out the smaller agencies who really have a lot to offer both clients and translators.

XLIFF mixed language -- any tool/process to input into a translation workflow? | Wrong tools?

Forum: CAT Tools Technical Help
Topic: XLIFF mixed language -- any tool/process to input into a translation workflow?
Poster: Rodolfo Raya
Post title: Wrong tools?

Today most modern tools can handle partially translated XLIFF files without problems.

Having an XLIFF file that has target text in some segments and TM matches in others is quite common. You haven't mentioned what tools you use but it looks like they are outdated or not mainstream apps.

Regards,
Rodolfo M. Raya

XLIFF mixed language -- any tool/process to input into a translation workflow? | Some do, some don't

Forum: CAT Tools Technical Help
Topic: XLIFF mixed language -- any tool/process to input into a translation workflow?
Poster: Samuel Murray
Post title: Some do, some don't

[quote]Rodolfo Raya wrote:
Having an XLIFF file that has target text in some segments and TM matches in others is quite common. You haven't mentioned what tools you use but it looks like they are outdated or not mainstream apps. [/quote]

I agree with Rodolfo that there are definitely CAT tools that can deal with the type of file you mention (in which some text is translated and some is not, and/or the non-translated text is either pre-segmented or pre-translated or not). For example, as far as I know, Wordfast Pro 3 and OmegaT vanilla can't handle such files, but Wordfast Pro 5 and OmegaT with the Okapi plugin can. Trados and MemoQ can also handle such files.

--

[quote]SoerenB wrote:
The normal process for XLIFFs is to get:
either a delta-only file - with untranlated translation units with the new/changed source
or a full, untranslated file - with all units in the source language (and then use a memory to 'translate' the unchanged stuff). [/quote]

I don't think that this is the only "normal" process. A small number of my clients send me files that you refer to as "delta files", i.e. they contain only segments whose source text had changed. But most of my clients who send me XLIFF files send either 100% untranslated files or partially translated files.

[quote]In the CAT tools I know of this could never work. Because the already translated <target> values would be considered (unknown) source. [/quote]

I've read this several times, but I don't see the logic of that... unless you're using a CAT tool that reads the target field as if it contains the source text (some CAT tools with more primitive XLIFF filters do that, yes).

[quote]Unless there is some attribute info for those units of unchanged content. [/quote]

I suspect that what you're talking about is specifically software localization translation, where the originating systems can distinguish between changed and unchanged content, and in which each segment has a unique key (so that multiple identical segments can have non-identical translations).

Not all XLIFF workflows work on the principle of changed vs. unchanged content, however. Some clients create XLIFF files by converting the entire new version of a file (or project) to XLIFF, and then pre-translating unchanged content against the TM. In other words, they don't distinguish between changed and unchanged content when creating the XLIFF file, and they rely on in-context-matching instead of segment keys to ensure that the right translation sits with the right source text.

[quote]So far I told the customer, that this is a no-go, and requested either delta-only or full source and memory. [/quote]

Well, one thing you should not do is use the term "delta". (-:

[Edited at 2019-07-29 16:16 GMT]

XLIFF mixed language -- any tool/process to input into a translation workflow? | For XLIFF without 'state' or similar to flag which TUs store existing translations

Forum: CAT Tools Technical Help
Topic: XLIFF mixed language -- any tool/process to input into a translation workflow?
Poster: SoerenB
Post title: For XLIFF without 'state' or similar to flag which TUs store existing translations

Thank you for all comments. I confess lack of knowledge about some modern CAT tools, and I should have been more precise.

I know that you can add your own information to an XLIFF file, so fx. CAT tools can flag an internal (known only to that tool) status.

My question relates to some overly simple XLIFFs where the TUs look like this:

<trans-unit id="1586926" datatype="plaintext" size-unit="char" maxwidth="1000">
<source>Electric</source>
<target>Elektric</target>
</trans-unit>

I.e. no use of 'state' attribute or internal attributes to inform the CAT tool or the translator about which target elements have existing translations, and which have a copy of the source, needing translation.

To me there is nothing in that syntax to tell me or the CAT tool to know which of the hundreds of thousands target element strings need translation, and which are just the existing translated values.

[Edited at 2019-07-30 08:43 GMT]

XLIFF mixed language -- any tool/process to input into a translation workflow? | Default values

Forum: CAT Tools Technical Help
Topic: XLIFF mixed language -- any tool/process to input into a translation workflow?
Poster: Rodolfo Raya
Post title: Default values

In a translation unit like the one in your example, you start with the default attribute values.

Any translation present in ‹target› is just a hint unless the "approved" attribute of ‹trans-unit› is added and set to "yes". If the attribute is missing, the segment needs review before the translation can be used. CAT tools are used to set the attribute value.

Regards,
Rodolfo

[Edited at 2019-07-30 10:20 GMT]
Viewing all 3915 articles
Browse latest View live