Archive for the 'Felix' Category

New documentation for scripting API

Dec. 10th 2010

I’ve just published new documentation for the Felix scripting API.

Go to the online API docs.

These new docs are updated and go into a fair amount of detail.

You can also download the docs in Microsoft Help format. If clicking the link doesn’t download the file for you, then right-click the link and select “Save Link As…” Also note that Windows may block the content because it’s from the Internet. To release the block, right click on the file on your computer, and from the Properties dialog, click the button to unlock it.

What is the scripting API?

The scripting (automation) API is a COM interface for controlling Felix. It lets you write macros/scripts to control the behavior of Felix, and automate repetitive tasks. This API is available for all Felix installations.?

Posted by Ryan Ginstrom | in Felix, resources | No Comments »

Getting data into Felix

Dec. 9th 2010

Translation data can come in a wide range of formats; this is especially true of glossaries. Felix supports a variety of translation-memory and glossary formats, and by using the Felix import features in Excel, you can get data in many different formats into Felix.

Below are some of the many file formats that you can get into Felix.

Translation Memory Formats

Format How to Open
FTM .ftm is the native Felix translation memory format. You can open it by selecting File >> Open from the Felix Memory window, or dragging and dropping the file into the Memory window.
Felix XML Felix translation memories are XML files. Felix TMs saved with the .ftm and .xml extensions have the same structure, and can be opened in the same way.
TMX Felix supports both the 1.1 and 1.4 TMX standards. To open a TMX memory, select File >> Open from the Felix Memory window, and set the file type to “TMX,” or drag and drop a TMX file into the Memory window.
Trados Text Trados memories can be exported as a special text format. You can also open these TMs in Felix.
To open a translation memory in Trados text format, select File >> Open from the Felix Memory window, and set the file type to “Trados Text,” or drag and drop a Trados text file into the Memory window.
CSV You can import translation memories in this format by going through MS Excel. Open the file in Excel, and if necessary, arrange the columns so that the translation column is the next column to the right from the source column. If there is a context column, make sure that is to the right of the translation column. Next, select the source cell of the top row, and from the Felix menu, select Add Memory. See the relevant section of the manual for details.
Tab-separated Text The process for importing translation memories in this format is the same as for CSV files, above
Other XML Any translation memory in a tabular/table format can be imported into Felix via Excel. The process for importing translation memories in this format is the same as for CSV files, above

Glossary Formats

Format How to Open
FGLOSS .fgloss is the native Felix glossary format. You can open it by selecting File >> Open from the Felix Glossary window, or dragging and dropping the file into the Glossary window.
Felix XML Felix glossaries are XML files. Felix glossaries saved with the .fgloss and .xml extensions have the same structure, and can be opened in the same way.
Multiterm Multiterm is a Trados text-based glossary format. Felix can open both versions 5.x and 6.x of Multiterm text files.
To open a Multiterm glossary, select File >> Open from the Felix Glossary window, and set the file type to “Multiterm,” or drag and drop a Multiterm file into the Glossary window.
Tabbed Text You can open glossaries in tabbed-text format in Felix. To do so, select File >> Open from the Felix Glossary window, and set the file type to “Tabbed Text.”
CSV You can import glossaries in this format by going through MS Excel. Open the file in Excel, and if necessary, arrange the columns so that the translation column is the next column to the right from the source column. If there is a context column, make sure that is to the right of the translation column. Next, select the source cell of the top row, and from the Felix menu, select Add Glossary. See the relevant section of the manual for details.
Other XML Any glossary in a tabular/table format can be imported into Felix via Excel. The process for importing translation memories in this format is the same as for CSV files, above

In addition to the formats listed above, any tabular/table-based file that can be opened in Excel can be imported into Felix. For example, you can download a glossary in HTML format from the Internet, open it in Excel, and from there import it into Felix.

If you have an existing translation and original, and want to create a translation memory from it, then I suggest using the free Align Assist tool.

If you have the need to import a file format that’s not supported now, please let me know in the comments, or from the contact page.

Posted by Ryan Ginstrom | in Felix, tips | No Comments »

Version 1.6.4.1 of Felix released

Dec. 5th 2010

I’ve just released version 1.6.4.1 of Felix

