Low-level Writing Functions In Details

If all you are interested in is getting the textual content of all the document properties, such as for full text indexing, then - take a look at + take a look at org.apache.poi.hpsf.extractor.HPSFPropertiesExtractor. However, if you want full access to the properties, please read on!

As explained above, standard properties are located in the summary @@ -1236,7 +1235,7 @@ No property set stream: "/1Table"

Purpose

The POI project consists of APIs for manipulating various file formats - based upon Microsoft's OLE 2 Compound Document format, and Office OpenXML format, using + based upon Microsoft's OLE 2 Compound Document format, and Office OpenXML format, using pure Java. In short, you can read and write MS Excel files using Java. In addition, - you can read and write MS Word and MS PowerPoint files using Java. POI is your Java Excel - solution (for Excel 97-2007). However, we have a complete API for porting other OLE 2 + you can read and write MS Word and MS PowerPoint files using Java. POI is your Java Excel + solution (for Excel 97-2007). However, we have a complete API for porting other OLE 2 Compound Document formats and welcome others to participate.

@@ -86,8 +86,8 @@ provide this functionality. Examples include: Cocoon for which there are serializers for HSSF; Open Office.org with whom we collaborate in documenting the - XLS format; and Lucene - for which we provide format interpretors. When practical, we donate + XLS format; and Lucene + for which we provide format interpretors. When practical, we donate components directly to those projects for POI-enabling them.

Why/when would I use POI? @@ -124,10 +124,10 @@ definition. Please see the POIFS project page for more information.

HSSF and XSSF for Excel Documents -

HSSF is our port of the Microsoft Excel 97(-2007) file format (BIFF8) to pure +

HSSF is our port of the Microsoft Excel 97(-2007) file format (BIFF8) to pure Java. XSSF is our port of the Microsoft Excel XML (2007+) file format (OOXML) to - pure Java. They both supports read and write capability. Please see - the HSSF+XSSF project page for more + pure Java. They both supports read and write capability. Please see + the HSSF+XSSF project page for more information.

HWPF for Word Documents @@ -172,7 +172,7 @@

Component map

The POI distribution consists of several JAR files. Not all of them are needed in every case. The following table - shows the relationships between POI components and the JAR files. + shows the relationships between POI components and the JAR files.

@@ -257,7 +257,6 @@ diff --git a/src/documentation/content/xdocs/legal.xml b/src/documentation/content/xdocs/legal.xml index 8b8d273d30..f8923e2a04 100644 --- a/src/documentation/content/xdocs/legal.xml +++ b/src/documentation/content/xdocs/legal.xml @@ -30,17 +30,17 @@

Apache POI - Legal Stuff

-Sun, Sun Microsystems, Solaris, Java, JavaServer Web Development Kit, -and JavaServer Pages are trademarks or registered trademarks of Sun -Microsystems, Inc. UNIX is a registered trademark in the United States +Sun, Sun Microsystems, Solaris, Java, JavaServer Web Development Kit, +and JavaServer Pages are trademarks or registered trademarks of Sun +Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, exclusively licensed through 'The Open Group'. Microsoft, Windows, WindowsNT, Excel, Word, PowerPoint and Win32 are -registered trademarks of +registered trademarks of Microsoft Corporation. Linux is a registered trademark of Linus Torvalds. All other product names mentioned herein and throughout the entire web site are trademarks of their respective owners. @@ -51,7 +51,6 @@ web site are trademarks of their respective owners.

diff --git a/src/documentation/content/xdocs/mirrors.xml b/src/documentation/content/xdocs/mirrors.xml index 1db26641d9..f273f5c123 100644 --- a/src/documentation/content/xdocs/mirrors.xml +++ b/src/documentation/content/xdocs/mirrors.xml @@ -26,17 +26,17 @@ - +

Mirrors

- These are mirrors of the + These are mirrors of the POI website. If you know of others...report them! :-) -

Austria -

Austrian Mirror of Jakarta POI

@@ -49,7 +49,6 @@ diff --git a/src/documentation/content/xdocs/news.xml b/src/documentation/content/xdocs/news.xml index bd2c0cda9f..daaf1a28ab 100644 --- a/src/documentation/content/xdocs/news.xml +++ b/src/documentation/content/xdocs/news.xml @@ -27,7 +27,7 @@ - +

POI in the news

@@ -39,15 +39,15 @@ equal time will be given so please feel free to send inflamatory defamation as well as favorable, technical and factual. Really stupid things won't be mentioned (sorry). -

English

+
Discussion about using POI on AS/400s
- Discussion from back when we almost had POI as the filter for KOffice if politics and licenses hadn't killed iit + Discussion from back when we almost had POI as the filter for KOffice if politics and licenses hadn't killed iit
Java discussion on O'Reilly Network including discussion about POI - O'Reilly.net @@ -55,7 +55,7 @@
Poor Obfuscation Implementation. - Blog of David M. Johnson
+
POI 1.5-dev-rc2 released - JSurfer
Jakarta POI 1.4583 Released - JavaLobby -
- POI project moves to Jakarta (OLE 2 CDF/Excel/Word in + POI project moves to Jakarta (OLE 2 CDF/Excel/Word in pure java) - JavaLobby
@@ -104,7 +104,7 @@
Chicago Developer Page - +
@@ -118,26 +118,26 @@ News Around the Net - Java World

Nederlandstalige (Dutch)

- - Een Excel-werkboek maken vanuit Java - Lieven Smits + Een Excel-werkboek maken vanuit Java - Lieven Smits

Deutsch (German)

Apache POI verffentlicht - entwicker.com +
Apache POI verffentlicht - entwicker.com
- Apache Jakarta-Projekt bringt Word und Excel in die Java-Welt - jsp-develop.de (for the misguided who use JSP ;-) )
Spanish discussion about Excel and Java including POI from Wrox forums -

