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

Studio compatibility

$
0
0
Forum: Wordfast support
Topic: Studio compatibility
Poster: Edward Potter

I've been a WF user for many years but I'm considering ditching it.

I upgraded to WF Pro 5 recently and it has done nothing but slow me down and give compatibility problems with Studio.

My problem: I imported a Studio package (SDLPPX) for postediting. I did all the editing, did a Commit All, and saved it. I did a cleanup and got an SDLXLIFF file in XML format out of it.

I then exported the TMX. When I import the TMX back in (using the Word source file for populating) about 10% of the segments are left empty.

I am now going to manually insert all the missing segments.

Can someone tell me what is going on here?

[Edited at 2020-11-12 20:35 GMT]

Studio compatibility | @Edward

$
0
0
Forum: Wordfast support
Topic: Studio compatibility
Poster: Samuel Murray
Post title: @Edward

[quote]Edward Potter wrote:
1. I did all the editing, did a Commit All, and saved it.
2. I did a cleanup and got an SDLXLIFF file in XML format out of it.
3. I then exported the TMX. When I import the TMX back in (using the Word source file for populating) about 10% of the segments are left empty. [/quote]

Were all the segments in the SDLXLIFF file properly translated?

In WFP5, when you're in the main screen, press F9 (settings) and go to "Translation Memory" on the left. Check the options on the right. Could any of them possibly explain why some segments were not added to the TM? For example, by default, unedited MT matches are not written to the TM.

Studio compatibility | It worked! F9 then check the boxes.

$
0
0
Forum: Wordfast support
Topic: Studio compatibility
Poster: Edward Potter
Post title: It worked! F9 then check the boxes.

[quote]
Were all the segments in the SDLXLIFF file properly translated?
[/quote]
I don't have Studio on my computer so I couldn't tell you. I sent it off the client and they didn't seem to know what to do with it and requested a Word file. That is when I exported the TMX and called in the source Word file, imported the TMX, ending up with all the blank segments.

[quote]
In WFP5, when you're in the main screen, press F9 (settings) and go to "Translation Memory" on the left. Check the options on the right. Could any of them possibly explain why some segments were not added to the TM? For example, by default, unedited MT matches are not written to the TM.
[/quote]

Bingo! My TM updated properly after checking the boxes. They were unchecked as can be seen in my screen shot.

WF Pro 5 still has me miffed. I never would have thought to hit F9 or look for those memory options. I couldn't find this in the manual, at least not quickly. When issues like this pop up I need to resolve them quickly and intuitively. I spent a lot of time learning WF Pro 3, and now they want me to go through another learning curve. WF Pro 5 has everything in a different place and seems like a confusing fjumble.

Thanks for helping, Samuel. If I ever see you at a conference I'll buy you a beer. See ya!

[Edited at 2020-11-12 22:07 GMT]

[Edited at 2020-11-12 22:08 GMT]

Studio compatibility | @Edward

$
0
0
Forum: Wordfast support
Topic: Studio compatibility
Poster: Samuel Murray
Post title: @Edward

[quote]Edward Potter wrote:
I imported a Studio package (SDLPPX)...
I did a cleanup and got an SDLXLIFF file. [/quote]

Yes, that is what was supposed to happen. Your source file is SDLXLIFF, so the translated file that WFP5 creates is an SDLXLIFF file. However, WFP5 can't convert the SDLXLIFF file to the format that it was originally converted from -- only Trados can do that. So, you can translate SDLXLIFF files in WFP5 but you can't convert SDLXLIFF files back to the original original format (in your case, presumably a DOCX file).

[quote]Edward Potter wrote:
I sent the SDLXLIFF file off the client and they didn't seem to know what to do with it and requested a Word file. That is when I exported the TMX and called in the source Word file, imported the TMX, ending up with all the blank segments. [/quote]

Odd that the client did not know how to generate the DOCX file from the SDLXLIFF file. (Perhaps your client is an intermediary client who doesn't have Trados, because SDLPPX packages can only be created with the agency version of Trados, so somewhere in the upstream there must have been an agency with Trados Professional who created the file.)

It is also possible that your client doesn't understand that although you can translate SDLXLIFF files with your non-Trados CAT tool, you are not able to generate e.g. a Trados TM or the the final file in the original format.

[quote]Bingo! My TM updated properly after checking the boxes. They were unchecked as can be seen in my screen shot. [/quote]

You're not the first translator I've met who was miffed to discover this, but if you think about it, this is a safety feature and it's best that it is active (i.e. disabled in the settings) by default.

[quote]I spent a lot of time learning WF Pro 3, and now they want me to go through another learning curve. [/quote]

I use both WFP3 and WFP5. They are utterly different programs. They're as different as Trados and MemoQ. Both have their strong and weak points. WFP5 is more cumbersome to use, though.

I suggest you browse through all the settings to get an idea of some of the hidden "gems". To access the settings, press F9 or click the frogger icon on the bottom left. The frogger icon used to have a name, but the WFP5 developers are fans of mystery meat navigation, so in a recent update they removed most of the labels and left only the icons. Fortunately, hovering with your mouse over icons still yields a tool-tip (to be removed in an upcoming update, for sure).

Studio compatibility | @Samuel

$
0
0
Forum: Wordfast support
Topic: Studio compatibility
Poster: Edward Potter
Post title: @Samuel

[quote]Odd that the client did not know how to generate the DOCX file from the SDLXLIFF file.[/quote]

I think the PM was new. He was asking for a Word file, which I thought was odd, but I didn't know enough about Trados to assert that I couldn't send it back in that format. I did have the source file which I could turn into a TXLF, do a Translate All, then do a Cleanup. In the end that is what I did.

[quote]I suggest you browse through all the settings to get an idea of some of the hidden "gems". To access the settings, press F9 or click the frogger icon on the bottom left. The frogger icon used to have a name, but the WFP5 developers are fans of mystery meat navigation, so in a recent update they removed most of the labels and left only the icons. Fortunately, hovering with your mouse over icons still yields a tool-tip (to be removed in an upcoming update, for sure). [/quote]

I just started poking around those screens. I wish they could have put at least a few things in the old places. C'est la vie. :-)

Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)?

