ProZ.com Translation Forums

SAXParseException : where to look? | Check the log file

Didier Briel — Fri, 10 Feb 2012 19:37:00 +0000

Forum: OmegaT support
Topic: SAXParseException : where to look?
Poster: Didier Briel
Post title: Check the log file

[quote]JoyeuxDrille wrote:

I call "launching my TM", loading the project I already created with OmegaT.

I know it's very probably a TMX file, I just don't know how to find out which one it is. That is the essence of my question. [/quote]
Check the log file.

Location (depending on your operating system) is given in the (at least English) manual.

Didier

SAXParseException : where to look? | Pinpointing the right TMX file

JoyeuxDrille — Fri, 10 Feb 2012 18:20:00 +0000

Forum: OmegaT support
Topic: SAXParseException : where to look?
Poster: JoyeuxDrille
Post title: Pinpointing the right TMX file

I call "launching my TM", loading the project I already created with OmegaT.

I know it's very probably a TMX file, I just don't know how to find out which one it is. That is the essence of my question.

SAXParseException : where to look? | What do you call "launching your TM"?

Didier Briel — Fri, 10 Feb 2012 16:48:00 +0000

Forum: OmegaT support
Topic: SAXParseException : where to look?
Poster: Didier Briel
Post title: What do you call "launching your TM"?

[quote]JoyeuxDrille wrote:
BUT. But, but, but, now I've got an issue. Here's the error shown by OmegaT when I try launching my TM.[/quote]

What do you call "launching your TM"?

[quote]
Fatal error at line 8, column 153
org.xml.sax.SAXParseException: The element type "e0" must be terminated by the matching end-tag ""

I also see this message for column 60 and column 204. This should be self-explanatory, but unfortunately I don't know which file I should be looking into... Does anyone know how I may find out which is the faulty file? [/quote]
Hard to say without the circumstances.

If it happens when opening OmegaT, it is possible it's one of the TMXs (either project_save.tmx in the /omegat folder, or one of the external TMXs).

Didier

[Edited at 2012-02-10 16:49 GMT]

SAXParseException : where to look?

JoyeuxDrille — Fri, 10 Feb 2012 16:02:00 +0000

Forum: OmegaT support
Topic: SAXParseException : where to look?
Poster: JoyeuxDrille

Hi,

I have used OmegaT for about a week now. I aligned five texts withtout any issue. Then, I translated a text using OmegaT, produced the target text and voilà! Got myself a nice translation, and got my TM going.

BUT. But, but, but, now I've got an issue. Here's the error shown by OmegaT when I try launching my TM.

Fatal error at line 8, column 153
org.xml.sax.SAXParseException: The element type "e0" must be terminated by the matching end-tag ""

I also see this message for column 60 and column 204. This should be self-explanatory, but unfortunately I don't know which file I should be looking into... Does anyone know how I may find out which is the faulty file?

Can't install the spell check dictionary | OmegaT dictionary

mistigri — Thu, 02 Feb 2012 15:16:00 +0000

Forum: OmegaT support
Topic: Can't install the spell check dictionary
Poster: mistigri
Post title: OmegaT dictionary

Thanks alot, Didier

I will follow your steps – I am working with version 2.30_3
Hope itll work this time ...

Yvonne

Can't install the spell check dictionary | Update your version, or install the dictionaries manually

Didier Briel — Thu, 02 Feb 2012 14:48:00 +0000

Forum: OmegaT support
Topic: Can't install the spell check dictionary
Poster: Didier Briel
Post title: Update your version, or install the dictionaries manually

[quote]mistigri wrote:
I cannot even find an English dictionary that could be used for this purpose

Otherwise Omegat runs smoothly on my Mac

But it is pretty disturbing to counter-check every document with word or TextEdit afterwards [/quote]
The automatic installation stopped working because Oracle transferred OpenOffice.org to Apache and, in the process, broke some web pages.