Français (French)

- Excel/OLE accessibles + Excel/OLE accessibles - Da Linux French Page
@@ -188,7 +188,7 @@
Various discussion in Japanese including on POI
Japanese resources on Jakarta projects including POI
Kishida's site -- Weekly Forte Lectures -- includes a snip about POI and Japanese.

Russkii Yazyk (Russian) @@ -213,8 +213,8 @@ telling us what language it is and we'll categorize it!

- + If I had to guess, I'd say this is Thai, but maybe you actually know - javacentrix.com @@ -225,7 +225,6 @@
Copyright (c) @year@ The Apache Software Foundation All rights reserved. - $Revision$ $Date$
diff --git a/src/documentation/content/xdocs/news/logocontest.xml b/src/documentation/content/xdocs/news/logocontest.xml index a8c9e4b7de..3d796090c2 100644 --- a/src/documentation/content/xdocs/news/logocontest.xml +++ b/src/documentation/content/xdocs/news/logocontest.xml @@ -186,7 +186,6 @@
Copyright (c) @year@ The Apache Software Foundation All rights reserved. - $Revision$ $Date$
diff --git a/src/documentation/content/xdocs/overview.xml b/src/documentation/content/xdocs/overview.xml index a8ce13f1cf..19dd9f62eb 100644 --- a/src/documentation/content/xdocs/overview.xml +++ b/src/documentation/content/xdocs/overview.xml @@ -27,7 +27,7 @@ - +
What is it?
The POI project is the master project for developing pure @@ -43,47 +43,47 @@

POIFS
- POIFS is the set of APIs + POIFS is the set of APIs for reading and writing OLE 2 Compound Document Formats using (only) Java. -
+

- +
HSSF and XSSF
- HSSF and XSSF are - the set of APIs for reading and writing Microsoft Excel + HSSF and XSSF are + the set of APIs for reading and writing Microsoft Excel 97-2007 and OOXML spreadsheets using (only) Java.

HWPF
- HWPF is the set of APIs + HWPF is the set of APIs for reading and writing Microsoft Word 97(-XP) documents using (only) Java.

HSLF
- HSLF is the set of APIs + HSLF is the set of APIs for reading and writing Microsoft PowerPoint 97(-XP) documents using (only) Java.

HPSF
- HPSF is the set of APIs + HPSF is the set of APIs for reading property sets using (only) Java. -
+

POI-Utils
POI-Utils are general purpose artifacts - from POI development that have not yet been implemented elsewhere. We're + from POI development that have not yet been implemented elsewhere. We're always looking to donate these and maintain them as part of a general library used in another project. These are things we need to complete our mission but - are generally outside of it. + are generally outside of it.

@@ -96,7 +96,7 @@ studying the source code you might want to have a look at the "Examples" section of the POI API - documentation.
+ documentation.

Contributed Software @@ -119,7 +119,6 @@ diff --git a/src/documentation/content/xdocs/poi-ruby.xml b/src/documentation/content/xdocs/poi-ruby.xml index ce034b4447..07fe1ab090 100644 --- a/src/documentation/content/xdocs/poi-ruby.xml +++ b/src/documentation/content/xdocs/poi-ruby.xml @@ -26,7 +26,7 @@ - +

Intro

The POI library can now be compiled as a Ruby extension, allowing the API to be called from @@ -35,7 +35,7 @@

The bindings are generated by compiling POI with gcj, and generating the Ruby wrapper using SWIG. The aim is the keep - the POI api as-is. However, where java standard library objects are used, an effort is made to transform them smoothly + the POI api as-is. However, where java standard library objects are used, an effort is made to transform them smoothly into Ruby objects. Therefore, where the POI API takes an OutputStream, you can pass an IO object. Where the POI works java.util.Date or java.util.Calendar object, you can work with a Ruby Time object.

@@ -44,18 +44,18 @@

Getting Started

Pre-Requisites

The bindings have been developed with GCC 3.4.3 and Ruby 1.8.2. You are unlikely to get correct results with - versions of GCC prior to 3.4 or versions of Ruby prior to 1.8. To compile the Ruby extension, you must have + versions of GCC prior to 3.4 or versions of Ruby prior to 1.8. To compile the Ruby extension, you must have GCC (compiled with java language support), Ruby development headers, and SWIG. To run, you will need Ruby (obviously!) and - libgcj , presumably from the same version of GCC with which you compiled. -

+ libgcj , presumably from the same version of GCC with which you compiled. +

Subversion

The POI-Ruby module sits under the POI Subversion in the src/contrib/poi-ruby directory. Running make - inside that directory will create a loadable ruby extention poi4r.so in the release subdirectory. Tests + inside that directory will create a loadable ruby extention poi4r.so in the release subdirectory. Tests are in the tests/ subdirectory, and should be run from the poi-ruby directory. Please read the tests to figure out the usage.

Note that the makefile, though designed to work accross Linux/OS X/Cygwin, has been tested only on linux. +

Note that the makefile, though designed to work accross Linux/OS X/Cygwin, has been tested only on linux. There are likely to be issues on other platform; fixes gratefully accepted!

Binary @@ -63,7 +63,7 @@ with GCC 3.4.3 and Ruby 1.8.2. It dynamically links to libgcj. No guarantees about working on any other box.