You can download the latest version here.

This is a minor bug-fix release. The main improvements are as follows.

  1. Bug fix: Saving results as TMX or Trados text saved entire translation memory
  2. Translation memories and glossaries can be saved in tabbed text format
  3. Bug fix: All details became visible in Edit mode

1. Bug fix: Saving results as TMX or Trados text saved entire translation memory

Saving search results in the Search Window in TMX or Trados text format caused the entire translation memory to be saved.

Back to top

2. Translation memories and glossaries can be saved in tabbed text format

You can now save translation memories (TMs) and glossaries in tabbed-text format. For now, it’s not possible to select which fields are saved; it will be possible to select the fields (and whether a header row is output).

Back to top

3. Bug fix: All details became visible in Edit mode

When switching to Edit mode (Ctrl+E), all detailed record information became visible. This information now stays hidden.

Back to top

Posted by Ryan Ginstrom | in Felix, release | No Comments »

Felix tip: Use a macro to give Felix focus

Dec. 4th 2010

The latest version of Felix (1.6.4) has an expanded COM API. One of the new things you can do with this API is control the size and focus of the memory and glossary windows.

As an example, here is a Word macro that will raise Felix to the top of your screen, while keeping the keyboard focus in Word. This is useful if you return to Word after an internet search, etc., and don’t want to go searching around for the Felix window.

Sub ActivateFelix()

    Dim felix As Object
    Set felix = CreateObject("Felix.App")
    felix.Visible = True
    Call felix.app2.MemoryWindow.Raise

End Sub

Now if you assign a keyboard shortcut for this (in Word 2010, it would be File >> Options >> Customize Ribbon >> “Customize” keyboard shortcuts button, then select Macros >> ActivateFelix >> “your keyboard shortcut”).

You could also create a “document changed” event handler, so that every time Word gets focus, Felix is raised to be visible. The code for this is a bit too involved for this blog post, but you can see the Microsoft documentation for how to write document event handlers.

In a future release of Felix, I plan on making functionality similar to this (also remembering the widow sizes and positions) available as a Felix option.

I’ll be updating the API documentation soon with all the new stuff, but for the meantime, here are the APIs for the memory and glossary windows:

App.App2.MemoryWindow:

  • Raise (method)
  • Left (int)
  • Top (int)
  • Width (int)
  • Height (int)

App.App2.GlossaryWindow:

  • Raise (method)
  • Left (int)
  • Top (int)
  • Width (int)
  • Height (int)
Posted by Ryan Ginstrom | in Felix, tips | 1 Comment »

Felix version 1.6.4 released

Dec. 3rd 2010

I’ve just released version 1.6.4 of Felix.

Download the latest version here.

The main fixes and improvements are as follows.

  1. Bug fix: Felix was failing to load corrupt TMs
  2. “Details” links for Felix matches
  3. Simple glossary view
  4. Expanded COM API
  5. Default context
  6. Memory Manager: Undo action added for deleted records
  7. Search Window: Searches are now faster
  8. Search Window: Delete search results
  9. Search Window: Able to search by TM/glossary name
  10. Excel: Hidden cells are skipped
  11. PowerPoint bug fix: Could not cancel from “Next Slide” dialog

1. Bug fix: Felix was failing to load corrupt TMs

Felix would sometimes fail to load corrupt TMs. This was fixed so that the user has the option of discarding the corrupt/invalid entry and continuing.

Back to top

2. “Details” links for Felix matches

There are now “Details” links ([>>] in glossary windows) to view details about translation and glossary matches. Click a link to view information such as the date the record was created, who created it, and how many times it has been used.

Back to top

3. Simple glossary view

You can now choose a streamlined glossary view, with only the minimum information displayed. This allows more matches to fit on the screen, and makes it easier to check glossary matches.

To toggle between full and simple view, select View >> Simple View.

Back to top

4. Expanded COM API

The COM interface has been expanded considerably. Now it is possible to load and save TMs/glossaries, set TM/glossary properties, iterate through records, and more.

Back to top

5. Default context

You can now set a default context entry for all new translations you add. To do so, go to the Memory Manager (Tools >> Memory Manager), and click “Edit” for the desired TM/glossary. Next, enter a context value and click Submit.