$
0
0
Forum: Wordfast support
Topic: Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)?
Poster: Jeff Chapman

macOS Big Sur (11.0) is out. Any Wordfast users here who have upgraded to Big Sur? Any issues or new problems that were not present in Catalina (10.15)?

The Wordfast website specifies that "Mac 10.11 and higher" (SIC) is required, but the software still has issues even more than a year after the release of 10.15 (Catalina) as documented in their release notes ( [url removed] ). Without belaboring the ever-present "crash on quit" issue and "accessibility nag" issue that Wordfast 5 still suffers from, I'm curious if the app will even run on the new OS.

Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)? | Normal practice

$
0
0
Forum: Wordfast support
Topic: Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)?
Poster: Tom in London
Post title: Normal practice

[quote]Jeff Chapman wrote:

macOS Big Sur (11.0) is out. Any Wordfast users here who have upgraded to Big Sur? Any issues or new problems that were not present in Catalina (10.15)?

The Wordfast website specifies that "Mac 10.11 and higher" (SIC) is required, but the software still has issues even more than a year after the release of 10.15 (Catalina) as documented in their release notes ( [url removed] ). Without belaboring the ever-present "crash on quit" issue and "accessibility nag" issue that Wordfast 5 still suffers from, I'm curious if the app will even run on the new OS.
[/quote]

It is normal practice not to use new iterations of the Mac OS until it has been through at least two or three updates. The first version will always contain numerous glitches that could affect your work. You can, of course, install it on a separate computer, drive, or partition and try it out, but for serious activity you should stay with what you know works.

Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)? | Prudent advice

$
0
0
Forum: Wordfast support
Topic: Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)?
Poster: Jeff Chapman
Post title: Prudent advice

Yes, Tom, that is of course prudent advice. I'm just wondering if there are any specific issues right off the bat that anyone has encountered.

Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)? | No problem so far

$
0
0
Forum: Wordfast support
Topic: Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)?
Poster: JohnWhi
Post title: No problem so far

I have not noticed any problem so far with Wordfast Pro 5.18 in 11.0.1. I admit I have not yet completed a project in Big Sur, just looked around Wordfast to see things were in place.

Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)? | So far, so good...

$
0
0
Forum: Wordfast support
Topic: Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)?
Poster: Jeff Chapman
Post title: So far, so good...

Wordfast 5.18.0 on macOS 11.0.1 does seem to open, and I'm able to reload one of my previous projects. So far, so good, although I haven't done much else with it yet.