- + @@ -74,45 +74,45 @@ h=Poi4r::HSSFWorkbook.new #Test Sheet Creation s=h.createSheet("Sheet1") - + #Test setting cell values s=h.getSheetAt(0) r=s.createRow(0) c=r.createCell(0) c.setCellValue(1.5) - + c=r.createCell(1) c.setCellValue("Ruby") - + #Test styles st = h.createCellStyle() c=r.createCell(2) st.setAlignment(Poi4r::HSSFCellStyle.ALIGN_CENTER) c.setCellStyle(st) c.setCellValue("centr'd") - + #Date handling c=r.createCell(3) t1=Time.now c.setCellValue(Time.now) t2= c.getDateCellValue().gmtime - + st=h.createCellStyle(); st.setDataFormat(Poi4r::HSSFDataFormat.getBuiltinFormat("m/d/yy h:mm")) c.setCellStyle(st) - + #Formulas c=r.createCell(4) c.setCellFormula("A1*2") c.getCellFormula() - + #Writing h.write(File.new("test.xls","w"))

The tc_base_tests.rb file in the tests sub directory of the source distribution contains examples of simple uses of the API. The quick quide is the best place to learn HSSF API use. (Note however that none of the Drawing features are implemented in the Ruby binding.) - See also the POI API documentation for more details. + See also the POI API documentation for more details.

@@ -122,28 +122,27 @@

Implement support for reading Excel files (easy)
Expose POIFS API to read raw OLE2 files from Ruby
Expose HPSF API to read property streams
Tests... Tests... Tests...
Expose HPSF API to read property streams
Tests... Tests... Tests...

Limitations

Check operations in 64bit machines - Java primitive types are fixed irrespective of machine type, unlike C/C++ types. The wrapping code +
Check operations in 64bit machines - Java primitive types are fixed irrespective of machine type, unlike C/C++ types. The wrapping code that converts C/C++ primitive types to/from Java types is making assumptions on type sizes that MAY be incorrect on wide architectures.
The current implementation is with the POI 2.0 release. The 2.5 release adds support for Excel drawing primitives, and +
The current implementation is with the POI 2.0 release. The 2.5 release adds support for Excel drawing primitives, and thus has a dependency on java AWT. Since AWT is not very mature in gcj, leaving it out seemed to be the safer option.
Packaging - The current make file makes no effort to install the extension into the standard ruby directories. This should probably be packaged as a gem.

- + - + diff --git a/src/documentation/content/xdocs/trans/de/index.xml b/src/documentation/content/xdocs/trans/de/index.xml index d4e9a33fea..32da9d2098 100644 --- a/src/documentation/content/xdocs/trans/de/index.xml +++ b/src/documentation/content/xdocs/trans/de/index.xml @@ -64,7 +64,7 @@ zu stellen. Einige Beispiele: Für Cocoon werden bald Generatoren und Serializer zur Verfügung stehen. Wir - arbeiten mit + arbeiten mit Open Office.org zusammen, um das Excel-Dateiformat zu dokumentieren. @@ -110,7 +110,7 @@ wie tar, gzip, zip oder arc genutzt, sondern stattdessen ein eigenes Archivformat erfunden, das keinerlei Standardverschlüsselung oder -komprimierung - bietet, das schlecht erweiterbar ist, und das zur + bietet, das schlecht erweiterbar ist, und das zur Fragmentierung neigt.

POI ist außerdem eine Spezialität der hawaiianischen Küche. Sie wird @@ -203,7 +203,6 @@

diff --git a/src/documentation/content/xdocs/trans/es/casestudies.xml b/src/documentation/content/xdocs/trans/es/casestudies.xml index 769a5325b6..7aa558bd6b 100644 --- a/src/documentation/content/xdocs/trans/es/casestudies.xml +++ b/src/documentation/content/xdocs/trans/es/casestudies.xml @@ -28,14 +28,14 @@ - +

Introducción

Mucha gente está utilizando POI para distintos propósitos. Como con cualquier nueva API o tecnologia, la primera pregunta que la gente pregunta normalmente - no es "cómo puedo" sino "Quién más está haciendo lo que yo estoy a punto de + no es "cómo puedo" sino "Quién más está haciendo lo que yo estoy a punto de hacer?" Esto es comprensible con el abismal porcentage de éxito en el negocio del software. Estos Casos pretenden ayudar a crear confianza y comprensión. @@ -62,17 +62,17 @@ solución de informes basada en POI para un paquete software de optimización de precios que se usa en grandes cadenas de venta.

La solución permitió a los planificadores y gestores de la mercancía mercancía pedir - unos informes de soporte a la decisión e informes de cambios de precios utilizando un +

La solución permitió a los planificadores y gestores de la mercancía mercancía pedir + unos informes de soporte a la decisión e informes de cambios de precios utilizando un navegador estándar. Los usuarios pueden especificar el tipo de informe, las opciones, así como criterios de filtros como la división de la compañía - o departamento. La generación de informes se llevó a cabo en el + o departamento. La generación de informes se llevó a cabo en el servidor de aplicaciones multi-hilo y fue capaz de soportar muchas peticiones de informe simultáneas.

La aplicación de informes recogía información del negocio de la base - de datos Oracle de la aplicación de optimización de precios. - Los datos se agregaban y resumían basándose en el tipo específico + de datos Oracle de la aplicación de optimización de precios. + Los datos se agregaban y resumían basándose en el tipo específico de informe y los criterios de filtro pedidos por el usuario. El informe final se generaba como una hoja de cálculo de Microsoft Excel utilizando el API de POI HSSF y se almacenaba en el @@ -84,7 +84,7 @@ a datos del negocio críticios a través de una interfaz basada en navegador extremadamente fácil de usar. No necesitaban entrenar a su amplia comunidad de usuarios en las complejidades de la - aplicación de optimización. Lo que es más, los informes se generaban en un formato de + aplicación de optimización. Lo que es más, los informes se generaban en un formato de hoja de cálculo Excel, que todo el mundo conocía y que también permitía análisis de datos adicionales utilizando @@ -98,12 +98,12 @@