Note that default context values are for that TM/glossary only, and only apply for the current session. This will be improved in a future release.

Back to top

6. Memory Manager: Undo action added for deleted records

It’s now possible to undo a deleted entry from the Browse page.

Back to top

7. Search Window: Searches are now faster

The searches in the Search Window are now considerably faster if you have a large TM/glossary.

Back to top

8. Search Window: Delete search results

There is now an option to delete all matching results in the Search Window. This is useful when you want to delete many entries at once. It is also useful for splitting TMs/glossaries: if you first save the search results to a separate TM, and then delete them from the current one, you have split your TM.

Back to top

9. Search Window: Able to search by TM/glossary name

You can now use the “mem:” or “gloss:” tag to search in a specific TM or glossary. In the Search Window, click “Search Help” to get a full list of available tags, with examples.

Back to top

10. Excel: Hidden cells are skipped

Hidden cells are skipped in Excel when using the “Look up Next” action, auto translation, or register glossary/memory action

Back to top

11. PowerPoint bug fix: Could not cancel from “Next Slide” dialog

Clicking Cancel in the Next Slide dialog would just bring that dialog up again until you made a choice and clicked OK. It’s now possible to cancel.

Back to top

Posted by Ryan Ginstrom | in Felix, release | 1 Comment »

Using Analyze Assist with MS Office 2007/2008 format

Dec. 2nd 2010

The current version of Analyze Assist can’t recognize the new “.docx”/”.pptx”/”xlsx” file extensions in MS Office 2007/2010 by default. I will be adding these definitions in the next release of Analyze Assist, but in the meantime, you can configure Analyze Assist to recognize these file formats.

Analyze Assist uses something called “segmenters,” and you can add the “-x” extensions to the various segmenters to make Analyze Assist recognize them.

To do this, from the Tools menu, select Options. The following dialog appears.

Screen shot of the Options dialog in Analyze Assist

As shown in the screenshot above, add “;*.docx”, “;*.pptx”, and “;*.xlsx” to the respective fields, and click OK.

Analyze Assist will now recognize the “-x” formats.

Posted by Ryan Ginstrom | in Felix, tips, tools | No Comments »

Response to user feedback

Nov. 26th 2010

I recently got some great feedback on the Felix mailing list from Felix user Brian.

I thought that a blog post would be more fitting for my response, so here we go. Below, feedback from Brian is in blockquotes (gray background), and my responses are below that.

FELIX

Automatically disable Glossary searches during Auto Translate
(unnecessarily slows the AT process down).

This is a good point, especially if you’re using fuzzy glossary matching, which can be slow. The reason why Felix does glossary lookups during auto translate is because of an implementation detail that doesn’t really matter; it will be fairly easy to change it, so I’ll plan on doing so within the next few minor releases.

Ability to run through cells vertically in Excel (instead of just horizontally).

I’ve got a ticket for this, with a planned fix of releases 1.6.5 (the upcoming release is 1.6.4, due within a week).

Ability to skip hidden cells (rows/columns) in Excel. Not just for Auto Translate, but also when going through cells one at a time.

As you noted, I recently changed the Auto Translate functions so that they skip hidden cells. At the time, I didn’t make it a rule to skip hidden cells in general, because I wasn’t sure if I should make that a user option. I’ve convinced myself that it doesn’t need to be a user option (you could just tell the user to unhide the cells if they want them translated), so I’m now planning to skip hidden cells in all cases.

Ability to specify characters to ignore (assuming entire character string is made of up ignore characters). There was a separate post for this a few months ago.

This is another feature that I have a ticket for. To step back and talk about the big picture for a moment, I’m planning on changing the preference interfaces for MS Office/Excel/PPT. The first look at what the new interfaces will be like can be seen in the new shortcut customization/abbreviations list dialogs.

Therefore, what’s been holding up this feature has been the implementation of the new interface. Once the new preferences interface is done, there will be a cascade of new customization features for MS Office. I’m planning on doing this change by release 1.6.5 or (probably more realistically) 1.6.6.

Perhaps this is a MS limitation, but using Felix in a textbox in Excel, allow for running through individual sentences (segments) instead of only the entire textbox. Larger textboxes with lots of sentences get chopped off.