[quote]
Is there someone out there who could possibly post a step for step manual
[/quote]

You can read [url removed] if you are using the "Latest version" (2.5) or wish to do a manual installation, or update to the latest version if you are using 2.3.

In 2.3.0 update 6, the URL used for the dictionaries has been fixed, after we found a working one.

Didier

Can't install the spell check dictionary | I do experience the same problem

mistigri — Thu, 02 Feb 2012 14:37:00 +0000

Forum: OmegaT support
Topic: Can't install the spell check dictionary
Poster: mistigri
Post title: I do experience the same problem

I cannot even find an English dictionary that could be used for this purpose

Otherwise Omegat runs smoothly on my Mac

But it is pretty disturbing to counter-check every document with word or TextEdit afterwards

Is there someone out there who could possibly post a step for step manual

Y

Google Translate API key not working on Mac OS X Lion

Jennifer Barnett — Mon, 12 Dec 2011 22:23:00 +0000

Forum: OmegaT support
Topic: Google Translate API key not working on Mac OS X Lion
Poster: Jennifer Barnett

I cannot get Google Translate to work, been trying on and off for 2 weeks with kind advice from the OmegaT forum on Yahoo. However, next to not liking the message string layout there, my replies don't always get posted despite a notice that they've been received so I've given up there and moved over here.

Also tried making a script as instructed in the blog below but it did not connect with the OmegaT application. I am waiting for a reply from the blogger regarding this failure.
japanesetranslator.co.uk/2011/11/omegat-google-translate-v2-mac-os-x/

The set up:
iMac PowerPC G4 bought in 2003, version 10.5.8
iMac intel core i5, bought in 2011, version 10.7.2 (Lion)
OmegaT 2.3.0_3 ( appears in the MT window but no translation)
Text Wrangler was used to enter the api key in the OmegaT plist.

Have created a new API key: didn't work.

I was not so surprised that it didn't work on my old iMac but am perplexed to find the problem repeated on the new one with newly downloaded applications. This could indicate that I am repeating the same mistake(s) but I can't find any.

Looked around in my Google account, and found 'report' in the menu items on the left. The contents read 'plug in missing'. Did not say what or where. Which plug-in could this be and where should it plug in?

There's something else that's odd that may possibly have something to do with the problem. On the new iMac, OmegaT unhelpfully inserts the source text for each segment and that must then be deleted. Nothing I change in the 'view' menu helps and I am at a loss to find a relevant item in the other menus. This will probably turn out to be terribly simple but what caused this and how can I make it stop? Should this turn out to be a definite separate issue, I will happily start a new post on it.

Luckily I carry on very well, if not faster, without the Google suggestions but it is supposed to work after all.

OmegaT automatic glossary insertion - anything new? | It could be other languages

Didier Briel — Thu, 08 Dec 2011 14:40:00 +0000

Forum: OmegaT support
Topic: OmegaT automatic glossary insertion - anything new?
Poster: Didier Briel
Post title: It could be other languages

[quote]esperantisto wrote:
no such functionality. That’s life. AFAIK, there’s been an RFE on such feature, but its implementation is a matter of more or less distant future. If you want it quick, learn Java and code ;-)

[Edited at 2011-12-08 14:33 GMT] [/quote]
With the new scripting plugin, it could be in other languages.

Didier

OmegaT automatic glossary insertion - anything new? | So far,

esperantisto — Thu, 08 Dec 2011 14:31:00 +0000

Forum: OmegaT support
Topic: OmegaT automatic glossary insertion - anything new?
Poster: esperantisto
Post title: So far,

no such functionality. That’s life. AFAIK, there’s been an RFE on such feature, but its implementation is a matter of more or less distant future. If you want it quick, learn Java and code ;-)

[Edited at 2011-12-08 14:33 GMT]

OmegaT automatic glossary insertion - anything new? | ok

VojtaDziewiecki — Thu, 08 Dec 2011 07:04:00 +0000