El Banco de Lituania - genera informes de datos estadísticos financieros en formato Excel + genera informes de datos estadísticos financieros en formato Excel utilizando el API - HSSF del proyecto + HSSF del proyecto Jakarta POI El sistema está basado en Oracle JServer y utiliza - un procedimiento almacenado Java que utilizando el API HSSF + un procedimiento almacenado Java que utilizando el API HSSF responde en formato XLS. - Arian Lashkov (alaskov at lbank.lt)

@@ -132,7 +132,7 @@ para la industria de las Telecomunicaciones. basado en Turbine y Velocity. Originalmente la factura se hacía con una sencilla - hoja CVS que era entonces + hoja CVS que era entonces marcada por cada cuenta y particularizada para cada cliente. Como el crecimiento ha sido consistente con la aplicación, las necesidades de facturas que no necesitasen ser retocadas a mano aumentaron. POI proporcionó la @@ -176,13 +176,12 @@

Es evidente que los ficheros de Microsoft Excel también estan soportados. POI se ha utilizado para implementar con éxito este soporte en ETL4ALL.

- + diff --git a/src/documentation/content/xdocs/trans/es/historyandfuture.xml b/src/documentation/content/xdocs/trans/es/historyandfuture.xml index dde8ef956a..74104584da 100644 --- a/src/documentation/content/xdocs/trans/es/historyandfuture.xml +++ b/src/documentation/content/xdocs/trans/es/historyandfuture.xml @@ -27,7 +27,7 @@ - + @@ -71,7 +71,7 @@ y trabajen hacer que la gente conociera este proyecto.

Poco antes de la distribuci, POI tuvo la fortuna de entrar en contacto con Nicola -Ken- Barrozzi quien proporcionejemplos para el Serializador HSSF y ayuda descrubir sus desafortunados @@ -119,7 +119,7 @@

Despu, tenemos algo de trabajo que hacer aquen Jakarta para terminar de integrar POI en la comunidad. Lo que es m, - todav estamos realizando la transici del Serializador a + todav estamos realizando la transici del Serializador a Cocoon.

@@ -132,7 +132,7 @@ para escribir o modificar, uno necesita ser capaz de actualizar punteros del flujo de subida (upstream pointers) a datos del flujo de bajada. Para hacer esto hay que tener todo lo que haya en - medio en memoria. En vez de eso, un Generador permitir que se + medio en memoria. En vez de eso, un Generador permitir que se procesaran eventos SAX. (Esto se basaren las estructuras de bajo nivel). Una de las mejores cosas sobre esto es que asno so tendremos una manera m eficiente de leer el fichero, tambi @@ -143,7 +143,7 @@ El Serializador HSSF, se separarm aíì en un marco genico para la creaci de serializadores para otras plataformas y en la implementaci especica del serializador HSSF. (Esto ya - es cierto en gran medida). Tambi adiremos soporte para + es cierto en gran medida). Tambi adiremos soporte para caracterticas ya soportadas por HSSF (estilos, fuentes, formatos de texto). Esperamos adir soporte para fmulas durante este ciclo.

@@ -162,7 +162,6 @@ diff --git a/src/documentation/content/xdocs/trans/es/index.xml b/src/documentation/content/xdocs/trans/es/index.xml index 7ec2685136..256ca4f4a1 100644 --- a/src/documentation/content/xdocs/trans/es/index.xml +++ b/src/documentation/content/xdocs/trans/es/index.xml @@ -35,21 +35,21 @@

El proyecto POI consiste en APIs para manipular varios formatos de ficheros basados en el formato de Documento Compuesto OLE 2 de Microsoft, utilizando Java puro. En concreto, se pueden - leer y escribir ficheros MS Excel utilizando Java. Pronto se podrá leer y escribir + leer y escribir ficheros MS Excel utilizando Java. Pronto se podrá leer y escribir ficheros Word utilizando Java. POI es su solución Java Excel así como su solución Java Word. En cualquier caso, tenemos un API completo para portar otros formatos de Documento Compuesto OLE 2 y todo aquel que quiera participar será bienvenido.

- Entre los ficheros basados en el formato de Documento Compuesto OLE 2 de Microsoft se incluyen la mayor parte de los + Entre los ficheros basados en el formato de Documento Compuesto OLE 2 de Microsoft se incluyen la mayor parte de los ficheros de Microsoft Office tales como XLS y DOC así como formatos de fichero basados en el API de serialización MFC.

Como regla general intentamos colaborar lo más posible con otros proyectos para proporcionar esta funcionalidad. Algunos ejemplos: Cocoon para el que hay serializadores para HSSF; - Open Office.org con quienes colaboramos en la documentación del - formato XLS; y Lucene para el que pronto tendremos intérpretes del + Open Office.org con quienes colaboramos en la documentación del + formato XLS; y Lucene para el que pronto tendremos intérpretes del formato de fichero. Cuando es práctico, donamos componentes directamente a los proyectos para dotarles de capacidad-POI.

¿Por qué/cuándo utilizar POI? @@ -60,13 +60,13 @@ Así que, ¿por qué debería utilizar POIFS o HSSF?

