RE: IllegalMonitorStateException
Easier said than done unless you know how to replace oracles JDK. I've found when the problem is arising from. In the FormulaParser's parse method. It does a synchronize on tokens. I commented this out and it all worked real nice. I put a synchronized in the method and it worked nice. I created a different object and synchronized on it failed again. I don't know what all this means, but I hope this can lead you in the right direction. Shawn Laubach SAIC - Web Developer B-1B System Support Management Division OC-ALC/LAB, Building 3001, Tinker AFB, Oklahoma dsn: 336-2473 comm: 405-736-2473 mobile: 405-245-9562 -Original Message- From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]] Sent: Friday, July 05, 2002 10:35 PM To: POI Users List Subject: Re: IllegalMonitorStateException oh and try another jdk just for kicks. Shawn Laubach wrote: Inside a class being called by a servlet, I'm getting a IllegalMonitorStateException thrown. I've narrowed it down to three lines of code where it is occuring. A row.createCell, cell.setCellValue, and cell.setCellStyle calls. I haven't had time to narrow it down any furthur. What I'm curious about, is why it would be thrown anyways. I've just started using the 1.8 dev release and I plan to try the 1.7 release next chance to see if that works. BTW, it runs fine standalone and other similar code runs fine both standalone and as a servlet. Shawn -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: IllegalMonitorStateException
On Sat, 2002-07-06 at 10:05, Adam wrote: Just a question from the lurker pool, but why are you stuck using JServ? The whole point of using 9iAS is the OC4J container, which is a licensed version of the Orion server. JServ hasn't been updated in years. Just for clarification (from my understanding): JServ | | Planning starts for a JServ 2.0 - complete rewrite. | | | Sun Donates Tomcat 3.0 | (which was a white elephant of sorts) | | Plans for JServ 2.0 discontinued | | | Tomcat 3.1 | | Tomcat 3.2 | | Plans for JServ 2.0 revised/reincarnated as Tomcat 4.0 | | Some dissenters from the Tomcat 4.0 (complete rewrite/redesign) | create Tomcat 3.3 (refactoring, incremental improvement over 3.2) | | Tomcat 4.0 born | | Several bugfixes later you can even run Tomcat 4.04 and have it | actuall work! | | Tomcat 4.1 development starts Oracle chose to not upgrade to Tomcat at any point in the last 4 years Adam Weed -Original Message- From: Laubach, Shawn - TAFB/LAB NCC (SAIC) [mailto:[EMAIL PROTECTED]] Sent: Saturday, July 06, 2002 8:51 AM To: 'POI Users List' Subject: RE: IllegalMonitorStateException This is running under Oracle 9ias Rel. 1 so 1. A 1.2.1 version is what they say the are completely compatible with. 2. JServ 1.1 (Don't have a choice in this) 3. Win2k fully patched 4. P4 1.4 1gig 2x36gig SCSI Hardrives I went back to the 1.5 version of POI and it reacted the same. Shawn Laubach SAIC - Web Developer B-1B System Support Management Division OC-ALC/LAB, Building 3001, Tinker AFB, Oklahoma dsn: 336-2473 comm: 405-736-2473 mobile: 405-245-9562 -Original Message- From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]] Sent: Friday, July 05, 2002 10:34 PM To: POI Users List Subject: Re: IllegalMonitorStateException Thats a threading error. POI isn't threaded. That totally makes no sense. I bet its a cooincidence as to where its happening. Please provide: 1. JDK version 2. Servlet container version 3. OS version 4. Hardware statistics. -Andy Shawn Laubach wrote: Inside a class being called by a servlet, I'm getting a IllegalMonitorStateException thrown. I've narrowed it down to three lines of code where it is occuring. A row.createCell, cell.setCellValue, and cell.setCellStyle calls. I haven't had time to narrow it down any furthur. What I'm curious about, is why it would be thrown anyways. I've just started using the 1.8 dev release and I plan to try the 1.7 release next chance to see if that works. BTW, it runs fine standalone and other similar code runs fine both standalone and as a servlet. Shawn -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- http://www.superlinksoftware.com - software solutions for business http://jakarta.apache.org/poi - Excel/Word/OLE 2 Compound Document in Java http://krysalis.sourceforge.net/centipede - the best build/project structure a guy/gal could have! - Make Ant simple on complex Projects! The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: IllegalMonitorStateException
Well here is the problem: http://java.sun.com/products/jdk/1.2/docs/api/java/lang/IllegalMonitorStateException.html public class IllegalMonitorStateException extends RuntimeException Thrown to indicate that a thread has attempted to wait on an object's monitor or to notify other threads waiting on an object's monitor without owning the specified monitor. Since POI *does not* utilize threads in any way, the exception doesn't make sense. Its showing up in POI, but I highly doubt that POI is the actual cause of it. Oh and POI especially doesn't monitor threads (something I have successfully avoided doing in java for the entire time I've used it). So this means to me that someone else is trying to monitor the thread the POI servlet is running in without owning it. I suspect: 1. There is a bug in your JDK (the string pool maybe?) 2. There is a bug in your app server, in that its trying to monitor an object belonging to POI without owning the servlet/whatever that POI is running in (meaning its thread). 3. If the app code is doing threading and monitoring, etc, a bug in it. Since the code runs fine stand alone (assuming on the same OS and JDK/etc) and there really aren't many apps that use monitors, I suspect the second. I can't think of a good reason for an App server to monitor a thread in such a way unless its for the purpose of updating say a debugger, profiler or something of the such (if so, turn that debugger or what-have-you off). I've never used Oracle app servers, but I'll bet there is some kind of kludgy coupling between it and JServ, in which case thats a possibility. Also...try running without the JIT. Do you have a stack trace? -Andy PS possibilities: http://developer.java.sun.com/developer/bugParade/bugs/4307780.html http://developer.java.sun.com/developer/bugParade/bugs/4212414.html http://developer.java.sun.com/developer/bugParade/bugs/4131519.html application bug: http://developer.java.sun.com/developer/bugParade/bugs/4025841.html On Sat, 2002-07-06 at 09:51, Laubach, Shawn - TAFB/LAB NCC (SAIC) wrote: This is running under Oracle 9ias Rel. 1 so 1. A 1.2.1 version is what they say the are completely compatible with. 2. JServ 1.1 (Don't have a choice in this) 3. Win2k fully patched 4. P4 1.4 1gig 2x36gig SCSI Hardrives I went back to the 1.5 version of POI and it reacted the same. Shawn Laubach SAIC - Web Developer B-1B System Support Management Division OC-ALC/LAB, Building 3001, Tinker AFB, Oklahoma dsn: 336-2473 comm: 405-736-2473 mobile: 405-245-9562 -Original Message- From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]] Sent: Friday, July 05, 2002 10:34 PM To: POI Users List Subject: Re: IllegalMonitorStateException Thats a threading error. POI isn't threaded. That totally makes no sense. I bet its a cooincidence as to where its happening. Please provide: 1. JDK version 2. Servlet container version 3. OS version 4. Hardware statistics. -Andy Shawn Laubach wrote: Inside a class being called by a servlet, I'm getting a IllegalMonitorStateException thrown. I've narrowed it down to three lines of code where it is occuring. A row.createCell, cell.setCellValue, and cell.setCellStyle calls. I haven't had time to narrow it down any furthur. What I'm curious about, is why it would be thrown anyways. I've just started using the 1.8 dev release and I plan to try the 1.7 release next chance to see if that works. BTW, it runs fine standalone and other similar code runs fine both standalone and as a servlet. Shawn -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- http://www.superlinksoftware.com - software solutions for business http://jakarta.apache.org/poi - Excel/Word/OLE 2 Compound Document in Java http://krysalis.sourceforge.net/centipede - the best build/project structure a guy/gal could have! - Make Ant simple on complex Projects! The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: IllegalMonitorStateException
Yes. I sometimes question their judgment on that. The current release (which is out for everything but windows) is based off of tomcat so. Shawn Laubach SAIC - Web Developer B-1B System Support Management Division OC-ALC/LAB, Building 3001, Tinker AFB, Oklahoma dsn: 336-2473 comm: 405-736-2473 mobile: 405-245-9562 -Original Message- From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]] Sent: Saturday, July 06, 2002 9:53 AM To: POI Users List Subject: RE: IllegalMonitorStateException On Sat, 2002-07-06 at 10:05, Adam wrote: Just a question from the lurker pool, but why are you stuck using JServ? The whole point of using 9iAS is the OC4J container, which is a licensed version of the Orion server. JServ hasn't been updated in years. Just for clarification (from my understanding): JServ | | Planning starts for a JServ 2.0 - complete rewrite. | | | Sun Donates Tomcat 3.0 | (which was a white elephant of sorts) | | Plans for JServ 2.0 discontinued | | | Tomcat 3.1 | | Tomcat 3.2 | | Plans for JServ 2.0 revised/reincarnated as Tomcat 4.0 | | Some dissenters from the Tomcat 4.0 (complete rewrite/redesign) | create Tomcat 3.3 (refactoring, incremental improvement over 3.2) | | Tomcat 4.0 born | | Several bugfixes later you can even run Tomcat 4.04 and have it | actuall work! | | Tomcat 4.1 development starts Oracle chose to not upgrade to Tomcat at any point in the last 4 years Adam Weed -Original Message- From: Laubach, Shawn - TAFB/LAB NCC (SAIC) [mailto:[EMAIL PROTECTED]] Sent: Saturday, July 06, 2002 8:51 AM To: 'POI Users List' Subject: RE: IllegalMonitorStateException This is running under Oracle 9ias Rel. 1 so 1. A 1.2.1 version is what they say the are completely compatible with. 2. JServ 1.1 (Don't have a choice in this) 3. Win2k fully patched 4. P4 1.4 1gig 2x36gig SCSI Hardrives I went back to the 1.5 version of POI and it reacted the same. Shawn Laubach SAIC - Web Developer B-1B System Support Management Division OC-ALC/LAB, Building 3001, Tinker AFB, Oklahoma dsn: 336-2473 comm: 405-736-2473 mobile: 405-245-9562 -Original Message- From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]] Sent: Friday, July 05, 2002 10:34 PM To: POI Users List Subject: Re: IllegalMonitorStateException Thats a threading error. POI isn't threaded. That totally makes no sense. I bet its a cooincidence as to where its happening. Please provide: 1. JDK version 2. Servlet container version 3. OS version 4. Hardware statistics. -Andy Shawn Laubach wrote: Inside a class being called by a servlet, I'm getting a IllegalMonitorStateException thrown. I've narrowed it down to three lines of code where it is occuring. A row.createCell, cell.setCellValue, and cell.setCellStyle calls. I haven't had time to narrow it down any furthur. What I'm curious about, is why it would be thrown anyways. I've just started using the 1.8 dev release and I plan to try the 1.7 release next chance to see if that works. BTW, it runs fine standalone and other similar code runs fine both standalone and as a servlet. Shawn -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- http://www.superlinksoftware.com - software solutions for business http://jakarta.apache.org/poi - Excel/Word/OLE 2 Compound Document in Java http://krysalis.sourceforge.net/centipede - the best build/project structure a guy/gal could have! - Make Ant simple on complex Projects! The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Try it now (was: RE: IllegalMonitorStateException)
Hi Shawn, I just removed the thread safety stuff from the head. Give it a whirl. We need a better solution for formula workbook context, but this should at least make us nice and able to run in single threaded contexts for the moment. Thanks, Andy On Sat, 2002-07-06 at 11:08, Laubach, Shawn - TAFB/LAB NCC (SAIC) wrote: Yes. I sometimes question their judgment on that. The current release (which is out for everything but windows) is based off of tomcat so. Shawn Laubach SAIC - Web Developer B-1B System Support Management Division OC-ALC/LAB, Building 3001, Tinker AFB, Oklahoma dsn: 336-2473 comm: 405-736-2473 mobile: 405-245-9562 -Original Message- From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]] Sent: Saturday, July 06, 2002 9:53 AM To: POI Users List Subject: RE: IllegalMonitorStateException On Sat, 2002-07-06 at 10:05, Adam wrote: Just a question from the lurker pool, but why are you stuck using JServ? The whole point of using 9iAS is the OC4J container, which is a licensed version of the Orion server. JServ hasn't been updated in years. Just for clarification (from my understanding): JServ | | Planning starts for a JServ 2.0 - complete rewrite. | | | Sun Donates Tomcat 3.0 | (which was a white elephant of sorts) | | Plans for JServ 2.0 discontinued | | | Tomcat 3.1 | | Tomcat 3.2 | | Plans for JServ 2.0 revised/reincarnated as Tomcat 4.0 | | Some dissenters from the Tomcat 4.0 (complete rewrite/redesign) | create Tomcat 3.3 (refactoring, incremental improvement over 3.2) | | Tomcat 4.0 born | | Several bugfixes later you can even run Tomcat 4.04 and have it | actuall work! | | Tomcat 4.1 development starts Oracle chose to not upgrade to Tomcat at any point in the last 4 years Adam Weed -Original Message- From: Laubach, Shawn - TAFB/LAB NCC (SAIC) [mailto:[EMAIL PROTECTED]] Sent: Saturday, July 06, 2002 8:51 AM To: 'POI Users List' Subject: RE: IllegalMonitorStateException This is running under Oracle 9ias Rel. 1 so 1. A 1.2.1 version is what they say the are completely compatible with. 2. JServ 1.1 (Don't have a choice in this) 3. Win2k fully patched 4. P4 1.4 1gig 2x36gig SCSI Hardrives I went back to the 1.5 version of POI and it reacted the same. Shawn Laubach SAIC - Web Developer B-1B System Support Management Division OC-ALC/LAB, Building 3001, Tinker AFB, Oklahoma dsn: 336-2473 comm: 405-736-2473 mobile: 405-245-9562 -Original Message- From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]] Sent: Friday, July 05, 2002 10:34 PM To: POI Users List Subject: Re: IllegalMonitorStateException Thats a threading error. POI isn't threaded. That totally makes no sense. I bet its a cooincidence as to where its happening. Please provide: 1. JDK version 2. Servlet container version 3. OS version 4. Hardware statistics. -Andy Shawn Laubach wrote: Inside a class being called by a servlet, I'm getting a IllegalMonitorStateException thrown. I've narrowed it down to three lines of code where it is occuring. A row.createCell, cell.setCellValue, and cell.setCellStyle calls. I haven't had time to narrow it down any furthur. What I'm curious about, is why it would be thrown anyways. I've just started using the 1.8 dev release and I plan to try the 1.7 release next chance to see if that works. BTW, it runs fine standalone and other similar code runs fine both standalone and as a servlet. Shawn -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- http://www.superlinksoftware.com - software solutions for business http://jakarta.apache.org/poi - Excel/Word/OLE 2 Compound Document in Java http://krysalis.sourceforge.net/centipede - the best build/project structure a guy/gal could have! - Make Ant simple on complex Projects! The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- http://www.superlinksoftware.com - software solutions for business http://jakarta.apache.org/poi - Excel/Word/OLE 2 Compound Document in Java http://krysalis.sourceforge.net/centipede - the best build/project structure a guy/gal could have! - Make Ant simple on complex Projects! The avalanche has already started. It is too late for the pebbles to vote.
Translation (JP)
Hi, All. I am a newer of this project, living in Japan. Wandering the Jakarta Project Web Site, I've luckily found this project. I am using XLS file format a lot because my clients want to. I wondered how to contribute to this project, and I noticed that the translation is the best way for me. # Also, translation is the best way to know more about these # kind of projects, I am sure. G I am trying to translate the documents into Japanese right now. (experimental: http://www.terra-intl.com/jakarta/poi/ ) Of course, I am doing the translation on xdocs at the same time. (Also, I am trying for some other projects in Jakarta) In Japanese standard Windows environment, Shift_JIS code is popular, however, I think using UTF-8 for docs is preferable. What do you think? Thanks a lot. -- Tetsuya Kitahata [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Translation (JP)
On Sat, 2002-07-06 at 17:07, Tetsuya Kitahata wrote: Hi, All. I am a newer of this project, living in Japan. Wandering the Jakarta Project Web Site, I've luckily found this project. I am using XLS file format a lot because my clients want to. Excellent. If you get the opportunity please contribute a Case Study: http://jakarta.apache.org/poi/casestudies.html I wondered how to contribute to this project, and I noticed that the translation is the best way for me. # Also, translation is the best way to know more about these # kind of projects, I am sure. G I am trying to translate the documents into Japanese right now. (experimental: http://www.terra-intl.com/jakarta/poi/ ) Of course, I am doing the translation on xdocs at the same time. (Also, I am trying for some other projects in Jakarta) I think thats great. I cannot comment of course on the quality of the translation (Still working on Spanish and German, one day I'll try Japanese but one can only learn so much in a given time period), but I'm very pleased! In Japanese standard Windows environment, Shift_JIS code is popular, however, I think using UTF-8 for docs is preferable. What do you think? UTF-8 or 16 is the general standard. Due to the nature of this project, we should assume that the user may be using non-windows environments as well. (I hail from a Linux box) If you can post a zip file into bugzilla with the translated xdocs in the same directory format as the Spanish translation, I'll incorporate this into the POI build and get it up on the site. Chances are this will encourage others to assist you in this (by submitting patches) and accelerate the process for you. Just a thought One thing I'd really like to do is incorporate language into the docs. Meaning section title=Some Section name=Some Section language=default !-- english -- p Blablabla /p /section section title=Japanese translation name=Some Section language=jp p !-- japanese characters here -- /p /section This would help keep things up to date. Especially if the XSL transformation process put placeholders where there were untranslated sections. Unfortunately, my XSL/Centipede skills have not progressed to the point where I can do this. Thanks a lot. No thanks required, I should instead thank you! This is an outstanding development. I'll link to it shortly. -Andy -- Tetsuya Kitahata [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- http://www.superlinksoftware.com - software solutions for business http://jakarta.apache.org/poi - Excel/Word/OLE 2 Compound Document in Java http://krysalis.sourceforge.net/centipede - the best build/project structure a guy/gal could have! - Make Ant simple on complex Projects! The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Translation (JP)
Hi, Andrew, I am very glad to your prompt reply. UTF-8 or 16 is the general standard. Due to the nature of this project, we should assume that the user may be using non-windows environments as well. (I hail from a Linux box) In xdocs files (.xml files), the encoding is not UTF-8 but ISO-8859-1... In my thought (Japanese Translation Version) xdocs files should be encoded by Shift_JIS (This is Windows Standard) and docs files generated by xdocs files should be encoded by UTF-8. # Still there're a few text editors which can deal with the UTF-8 # format (I have and can, but..). HTML side, of course UTF-8 is O.K. This can be done by modifying build.xml (using Velocity/Anakia + ANT) or velocity.properties, I think. # I've done the same thing for other projects. For the time being, I'd like to do the translation on my web. However, I am thinking of the translation of xdocs also for easy transfer to http://jakarta.apache.org/poi/trans/jp/ .. or somewhere. If you can post a zip file into bugzilla with the translated xdocs in the same directory format as the Spanish translation, I'll incorporate this into the POI build and get it up on the site. Chances are this will encourage others to assist you in this (by submitting patches) and accelerate the process for you. Thanks a lot. One thing I'd really like to do is incorporate language into the docs. Meaning I think this will be great. However, current xdocs files should be changed in some way (especially ISO-8859-1 part). No thanks required, I should instead thank you! This is an outstanding development. I'll link to it shortly. Right. I'd like to hurry up the translation G. - Tetsuya -- Tetsuya Kitahata [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Translation (JP)
On Sat, 2002-07-06 at 18:50, Tetsuya Kitahata wrote: Hi, Andrew, I am very glad to your prompt reply. UTF-8 or 16 is the general standard. Due to the nature of this project, we should assume that the user may be using non-windows environments as well. (I hail from a Linux box) In xdocs files (.xml files), the encoding is not UTF-8 but ISO-8859-1... Thats not a serious issue to change. In my thought (Japanese Translation Version) xdocs files should be encoded by Shift_JIS (This is Windows Standard) and docs files generated by xdocs files should be encoded by UTF-8. # Still there're a few text editors which can deal with the UTF-8 # format (I have and can, but..). HTML side, of course UTF-8 is O.K. I'm not sure I agree. One of the principles behind POI is that its multi-platform. I for one don't have a Windows box. (I run Excel on Linux via CrossOver Office distro of WINE from www.codeweavers.com). If this is an open multi-platform standard than thats fine. This can be done by modifying build.xml (using Velocity/Anakia + ANT) or velocity.properties, I think. # I've done the same thing for other projects. POI uses Centipede instead of Velocity/Anakia. See http://www.krysalis.org/centipede for details For the time being, I'd like to do the translation on my web. However, I am thinking of the translation of xdocs also for easy transfer to http://jakarta.apache.org/poi/trans/jp/ .. or somewhere. Thats too bad, I think it would be nice to have collaboration on this effort. If you can post a zip file into bugzilla with the translated xdocs in the same directory format as the Spanish translation, I'll incorporate this into the POI build and get it up on the site. Chances are this will encourage others to assist you in this (by submitting patches) and accelerate the process for you. Thanks a lot. One thing I'd really like to do is incorporate language into the docs. Meaning I think this will be great. However, current xdocs files should be changed in some way (especially ISO-8859-1 part). I've no objection really. How do we go about that exactly? No thanks required, I should instead thank you! This is an outstanding development. I'll link to it shortly. Right. I'd like to hurry up the translation G. Well I think the best way to do that is to enable others to contribute. By incorporating the translation into the project, you make it so that: 1. everyone who downloads new releases of POI will get the updated documentation. 2. Exposure. 3. everyone can submit patches to the CVS repository and have them incorporated. Otherwise, you have to do all the work yourself which maybe is okay with you, but I suspect it will take longer. -Andy - Tetsuya -- Tetsuya Kitahata [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- http://www.superlinksoftware.com - software solutions for business http://jakarta.apache.org/poi - Excel/Word/OLE 2 Compound Document in Java http://krysalis.sourceforge.net/centipede - the best build/project structure a guy/gal could have! - Make Ant simple on complex Projects! The avalanche has already started. It is too late for the pebbles to vote. -Ambassador Kosh -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