Forum: OmegaT support
Topic: OmegaT automatic glossary insertion - anything new?
Poster: VojtaDziewiecki
Post title: ok

Ok, thanks, I'll probably try asking there.

OmegaT automatic glossary insertion - anything new? | Try the yahoo list

Susan Welsh — Tue, 06 Dec 2011 20:55:00 +0000

Forum: OmegaT support
Topic: OmegaT automatic glossary insertion - anything new?
Poster: Susan Welsh
Post title: Try the yahoo list

You'll get more of a response there. I don't know the answer to your question. In my language pairs it would not be useful, I don't think.

OmegaT automatic glossary insertion - anything new? | That's not the point

VojtaDziewiecki — Tue, 06 Dec 2011 19:48:00 +0000

Forum: OmegaT support
Topic: OmegaT automatic glossary insertion - anything new?
Poster: VojtaDziewiecki
Post title: That's not the point

Thanks Susan.
I know about the right clicking, but I need to insert all the translations from the given segment at once, each in place of the original word, the feature described in the discussion on yahoo groups.
Right clicking is useful, however, it is time consuming.

OmegaT automatic glossary insertion - anything new? | Right click

Susan Welsh — Tue, 06 Dec 2011 19:25:00 +0000

Forum: OmegaT support
Topic: OmegaT automatic glossary insertion - anything new?
Poster: Susan Welsh
Post title: Right click

In 2.5.0_02, which is what I'm using, you highlight the term in the glossary and right click, and it inserts it in your text. I'm not sure how long this has been an option.
Also ctrl+g creates a glossary entry from the highlighted word in the source text.

OmegaT automatic glossary insertion - anything new?

VojtaDziewiecki — Tue, 06 Dec 2011 13:18:00 +0000

Forum: OmegaT support
Topic: OmegaT automatic glossary insertion - anything new?
Poster: VojtaDziewiecki

I've read this old discussion recently:
[url removed]
I really miss the possibility to insert glossary matches to every segment automatically, or with one keyboard short cut for all glossary matches in that segment, like here.

The word order in Czech and Polish is often very similar, this would help me a lot...

Has there been any development of this feature? Can I hope to find it in some future version of OmegaT? Or did the developers decide not to make it?

[Edited at 2011-12-06 13:39 GMT]

java.lang.ArrayIndexOutOfBoundsException | java.lang.ArrayIndexOutOfBoundsException [solved ?]

Jon Babcock — Fri, 02 Dec 2011 13:08:00 +0000

Forum: OmegaT support
Topic: java.lang.ArrayIndexOutOfBoundsException
Poster: Jon Babcock
Post title: java.lang.ArrayIndexOutOfBoundsException [solved ?]

Thanks, Didier.

While waiting for my post here to be approved, I discovered the OmegaT yahoo group. I'll probably move subsequent questions about using OmegaT to that venue, as you suggest.

By installing the newer OmegaT-2.5.0_4 (both versions-- with and without embedded java) and by opening the Chinese 86577-line plain text file in LibreOffice and saving it as an .odt file, I was able import it into the appropriate OmegaT project without a problem. In fact, the job consists of two large files; the second one is 98778 lines in size. Once in .odt format, I was able to load both of these into the OmegaT project, producing about 185,355 segments in total. So I will use this later version of OmegaT with .odt source files henceforth.

Just now I tried again to load the text file that wouldn't load under OmegaT-2.3.0_1 and that originally prompted my post.
It loaded without a problem! In fact at some point while waiting for my post here to be approved yesterday I did change the Options > File Filters > Text Filter Options which you mention, from its default at Empty Lines to Line Breaks. Perhaps this was the solution, so simple after all!

Yesterday, I was indeed able to load much smaller utf8 text files of around 500 lines of Chinese into the project, but I didn't experiment enough to find the size at which OmegaT throws the ArrayIndexOutOfBoundsException error. And now I can't remember whether this was BEFORE or AFTER I had changed the Text Filter Options from Empty Lines to Line Breaks.

