Compact glossary layout updated

As announced previously, an alternative glossary pane layout was made available as a plugin. The newest update (v.1.1.0) now includes 4 variants of that compact layout:

  • 1A
    • source: target [comment] | target [comment] | [comment] (separator | is styled as normal text — the same as in the original version)
  • 1B
    • source: target [comment] | target [comment] | [comment] (separator | is styled as target terms)
  • 2A
    • source: target (comment), target (comment), (comment) (separator , is styled as normal text)
  • 2B
    • source: target (comment), target (comment), (comment) (separator , is styled as target terms)

Once again, here’s the project itself, and here is where you can download the compiled version. If you run OmegaT on Java8, make sure to download the right build. On Java11 it doesn’t matter which build is used.

Comments, bug reports, complains, latest gossips and donations are always welcome.

Take care and good luck!

Export #OmegaT Project to Excel (UPDATE)

The earlier version of this script was described in this article. Here I’m announcing the update to the script which makes it possible to include:

  • Segment ID for each segment (applicable only for some file types)
  • Translator’s ID of the segment’s translation creator
  • Translator’s ID of the segment’s translation editor
  • Segment notes
  • Visual marks to show segments’ uniqueness or repetitions (grayish background, marks 1 or + in the dedicated column: for the first occurrence, or further instances of the repeated segment, respectfully)
  • Visual marks for alternative translations (different font color, mark a with a different background in the dedicated column)
  • Visual marks for untranslated segments (mark NT in the dedicated column)
  • Visual marks for paragraph boundaries (upper border over the source and target text which visually groups the text belonging to the same paragraph)

All of the above features are optional, though they are on by default. To disable or change them, editing the script is required, but all those lines are very easy to understand, they have comments, and are placed almost in the very beginning of the script:

Scripting window with the script options in focus

Unlike the earlier version, the script produces the tabular output:

Segment #Source TextTarget TextUniq/AlSegment IDCreatorChangerNote

The script can be downloaded from
SF.net repository
GitHub repository

Comments, suggestions, complains and donations are always welcome!

Happy spreadsheeting!

Export OmegaT project to an HTML table

A few years ago I wrote a script that exported the whole OmegaT to an HTML table. I used it a lot myself, and I know quite a few other people found it helpful too. The problem with the table produced by that script was that it had no way to show repeated or alternatively translated segments. I’ve rewritten the script since, but never published an announcement about that new version. Now I did a few more changes, and thought that it’s about time to fix that omission.

Continue reading

Alternative OmegaT Glossary Layout

It has been possible for quite some time now to choose which Glossary pane layout to use in OmegaT. Selection isn’t that great, only two layouts are provided: Default and Dictionary. But at the same time this feature had been introduced, it became possible to add custom layouts via plugins. I haven’t seen any, but the possibility is there. And just recently, Hiroshi Miura, a very prolific OmegaT developer, published a plugin skeleton just for this purpose. I used what he generously shared, and made an alternative compact layout for the Glossary pane.

It puts target terms right after the source term on the same line, and separates them only by a vertical bar and spaces. If there’s a comment for the term, it follows it immediately enclosed in square brackets. If OmegaT is set up to merge multiple target definitions for the same source term, and there are duplicated entries (i.e. two or more identical target terms for the same source term) with different comments, the comments will be separated by the vertical bar, but the term itself won’t be repeated.

To enable this layout in OmegaT, download the plugin (the ready-to-use jar is in the Releases section), put it into plugins subfolder in your OmegaT config folder, restart OmegaT, and select it under PreferencesGlossaryGlossary layout: → Compact Glossary Layout

Happy translating!

A [slightly more] sane initial OmegaT setup. Part I

Over the years of my daily use of OmegaT (I started using it back in 2009), I helped quite a few translators to make their first steps with the program. The funny thing is that almost every time a new person tries to learn the program, we change some of the same defaults to make it more usable and comfortable. So I thought it might be a good idea to collect those few initial setup changes here as a small series of posts so that anyone could refer to them at any point.

The first thing I always have new users change is the Editor behavior.

Continue reading

OmegaT Live preview (based on LibreOffice)

Below you’ll find a quick and dirty live preview solution for OmegaT on GNU/Linux.

In order for it to work, you’ll need any command line converter to convert your target files to PDF, and any PDF viewer to view the converted file. In the solution provided here Zathura PDF viewer is used. It is a very lightweight, keyboard-driven (albeit with vi-like keybindings) application that can invert document colors using a custom color scheme, and, most importantly, it reloads documents as they are changed, but keeps the previously open position, which makes it ideal for live previewing. Target files are converted using LibreOffice since I had it installed anyway; but any other command line tool that converts to PDF would do.

Continue reading

#OmegaT Merge/Split script updated

These days I often get jobs in IDML format. Luckily such files can be translated in OmegaT either with Okapi filters plugin, or, if the files are not so plain and simple, by creating an OmegaT project in Okapi Rainbow. But it’s somewhat beyond the point. The point is that with these files the wonderful script to merge and split segments wasn’t working, at least for merging.
As you’ve rightly guessed, this tiny post is to inform that it has been fixed, and the updated script could be downloaded from the SF.net repository.

Happy merging and splitting, fellow OmegaTers!

Unlock Text Caret on #OmegaT Startup

As many have probably noticed, in OmegaT it’s now possible to unlock cursor. This means that one can select and copy text anywhere in the Editor pane without using the mouse. With the unlocked cursor you simply press up or down, and the text caret will move beyond the target segment. The lock is triggered with F2. Cool! But there’s no way to make this behavior default — every time OmegaT is started, cursor is locked.

Since I prefer it to be unlocked most of the time, here’s a little workaround. Below is a little script that needs to go into scripts_folder/application_startup/:

def gui() {
    editor.editor.lockCursorToInputArea = false
    editor.editor.updateLockInsertMessage()
}
return

This little snippet should be saved as a plaintext file with extension groovy, for instance, unlock.groovy. Next time OmegaT 4.2 or newer is started, the cursor is going to be unlocked from the get-go!

Zip current #OmegaT project

Here is a script that packs the current OmegaT project into a zip-file in the same location as the project folder.

Since the script doesn’t exclude anything, it might be a good idea to use another script to remove target and backup files.

Big kudos to cApStAn sprl for sponsoring the script for zipping.