- Utilizarías POIFS si tuvieras un documento escrito en el Formato de Documento Compuesto OLE 2, probablemente escrito utilizando - MFC, que necesitaras leer en Java. Alternativamente, utilizarías POI para escribir en el Formato de Documento Compuesto OLE 2 - si necesitaras inter-operar con programas ejecutándose en la plataforma Windows. No nos estamos jactando cuando decimos que + Utilizarías POIFS si tuvieras un documento escrito en el Formato de Documento Compuesto OLE 2, probablemente escrito utilizando + MFC, que necesitaras leer en Java. Alternativamente, utilizarías POI para escribir en el Formato de Documento Compuesto OLE 2 + si necesitaras inter-operar con programas ejecutándose en la plataforma Windows. No nos estamos jactando cuando decimos que ¡POIFS es la adaptación más completa y correcta de este formato de fichero hasta la fecha!

- Utilizarías HSSF si necesitaras leer o escribir un fichero Excel utilizando Java (XLS). También se pueden leer y modificar + Utilizarías HSSF si necesitaras leer o escribir un fichero Excel utilizando Java (XLS). También se pueden leer y modificar hojas de cálculo utilizando este API, aunque ahora mismo la escritura está más madura.

@@ -95,11 +95,11 @@

HPSF

HPSF es nuestra adaptación del formato de conjunto de propiedades OLE 2 a java puro. - Los conjuntos de propiedades se utilizan mayoritariamente para almacenar las propiedades - de un documento (título, autor, fecha de la última modificación etc.), pero también pueden ser - utilizados para propósitos específicos de una aplicación. Actualmente HPSF soporta + Los conjuntos de propiedades se utilizan mayoritariamente para almacenar las propiedades + de un documento (título, autor, fecha de la última modificación etc.), pero también pueden ser + utilizados para propósitos específicos de una aplicación. Actualmente HPSF soporta sólo funcionalidad de lectura. Por favor, vea - la página del proyecto HPSF [EN] para más + la página del proyecto HPSF [EN] para más información.

@@ -107,11 +107,11 @@

Contribuyendo

- Así que ¿te gustaría contribuir al proyecto? ¡Genial! Necesitamos gente entusiasta, que trabaje duro, que tenga talento para ayudarnos - con el proyecto en varias áreas. ¡La primera es petición de nuevas funciones y aviso de errores! La segunda es documentación - - estaremos a tu entera disposición si tienes alguna crítica o te gustaría contribuir o mejorar de alguna forma la documentación. + Así que ¿te gustaría contribuir al proyecto? ¡Genial! Necesitamos gente entusiasta, que trabaje duro, que tenga talento para ayudarnos + con el proyecto en varias áreas. ¡La primera es petición de nuevas funciones y aviso de errores! La segunda es documentación - + estaremos a tu entera disposición si tienes alguna crítica o te gustaría contribuir o mejorar de alguna forma la documentación. ¡Especialmente no nos vendría mal algo de ayuda en documentar el formato de fichero HSSF! ¡Por último, aunque no por ello - menos importante, nos vendría bien algunos programadores Java que mastiquen binario, para que le echen el diente a la convolución que caracteriza + menos importante, nos vendría bien algunos programadores Java que mastiquen binario, para que le echen el diente a la convolución que caracteriza los formatos de fichero de Microsoft y para que nos ayude a adaptar nuevos formatos a una plataforma Java superior!

¡Así que si estás motivado, listo, y tienes tiempo, únete a las listas de correo y estaremos encantados de ayudarte a @@ -124,7 +124,6 @@

diff --git a/src/documentation/content/xdocs/trans/es/news.xml b/src/documentation/content/xdocs/trans/es/news.xml index 088ff98381..1bbfdf7907 100644 --- a/src/documentation/content/xdocs/trans/es/news.xml +++ b/src/documentation/content/xdocs/trans/es/news.xml @@ -28,7 +28,7 @@ - +

POI en los medios de comunicación

@@ -40,23 +40,23 @@ dedicaremos el mismo tiempo así que no tengáis reparos en enviar difamaciones coléricas así como comentarios favorables, técnicos y objetivos. No mencionaremos mensajes realmente estúpidos (lo sentimos). -

Inglés

+
Discusión sobre el uso de POI en AS/400s
- Discusión de cuando casi tuvimos POI como el filtro para KOffice si asuntos de política y licencias no lo hubieran condenado al fracaso + Discusión de cuando casi tuvimos POI como el filtro para KOffice si asuntos de política y licencias no lo hubieran condenado al fracaso
Discusión Java en O'Reilly Network incluyendo discusión sobre POI - O'Reilly.net
+
Poor Obfuscation Implementation (Implementación Pobre de Ofuscación). - Blog de David M. Johnson
+
Descarga POI 1.5-dev-rc2 - JSurfer
Descarga Jakarta POI 1.4583 - JavaLobby -
- El proyecto POI se mueve a Jakarta (OLE 2 CDF/Excel/Word en + El proyecto POI se mueve a Jakarta (OLE 2 CDF/Excel/Word en java puro) - JavaLobby
@@ -104,7 +104,7 @@
Página del Desarrollador de Chicago - +
@@ -118,26 +118,26 @@ Noticias en la Red - Java World

Nederlandstalige (Holandés)

- - Een Excel-werkboek maken vanuit Java - Lieven Smits + Een Excel-werkboek maken vanuit Java - Lieven Smits

Deutsch (Alemán)

Apache POI verffentlicht - entwicker.com +
Apache POI verffentlicht - entwicker.com
- Apache Jakarta-Projekt bringt Word und Excel in die Java-Welt - jsp-develop.de (for the misguided who use JSP ;-) )
Discusión sobre Excel y Java incluyendo POI de los foros de Wrox -