I'm just beginning to try OmegaT for Chinese-English again after I gave up on it when it was in its very early stages of development many years ago. This time it looks like it's going to work. Persistence pays.

Jon-

PS:
Problem Solved:
Going back to OmegaT-2.3.0_1, I just confirmed that the problem in my case resulted from the Empty Lines default setting for Options > File Filters > Text Filter Options. After changing this to Line Breaks, I am able to load huge Chinese plain text files without a problem.

Note that my text files come from saving each file as plain text in LibreOffice ( [IP removed] ) [running on Linux Mint Debian Edition (LMDE)] where I am given Character Set and Paragraph Break options which I have set as UTF-8 and LF (line feed) respectively. IOW, I didn't choose CR&LF or CR for the paragraph breaks. Also note that I have added Language "Chinese" and Language Pattern "ZH-TW" with Break/Exception checked and Pattern Before set to \n (i.e. newline) and Pattern After set to nothing to the Options Segmentation Setup. This approach assumes that the text files have already been parsed into lines where each line will represent one segment in OmegaT. Of course there are many other ways to skin a cat, but this is working for me now.

[Edited at 2011-12-02 13:49 GMT]

Google MT v2 not working with Omega T | Vista and 7 require editing the .ini file in another place

Didier Briel — Fri, 02 Dec 2011 12:19:00 +0000

Forum: OmegaT support
Topic: Google MT v2 not working with Omega T
Poster: Didier Briel
Post title: Vista and 7 require editing the .ini file in another place

[quote]Susan Welsh wrote:
I tried to help a friend who uses Vista set up her GT key, and there was a problem with changing the configurations file--Vista would not allow it.[/quote]
This is addressed in the link I gave above.

[quote]
I believe he renamed the existing .ini file and made a new one with the key information in it. [/quote]
Yes. Quoting the howto:
[quote]
3.2. Move the .ini file somewhere else on your disk, as the files within
the original directory are in read-only mode
3.3. Open the file .ini in a plain-text editor
3.4. Ad the following line to the text in the file:
-Dgoogle.api.key=YourGoogleAPIKeyHereMineHas39Characters
3.5. Save the file and move it back to the OmegaT folder
(Users of Windows XP can edit the .ini file directly in Program Files
supposing they are being logged-in as Administrator)
[/quote]

Didier

Google MT v2 not working with Omega T | Vista problem?

Susan Welsh — Fri, 02 Dec 2011 12:03:00 +0000

Forum: OmegaT support
Topic: Google MT v2 not working with Omega T
Poster: Susan Welsh
Post title: Vista problem?

I tried to help a friend who uses Vista set up her GT key, and there was a problem with changing the configurations file--Vista would not allow it. I am NOT an expert by any stretch of the imagination, so I asked someone for help who knows more. If following Didier's link doesn't help, I will try to reconstruct what he did. I believe he renamed the existing .ini file and made a new one with the key information in it. It worked fine after that.

PS - your link is no good

[Edited at 2011-12-02 12:04 GMT]

OmegaT tmx parsing | Check for illegal characters

Samuel Murray — Fri, 02 Dec 2011 10:24:00 +0000

Forum: OmegaT support
Topic: OmegaT tmx parsing
Poster: Samuel Murray
Post title: Check for illegal characters

[quote]Didier Briel wrote:
TMXs produced by SDL/Trados often contain illegal XML characters.[/quote]

Yes. Here is a little program that fixes some of them:
[url removed]
Run your TM through the TMXfixer (use the silent one first), and see if OmegaT accepts it.

Google MT v2 not working with Omega T | Check how you entered your key

Didier Briel — Fri, 02 Dec 2011 10:05:00 +0000

Forum: OmegaT support
Topic: Google MT v2 not working with Omega T
Poster: Didier Briel
Post title: Check how you entered your key