Yes, this is due to a rather arcane “feature” of MS Excel (follow the link if you’re really interested in such things). There is a workaround, which I hope to implement within the next few minor releases.

In Excel, ability for Felix to include textboxes when running through document (both manually and Auto Translate). Separately clicking individual textboxes one-at-a-time can be cumbersome, particularly for files almost entirely comprised of textboxes (can sometimes literally be hundreds of textboxes).

I’ve got a ticket for this in both Excel and Word. There are a couple of complexities with this, which is why I’ve been pushing it back for a while now, but I hope to get it implemented soon.

A way to have Context entered globally as you work in Felix.

This is another ticket, and I’m planning to have it done by the next release (1.6.4). One of the reasons for the new Memory Manager interface in Felix was to hang on new options like this. Soon, you’ll be able to go to a TM properties page and set a default context.

Store only text data in the TM, not additional font formatting data, and have font formatting data used for that particular segment only. I’m noticing that I’m getting font formatting from previous jobs inadvertently inserted into subsequent jobs that I don’t want the formatting carried over.

You can do this now. In Word or PowerPoint, go to the Felix menu, and then Felix Properties >> Format, and clear all the format-type checkboxes.

MEMORY SERVES

The questions below relate to Memory Serves, which is a free program for sharing Felix TMs and glossaries via a server.

In Memory Serves, allow Replace feature to distinguish between either Source, Translation, or both. Does not allow searching and replacing of specific field (i.e. I may want to replace text only in target language).

You can do this now using tags. (source: for source and trans: for translation).

Example: Replace “apple” in the source with “banana”.

From: source:apple
To: banaana

From the replace page, click “Replace Help” for a list of all the tags, and some examples.

Expanding search/replace items further, I want to be able to search by specific field (e.g. all entries modified by a specific user). For example, Ted is a new user. I’ve noticed that almost all of Ted’s entries are incorrect. I want to be able to see all of Ted’s entries and I also want to be able to delete all of Ted’s entries as needed.

Right. As above, you can use tags to specify various things, including who created the entry, when it was created, and so on. From the replace page, click “Replace Help” for a list of all the tags, and some examples.

I’m also planning to add a feature called “delete all matches,” by the next release of Memory Serves, and within one or two minor releases of Felix. This will be along the lines of the also recently added “save matches to TM/glossary”.

As a former user of Wordfast, I’ve got a lot of segments with extraneous code. For example, “&’B;” (Wordfast coding for line break), “&’BB;” (Wordfast coding for katakana “sa”), among others. Is there a way to search/replace the line break string with a line break in Felix?

You can do this in Memory Serves now, using the “regex” tag.

Here’s an example:

From: regex:&’BB;
To: \n

Felix also supports the regex tag, but in this case you would need to use the HTML tag “<br />”, which will cause a newline to be added. I’ve filed a ticket to support the “\n” tag as well.

[Bug?] When edits are made to records in Memory Serves, “Modified by” field shows computer name of PC running as server, not the user name.

Yes, this is a bug. It should be set to the name of the logged-on user, and fall back to the computer name if no one is logged in. From Felix, it should use the Felix user name.

GENERAL QUESTION

Does memory search speed (when performing Look Up command) slow as the number of entries increases? What about when multiple memories are loaded and active in Memory Manager? Is it faster/slower to search
100,000 entries in one memory or 100,000 in two or more memories?

Yes, the search slows down with the total number of entries, but not the number of memories (unless you’ve got something ridiculous like thousands of memories). Therefore, speed shouldn’t be a consideration for deciding whether to split up TMs.

I’ll also note that since you can save and load preference files, with all the currently open TMs and glossaries, you can use multiple TMs and glossaries, and then load them all just by dragging and dropping in the prefs file (or going to Tools >> Load Preferences).

Two things that tend to slow down searches the most are very long query sentences, and large glossaries with fuzzy gloss matching enabled.


I’d like to thank Brian for the great feedback, and encourage any user with feedback, suggestions, or problems to let me know. In addition to the mailing list, there is a forum (Japanese forum here), and you can use the contact page and email me directly, or leave comments in the blog.

Posted by Ryan Ginstrom | in Felix | No Comments »

Latest development roadmap for Felix