It does still crash on quit. (I haven't seen a single app that exhibited such behavior in a very long time.) This was occurring back on macOS 10.15, though. Wordfast apparently released a beta that fixed it, but their official releases haven't caught up yet, and the latest official release still behaves the same.

Will post back with more, once I start using it a bit more as usual. (Obviously, as Tom mentioned, it's not advisable to upgrade your OS to the latest and shiniest version that's relatively untested, unless you're willing to live with more wonky behavior than usual. I just got curious about it and decided to try it out—I've got a few other machines that I can fall back on to return to "business as usual," in case it doesn't work out.)

XYZ project already exists (when in fact it doesn't)

$
0
0
Forum: Wordfast support
Topic: XYZ project already exists (when in fact it doesn't)
Poster: Reed James

For some reason, there are times when I import GLP files to WFP 5.18.0 and I get the message:

Sometimes this is true, but mostly it is not. Fortunately, I can translate the file in the online version of WFP, but if it is a longer project, it is much more cumbersome to do so. I have tried renaming the file and importing it from a different location on my computer, but it doesn't work. Thanks.

Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)? | I'm having problems with Big Sur

$
0
0
Forum: Wordfast support
Topic: Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)?
Poster: Joanna M Case
Post title: I'm having problems with Big Sur

Updated to Big Sur yesterday. Wordfast Pro working ok but (i) not highlighting the tag I want to include and (ii) not providing an open window with options from the glossary - I have to expand the window each time. And (iii) for some reason I can't now log into proz, so I've had to move over to the old iMac (Catalina) to write this message!
Update: Oh and now Wordfast has started crashing....

[Edited at 2020-11-20 13:28 GMT]

restore deleted project

$
0
0
Forum: Wordfast support
Topic: restore deleted project
Poster: Elene P.

Hello
Maybe you can help me. I was making neat my wordfast pro 5 working area and deleted all projects, among them the active one on which I have already worked for 5 hours.
How can I restore it?
I tried 'add project' - I don't understand where from.
In the project file there is no wf file, just the pdf..
I tried to import the project again, even if my work will be lost, it does not do it.
But maybe it is possible to restore it?!!!
Thanks a lot!!
Elene

Large translation memory (.txt) does not load

$
0
0
Forum: Wordfast support
Topic: Large translation memory (.txt) does not load
Poster: Luigi Benetton

I'm using Wordfast Pro 3 on a Mac, macOS 10.15.7 (Catalina)

When I load a translation memory, I usually get confirmation messages telling me the memory is "connected" to the project.

When I try to load a 350+ MB memory, I can go through the steps, but I don't get confirmation messages. I get no messages, not even error messages. WFPro3 seems to work at it, then returns to the dialog for loading memories.

This memory works fine for other people, even on remote server environments. It loads in a Windows remote environment I can access (but don't use).

Can anybody suggest why this might be happening, and how to fix it?

Wordfast Pro 5 Projects Not Showing Up on Project List + Problem with path

$
0
0
Forum: Wordfast support
Topic: Wordfast Pro 5 Projects Not Showing Up on Project List + Problem with path
Poster: Shizuka Otake

I'm having a very basic and very frustrating problem.
I bought Wordfast in July, tried using it a few times, and was successful with small documents. I never really did much with it.

My Mac had memory issues (unrelated to Wordfast), so I wiped the whole thing in November. I decided that the Catalina OS was problematic so I installed Mojave. I successfully reinstalled all my programs/applications and migrated my documents.

I was able to reinstall Wordfast. I tried creating projects, tms, and glossaries.
A few strange things happened.

1. Wordfast kept trying to save projects, tms, and glossaries in a specific path that no longer exists. (e.g. Users/Person1/desktop). The new path is Users/Person/desktop. I use browse to set up the path I want, this doesn't work, Wordfast keeps trying to go back to the old path, and I use browse again. Usually after I use browse twice, I can get Wordfast to select my desired path.

2. I'm able to create files called tms and glossaries and store them on the desired path.

3. When I try to save my project, I get an error message every time
saying "An error occurred during project creation."

4. But when I check the location on my computer, the project file has been created .

5. When I go to Wordfast, I can't see the project anywhere on the project list.

Long story short, I can't use Wordfast at all right now.
I DID send an urgent ticket on Thursday. I still haven't heard back.

Any help would be really appreciated.

Wordfast Pro 5 Projects Not Showing Up on Project List + Problem with path | Add Project

$
0
0
Forum: Wordfast support
Topic: Wordfast Pro 5 Projects Not Showing Up on Project List + Problem with path
Poster: JohnWhi
Post title: Add Project

To add existing project files to the list, "Add Project" may work.

Large translation memory (.txt) does not load | Just an idea

$
0
0
Forum: Wordfast support
Topic: Large translation memory (.txt) does not load
Poster: esperantisto
Post title: Just an idea

[quote]Luigi Benetton wrote:

This memory works fine for other people…[/quote]

Do you know those other people personally? Then ask them to convert it to TMX, then try to import the TMX version.

Wordfast Pro 5 Projects Not Showing Up on Project List + Problem with path | Solved

$
0
0
Forum: Wordfast support
Topic: Wordfast Pro 5 Projects Not Showing Up on Project List + Problem with path
Poster: Shizuka Otake
Post title: Solved

Permissions on project folder showed fetching, not my user name.
So I changed permissions to my user name and applied read and write permissions to the enclosed content.

This didn't solve the problem so I went into the hidden library, found all Wordfast related documents, threw them out, threw out Wordfast.
This time I made sure to trash the documents under Shared.

I reinstalled and now Wordfast is saving projects for me.

Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)? | All working normally

$
0
0
Forum: Wordfast support
Topic: Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)?
Poster: James Muir
Post title: All working normally

I am running Wordfast 5.19.RC1-SNAPSHOT (whatever all that means), which is a beta, I think (see that thread on freezing for d/l link).

Big Sur: I tried it on my MacBook 1st and found no issues, so then installed it on the iMac.

The only problem I have had is that Winzip stopped working - which caused a panic and sent me off to find another MacBook with Catalina to use. However, I have since installed Keka for my zipping issues and my zip files are now readable on the Windows computer I u/l to once again.

So, all in all, it's fine for me.

Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)? | Keka

$
0
0
Forum: Wordfast support
Topic: Wordfast Pro supported and operating correctly on macOS 11.0 (Big Sur)?
Poster: Jeff Chapman
Post title: Keka

Yes, Keka seems to work really well for archiving files on macOS to send to Windows users. Good mention. I haven't heard any complaints from clients using Windows so far.
Viewing all 6144 articles
Browse latest View live