Version 1.5 of Felix released

[Ryan Ginstrom]

I've just released version 1.5 of Felix. The latest version can be
downloaded here:

http://felix-cat.com/download/

Here are the main improvements/fixes in this release:
* New search and replace feature
* Bug fix: information was being dropped from TMX files
* Bug fix: F6 key works in glossary window to switch views
* Smaller memory footprint

You can see details about these changes in the following blog post:
http://felix-cat.com/blog/2009/10/08/felix-version-1-5-released/

Over the next month or so, I plan to make several mini releases with
fixes and new features.

[Charles Aschmann]

Just used the new Find feature. It found what I was looking for, but in
the results, it reversed the source and the target for some reason,
making English the source and Japanese the target. When I use the memory
normally to translate, the order is correct.
This was a memory exported from DVX, which for some reason screws up the
source and target. I reversed it in Olifant and imported the TMX into
Felix. Memory Manager shows the Japanese Source and English Target, but
the new Find function has them reversed.

Charles Aschmann

[Ginstrom IT Solutions (GITS)]

> [mailto:felix...@googlegroups.com] On Behalf Of Charles Aschmann

> Just used the new Find feature. It found what I was looking
> for, but in the results, it reversed the source and the
> target for some reason, making English the source and
> Japanese the target. When I use the memory normally to
> translate, the order is correct.

Is it only with this particular memory? The source and target languages are
in the right order for other memories?

Would it be possible to send me this memory file to look at?

Regards,
Ryan

=================================
Ryan Ginstrom
Felix Translation Memory Software
sup...@felix-cat.com
http://felix-cat.com/
=================================

[Charles Aschmann]

I think I found the problem with this.

The memory I was using was TMX from DVX. The version of DVX I am using
has a peculiar habit of reversing the memory when exporting to TMX. I
put it back in the JA source EN-US arrangement in Olifant, and I saved
it on top of itself. When I opened this TMX in Felix, I got the problem.
I the same memory as ftm in Felix, and the problem disappeared.
I then took another exported memory, reversed it in Olifant and used
Save As. No problem, even when using it directly from the TMX file. So I
guess saving over the file in Olifant left something in the header
material that triggered the problem in Felix. Probably an Olifant
problem, not Felix problem.

Charles Aschmann

[Ginstrom IT Solutions (GITS)]

> [mailto:felix...@googlegroups.com] On Behalf Of Charles Aschmann

> from the TMX file. So I guess saving over the file in Olifant
> left something in the header material that triggered the
> problem in Felix. Probably an Olifant problem, not Felix problem.

OK, thanks for the follow-up.

If you only want to reverse the source and translation of a Felix memory,
there is a stand-alone app that was mentioned recently on this site: Xelif.
Here's the URL:

http://felix-cat.com/tools/xelif/