[quote]JMonte wrote:
I tried to use my Google MT v2 API in Omega T with Windows Vista, the automatic translation
will not work. The error message runs: Server returned HTTP response
code: 400 for URL:
[url removed]

I checked the MT configurations of Omega T (the INI file), they are
ok. I changed my Google MT v2 API key, the new key will not work, same error message as above.
[/quote]
I can only reproduce your error if I do not enter an API key correctly.

You could check this recent howto:
[url removed]

Didier

java.lang.ArrayIndexOutOfBoundsException | Submit a bug report or subscribe to the user group

Didier Briel — Fri, 02 Dec 2011 09:56:00 +0000

Forum: OmegaT support
Topic: java.lang.ArrayIndexOutOfBoundsException
Poster: Didier Briel
Post title: Submit a bug report or subscribe to the user group

[quote]Jon Babcock wrote:
Just started with OmegaT. Ver. 2.3.0_1 on Linux Mint Debian Edition (LMDE), with Chinese-English.
When I try to import a plain text, utf-8 encoded file of ZH-TW consisting of 86577 lines at an average of 6 or 7 Chinese characters per line, I get a java.lang.ArrayIndexOutOfBoundsException: -32768 error and the file won't load. Wonder if anyone has any suggestions what I might try. [/quote]
I couldn't reproduce it with a text file with 345,000 lines.

So, you could submit a [url= [url removed] ]bug report on Sourceforge[/url], or you could subscribe to the OmegaT Yahoo support group, where the issue could be analyzed in details.

What parameter are you using for the Text file filter (Options > File Filters > Text Files > Options)?

Just out of pure logic, you could try to split your file in three pieces, and see whether you are able to load the three pieces separately.

Didier

OmegaT tmx parsing | Is it…

esperantisto — Fri, 02 Dec 2011 06:08:00 +0000

Forum: OmegaT support
Topic: OmegaT tmx parsing
Poster: esperantisto
Post title: Is it…

[quote]liciamilo wrote:

I was sent a tmx file (SDL, level 1, utf-8 encoding) [/quote]

really UTF-8? As I remember, SDL exports to UTF-16. Make sure, it’s a) real UTF-8, and b) the encoding is correctly declared in the file header. To do that, open the file in any good text editor.

java.lang.ArrayIndexOutOfBoundsException

Jon Babcock — Thu, 01 Dec 2011 21:54:00 +0000

Forum: OmegaT support
Topic: java.lang.ArrayIndexOutOfBoundsException
Poster: Jon Babcock

Just started with OmegaT. Ver. 2.3.0_1 on Linux Mint Debian Edition (LMDE), with Chinese-English.
When I try to import a plain text, utf-8 encoded file of ZH-TW consisting of 86577 lines at an average of 6 or 7 Chinese characters per line, I get a java.lang.ArrayIndexOutOfBoundsException: -32768 error and the file won't load. Wonder if anyone has any suggestions what I might try. Thanks. Jon-
PS Java version is: Java(TM) SE Runtime Environment (build 1.6.0_26-b03)

[Edited at 2011-12-01 22:07 GMT]

Google MT v2 not working with Omega T

JMonte — Thu, 01 Dec 2011 19:58:00 +0000

Forum: OmegaT support
Topic: Google MT v2 not working with Omega T
Poster: JMonte

Hello,

I tried to use my Google MT v2 API in Omega T with Windows Vista, the automatic translation
will not work. The error message runs: Server returned HTTP response
code: 400 for URL:
[url removed]

I checked the MT configurations of Omega T (the INI file), they are
ok. I changed my Google MT v2 API key, the new key will not work, same error message as above.

any help is welcome! :-)

OmegaT tmx parsing | Check the log file, ask in the support group

Didier Briel — Thu, 01 Dec 2011 10:13:00 +0000

Forum: OmegaT support
Topic: OmegaT tmx parsing
Poster: Didier Briel
Post title: Check the log file, ask in the support group

You did dig an old post!

