Menu
▾
▴
omegat-users
|
From: bluesepia <dv.green@...> - 2004-06-04 07:57:19
|
Hi,I just tried to reinstall OmegatT on Linux Suse 8.2 but when I try to run the program I get this error message Exception in thread "main" java.util.zip.ZipException: No such file or directory at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:112) at java.util.jar.JarFile.<init>(JarFile.java:117) at java.util.jar.JarFile.<init>(JarFile.java:55) I have Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.4.1-01) Java HotSpot(TM) Client VM (build Blackdown-1.4.1-01, mixed mode) I tried reinstalling java and OmegaT but I still get the same message. Where have I gone wrong? Thanks for any help. |
|
From: Karsten V. <vossdoku@...> - 2004-06-04 08:12:38
|
bluesepia wrote: > Hi,I just tried to reinstall OmegatT on Linux Suse 8.2 > but when I try to run the program I get this error message > > Exception in thread "main" java.util.zip.ZipException: No such file or > directory > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.<init>(ZipFile.java:112) > at java.util.jar.JarFile.<init>(JarFile.java:117) > at java.util.jar.JarFile.<init>(JarFile.java:55) > > I have Java(TM) 2 Runtime Environment, Standard Edition (build > Blackdown-1.4.1-01) > Java HotSpot(TM) Client VM (build Blackdown-1.4.1-01, mixed mode) Hi, I had a similar problem on Debian. I don't know what exactly is the problem, but with Sun Java 1.4.02 instead of Blackdown Java it works well. HTH Karsten -- Karsten Vo� ICQ#:129656852; Jabber:qxvxq@...; GG:5393896 |
|
From: Marc P. <mail@...> - 2004-06-04 08:29:35
|
Bluesepia, See Karsten's message. Until very recently, all the code was written by Keith, who aimed to make OmegaT compatible with Java 1.3.1 onwards. Ben and Maxym have introduced code in some very recent test versions which exploits the functionality of later versions of Java. Keith may still release a final build which is compatible with an older version of Java (the reason being that very recent versions of Java can't be installed on some older operating systems, notably Windows 95), but the consensus in the team is that future builds will be developed against the latest version of Java. This is necessary in order for OmegaT to take advantage of added functionality in Java, such as the automatic LaF detection or support for right-to-left languages. So, the upshot of this is that you may need an even newer version of Java, even though yours is quite recent. Just for the record, I am running OmegaT 1.3.15 on Java 1.4.1 (Sun, not Blackdown) on SuSE 7.1. I'm presuming by the way that you're launching OmegaT from the OmegaT directory. Launching it from a different directory returns a similar error but I doubt this is the cause of the problem - just wanted to make sure. Marc |
|
From: yosato_uk <yosato16@...> - 2004-07-13 00:03:53
|
Hi, Sorry to rake up an old problem but... I am trying to run OmegaT for the first time after installation but I have exactly the same error messages as below. Karsten and later Marc suggest updating JAVA, but I have not been able to solve the problem this way. I have tried various combinations -- various versions, including the latest one of Sun JAVA skd and of OmegaT, but no avail. I am using Fedora Core 2. If anybody has an idea -- say some combination known to work on Fedora, please let me know. Thanks in advance, Yo --- In Om...@ya..., Karsten Voss <vossdoku@g...> wrote: > bluesepia wrote: > > Hi,I just tried to reinstall OmegatT on Linux Suse 8.2 > > but when I try to run the program I get this error message > > > > Exception in thread "main" java.util.zip.ZipException: No such file or > > directory > > at java.util.zip.ZipFile.open(Native Method) > > at java.util.zip.ZipFile.<init>(ZipFile.java:112) > > at java.util.jar.JarFile.<init>(JarFile.java:117) > > at java.util.jar.JarFile.<init>(JarFile.java:55) > > > > I have Java(TM) 2 Runtime Environment, Standard Edition (build > > Blackdown-1.4.1-01) > > Java HotSpot(TM) Client VM (build Blackdown-1.4.1-01, mixed mode) > Hi, > I had a similar problem on Debian. I don't know what exactly is the > problem, but with Sun Java 1.4.02 instead of Blackdown Java it works well. > HTH > Karsten > > -- > Karsten Voß > ICQ#:129656852; Jabber:qxvxq@j...; GG:5393896 |
|
From: Marc P. <mail@...> - 2004-07-13 05:41:04
|
Hi Yo, Can you confirm that you are trying to launch OmegaT from the directory containing the jar file? Are you able to launch other Java applications? Marc |
|
From: Y S. <yosato16@...> - 2004-07-13 13:45:32
|
Hi Marc, Thanks for your reply. Just to answer your questions, 2004/07/13 (火) 06:41 に Marc Prior さんは書きました: > Can you confirm that you are trying to launch OmegaT from the directory > containing the jar file? > > Are you able to launch other Java applications? Yes to both questions. Regards, Yo > > > > OmegaT_1.4_beta is at: http://sourceforge.net/projects/omegat > > > Yahoo! Groups Links > > > > > > |
|
From: Marc P. <mail@...> - 2004-07-13 17:42:40
|
Hi Yo, This looks like a tough one, I must admit. One possibility: when you installed newer versions of the JRE or the SDK, did you ensure that the new version was actually launched? If you install a new version, unless you configure it as the default, the previous version will still be launched by default. You can launch the new version explicitly by entering the full path of the command. Apologies if this is very basic; I can't think of any other reason off-hand. Marc |
|
From: Y S. <yosato16@...> - 2004-07-13 18:05:37
|
Hi Marc, Thanks for your reply, but On 火, 2004-07-13 at 18:42, Marc Prior wrote: > did > you ensure that the new version was actually launched? If you install a new > version, unless you configure it as the default, the previous version will > still be launched by default. You can launch the new version explicitly by > entering the full path of the command. I was using the full path all the way through anyway... haven't set up the path yet. I wonder if there's any way round - even a radical one. Is it possible that something like this is due to some mismatch with a particular distribution or kernel? Or any other speculation? Regards, Yo |
|
From: Marc P. <mail@...> - 2004-07-13 18:26:34
|
Hi Yo, > I was using the full path all the way through anyway... haven't set up the path yet. Yes, I thought you probably knew what you were doing. :-) It was just a hunch. It has given me an idea though. I have the Blackdown JRE (not the SDK) installed on this system (SuSE 9.1), but I also installed the Sun SDK in order to be able to make modifications to the code and recompile. I then found that the binaries compiled on the Sun SDK would run on the SDK but not on the Blackdown JRE. Have you tried recompiling from the SDK, then running on the SDK? You might also try executing the binaries rather than creating a jar file. Marc |
|
From: Y S. <yosato16@...> - 2004-07-14 10:15:13
|
Hi Marc, Thank you very much for patiently considering my question. > Yes, I thought you probably knew what you were doing. :-) It was just a hunch. No, no, don't flatter me! I am in fact very much of a newbie in the linux world and have no Java programming experience. Thus, it's a bit tough to make sense out of the following but... > It has given me an idea though. I have the Blackdown JRE (not the SDK) > installed on this system (SuSE 9.1), but I also installed the Sun SDK in > order to be able to make modifications to the code and recompile. I then > found that the binaries compiled on the Sun SDK would run on the SDK but not > on the Blackdown JRE. > Have you tried recompiling from the SDK, then running on the SDK? You might > also try executing the binaries rather than creating a jar file. Are you talking about (re)compiling a JAVA source file? Presumably there is a source file in the OmegaT package and you can compile it yourself with SDK? Could you advise me on how to do this or refer me to some brief tutorial on the net? I don't even know what the difference is between binary and jar files. Regards, Yo |
|
From: Marc P. <mail@...> - 2004-07-14 14:57:32
|
Hi Yo, > No, no, don't flatter me! I am in fact very much of a newbie in the linux world Well, it makes a change for me to be advising another Linux user. Most OmegaT users are on Windows, and often I have no idea at all... > Are you talking about (re)compiling a JAVA source file? Yes. This is not at all difficult, believe me. You need the SDK. The source files are supplied with OmegaT and are in the directory /source. You execute the file "javac" and the source files as arguments, i.e.: cd <OmegaT path>/source <Java SDK path>/bin/javac *.java Execute the resulting binaries with java OmegaT instead of java -jar OmegaT.jar Producing a jar file is a little more involved but still not difficult; there is a description in the documentation on localization/customization on the home page. Marc |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X