Francais (Francés)

- Excel/OLE accessibles + Excel/OLE accessibles - Da Linux French Page
@@ -212,8 +212,8 @@ diciéndonos en qué idioma está escrito y lo pondremos donde corresponda!
- - + Si tuviera que adivinar, diría que es Tailandés, pero a lo mejor alguno de vosotros lo sabe con seguridad. - javacentrix.com @@ -224,7 +224,6 @@
  Copyright (c) @year@ The Apache Software Foundation All rights reserved. - $Revision$ $Date$
  diff --git a/src/documentation/content/xdocs/trans/es/overview.xml b/src/documentation/content/xdocs/trans/es/overview.xml index b971ec814a..c1cf94678a 100644 --- a/src/documentation/content/xdocs/trans/es/overview.xml +++ b/src/documentation/content/xdocs/trans/es/overview.xml @@ -27,7 +27,7 @@ - +
  ¿Qué es?
  El proyecto POI es el proyecto principal para el desarrollo de adaptaciones (ports) @@ -43,11 +43,11 @@
  
  POIFS
  - POIFS [EN] es el conjunto de APIs (Interfaces de Aplicación) + POIFS [EN] es el conjunto de APIs (Interfaces de Aplicación) para la lectura y escritura del Formato de Documento Compuesto OLE 2 utilizando (únicamente) Java. -
  +
  
  - +
  HSSF
  HSSF [EN] es el conjunto de APIs para la lectura y @@ -66,7 +66,7 @@
  HPSF [EN] es el conjunto de APIs para la lectura de conjuntos de propiedades utilizando (únicamente) Java. -
  +
  
  Utilidades-POI (POI-Utils) @@ -83,7 +83,6 @@
  Copyright (c) @year@ The POI Project All rights reserved. - $Revision$ $Date$
  diff --git a/src/documentation/content/xdocs/trans/guidelines.xml b/src/documentation/content/xdocs/trans/guidelines.xml index 1d789f20d1..7564ab743e 100644 --- a/src/documentation/content/xdocs/trans/guidelines.xml +++ b/src/documentation/content/xdocs/trans/guidelines.xml @@ -30,82 +30,82 @@
  Purpose -
  This document hopes to serve as a general introduction and helpful set of - guidelines for translating POI documentation into other languages. We hope +
  This document hopes to serve as a general introduction and helpful set of + guidelines for translating POI documentation into other languages. We hope to capture both general information here (such as "how do I test my changes") as well as language specific guidelines and translation conventions.
  
  Introduction
  POI's XML based documentation is built along side the sources. To build poi's documentation - you run "./build.sh docs" (UNIX/cygwin) or "build docs" (Windows) from the jakarta-poi + you run "./build.sh docs" (UNIX/cygwin) or "build docs" (Windows) from the jakarta-poi directory. This will put the documentation under the build/docs directory, you can navigate there using your browser generally by typing in the path name or File -> Open new web location - (or some similar wording) - and browsing to the "index.html" file. You may also want to run "./build.sh clean docs" or + (or some similar wording) + and browsing to the "index.html" file. You may also want to run "./build.sh clean docs" or "build clean docs" so that all documentation previously built is erased before running the build. - The words "clean" and "docs" are called "targets", from here on out we will refer to them as - "targets" in which case you may assume you type "./build.sh" or "build" before them in order to - execute them. + The words "clean" and "docs" are called "targets", from here on out we will refer to them as + "targets" in which case you may assume you type "./build.sh" or "build" before them in order to + execute them.
  
  - To generate all of the documentation such as it would appear on the + To generate all of the documentation such as it would appear on the POI Website you can execute the "site" target (optionally preceeded by the "clean" target. See "How to Build" page for more detail (Now, POI build uses Forrest).
  -
  +
  The source for POI's XML documentation is in src/documentation/content/xdocs. To edit one of these files you can use - a standard text editor. Translated documentation is under src/documentation/content/xdocs/trans/xx, where xx is a + a standard text editor. Translated documentation is under src/documentation/content/xdocs/trans/xx, where xx is a two to three letter country code, in general this should match the internet domain suffix of the country where - that language generally evolved or just be generally recognizable and unique. The directory structure under - build/site/trans/xx should match the structure of build/site (the English edition) minus the - trans directory. + that language generally evolved or just be generally recognizable and unique. The directory structure under + build/site/trans/xx should match the structure of build/site (the English edition) minus the + trans directory.
  
  The translated documentation should match the content and meaning of the "master" or English documentation. All documentation should originate in English (this is for simplicity). While documentation written in other - languages is certainly welcome, it must first be translated (perhaps by posting it to the mail list and + languages is certainly welcome, it must first be translated (perhaps by posting it to the mail list and requesting it be translated) into English and applied to the master before being applied to a translation.
  
  We prefer you donate translations directly to the Apache POI - project rather than hosting them offsite. We will make every effort to accomidate you as we greatly appreciate your + project rather than hosting them offsite. We will make every effort to accomidate you as we greatly appreciate your efforts. However, we understand that sites located within a country are the fastest and most searchable. Therefore, - we recommend and welcome folks mirroring the POI site and making the translated page the home page. You can do this + we recommend and welcome folks mirroring the POI site and making the translated page the home page. You can do this either via an HTML copy with some appropriate software or the preferred method of executing the POI build directly. You can contact us via the mail list for both push and pull options. The same scripts which regenerate the POI website every 2 hours, should work for others. These are not yet in CVS as they are nasty dirty shell scripts ;-). If you mirror us, tell us so we can link you. (This will help google - associate you strongly with the project) + associate you strongly with the project)
  
  - Submitting translations is simple, you follow the same + Submitting translations is simple, you follow the same instructions as you would for submitting a code patch. Remeber to always generate patchs in diff -u format preserving the context relative to the jakarta-poi directory. Also remember - to submit any new files in a directory preserving archive format. Never post these to the list, always use + to submit any new files in a directory preserving archive format. Never post these to the list, always use Bugzilla and create attachments per the above linked instructions.
  
  Credits
  - Some people feel uncomfortable putting themselves in the <authors> tags at the top of the documentation as they feel that + Some people feel uncomfortable putting themselves in the <authors> tags at the top of the documentation as they feel that translation does not give them the right to claim authorship. Please don't feel this way, please add yourself to the authors tags. It can be assumed that authors on the master documentation are all content creators and any additional authors listed - on the translation that are not on the master document are translators of the documentation. You authored the xx language - version of the document and should freely add yourself there. Additionally, please supply a patch to the - Who We Are page noting you as a developer once you've submitted a few translation patches. You deserve + on the translation that are not on the master document are translators of the documentation. You authored the xx language + version of the document and should freely add yourself there. Additionally, please supply a patch to the + Who We Are page noting you as a developer once you've submitted a few translation patches. You deserve credit and it helps the project to give you credit. Remember documentation is on par with code contribution.
  
  Starting a new translation
  - To start a translation for a language not already in existance you must create a directory under src/documentation/content/xdocs/trans with a + To start a translation for a language not already in existance you must create a directory under src/documentation/content/xdocs/trans with a two or three letter designation of the country where the language originated. (For example es = Spanish, de = German) - Copy the book.xml and index.xml file from src/documentation/content/xdocs directory into the src/documentation/content/xdocs/trans/xx directory. - Change all paths in the book.xml and index.xml to match the relative location of the English version. For example if there is a + Copy the book.xml and index.xml file from src/documentation/content/xdocs directory into the src/documentation/content/xdocs/trans/xx directory. + Change all paths in the book.xml and index.xml to match the relative location of the English version. For example if there is a link in index.html that references ./poifs/index.html, you'd change that to ../../poifs/index.html (up 2 directories from trans/xx). - Create a link from the book.xml file in the src/documentation/content/trans directory (this is necessary or the build will ignore your + Create a link from the book.xml file in the src/documentation/content/trans directory (this is necessary or the build will ignore your documentation) similar to the other languages. Run the clean target followed by the docs target. If the build is successful, congratulations! If it fails, you probably got one of the relative paths incorrect! Go fix it (the first error message generally contains the most useful information). If you need help @@ -114,24 +114,24 @@
  So now you have a directory with a copy of the index from the master documentation...so what? Well now translate book.xml and index.xml. Try to build again. It probably won't work. Why? The encoding. At the top of every file there is an encoding="UTF-8" (in general). - This encoding will work for many Western European languages, but not for others, or will require some nasty escape sequencing. This is - where trial and error + guess work come in. This Table of encodings may help. There is a + This encoding will work for many Western European languages, but not for others, or will require some nasty escape sequencing. This is + where trial and error + guess work come in. This Table of encodings may help. There is a catch. Your encoding should work on a Linux system under Java 1.3.1 and of course with the build in general. If in doubt, ask. (This is a practical consideration as thats the setup of the machine currently running the nightly/site builds.)
  
  Need help? -
  - Andy Oliver is the cofounder of the POI project and one of its most active documentation contributers. Well, Andy used to think he - spoke very clearly until he traveled abroad and discovered his speech was composed almost entirely of coloquialisms. This can make some +
  + Andy Oliver is the cofounder of the POI project and one of its most active documentation contributers. Well, Andy used to think he + spoke very clearly until he traveled abroad and discovered his speech was composed almost entirely of coloquialisms. This can make some of the POI documentation difficult to translate, if in doubt...ask. Its also appropriate to eliminate these from the master documentation - where it makes it clearer. + where it makes it clearer.
  
  Translation Conventions
  - In addition to the above practical guidelines we hope to come up with a set of translation guidelines here (or linked from here) for + In addition to the above practical guidelines we hope to come up with a set of translation guidelines here (or linked from here) for general use as well as language specific translation guidelines and conventions. We assume that the POI translators will document them here as they develop.
  @@ -140,7 +140,6 @@
  Copyright (c) @year@ The Apache Software Foundation All rights reserved. - $Revision$ $Date$
  diff --git a/src/documentation/content/xdocs/trans/index.xml b/src/documentation/content/xdocs/trans/index.xml index 3d692ef6db..5f6aec70e0 100644 --- a/src/documentation/content/xdocs/trans/index.xml +++ b/src/documentation/content/xdocs/trans/index.xml @@ -30,16 +30,16 @@
  Introduction
  - The POI project has always had a very international following. In fact even today POI is - more popular in Europe than in the US where the original founders reside. Today POI is - developed by people from all over the world including India, Austrailia, Japan, and Russia. + The POI project has always had a very international following. In fact even today POI is + more popular in Europe than in the US where the original founders reside. Today POI is + developed by people from all over the world including India, Austrailia, Japan, and Russia. We recognize and welcome our geographically and culturally diverse users and contributors and - wish to accomidate you as best as we can. + wish to accomidate you as best as we can.
  
  - Documentation has always been a cornerstone to POI's success. No matter how fluent one is in + Documentation has always been a cornerstone to POI's success. No matter how fluent one is in a second language, it is always easier to comprehend concepts explained in one's native language, - therefore, we encourage volunteers to come and help us translate the documentation into other + therefore, we encourage volunteers to come and help us translate the documentation into other languages. Below is a list of the translations that are currently in progress and their status.
  
  @@ -60,7 +60,6 @@
  Copyright (c) @year@ The Apache Software Foundation All rights reserved. - $Revision$ $Date$
  diff --git a/src/documentation/skins/common/xslt/html/book2menu.xsl b/src/documentation/skins/common/xslt/html/book2menu.xsl index 866452763e..619d1decff 100644 --- a/src/documentation/skins/common/xslt/html/book2menu.xsl +++ b/src/documentation/skins/common/xslt/html/book2menu.xsl @@ -24,7 +24,6 @@ book2menu.xsl generates the HTML menu. It outputs XML/HTML of the form: which is then merged with other HTML by site2xhtml.xsl -$Id$ --> diff --git a/src/documentation/skins/common/xslt/html/document2html.xsl b/src/documentation/skins/common/xslt/html/document2html.xsl index 09070b3dfd..fc9eaaabd6 100644 --- a/src/documentation/skins/common/xslt/html/document2html.xsl +++ b/src/documentation/skins/common/xslt/html/document2html.xsl @@ -31,21 +31,20 @@ and tabs (tab2menu.xsl) to generate the final HTML. Section handling - anchors are added if the id attribute is specified -$Id$ --> - - + - + @@ -59,7 +58,7 @@ $Id$ 2 - + @@ -78,21 +77,21 @@ $Id$ - +