[quote]liciamilo wrote:
I was sent a tmx file (SDL, level 1, utf-8 encoding) alongside a text to translate. I moved it into the /tm folder, made sure that the languages where called the same in the tmx file and in my project, but still OT doesn't seem able to connect to the tmx file and search it.

I must be making a mistake (I'm quite new to the business) but I can't figure out what it is.

Any ideas/suggestions?
[/quote]
Do you have an error message?
TMXs produced by SDL/Trados often contain illegal XML characters.

What version of OmegaT are you using?

If running 2.3, you could check the log file (look at the user manual to find the location on your system) to see whether your TMX is loaded.
(In 2.5, TMX loading information is temporarily missing in the log.)

Ultimately, the more practical solution is to subscribe to the OmegaT Yahoo support group, where people will be able to give further advice and analyse your TMX if needed.

Didier

OmegaT tmx parsing | problems importing TM into OmegaT

liciamilo — Wed, 30 Nov 2011 15:02:00 +0000

Forum: OmegaT support
Topic: OmegaT tmx parsing
Poster: liciamilo
Post title: problems importing TM into OmegaT

Hi,

I was sent a tmx file (SDL, level 1, utf-8 encoding) alongside a text to translate. I moved it into the /tm folder, made sure that the languages where called the same in the tmx file and in my project, but still OT doesn't seem able to connect to the tmx file and search it.

I must be making a mistake (I'm quite new to the business) but I can't figure out what it is.

Any ideas/suggestions?

Thank you!

Li

Anyone using OmegaT on Mac? | Not always

esperantisto — Wed, 16 Nov 2011 05:57:00 +0000

Forum: OmegaT support
Topic: Anyone using OmegaT on Mac?
Poster: esperantisto
Post title: Not always

[quote]DouglasCarnall wrote:

It seems better to convert .rtf or .doc files to .docx [/quote]

Depends. With a DOCX file, you’re likely to end up with a tag forest, dealing with which may be more time-consuming as compared to formatting losses after DOC→ODT→DOC.

Anyone using OmegaT on Mac? | .docx superior to .doc with OmegaT

DouglasCarnall — Tue, 15 Nov 2011 22:58:00 +0000

Forum: OmegaT support
Topic: Anyone using OmegaT on Mac?
Poster: DouglasCarnall
Post title: .docx superior to .doc with OmegaT

It's worth adding that the direct import of Microsoft Word .docx files into OmegaT seems better than anything you can do with .doc-->.odt (open/libreoffice)-->OmegaT

It seems better to convert .rtf or .doc files to .docx in a recent version of Word (Microsoft Word 2008 for Mac), then import the .docx into OmegaT.

Help! Tokenizer wanted | No launch script on a Mac

Didier Briel — Fri, 11 Nov 2011 16:12:00 +0000

Forum: OmegaT support
Topic: Help! Tokenizer wanted
Poster: Didier Briel
Post title: No launch script on a Mac

[quote]Claude Koch wrote:
Yes, I did but I can't found the "OmegaT launch script"? Sorry, I sure miss something ;-( [/quote]
There is no launch script on a Mac.

So, either you get and unzip the generic version (e.g., OmegaT_2.3.0_03_Without_JRE.zip), and then you can follow the Linux howto, or you modify OmegaT.app, which is actually a folder.

See [url removed]

Basically, you put the content of the plugin in /plugins inside OmegaT.app, and you modify Info.plist with the same information you would use on a command line, except it uses XML syntax.

For more detailed support, I would recommend, as David did, to subscribe to the OmegaT Yahoo support group.

Didier

Help! Tokenizer wanted | I did!

Claude Koch — Fri, 11 Nov 2011 15:33:00 +0000

Forum: OmegaT support
Topic: Help! Tokenizer wanted
Poster: Claude Koch
Post title: I did!

Yes, I did but I can't found the "OmegaT launch script"? Sorry, I sure miss something ;-(