Oct. 26th 2010

As the new search and TM management features start to shape up in Felix, I want to give an updated roadmap for Felix development. Below are the main features/improvements I’m planning for the upcoming releases.

Please let me know if there’s something you want that’s not on the list, or if there’s a feature that’s especially important to you.

1.6 series (current series)

  • Improved search features
  • Improved memory management
  • QC features

1.7 series (early 2011)

  • Glossary placement
    (Automatically insert glossary translations)
  • Term extraction
    (Automatically extract glossary entries from TMs)
  • Template creation
    (Finding patterns/called “assembly” in Déjà Vu I think)
  • Rule-based glossary matching/placement
    (E.g. [\d\d億円] -> [\d.\d billion yen])

2.0 series (summer/fall 2011)

  • Plug-in framework
Posted by Ryan Ginstrom | in Felix | 3 Comments »

Version 1.3 of Align Assist released

Oct. 21st 2010

I’ve just released version 1.3 of Align Assist.

You can download the latest version here.

Wow, has it really been a year since version 1.2 was released? I had been neglecting Align Assist for a while, but fortunately some Align Assist users gave me good feedback, and spurred me to make some improvements. There are still a few things on my list, but I want to release the improvements so far now.

This is a good example of how the best way to get new features in your software is to tell the developers that you want them!

Below are the main improvements in this release.

  1. Default settings for TMs and records
  2. “Move To” command
  3. Improved Split function

1. Default settings for TMs and records

You can now set default values for translation memories and records. To set default values, in the Align window, from the Tools menu, select Defaults.

These default values will be saved in your Felix TM.

Back to top

2. “Move To” command

There is now a Move To command on the context menu. Right click a cell and select Move To from the menu, then enter a row number to move a cell to an arbitrary row.

Back to top

3. Improved Split function

The Split function (for splitting a segment into two segments) is now easier to use. Instead of cutting and pasting the text to split, you can just click in the text box where you want the segment to be split. The segment will be split at the location of the cursor.

Back to top

About Align Assist

Align Assist is a free (MIT license) utility for aligning legacy translations into translation memories. It supports a wide range of formats, and can create Felix and TMX memory files.

Posted by Ryan Ginstrom | in Align Assist, Felix | 3 Comments »

Version 1.6.3 of Felix released

Oct. 13th 2010

I’ve just released version 1.6.3 of Felix.

You can download the latest version here.

The main improvements and bug fixes in this version are as follows.

  1. Regular expressions allowed in Search window
  2. Manager action: Strip tags
  3. Manager action: Trim spaces
  4. Excel: Press escape key to halt long operations
  5. Excel: Hidden cells are not auto-translated
  6. Word: Press escape key to halt long operations
  7. Bug fix: Hiragana characters were not found in Search window


1. Regular expressions allowed in Search window

You can now use regular expressions in the Search window. To use a regular expression, prefix the query by the string “regex:”.

Back to top

2. Manager action: Strip tags

You can now batch strip all formatting tags from a TM or glossary from the Mangaer window.

To perform a batch action, go to the View or Browse page for the TM or glossary, and then click “Global Actions for {Memory Name}”.

Back to top

3. Manager action: Trim spaces

You can now trim surrounding spaces from the segments in a TM or glossary from the Mangaer window.

To perform a batch action, go to the View or Browse page for the TM or glossary, and then click “Global Actions for {Memory Name}”.

Back to top

4. Excel: Press escape key to halt long operations

In Excel, you can press the escape key to halt long operations: auto translation, adding glossaries, and adding memories.

Back to top

5. Excel: Hidden cells are not auto-translated

In Excel, hidden cells are no longer counted for auto translation

Back to top

6. Word: Press escape key to halt long operations

In Word, you can press the escape key to halt auto-translate actions

Back to top

7. Bug fix: Hiragana characters were not found in Search window

In the Search window, Hiragana characters were not found in some circumstances. This is now fixed.

Back to top

Posted by Ryan Ginstrom | in Felix, release | No Comments »
  • Search

  • Categories

  • Calendar

    April 2018
    M T W T F S S
    « Sep    
     1
    2345678
    9101112131415
    16171819202122
    23242526272829
    30  
  • Pages

  • Meta