- - + - +

@@ -118,15 +117,15 @@ $Id$ - + @@ -148,14 +147,14 @@ if (VERSION > 3) { - + - + @@ -166,7 +165,7 @@ if (VERSION > 3) { - +

@@ -287,8 +286,8 @@ if (VERSION > 3) { @@ -347,9 +346,9 @@ if (VERSION > 3) {

- + - +

@@ -408,19 +407,19 @@ if (VERSION > 3) { - + v - +

- +

@@ -463,6 +462,5 @@ if (VERSION > 3) { - - + diff --git a/src/documentation/skins/common/xslt/html/pathutils.xsl b/src/documentation/skins/common/xslt/html/pathutils.xsl index 81be900e0c..4d147a54ba 100644 --- a/src/documentation/skins/common/xslt/html/pathutils.xsl +++ b/src/documentation/skins/common/xslt/html/pathutils.xsl @@ -29,7 +29,6 @@ ext: return the last extension of the filename in a path filename-noext: return the file part of a path without its last extension @author Jeff Turner -$Id$ --> @@ -83,11 +82,11 @@ Examples: @@ -235,7 +234,7 @@ Usage: saxon pathutils.xsl pathutils.xsl path=foo/bar path-nofrag =

- + --> diff --git a/src/documentation/skins/common/xslt/html/site2xhtml.xsl b/src/documentation/skins/common/xslt/html/site2xhtml.xsl index 4037c2d541..90cd78b6f3 100644 --- a/src/documentation/skins/common/xslt/html/site2xhtml.xsl +++ b/src/documentation/skins/common/xslt/html/site2xhtml.xsl @@ -34,7 +34,6 @@ footer, searchbar, css etc. As input, it takes XML of the form: -$Id$ --> @@ -135,12 +134,12 @@ $Id$ -

diff --git a/src/documentation/skins/poi-site/xslt/html/document2html.xsl b/src/documentation/skins/poi-site/xslt/html/document2html.xsl index cad0b0869e..6e8a05d5e0 100644 --- a/src/documentation/skins/poi-site/xslt/html/document2html.xsl +++ b/src/documentation/skins/poi-site/xslt/html/document2html.xsl @@ -28,7 +28,6 @@ to HTML. It renders XML as HTML in this form: ..which site2xhtml.xsl then combines with HTML from the index (book2menu.xsl) and tabs (tab2menu.xsl) to generate the final HTML. -$Id$ --> @@ -53,7 +52,7 @@ $Id$ -

by @@ -65,14 +64,14 @@ $Id$

- + - - + +

@@ -81,8 +80,8 @@ $Id$

- - + + @@ -96,9 +95,9 @@ $Id$ - + - +

@@ -114,15 +113,15 @@ $Id$

- + - + - + @@ -146,11 +145,11 @@ $Id$

- +

@@ -162,7 +161,7 @@ $Id$

- +

@@ -194,7 +193,7 @@ $Id$ b - +

@@ -210,7 +209,7 @@ $Id$

- + @@ -230,7 +229,7 @@ $Id$

- + @@ -238,7 +237,7 @@ $Id$

- +

@@ -269,7 +268,7 @@ $Id$

+ @@ -281,7 +280,7 @@ $Id$ - +

PDF diff --git a/src/documentation/skins/poi-site/xslt/html/site2xhtml.xsl b/src/documentation/skins/poi-site/xslt/html/site2xhtml.xsl index b13ff57041..74c0661d17 100644 --- a/src/documentation/skins/poi-site/xslt/html/site2xhtml.xsl +++ b/src/documentation/skins/poi-site/xslt/html/site2xhtml.xsl @@ -34,7 +34,6 @@ footer, searchbar, css etc. As input, it takes XML of the form:

-$Id$ --> @@ -54,13 +53,13 @@ $Id$ - + - + ================= start Banner ==================

PDF

- + ================= start Group Logo ================== @@ -89,24 +88,24 @@ $Id$ ================= end Project Logo ================== - +

================= end Banner ================== ================= start Main ================== - + ================= start Status ==================

================= start BreadCrumb ================== -

- | +

+ |

- | + |