This is an automated email from the ASF dual-hosted git repository. wave pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
commit 0db9bd165c439bcaaed458b08118a44b76fb3608 Author: Dave Fisher <[email protected]> AuthorDate: Sun Nov 1 13:10:48 2020 -0800 Migration of lingucomponent html content --- content/lingucomponent/auto_instal.html | 87 ++ .../dicooo/Tut_es/Tutorial_DicOOo_es.html | 286 +++++++ content/lingucomponent/dictionary.html | 75 ++ content/lingucomponent/dictpack.html | 10 + content/lingucomponent/download_dictionary.html | 29 + content/lingucomponent/grammar.html | 60 ++ content/lingucomponent/hyph_dic.html | 10 + content/lingucomponent/hyphenator.html | 37 + content/lingucomponent/index.html | 120 +++ content/lingucomponent/index_template.html | 76 ++ content/lingucomponent/instal_difs.html | 53 ++ content/lingucomponent/instal_fonts.html | 43 + content/lingucomponent/instal_reinstal.html | 145 ++++ content/lingucomponent/manual_instal.html | 129 +++ content/lingucomponent/spell_dic.html | 10 + content/lingucomponent/style_guide.html | 926 +++++++++++++++++++++ content/lingucomponent/thes_dic.html | 10 + content/lingucomponent/thesaurus.html | 50 ++ 18 files changed, 2156 insertions(+) diff --git a/content/lingucomponent/auto_instal.html b/content/lingucomponent/auto_instal.html new file mode 100644 index 0000000..a201cfb --- /dev/null +++ b/content/lingucomponent/auto_instal.html @@ -0,0 +1,87 @@ +<html><head> + <title>Auto-Install</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + </head> + <body> + <a href="download_dictionary.html">return to Table of Contents</a><br /> + + <table width="80%" border="0" cellpadding="0" cellspacing="0"> + <tr> + <td> + <h2 align="center">Automated Dictionary Installers:</h2> + <h2>===> <a href="#dicooo"> <b>DicOOo Macro</b></a>: multi-platform<br /> + ===> <a href="#dictinstall"><b>DictInstall</b></a>: Windows<br /> + ===> <a href="#ooodi"> <b>OOoDI</b></a>: Unix, Linux</h2> + <br /> + + <h4><a name="dicooo">*** DicOOo Macro:</a> + Multi-Platform, Multi-Language, On/Off-Line Dictionary Installer</h4> + The macro in <a href="dictpack.html"> DicOOo.sxw</a>, + created by Laurent Godard, is a multi-platform solution for installing dictionaries: + <ol> + <li>on any platform executing OpenOffice.org and with DicOOo.sxw available;</li> + <li>On-Line: install dictionaries from the Internet while connected; or</li> + <li>Off-Line: use <a href="dictpack.html">Dictionary Packs</a> for installation from a local network, hard disk or Community CD.</li> + </ol> + <hr /> + <p>We hope that <b>Community distributors</b> will find DicOOo and dictionary packs a useful addition on their CDs.<br /> + <br /> + Some notes on building or modifying Off-Line Dictionary Packs for your requirements:<br /> + This feature is especially dedicated to distributing dictionaries with CDs. An Off-Line Dictionary Pack contains 3 text files and the + included dictionary zip files. The 3 text files describe what the off-line pack contains for each dictionary type:<br /> + <ol> + <li>spell.txt: for the included spellchecker zip files. Uses same structure as the <a href="available.lst">http://lingucomponent.openoffice.org/available.lst</a> file.</li> + <li>hyph.txt: for the included hyphenation zip files. Uses same structure as the <a href="hyphavail.lst">http://lingucomponent.openoffice.org/hyphavail.lst</a> file.</li> + <li>thes.txt: for the included thesaurus zip files. Uses same structure as the <a href="thesavail.lst">http://lingucomponent.openoffice.org/thesavail.lst</a> file.</li> + </ol> + Moreover, DicOOo code has been designed to limit the needed modification to the code, to let it start in off-line mode by default. + Users who want to adapt it, have only to focus on two global constants in the LangPack module:<br /> + StartOffLine=0 ; 0/1 to deactivate/activate off-line mode by default<br /> + NomPackLang="" ; Name of the off-line pack zip file. Relative URLs to DicOOo location are allowed<br /> + <hr /> + <blockquote> + Tech Notes:<br /> + <br /> + When finished installing dictionaries, exit OpenOffice.org and exit the QuickStarter if it's running.<br /> + Restart OpenOffice.org and navigate to Tools>Options>Language Settings>Writing Aids.<br /> + Select your new dictionaries. :-)) + </blockquote> + <h4 align="center">DicOOo Tutorials Available:</h4> + <p> + <a href="http://de.openoffice.org/spellcheck/about-spellcheck-dicooo.html";>Deutsch, html</a> :: + <a href="http://www.linuxplusvalue.be/download/tutoriel_dicooo-en.pdf";>English, pdf</a> & + <a href="http://www.linuxplusvalue.be/download/tutoriel_dicooo-en.sxw";> sxw</a> :: + <a href="dicooo/Tut_es/Tutorial_DicOOo_es.html">Español, html</a> :: + <a href="http://www.linuxplusvalue.be/download/tutoriel_dicooo-fr.pdf";>Français, pdf</a> & + <a href="http://www.linuxplusvalue.be/download/tutoriel_dicooo-fr.sxw";> sxw</a> :: + </p> + <br /> + Make a tutorial in another lang? Suggestion for improvement? Error? Contact Richard at openoffice.org.<br /> + <hr /><br /> + + <h4><a name="dictinstall">*** DictInstall: OOo Dictionary Installer for Windows</a></h4> + + <p>For Windows, Lee Corbin has created a nicely automated Dictionary Installer. Binary and source are available for <br /> + <a href="http://ooodocs.sourceforge.net/dictinstall/";>Lee Corbin's DictInstall for Windows</a>.</p> + + <p> --> Lee's Dictionary Install Tips for Windows, in<br /> + <b>English | Deutsch | Français | Español | Finnish | Danish | Greek | Italian | Nederlands</b></p> + <hr /><br /> + + <h4><a name="ooodi">*** OOoDI: OOo Dictionary Installer for Linux/Unix</a></h4> + + <p>For Linux/Unix, Jonathan Hudson has created a nice, automated Dictionary Installer. Binary and source are available at + <a href="http://ooodi.sourceforge.net";>http://ooodi.sourceforge.net</a>.</p> + + <p> --> <a href="http://ooodi.sourceforge.net/OOodi.html#usage";> + Jonathan's Dictionary Install Tips for Linux.</a></p> + <hr /> + + <p><a href="download_dictionary.html">return to Table of Contents for Writer's Aids</a></p> + + </td> + </tr> + </table> + </body> +</html> + \ No newline at end of file diff --git a/content/lingucomponent/dicooo/Tut_es/Tutorial_DicOOo_es.html b/content/lingucomponent/dicooo/Tut_es/Tutorial_DicOOo_es.html new file mode 100755 index 0000000..d167cb8 --- /dev/null +++ b/content/lingucomponent/dicooo/Tut_es/Tutorial_DicOOo_es.html @@ -0,0 +1,286 @@ +<html><head> + <title>Tutorial de DicOOo</title> + <meta http-equiv="content-type" content="text/html; charset=UTF-8"> + </head> + <body> +<p class="c2"><em><u class="c1">Tutorial para DicOOo</u></em></p> +<p class="c2"> </p> + +<p class="c3"> </p> + +<p class="c3"><em class="c6"><span class="c4">Q</span><span class="c5">ué es DicOOo</span> ?</em></p> + +<p class="c3"> </p> + +<p class="c8"><img src="DicOOo_es.png" name="Image2" alt="Image de DicOOo" align="left" vspace="15" width="255" height="125" +border="0"><span class="c7">Dicoo es un asistente de software que permite a los usuarios la instalación fácil de diccionarios (ortografía, +separación en sílabas y sinónimos)</span></p> + +<p class="c9">Este programa usa una macro escrita en OOBasic que conecta al servidor web y suministra una lista de los diccionarios +disponibles.</p> + +<p class="c11">El producto ha sido creado por <em><a class="c10" href="mailto:[email protected]";>Laurent Godard</a><span class= +"c7">,</span></em> un consultor y desarrollador independiente para OpenOffice.</p> + +<p class="c3"> </p> + +<p class="c3"><em class="c12"><span class="c4">C</span><span class="c5">ómo trabaja DicOOo?</span></em></p> + +<p class="c3"> </p> + +<p class="c3"><em><span class="c13">La macro primero hace algunas preguntas y luego conecta al usuario con un servidor web de OpenOffice.org. A +continuación muestra la lista de diccionarios disponible (ortografía, separación en sílabas y sinónimos) Una vez que se ha seleccionado el lenguaje +deseado, Dic Ooo descarga e instala los diccionartios. Si es necesario se le pedirá que configure los parámetros lingüisticos.</span></em></p> + +<p class="c3"> </p> + +<p class="c3"><em class="c12"><span class="c4">C</span><span class="c5">aracterísticas principales</span></em></p> + +<p class="c3"> </p> + +<ul> + <li> + <p class="c3"><em class="c14">MultiOS: Disponible para Windows, Linux, Mac, Solaris</em></p> + </li> + + <li> + <p class="c3"><em class="c14">Multiversión: compatible con todas las versiones de OOo</em></p> + </li> + + <li> + <p class="c3"><em class="c14">Multilenguaje: el lenguaje de GUI puede ser cambiado. La primera verisón está disponible en 10 + lenguajes.</em></p> + </li> + + <li> + <p class="c3"><em class="c14">Varios modos de instalación: se puede elegir entre la instalación en un servidor (los diccionarios pueden ser + usados por todos los usuarios) o instlación para un usuario único</em></p> + </li> + + <li> + <p class="c3"><em class="c14">Auto-actualización: Cada vez que se lo usa, DicOOo verifica la disponibilidad de una nueva versión y permite + <em class="c14">al usuario</em> instalarla.</em></p> + </li> + + <li> + <p class="c3"><em><span class="c7">Maneja la instalación fuera-de-línea usando instaladores. Estos instaladores están disponibles en el + servidor del proyecto</span> <a class="c15" href= + "http://lingucomponent.openoffice.org/download_dictionary.html#dictpack";>Lingucomponent</a><span class="c7">.</span></em></p> + </li> + + <li> + <p class="c3"><em class="c14">Licencia LGPL, autor: Laurent Godard</em></p> + </li> +</ul> + +<p class="c2"> </p> + +<p class="c3"> </p> + +<p class="c16"><em class="c12"><span class="c4">U</span><span class="c5">sando DicOOo</span></em></p> + +<p class="c3"> </p> + +<p class="c3"><em class="c14">Descargue DicOOo y abra el archivo Dicooo.sxw, acepte el uso de la Macro y verá el siguiente mensaje</em></p> + +<p class="c3"> </p> + +<p class="c3"><img src="Primera.png" name="Imagen5" align="left" width="237" height="176" border="0"></p><br clear="left"> + +<p class="c3"><em class="c14">Haga "click" en Ejecutar y verá la siguiente página:</em></p> + +<p class="c3"> </p> + +<p class="c3"><img src="DicOOo_es.png" name="Image3" align="left" width="393" height="327" border="0"></p><br clear="left"> + +<p class="c3"> </p> + +<p class="c3"><em class="c14">Seleccionando uno de los idiomas, la página correspondiente se muestra como una página web en HTML. En la imágen de +abajo se la puede observar</em></p> + +<p class="c3"> </p> + +<p class="c3"><img src="Segunda.png" name="Imagen6" align="left" width="526" height="403" border="0"></p><br clear="left"> + +<p class="c17"> </p> + +<p class="c18">Ahora haga "click" en el Botón "Ejecutar DicOOo". La macro comenzará a ejecutarse.</p> + +<p class="c19"> </p> + +<p class="c20">Esta guía explica como manejar el proceso de instalación, paso a paso a partir de aquí.</p> + +<p class="c21"> </p> + +<h2 class="c22"><span class="c4">I</span><span class="c5">nstalación paso a paso</span></h2> + +<p class="c3"> </p> + +<h3 class="c23">1) Seleccionar el modo de actualización</h3> + +<p class="c3"> </p> + +<p class="c3"><img src="Dialogo1.png" name="Imagen1" align="left" width="565" height="378" border="0"></p><br clear="left"> + +<p class="c9">Disponemos de 4 alternativas:</p> + +<p class="c3"> </p> + +<ul> + <li> + <p class="c9">Estoy conectado a Internet, descargo directamente y:</p> + + <ul> + <li> + <p class="c9">Quiero instalar los diccionarios en forma automática para un usuario único</p> + </li> + + <li> + <p class="c9">Soy un administrador y quiero instalar los diccionarios para todos los usuarios</p> + </li> + </ul> + </li> + + <li> + <p class="c9">No estoy conectado a Intener pero he bajado el paquete y:</p> + + <ul> + <li> + <p class="c9">Quiero instalarlo para un usuario único</p> + </li> + + <li> + <p class="c9">Soy un administrador y quiero instalar los diccionarios para todos los usuarios</p> + </li> + </ul> + </li> +</ul> + +<p class="c3"> </p> + +<p class="c9">En el ejemplo siguiente, tengo acceso a Internet, soy un administrador y quiero instalar los diccionarios para todos los +usuarios.</p> + +<p class="c3"> </p> + +<h3 class="c23">2) Selección del diccionario principal</h3> + +<p class="c3"> </p> + +<p class="c3"><img src="Dialogo2.png" name="Imagen2" align="left" width="566" height="377" border="0"></p><br clear="left"> + +<p class="c9">Al menos debe seleccionar un diccionario, sin embargo, no hay límites para la cantidad de diccionarios a seleccionar. Se recomienda +no seleccionar más de 10 diccionarios para no tener problemas de inestabilidad.</p> + +<p class="c3"> </p> + +<p class="c9">Al oprimir el botón Recuperar la Lista aparece la lista de Diccionarios disponibles en el sitio de la web de OpenOffice.org</p> + +<p class="c3"> </p> + +<p class="c9">Aquí, elegimos el diccionario Español (Spain) así como su separador en sílabas, el paso siguiente es pués, podríamos elegir también +un diccionario Español para algún país específico distinto de España.</p> + +<p class="c3"> </p> + +<p class="c9">Si deseamos hacer una selección múltiple se debe usar la tecla <Ctrl> que se mantiene oprimida mientras se seleccionan los +diccionarios.</p> + +<p class="c3"> </p> + +<p class="c9">Al terminar la selección se oprime la tecla <Siguiente></p> + +<p class="c3"> </p> + +<h3 class="c24">3) Selección del diccionario de separación por sílabas</h3> + +<p class="c3"> </p> + +<p class="c25">Aparece la siguiente pantalla:</p> + +<p class="c3"><img src="Dialogo3.png" name="Imagen3" align="left" width="566" height="381" border="0"></p><br clear="left"> + +<p class="c9">Otra vez, oprimimos la tecla "Recuperar la lista" y aparecerán todos los diccionarios disponibles para la separación por sílabas, con +el prefijo "hyph" seguido por el símbolo del idioma.</p> + +<p class="c9">Seleccione el diccionario de la lista.</p> + +<p class="c26">(N del T) Si selecciona más de un diccionario, mantenga oprimida la tecla <Ctrl></p> + +<p class="c3"> </p> + +<p class="c9">Ahora, haga click en "Siguiente" para seleccionar el diccionario de Sinónimos</p> + +<p class="c3"> </p> + +<h3 class="c23">4) Selección del Diccionario de Sinónimos</h3> + +<p class="c9">Como en el otro Diccionario, haga "click" sobre "Recuperar la lista"</p> + +<p class="c3"> </p> + +<p class="c3"><img src="Dialogo4.png" name="Imagen4" align="left" width="565" height="375" border="0"></p><br clear="left"> + +<p class="c3"> </p> + +<p class="c9">Seleccion el diccionario de la lista.</p> + +<p class="c26">(N del T) Si va a seleccionar más de un diccionario, mantenga oprimida la tecla <Ctrl></p> + +<p class="c26">(N del T) No hay diccionario de sinónimos en idioma Español (Castellano) ni para los demás idiomas que se hablan en España (Catalá, +Gallego, Valenciano o Vasco)</p> + +<p class="c3"> </p> + +<h3 class="c23">5. Paso final</h3> + +<p class="c9">Esto es todo! La macro comenzará ahora a descargar e instalar los diccionarios seleccionados.</p> + +<p class="c3"> </p> + +<p class="c9">La instalación está completa ahora. Usted puede desplegar los archivos "Leame" de los diccionarios haciendo "click" en "Lea los +archivos de información para cada diccionario instalado" (autores, licencias, información de instalación, etc)</p> + +<p class="c3"> </p> + +<p class="c26">(N del T) Para activar los diccionarios cargados necesitará recurrir a Herramientas > Opciones > Lingüística.</p> + +<p class="c3"> </p> + +<p class="c3"> </p> + +<p class="c27">Escrito con OpenOffice.org 1.1 RC4</p> + +<p class="c30"><span class="c28">Copyright : (Texto del documento) <span class="c7">©</span>2003 -</span> <a class="c29" href= +"mailto:[email protected]";>Stéphane Purnelle</a></p> + +<p class="c31"><span class="c28">Translation in English :</span> <a class="c29" href= +"mailto:[email protected]?subject=translation%20of%20the%20dicOOo%20document";>Yves Jacolin</a> <span class="c28">and</span> <a class="c29" href= +"mailto:[email protected]";>Derek Torres</a></p> + +<p class="c31"><span class="c32">Traducción al castellano: <a href="mailto:[email protected]";>Alfredo Russo</a></span></p> + +<h1 class="c33">Nota sobre la Licencia Pública de Documentación</h1> + +<p class="c34">Los contenidos de esta Documentación están sujetos la Versión 1.0 de la Licencia Pública de Documentación (la "Licencia") usted +puede usar esta Documentación si satisface los requerimientos de esta Licencia. Una copia de la Licencia está disponible en +http://www.openoffice.org/licenses/PDL.html.</p> + +<p class="c35">La Documentación Original es: Tutoriel de DicOOo. El Autor de la Documentación Original es Stéphane Purnelle Copyright <span class= +"c5">©</span> 2003. All Rights Reserved. (Contactos con el Autor: [email protected]).</p> + +<p class="c34">Aportes realizados por: Stéphane Purnelle, Yves Jacolin (traducción), Derek Torres (traducción) y Alfredo Russo (traducción).</p> + +<p><span class="c28">Los párrafos creados por tienen Copyright <span class="c7">©</span>2003. All Rights Reserved. (</span><a class="c10" href= +"mailto:[email protected]";>Stéphane Purnelle</a>, <a class="c29" href= +"mailto:[email protected]?subject=translation%20of%20the%20dicOOo%20document";>Yves Jacolin</a> y <a class="c29" href= +"mailto:[email protected]";>Derek Torres</a>).</p> + +<p class="c34">NOTA: El texto de este Apéndice así como partes del texto principal pueden diferir ligeramente del texto en los archivos originales +de la Documentación. Para la instalación en Español usted debiera usar el texto de esta traducción en lugar de la que aparece en el original en +Francés.</p><br> + + $Date: 2004/01/02 01:39:12 $ + </body> +</html> + \ No newline at end of file diff --git a/content/lingucomponent/dictionary.html b/content/lingucomponent/dictionary.html new file mode 100755 index 0000000..15aeeef --- /dev/null +++ b/content/lingucomponent/dictionary.html @@ -0,0 +1,75 @@ +<html><head> + <title>Spell Checking and Dictionaries</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> +</head> +<body> + <!--Heading: H2, default font (we use css, which defines color (as #cc6600) and font face; body text: default; subheadings: H4, default font--> + <!--Language here is supposed to offer a start, not a finish. Feel free to change it as necessary, but try to keep within the bounds described.--> + <!--Project mailing lists, project news, are all taken care of now by SourceCast's top navbar. You do not need to add a table for them.--> + <!--You might wish to include a "to-dos" list or something like that.--> + <h2>Spell Checking and Dictionaries </h2> + + <h4>Dictionaries/Affix files Now Available</h4> + + <p>Please see the <a href="download_dictionary.html">Dictionary Download Page</a> for more information.</p> + + <h4>How to Create Dictionary and Affix File for Another Language</h4> + + <p>The MySpell spell checker uses a modified version of Ispell's + dictionaries and affix files (modified to permit fast parsing, to be case + sensitive, etc.) so that "munched" dictionaries can be kept in straight + text. The same is true for <a href="http://hunspell.sourceforge.net/";>Hunspell</a> + which has replaced MySpell in OpenOffice.org 2.0.2 and later.</p> + + <p>So, the simplest way to add spell checking capabilities is to:</p> + + <p><b>1.</b> Find an Ispell dictionary and affix file (both have to be + modified to work). See <a href="http://fmg-www.cs.ucla.edu/geoff/ispell-dictionaries.html";> + http://fmg-www.cs.ucla.edu/geoff/ispell-dictionaries.html</a> for a good starting point. + Hunspell files will work with no modifications.</p> + + <p><b>2.</b> Contact the author of the wordlist to make sure licenses + are clear and acceptable. A list of compatible licenses is at + <a href="https://www.apache.org/legal/resolved.html";>the Apache license compatibility page</a> + but since you will be packaging an extension + <a href="https://issues.apache.org/jira/browse/LEGAL-117";>many free software licenses are considered acceptable</a> + in this particular case. + </p> + + <p><b>3.</b> (Obsolete; only if you use Ispell files) Convert the affix file and wordlist from the Ispell formats + to the formats needed by MySpell/Hunspell. Converting an affix file is time + consuming (several hours) but no programming skills are required and all that + is needed is a simple text editor. The best way to understand + how to translate an affix file to MySpell format is by example: <a + href="english.aff"> Ispell's English Affix File</a> and <a + href="http://lingucomponent.openoffice.org/en_US.aff";>MySpell's + English Affix File</a> and then grab the following <a href="affix.readme">README + (text file)</a> that explains in more detail what must be done. Also + check out the <a href="http://hunspell.sourceforge.net/";>Hunspell homepage</a>. + Hunspell supports MySpell syntax but offers several extensions which you + might need.</p> + + <p><b>5.</b> Package an extension following the + <a href="https://wiki.openoffice.org/wiki/Extension_Dictionaries";>guidelines for dictionary extensions</a>, + test it with OpenOffice and publish it to <a href="http://extensions.openoffice.org";>the OpenOffice + Extensions repository</a>. Should you need help, contact the + <a href="http://openoffice.apache.org/mailing-lists.html#localization-mailing-list-public";>localization mailing list</a>. + You must also include a README.txt file that specifies the + author; original ispell author, if any; the specific language and locale + supported; and the license you are releasing your dictionary under + (GPL, LGPL, BSD, or other). + </p> + + <p><b>6.</b> Either contact the + <a href="http://openoffice.apache.org/mailing-lists.html#localization-mailing-list-public";>localization mailing list</a> + or <a href="https://issues.apache.org/ooo/enter_bug.cgi?product=Internationalization";>Create + an issue</a> (you must be logged in) for the Internationalization project + asking the developers to include support for spell checking in your locale + (en_US, en_CA, de_DE, pt_PT, etc) and supply the link to the latest release + of your extension.</p> + + <h4>Once you have reached here: Congrats! You have helped the + OpenOffice effort - Thank You!</h4> + <p> </p> +</body> +</html> diff --git a/content/lingucomponent/dictpack.html b/content/lingucomponent/dictpack.html new file mode 100644 index 0000000..a4e76e7 --- /dev/null +++ b/content/lingucomponent/dictpack.html @@ -0,0 +1,10 @@ +<html><head> + <title>DicOOo Packs for Offline Installation</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + </head> + <body> + <a href="download_dictionary.html">return to Table of Contents</a><br /> + + <p><a href="http://wiki.services.openoffice.org/wiki/Dictionaries";>This page has been moved to the Wiki</a></p> + </body> +</html> diff --git a/content/lingucomponent/download_dictionary.html b/content/lingucomponent/download_dictionary.html new file mode 100644 index 0000000..4f066c5 --- /dev/null +++ b/content/lingucomponent/download_dictionary.html @@ -0,0 +1,29 @@ +<html><head> + <title>Writing Aids</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + + + +</head> +<body> +<h2 align="center"> Spelling, Hyphenation, and Thesaurus Dictionaries:<br /> + Download / Installation </h2> + +<hr /> + +<p><b>List of Dictionaries for Manual Installation</b></p> + +<ul> + <li><a href="http://extensions.openoffice.org";><b>Download dictionaries from the Extensions site</b></a></li> + <li><a href="http://wiki.services.openoffice.org/wiki/Dictionaries";><b>Dictionaries sorted by language</b></a></li> + <!-- + <li><a href="spell_dic.html"><b>Spelling dictionaries</b></a></li> + <li><a href="hyph_dic.html"><b>Hyphenation dictionaries</b></a></li> + <li><a href="thes_dic.html"><b>Thesauruses</b></a></li> + <li><a href="dictpack.html"><b>DicOOo Dictionary packs for local/offline installation</b></a></li> + --> +</ul> + +<br /> +</body> +</html> diff --git a/content/lingucomponent/grammar.html b/content/lingucomponent/grammar.html new file mode 100755 index 0000000..65cf43a --- /dev/null +++ b/content/lingucomponent/grammar.html @@ -0,0 +1,60 @@ +<html><head> +<title>Grammar Checking</title> +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> +</head> +<body> + <h2>Lingucomponent Sub-Project: Grammar Checking</h2> + + <p>One of the goals of the Lingucomponent project is to design, develop, and + implement a Grammar checker for English and other supported languages. + A grammar checker API has been available in OpenOffice.org since version 3.0. + More information about the API is available at the following sources:</p> + + <ul> + <li><a href="http://wiki.services.openoffice.org/wiki/Grammar_Checking";>Grammar Checking page in Wiki</a></li> + <li><a href="http://specs.openoffice.org/appwide/linguistic/Spelling_and_Grammar.odt";>Specification (.odt)</a></li> + <li><a href="http://qa.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=TASK&issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&issue_status=CLOSED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue [...] + </ul> + </li> + </ul> + + <p>If you have any interest in helping to implement a + grammar checker for the OpenOffice.org project, please subscribe to the mailing list + [email protected] and introduce yourself, your skills, + and your willingness to help this project.</p> + + <h4>Links to Open Source grammar checkers</h4> + + <ul> + <li><a href="http://afterthedeadline.com/";>After the Deadline</a>, a grammar checker for English, with OpenOffice.org integration</li> + <li><a href="http://borel.slu.edu/gramadoir/";>An Gramadóir</a>, a grammar checker for the + Irish language</li> + <li><a href="http://cogroo.sourceforge.net/";>CoGrOO</a>, a grammar checker for Portuguese</li> + <li><a href="http://grac.sourceforge.net/";>GRAC</a>, corpus-based grammar checker + written in Python</li> + <li><a href="http://extensions.openoffice.org/project/Esperantilo";>Esperantilo</a>, Esperanto</li> + <li><a href="http://sourceforge.net/projects/graviax/";>graviax</a>, grammar rules + and grammar checker for the English language</li> + <!-- <li><a href="http://www.klebran.org.uk/index.php?lg=en";>Klebran</a>, a spelling and + grammar checker for Welsh</li> --> + <li><a href="http://www.languagetool.org/";>LanguageTool</a>, a style and grammar checker + with OpenOffice.org integration, for English, French, German, Polish, Dutch, and other languages</li> + <li><a href="http://www.link.cs.cmu.edu/link/";>Link Grammar</a>, not really a grammar + checker but a parser for the English language, also see the + <a href="http://www.abisource.com/projects/link-grammar/";>link grammar page at AbiWord</a></li> + <li><a href="http://extensions.openoffice.org/project/lightproof";>Lightproof</a>, Hungarian, also minimal rule sets for English and Russian</li> + </ul> + + <h4>Links to commercial grammar checkers</h4> + + <p>Listing a link here does not imply and kind of endorsement from OpenOffice.org.</p> + + <ul> + <li><a rel="nofollow" href="http://www.bangor.ac.uk/ar/cb/cysgliad.php.en";>Cysgliad</a>, Welsh</li> + <li><a rel="nofollow" href="http://extensions.openoffice.org/project/duden-korrektor";>Duden Korrektor</a>, German</li> + <li><a rel="nofollow" href="http://extensions.openoffice.org/project/eurooffice-language-tools-professional";>EuroOffice Language Tools</a>, Hungarian</li> + </ul> + + <br /> +</body> +</html> diff --git a/content/lingucomponent/hyph_dic.html b/content/lingucomponent/hyph_dic.html new file mode 100644 index 0000000..6c494e7 --- /dev/null +++ b/content/lingucomponent/hyph_dic.html @@ -0,0 +1,10 @@ +<html><head> + <title>Hyphenation Dictionaries</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + </head> + <body> + <a href="download_dictionary.html">return to Table of Contents</a><br /> + + <p><a href="http://wiki.services.openoffice.org/wiki/Dictionaries";>This page has been moved to the Wiki</a></p> + </body> +</html> diff --git a/content/lingucomponent/hyphenator.html b/content/lingucomponent/hyphenator.html new file mode 100644 index 0000000..2cb7227 --- /dev/null +++ b/content/lingucomponent/hyphenator.html @@ -0,0 +1,37 @@ +<html><head> + <title>Hyphenator</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> +</head> +<body> +<h2>Lingucomponent Sub-Project: Hyphenation</h2> + +<p>One of the goals of this projects is to improve the quality of the +hyphenator and include more hyphenation dictionaries from various languages.</p> + +<p>The OpenOffice.org hyphenator was based on the libhnj library by Raph Levien. It +uses TeX hyphenation dictionaries with small corrections. +There are many <a href="http://wiki.services.openoffice.org/wiki/Dictionaries";> currently supported languages</a>.</p> + +<p> It is reasonably easy to port the TeX hyphenation dictionary (usually located +in <strong>tex/generic/hyphen/</strong> directory of TeX tree) to OpenOffice.org's +hyphenation format. To help with hyphenation dictionary +creation there is a <strong><a href="http://sourceforge.net/project/showfiles.php?group_id=143754&package_id=231949";>standalone version of the +hyphenation code</a></strong> available with a simple example program +that can be used for development and testing. Some hints follow:</p> + +<p> </p> +<ul> + <li>You need to replace or remove all TeX macroses from library.</li> + <li>You need to call <tt>substrings.pl</tt> (can be found in the standalone hyphenator + linked above).<br /> + Usage: <tt>substrings.pl <patterns.dic> <newpatterns.dic></tt><br /> + This will write the modified file to <tt>newpatterns.dic</tt>.</li> + <li>You need to put an indicator of the character encoding used +as the first line of the dictionary file (look in <tt>hyph_en.dic</tt>). +Possible values are: ISO8859-1, ISO8859-2, ..., ISO8859-10, KOI8-R </li> + <li>See <a href="http://wiki.services.openoffice.org/wiki/Extensions_development";>Extensions development</a> + on how to deploy your hyphenation dictionary in OpenOffice.org.</li> +</ul> +<br /> +</body> +</html> diff --git a/content/lingucomponent/index.html b/content/lingucomponent/index.html new file mode 100644 index 0000000..3de0bff --- /dev/null +++ b/content/lingucomponent/index.html @@ -0,0 +1,120 @@ +<html><head> + <title>Main</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> +</head> +<body> + <h2 align="center">Lingucomponent Project</h2> + + <p><strong>The mission of the Lingucomponent Project is to provide + competitive writing aid features (spell checking, hyphenation, + thesaurus, grammar checking etc.) for as many languages as possible.</strong></p> + <br /> + + <table cellpadding="4" cellspacing="1" bgcolor="#ffffff" width="100%"> + <tr> + <th colspan="2" bgcolor="#00315a"><font color="#ffffff" face="Arial, Helvetica, sans-serif"> + Sub-Projects: Volunteers are greatly appreciated!</font></th> + </tr> + <tr> + <td colspan="2" bgcolor="#00315a" align="center"> + <div align="left"><font color="#ffffff" size="-1"><b> </b></font></div> + </td> + </tr> + <tr> + <td bgcolor="#f0f0f0" width="50%"> <font size="-1"> <b><a href="download_dictionary.html">Download Dictionaries</a></b></font></td> + <td bgcolor="#f0f0f0" width="50%"> <font size="-1"> Dictionaries for most supported languages</font></td> + </tr> + <tr> + <td bgcolor="#f0f0f0" width="50%"> <font size="-1"> <b><a href="dictionary.html">How-to create a Spelling Dictionary</a></b></font></td> + <td bgcolor="#f0f0f0" width="50%"> <font size="-1"> Create a dictionary for your language</font></td> + </tr> + <tr> + <td bgcolor="#f0f0f0" width="50%"> <font size="-1"> <b><a href="hyphenator.html">How-to create a Hyphenation Dictionary</a></b></font></td> + <td bgcolor="#f0f0f0" width="50%"> <font size="-1"> Enhance ALT Linux hyph module; add a dictionary for your language</font></td> + </tr> + <tr> + <td bgcolor="#f0f0f0" width="50%"> <font size="-1"> <b><a href="thesaurus.html">How-to create a Thesaurus</a></b> (updated 2009-10-10)</font></td> + <td bgcolor="#f0f0f0" width="50%"> <font size="-1"> Create a thesaurus for your language</font></td> + </tr> + <tr> + <td bgcolor="#f0f0f0" width="50%"> <font size="-1"> <b><a href="grammar.html">How-to develop a Grammar Checker</a></b> (updated 2010-09-04)</font></td> + <td bgcolor="#f0f0f0" width="50%"> <font size="-1"> Design, develop, and implement grammar checking for your language</font></td> + </tr> + </table> + + <p><strong>Participation</strong><br /> + Much of our work takes place on the mailing list. You may subscribe, unsubscribe, + and view archives from the table below. Please familiarize yourself with the discussions + that have taken place. Once you have done so, don't hesitate to join in! + Feel free to introduce yourself briefly to the list when you join.</p> + + <table cellpadding="4" cellspacing="1" bgcolor="#ffffff" width="100%"> + <tr> + <td colspan="5" bgcolor="#00315a" align="center"> + <div align="center"><font color="#ffffff" face="Arial, Helvetica"><b> Lingucomponent Project Mailing List </b></font></div> + </td> + </tr> + <tr> + <td bgcolor="#99ccff" align="center"> + <div align="left"> + <font color="#00315a" face="Arial, Helvetica" size="-1"><b>List (you must be subscribed to post)</b></font></div> + </td> + <td bgcolor="#99ccff" align="center"> + <font color="#00315a" face="Arial, Helvetica" size="-1"><b>Subscribe</b></font> + </td> + <td bgcolor="#99ccff" align="center"> + <font color="#00315a" face="Arial, Helvetica" size="-1"><b>Unsubscribe</b></font> + </td> + <td bgcolor="#99ccff" align="center"> + <font color="#00315a" face="Arial, Helvetica" size="-1"><b>Browse archives</b></font> + </td> + <td bgcolor="#99ccff" align="center"> + <font color="#00315a" face="Arial, Helvetica" size="-1"><b>Search archives</b></font> + </td> + </tr> + <tr> + <td bgcolor="#f0f0f0"><font face="Arial, Helvetica" size="-1"><a href="mailto:[email protected]";> + [email protected]</a> <br /></font></td> + <td bgcolor="#f0f0f0" align="center"><font face="Arial, Helvetica" size="-1"><a href="mailto:[email protected]";> + Normal</a></font></td> + <td bgcolor="#f0f0f0" align="center"><font face="Arial, Helvetica" size="-1"><a href="mailto:[email protected]";> + Normal</a></font></td> + <td bgcolor="#f0f0f0" align="center"><font face="Arial, Helvetica" size="-1"><a href="http://lingucomponent.openoffice.org/servlets/SummarizeList?listName=dev";> + go browsing</a></font></td> + <td bgcolor="#f0f0f0" align="center"><font face="Arial, Helvetica" size="-1"><a href="http://lingucomponent.openoffice.org/servlets/SearchList?listName=dev";> + go searching</a></font></td> + </tr> + </table> + + <p><strong>Open Issues by Sub-Project</strong><br /> + + <ul> + <li><a href="http://lingucomponent.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&component=lingucomponent&subcomponent=spell+checking&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&s [...] + <li><a href="http://lingucomponent.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&component=lingucomponent&subcomponent=thesaurus&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_ [...] + <li><a href="http://lingucomponent.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&component=lingucomponent&subcomponent=other&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc [...] + </ul> + + <p><strong>Open Issues by Version</strong><br /> + + <ul> + <li><a href="http://lingucomponent.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=TASK&issue_type=PATCH&component=lingucomponent&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=OOo+3.3&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=& [...] + <li><a href="http://lingucomponent.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=TASK&issue_type=PATCH&component=lingucomponent&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=OOo+3.4&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=& [...] + <li><a href="http://lingucomponent.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=TASK&issue_type=PATCH&component=lingucomponent&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=OOo+Later&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&am [...] + </ul> + + <p><strong>Background</strong><br /> + Lingucomponent was started by Kevin Hendricks to integrate various open source + spell checkers into the OpenOffice.org build. With a little prodding from + Kevin Atkinson, the author of Pspell (now <a href="http://aspell.sourceforge.net/";>Aspell</a>), + a new spell checker called MySpell + was written in C++ that supported affix compression, based on Ispell. + MySpell was used to support spell checking in + OpenOffice.org 1.x. MySpell has been replaced with + <a href="http://hunspell.sourceforge.net/";>hunspell</a> starting with OpenOffice.org 2.0.2. + Hunspell builds on MySpell but supports Unicode and adds several other useful features.</p> + + <br /> + <p align="center">Project Lead: László Németh<br /> + </p> +</body> +</html> diff --git a/content/lingucomponent/index_template.html b/content/lingucomponent/index_template.html new file mode 100755 index 0000000..1c6be66 --- /dev/null +++ b/content/lingucomponent/index_template.html @@ -0,0 +1,76 @@ +<html><head> +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> +</head> +<body> +<!--Start here. Do not add any header HTML--> +<!--Heading: H2, default font (we use css, which defines color (as #cc6600) and font face; body text: default; subheadings: H4, default font--> +<!--Language here is supposed to offer a start, not a finish. Feel free to change it as necessary, but try to keep within the bounds described.--> +<!--Project mailing lists, project news, are all taken care of now by SourceCast's top navbar. You do not need to add a table for them.--> +<!--You might wish to include a "to-dos" list or something like that.--> + +<h2>[Projectname] Project </h2> + +<p><i>Last modified: [date]</i></p> +<br> +<br> + +<h4>Mission Statement</h4> +<p>A sentence or two explaining the purpose of the project</p> + +<br> +<h4>Background</h4> +<p>A short history, if relevant, of the project.</p> + +<br> +<h4>Project Summary</h4> +<p>[A short paragraph informing interested people of the project's scope and to-dos. + You might wish instead to include a simple table listing to-dos or associated + projects, as below:]</p> + +<br> +<table cellpadding="4" cellspacing="1" bgcolor="#ffffff" width="100%"> + <tbody> + <tr> + <td colspan="3" bgcolor="#00315a" align="Center"> + <div align="left"><font color="#ffffff" size="-1"><b> [To-dos]/[associated projects]</b></font></div> + </td> + </tr> + <tr> + <td bgcolor="#99ccff" align="Center" width="30%"> + <div align="left"><font color="#00315a" size="-1"> <b>[Type]</b></font></div> + </td> + <td bgcolor="#99ccff" align="Left"> + <font color="#00315a" size="-1"> <b>[Description]</b></font> + </td> + </tr> + <tr> + <td bgcolor="#f0f0f0" width="30%"> <font size="-1"> <b>[item 1] </b></font></td> + <td bgcolor="#f0f0f0" align="Left"> </td> + </tr> + <tr> + <td bgcolor="#f0f0f0" width="30%"> <font size="-1"> <b>[item 2] </b></font></td> + <td bgcolor="#f0f0f0" align="Left"> </td> + </tr> + <tr> + <td bgcolor="#f0f0f0" width="30%"> <font size="-1"> <b>[item 3] </b></font></td> + <td bgcolor="#f0f0f0" align="Left"> </td> + </tr> + + </tbody> +</table> +<p> + <!--Simply replace the items with your own, or delete this table. Style: font size, -1; default face. --> +</p> +<br> +<h4>Participation</h4> +<!--This language can be changed!--> +<p> Much of our work takes place in our mailing lists page, which can viewed by + clicking on the "Mailing Lists" link in the navbar above. From there, + you can subscribe to our lists and view archives. Please familiarize yourself + with the discussions that have taken place. Once you have done so, don't hesitate + to join in! A convention is that new members introduce themselves briefly before + they present ideas and opinions to the community. +<p> +</body> +</html> + diff --git a/content/lingucomponent/instal_difs.html b/content/lingucomponent/instal_difs.html new file mode 100644 index 0000000..9594b6f --- /dev/null +++ b/content/lingucomponent/instal_difs.html @@ -0,0 +1,53 @@ +<html><head> + <title>Install Note: Differences</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + </head> + <body> + <a href="download_dictionary.html">return to Table of Contents</a><br /> + + <table width="80%" border="0" cellpadding="0" cellspacing="0"> + <tr> + <td> + <h2 align="center"><a name="differences">Install Note:<br /> + Dictionary Installation Differences between OOo100 and OOo101</a></h2> + + <p>In OOo100 and before, there were only <em>user</em> dictionaries, therefore, each user would have <br /> + to install the dictionaries of their choice in the directory:<br /> + c:\Program Files\OOo100\user\wordbook\ or + /home/jrandom/OOo100/user/wordbook/</p> + + <p><b>Network installation by SysAdmin: Linux and Windows</b><br /> + By popular demand, in OOo101 (the latest stable release), there is now a shared dictionary location:<br /> + <network installation directory>/OpenOffice.org1.0.1/share/dict/ooo/<br /> + so that System Administrators, or root types, can install dictionaries there, that will be available for users to activate <br /> + as needed. The process of registering the dictionaries by the SysAdmin is the same, add the appropriate lines to the<br /> + <net path>/OOo101/share/dict/ooo/dictionary.lst in the -net install location. (see Activation)</p> + + <p><b>Standalone installation by Windows user:</b><br /> + The installation for users on standalone boxes remains the same:<br /> + Unzip the dictionary of your choice into the directory: c:\Program Files\OOo101\user\wordbook\<br /> + then, edit / create the dictionary.lst file in this directory, by adding a line corresponding to the dictionary <br /> + you installed, e.g., DICT it IT it_IT (see Activation)</p> + + <p><b>Standalone installation by Linux user:</b><br /> + Since Linux is a multi-user OS, the network install is required for proper functioning.<br /> + Unzip the dictionary of your choice into the directory:<br /> + /home/jrandom/OOo10x/user/wordbook/ or<br /> + <network installation directory>/OpenOffice.org1.0.1/share/dict/ooo/<br /> + then, edit/create the dictionary.lst file in this directory, by adding a line corresponding to the dictionary <br /> + you installed, e.g., DICT es ES es_ES (see Activation)</p> + + <p><b>ACTIVATION of additional dictionaries by all users:</b><br /> + Each user now needs to restart OOo (and quickstarter) to force OOo to reparse the lines in dictionary.lst,<br /> + then go to: <b>Tools->Options->LanguageSettings->WritingAids</b> and press the <b>"Edit"</b> button.<br /> + There, each user, using the pulldown can select their language(s) and enable MySpell spellchecking<br /> + by putting a mark in the checkbox. Then, in Language, select the one in which you wish to write and spell check.</p> + <hr /> + + <p><a href="download_dictionary.html">return to Table of Contents for Writer's Aids</a></p> + + </td> + </tr> + </table> + </body> +</html> diff --git a/content/lingucomponent/instal_fonts.html b/content/lingucomponent/instal_fonts.html new file mode 100644 index 0000000..e9d124b --- /dev/null +++ b/content/lingucomponent/instal_fonts.html @@ -0,0 +1,43 @@ +<html><head> + <title>Install Note: Fonts</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + </head> + <body> + <a href="download_dictionary.html">return to Table of Contents</a><br /> + + <table width="80%" border="0" cellpadding="0" cellspacing="0"> + <tr> + <td> + <h2 align="center"><a name="uninstalled">Install Note:<br /> + Uninstalled Fonts won't Check</a></h2> + <pre> + > from [users] 2002-Nov-25 + > It turns out the problem was that OOo was defaulting to use the + > "Thorndale" font that is not installed on my Linux box. + > If OOo spell-checks an unknown font it considers it a symbol font. It + > never spellchecks symbol fonts so none of my text was flagged as misspelled. + </pre> + + <p>In Issue #7336: http://www.openoffice.org/issues/show_bug.cgi?id=7336 which was resolved 2002-Oct-08; <br /> + here is a condensed version:</p> + + <p>Spell checking does work. Please check the following:</p> + + <p>1. The font the text is written in must actually exist on the system for spell checking to work reliably.<br /> + <b><em>Thorndale and Albany do not exist on any system without StarOffice 6.0</em></b>.<br /> + So, please, highlight the text in your document and try changing it to some font that really does exist on your machine.</p> + + <p>2. Every document has a "language" associated with it (in fact every single character does in OOo). Please <br /> + highlight some mispelled text, then go to <b>Format->Character</b>, choose the <b>Font</b> tab, and look at the <br /> + <b>Language</b> pulldown. Change it to English (USA) and you should see a little checkmark [and Abc] beside it.<br /> + <br /> + [<b>Tools->Options->TextDocument->BasicFontsWestern</b>: change to fonts that <b>are</b> installed on your system.]</p> + <hr /> + + <p><a href="download_dictionary.html">return to Table of Contents for Writer's Aids</a></p> + + </td> + </tr> + </table> + </body> +</html> diff --git a/content/lingucomponent/instal_reinstal.html b/content/lingucomponent/instal_reinstal.html new file mode 100644 index 0000000..9a14f22 --- /dev/null +++ b/content/lingucomponent/instal_reinstal.html @@ -0,0 +1,145 @@ +<html><head> + <title>Install Note: Still not working?</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + </head> + <body> + <a href="download_dictionary.html">return to Table of Contents</a><br /> + + <table width="80%" border="0" cellpadding="0" cellspacing="0"> + <tr> + <td> + <h2 align="center"><a name="reinstall">Install Note:<br /> + If Spellcheck, still, not working</a></h2> + <pre> + From: Kevin B. Hendricks <[email protected]> + Subject: Re: [users] question (spellcheck still not working) + Date: Sun, 15 Dec 2002 09:28:26 -0500 + + Hi, + + I'm the author of the spellchecking system with which some seem to be having trouble. + I really want to nail down what is going wrong. + + > Apart from that, the spellchecker dialog presents every word + > of 2 or more characters as an "Unknown word". After clicking the + > "confirm (ABC tick)" button, the "Language" list box changes from + > "English (AU)" to "English (USA)", I then click on the "Add" button and + > the checker moves to the next "Unknown word". + > It is as if the checker is learning the language. I am not sure where + > the checked words are being saved - soffice [All] perhaps. When I rerun + > the checker, it skips the words it has already checked. + </pre> + + <p>No, this is wrong -- you are mixing two different types of dictionaries.<br /> + <br /> + Spellchecking *does* work and you do *not* need to add every word to a user specified dictionary. If you do, <br /> + you will simply interfere with the proper operation of other dictionaries and create bloat.<br /> + <br /> + Assuming we are talking about a Linux system (we can modify these steps for Windows). Please do the following <br /> + to test the spell checking system from scratch: We will delete any old or partially installed dictionariesand re-install <br /> + them from known, good copies and go from there)<br /> + <br /> + 1. Start with OOo1.0.1 or OOo643C (english only), spellchecking in OOo1.0.0 has too many bugs. <br /> + Please upgrade, if at all possible.<br /> + <br /> + 2. Exit out of OpenOffice and Quickstarter (make sure neither is running).<br /> + <br /> + 3. Next, let's remove any old dictionary files of any sort. (you may have to be root to perform this step):<br /> + cd PLACE_YOU_INSTALLED_OPENOFFICE/share/dict/ooo<br /> + rm *.dic<br /> + rm *.aff<br /> + rm dictionary.lst<br /> + <br /> + [as user]<br /> + cd YOUR_USER_SPECIFIC_LOCATION/user/wordbook/<br /> + rm *.dic<br /> + rm *.aff<br /> + rm dictionary.lst<br /> + <br /> + 4. Using en_GB as an example, ... go to http://lingucomponent.openoffice.org/download_dictionary.html <br /> + and download to your computer:<br /> + en_GB.zip<br /> + hyph_en.zip<br /> + en_US.zip<br /> + <br /> + 5. cd PLACE_YOU_INSTALLED_OPENOFFICE/share/dict/ooo<br /> + unzip PATH_TO/en_GB.zip<br /> + unzip PATH_TO/en_US.zip<br /> + unzip PATH_TO/hyph_en.zip<br /> + (this will create en_GB.dic and en_GB.aff in share/dict/ooo/ and <br /> + replace the en_US.aff, en_US.dic, and hyph_en.dic that came with OOo + originallywhich you deleted in step 3 above)<br /> + <br /> + 6. create a completely new dictionary.lst file at this location just in case the old one is messed up somehow:<br /> + echo "DICT en GB en_GB" > dictionary.lst<br /> + echo "HYPH en GB hyph_en" >> dictionary.lst<br /> + echo "THES en GB th_en_US" >> dictionary.lst<br /> + echo "DICT en US en_US" >> dictionary.lst<br /> + echo "HYPH en US hyph_en" >> dictionary.lst<br /> + echo "THES en US th_en_US" >> dictionary.lst<br /> + [Note: you can do this with a text editor, if preferred.]<br /> + <br /> + 7. If you did all of this, then share/dict/ooo/ should look like the following:<br /> + dictionary.lst<br /> + en_GB.aff<br /> + en_GB.dic<br /> + en_US.dic<br /> + en_US.aff<br /> + hyph_en.dic<br /> + th_en_US.dat<br /> + th_en_US.idx<br /> + <br /> + and dictionary.lst should look like this:<br /> + DICT en GB en_GB<br /> + HYPH en GB hyph_en<br /> + THES en GB th_en_US<br /> + DICT en US en_US<br /> + HYPH en US hyph_en<br /> + THES en US th_en_US<br /> + <br /> + 8. After double-checking that steps 1 to 7 have been done, then start up OOo (and quickstarter if you use it).<br /> + <br /> + 9. Go immediately to: Tools->Options->LanguageSettings->WritingAids<br /> + Hit "Edit" and use the *pull down* menu to select your locale<br /> + DO NOT FORGET TO HIT THE EDIT BUTTON AND USE THE LOCALE PULLDOWN and then, + make sure to check the box beside the MySpell Spell Checker for that locale, as well as hyphenator and theasurus, + if so desired.Then, once those are checked you should see checkboxes with ABC beside both en(US) and en(UK).<br /> + <br /> + 10. Now, to test if this has worked, do NOT open any previous document but simply go to an empty Writer doc (should be on screen already ) + and type the following lines:<br /> + This is a line of text in American, and<br /> + this is a line of text in British.<br /> + Then highlight both lines and use the Font pull-down menu and select a font you know absolutely certain is installed on your machine (i.e., + do NOT select Thorndale!). I chose Courier on my machine for this test.<br /> + <br /> + 11. Highlight the first line of the file and go to Format->Character->Font<br /> + and using the language pulldown menu select "en (US)" (you should see a<br /> + little check with ABC by it).<br /> + <br /> + 12. Highlight the second line of the file and go to Format->Character->Font and use the pulldown menu and select "en (UK)" (it should + also have a little check ABC beside it).<br /> + <br /> + 13. Then, once all of this is done, please put your cursor at the very beginning of this document and using Tools, tell it to spellcheck the + document.<br /> + <br /> + You should immediately see a spelling error with "linee" in a window with "line" as one of the suggestions (this is the spellling error in + the American line) and then once you replace that you should in fact see the exact same window (this time for the British spelling error) + which you can then replace.<br /> + <br /> + You should have now spellchecked a document successfully in two different languages in one pass. I have tested all of these procedures on my + machine and it works 100% of the time for me.<br /> + <br /> + If you have followed these instructions exactly and don't see what I see, then we have a bug I need to track down. Please contact me directly + with exactly what happened at each step and we can figure out why spellchecking is not working for you.<br /> + <br /> + Kevin</p> + <hr /> + + <p><a href="download_dictionary.html">return to Table of Contents for Writer's Aids</a></p> + + + </td> + </tr> + </table> + </body> +</html> diff --git a/content/lingucomponent/manual_instal.html b/content/lingucomponent/manual_instal.html new file mode 100644 index 0000000..879c6a2 --- /dev/null +++ b/content/lingucomponent/manual_instal.html @@ -0,0 +1,129 @@ +<html><head> + <title>Spelling / Hyphenation Install</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + </head> + <body> + <a href="download_dictionary.html">return to Table of Contents</a><br /> + + <table width="80%" border="0" cellpadding="0" cellspacing="0"> + <tr> + <td> + <h2 align="center">Non-automated Spelling / Hyphenation Installation</h2> + <br /> + + <h3 align="left"><a name="installspell">Non-automated Spelling Installation</a></h3> + + <ol> + <li>To install these dictionaries in build OO641C, OOo100, OOo101, OOo102, or later:</li> + <li>Close all open OOo windows and the Quickstarter, before installing and editing the dictionary.lst file.</li> + <li>Copy the compressed dictionary file into OpenOffice.org <font face="Courier New,Courier, mono">/share/dict/ooo/</font> + and unzip it.</li> + <li>Edit the dictionary.lst file in that <b>same</b> directory (create it if it doesn't exist) using a text editor, <br /> + to register a dictionary for a specific locale (the same dictionary can be registered for multiple locales).<br /> + + <p><b>For example:</b><br /> + To add the <font face="Courier New, Courier, mono">de_DE.zip</font> dictionary under the German (Germany) locale to OOo, + you would:</p> + <table width="75%" border="0" bgcolor="#CCCCCC"> + <tr> + <td><font face="Courier New, Courier, mono"><b>cd c:\Program_Files\OOo101\user\wordbook\<br /> + or<br /> + cd c:\Program_Files\OOo102\share\dict\ooo\<br /> + or<br /> + cd /home/jrandom/OOo101/user/wordbook/<br /> + or<br /> + cd /home/jrandom/OOo102/share/dict/ooo/</b><br /> + <br /> + unzip de_DE.zip</font></td> + </tr> + </table><br /> + <br /> + <br /> + + <p>And then using a text editor add the following line to dictionary.lst:</p> + + <table width="75%" border="0" bgcolor="#CCCCCC"> + <tr> + <td><b><font face="Courier New, Courier, mono">DICT de DE de_DE</font></b></td> + </tr> + </table>This line tells OOo to register the affix file <font face="Courier New, Courier, mono">de_DE.aff</font> + and the wordlist <font face="Courier New, Courier, mono">de_DE.dic</font> to the locale, de DE,<br /> + which is German (Germany). Save the changes.<br /> + <br /> + The specific fields of this line are:<br /> + Field 1: Entry Type "DICT" marks the entry as a dictionary pattern descriptor<br /> + Field 2: Language code from Locale "en" or "de" or "pt" ... + (see <a href="http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt";>ISO Language Code</a> page)<br /> + Field 3: Country code from Locale "US" or "GB" or "PT" ... + (see <a href="http://www.chemie.fu-berlin.de/diverse/doc/ISO_3166.html";>ISO Country Code</a> page)<br /> + Field 4: Root name of Dictionary "english" or "en_US" or ... (do not add the .aff or .dic extensions to the name)<br /> + <br /> + </li> + + <li>Now, start up OpenOffice.org, and click on:<br /> + <b>Tools->Options->LanguageSettings->WritingAids</b><br /> + Hit "<b>Edit</b>" and use the pull down menu to select your locale<br /> + and then, make sure to check the MySpell/Hunspell Spell Checker for that locale.</li> + </ol> + + <p>That's it! Your spelling dictionary is installed and registered for that language.</p> + + <p><b>Note:</b> Windows users may need to exit OpenOffice.org and close the QuickStarter <br /> + before being able to access the hyphenation patterns, since the QuickStarter caches the contents <br /> + of dictionary.lst and the changes are not seen until the next reload.</p> + <hr /> + <br /> + <a href="download_dictionary.html">return to Table of Contents for Writer's Aids</a> + <br /> + <br /> + + <h3 align="left"><a name="installhyph">Non-automated Hyphenation Installation</a></h3> + + <p>Unpack the archive into the directory <font + face="Courier"><OpenOffice.org installation directory>/share/dict/ooo</font></p> + + <p>Open the file "dictionary.lst" present in that + directory in your favourite text editor and add the following line: </p> + + <ol> + <table width="25%" border="10%" bgcolor="#C0C0C0"> + <tr> + <td><font face="Courier"><b>HYPH it IT hyph_it</b></font></td> + </tr> + <td>Save the changes. </td> + </table> + <br /> + <p>The meaning of the fields are as follows:</p> + <ol> + <p>Field 1: "HYPH" marks the entry as a hyphenation pattern descriptor.<br /> + Field 2: Language code from Locale "en" or "it" or "pt" or etc. + (see <a href="http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt";>ISO Language Code</a> page)<br /> + Field 3: Country code from Locale "IT" ... (see <a href="http://www.chemie.fu-berlin.de/diverse/doc/ISO_3166.html";> + ISO Country Code</a> page)<br /> + Field 4: Name of the file containing the patterns (without extention).<br /><br /><br /> + </p> + </ol> + <p>Now start up OpenOffice.org and go to:</p> + + <p><b>Tools->Options->LanguageSettings->WritingAids</b></p> + + <p>Hit "<b>Edit</b>" and use the pull down menu to select the language you want to add; + check the box next to ALTLinux LibHnj Hyphenator.<br /><br /></p> + + <p>That's it! Your hyphenation dictionary is installed and registered for that language.<br /><br /></p> + + <p><b>Note:</b> Windows users may need to exit OpenOffice.org and + close the QuickStarter before being able to access the + hyphenation patterns, <br />since the QuickStarter caches the + contents of dictionary.lst and the changes are not seen + until the next reload.<br /></p> + </ol> + <hr> + + <p><a href="download_dictionary.html">return to Table of Contents for Writer's Aids</a></p> + + </td> + </tr> + </table> + </body> +</html> diff --git a/content/lingucomponent/spell_dic.html b/content/lingucomponent/spell_dic.html new file mode 100644 index 0000000..d9ad566 --- /dev/null +++ b/content/lingucomponent/spell_dic.html @@ -0,0 +1,10 @@ +<html><head> + <title>Spell Checking Dictionaries</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + </head> + <body> + <a href="download_dictionary.html">return to Table of Contents</a><br /> + + <p><a href="http://wiki.services.openoffice.org/wiki/Dictionaries";>This page has been moved to the Wiki</a></p> + </body> +</html> diff --git a/content/lingucomponent/style_guide.html b/content/lingucomponent/style_guide.html new file mode 100755 index 0000000..3c746cf --- /dev/null +++ b/content/lingucomponent/style_guide.html @@ -0,0 +1,926 @@ +<html><head> +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> +</head> +<body> +<h2>OpenOffice.org Style Guide</h2> +<p><a href="mailto:[email protected]";>-Louis Suarez-Potts</a></p> +<p><i>Last modified 26 August 2001<br> + <br> + </i></p> +<h4>Preface</h4> +<p>This style guide has grown from it initial short version to something much + longer. However, thanks to the wonders of hypertext, one need not read all of + it; just the relevant sections. The three most important sections are featured + in the "<a href="#quickstart">Quick Start</a>" and include: <a href="#projectindex">The + Project Index Page</a>, <a href="#linking">Linking</a>, and <a href="#styles">style + sheets</a> (CSS). Other sections describe the OpenOffice.org <a href="#website">website</a>, + our <a href="#ooostyle">style</a>, how to do OpenOffice.org <a href="#tables">tables</a>, + and so on.</p> +<p>This guide is meant to be viewed by a Web browser, or by a WYSIWYG HTML editor. + If you do look at it through an editor such as HomeSite or BBEdit, things will + look strange, as I wrote it presuming people would see it from a browser's perspective. + I have tried to include as many "cut-and-paste examples" as I could + think of; these are clearly labeled as such below. You can also just copy from + the existing website.</p> +<p>If you have questions, please send them to me: <a href="mailto:[email protected]";>[email protected]</a>. +</p> +<br> +<hr> +<h3>Contents</h3> +<a name="top"></a> +<dl> + <dt><a href="#quickstart">Quick Start</a> + <dt><a href="#introductory">Introductory</a></dt> + <dd> + <li><a href="#overview">Overview: HTML</a> + <li><a href="#about">About the OpenOffice.org Website</a> + <li><a href="#ooostyle">The OpenOffice.org Style </a></li> + + <li><a href="#tidy">Using Tidy</a></li> + <li><a href="#styles">Style Sheets (CSS)</a> + <li><a href="#linking">Linking, Or, How to Write Links That <i>Work</i></a> + <li><a href="#linking">Absolute vs. Relative Links</a> + <li><a href="#projectindex">The Project Index Page</a> + <li><a href="#templates">Index Page Templates</a> + <li><a href="#samplepage">Samples: Viewed as HTML</a> + <dt><a href="#tables">Tables</a> + <dd><li><a href="#simptable">The Simple Table (Bordered)</a> + <li><a href="#simplesample">Sample</a></li> + <li><a href="#simpformatting">Table Formatting: General</a> </li> + <li><a href="#simpformatparticular">Table Formatting: Particular</a></li> + <li><a href="#htmlversion1">What this table looks like in HTML</a></li> + <li><a href="#cutnpaste1">Cut 'n' Paste Sample</a></li> + <li><a href="#simpunbordered">The Simple Table (Unbordered)</a> + <li><a href="#simpunbsample">Sample: Unbordered Simple Table</a></li> + <li><a href="#simpsamphtml"> Simple, Unbordered Table, in HTML</a></li> + <li><a href="#nestedtable">The Nested Table</a> + <li><a href="#extformatting1">Table Formatting, Exterior, General</a></li> + <li><a href="#extformatting2">Table Formatting, Exterior: Particulars</a> + </li> + <li><a href="#formattingint1">Table Formatting: Interior Table</a> </li> + <li><a href="#inttableparts">Interior Table Particulars</a></li> + <li><font color="#000000"><a href="#inttableHTML">Here is what this table + looks like in HTML</a></font></li> + <li><a href="#sampnestedtable">Sample Nested Table</a> </li> + <dt><a href="#conclusion">Conclusion</a> + <dt><a href="#otherguide">Another style guide: recommended!</a><br> +</dl> +<hr> +<a name="quickstart"></a> +<h3>Quick Start</h3> +<h4><b><u>What to do</u></b> </h4> +<blockquote> + <p>Use our index page <a href="index_template.html" target="_blank">template</a>. + Or, use StarOffice or OpenOffice.org to create your index page. Either way, + follow these conventions:</p> + <ul> + <li>Headings: No <b>h1.</b> Use <b>h2</b> for the largest heading, with h3 + and h4 for subheadings. If you use h1, nothing bad will happen, it will + just look odd. </li> + <li>Leave fonts as default. Exceptions: code font. </li> + <li>No document title. It won't appear, or it may appear in an ugly fashion + at the top of the page</li> + <li>Use <a href="#linking">relative links</a>.</li> + </ul> + <p>That is about it. There is no need for h1 heading, as it is rather too large. + If you use StarOffice/OpenOffice.org, you can conform your page to OpenOffice.org + standards using <a href="#tidy">Tidy.</a> Tidy will configure the page so + that it does not disrupt the operation of SourceCast. For more information + about the OpenOffice.org website, please read below, "<a href="#about">About + the OpenOffice.org Website</a>." </p> +</blockquote> +<br> +<hr> +<a name="introductory"></a> +<h3>Introduction</h3> +<h4><a name="overview">Overview: HTML</a></h4> +<p>I won't bore you with a definition of HTML, but basically an HTML page or document + is comprised of plain, unformatted text with embedded commands in the text adjacent + to the target text that stipulate the way the target text should look when viewed + according to certain conventions by certain technologies. These commands are + called "tags," come in paired sets, and look like regular text: <font face="Courier New, Courier, mono"><b>bold</b></font>, + for instance, gives you <b>bold</b>. Not terribly complicated, the idea is simplicity + itself. A browser constructed and instructed to view these tags according to + the accepted standards and conventions will thus read the tag for bold as indicating + that the characters within the brackets should be represented in boldface. More + involved tags do the same logical thing only more elaborately.</p> +<p><b>Note</b>: When coding in HTML you have to tell the browser when to start + reading something and when to end reading it: The opening and closing tags. + These tag pairs may be separated by any number of characters, but must be nested. + Thus: ABC...CBA.</p> +<p>Almost all modern word processing software such as StarOffice are able to convert + formatted text into HTML pages that <i>look</i> the same (or close enough), + when viewed by a suitable browser (less suitable: older browsers that are not + equipped to read the latest HTML conventions). As well, really rudimentary word + processors and text editors can be used. In fact the HTML hackers among us <i>prefer + </i>dumb programs that don't add any extra formatting, because they rightly + want to be in control of what it is they are creating, and have no nasty surprises + in store. A bugbear of HTML coders is that different browsers read code differently, + which makes sense, if you think of a browser as a mechanical renderer of text + that proceeds according to certain conventions.</p> +<p>(If you are interested in learning more about HTML construction, a good place + to start is <a href="http://www.w3.org/"; target="_blank">http://www.W3C.org</a>)</p> +<p>In short, you can create your Web (HTML) pages using StarOffice (or OpenOffice.org) + or some other text processor...but there are some caveats. I'll deal with them + in the next section.</p> +<p><a href="#top">Back to top</a><br> + <br> + <br> +<h4>About the OpenOffice.org Website<a name="about"></a></h4> +<p>We have a fairly simple architecture in which there is static element framing + a dynamic element. The static element comprises the header, footer, title, and + navbars. The dynamic only consists of the content in the middle: the body of + the text. Using the latest technology, these static and dynamic elements are + composited together, producing a coherent Web page. </p> +<p>Because of this arrangement, you cannot (or at least should not) create pages + that <i>also</i> have those parts the static section supplies. That is, any + page created for the OpenOffice.org website should start with whatever you have + to say--the content--and that's it. No<head>, <title>. <body> + tags. Only your content.</p> +<p>And if you do include such tags, what will happen? Probably nothing exciting. + Browsers read from left to right, top to bottom, so it will read the static + tags first (which is why all our pages are dumbly remembered in the browser + as "www.openoffice.org" no matter what their content), and will very + likely simply ignore your redundant tag. At most the text between the title + tags will appear at the top of your page in black default font.</p> +<p>There are exceptions. If you write a "meta" tag and are stipulating + XHTML or something else that deviates from the kind of HTML declared in the + static tag, the browser will likely understand your stipulation and proceed + accordingly. And, you can certainly use page-local cascading style sheets (CSS). + (StarOffice, like Microsoft Office, saves formatted documents using styles.) + However, unless the styles are clearly defined in the document or in a page + loaded with the document, they may not be read appropriately, as they may conflict + with OpenOffice.org's own styles. (See below, <a href="#styles"> Style Sheets</a>.)</p> +<p><b>Note</b>: For various reasons, please only use <i>lower case</i> not UPPER + CASE HTML formatting. Thus: <bold> not <BOLD>. If you use upper + case, nothing bad will happen. However, XHTML (which is a more flexible form + of HTML) does see case differences, so our preference now is for lower case + tags. </p> +<p><a href="#top">Back to top</a><br> + <br> + <br> + +<h4>The OpenOffice.org Style<a name="ooostyle"></a></h4> +<p>As already mentioned, our pages are simple, with very few jpgs, gifs, or any + other graphics, and no animation of any sort. We use a simple three-color scheme + of blues and lots of white spaces. This makes the pages easy to read. We also + use a kind of reddish-brown for h2 headings. All these attributes are determined + by our style sheet. See the above "<a href="#styles">Styles</a>" and + "<a href="#sample">Sample</a>" for further insight.</p> +<p><i>For general pages</i></p> +<ul> + <li>Background: Do not specify a color. Our style sheet in the static element + does that for you. You can specify a background color for a <i>table</i>; + see below.</li> + <li>Text: Black and default font</li> + <li>Page Heading: + <ul> + <li> Format: Heading 2 (h3) for big headers (page names, say), heading 3 + (h3) for smaller subheadings; heading 4 (h4) for below that + <li>Face: Default</li> + <li>For example, the heading to this page looks like this in HTML: <h2>< + > Style Guide</font></h2></li> + </ul> + </li> + <li>For smaller headings (section headings, for instance) use the same face + color/style, but diminish the size appropriately. (See below, example 1.)</li> +</ul> +<p><a href="#top">Back to top</a><br> + <br> + <br> +<p><a name="tidy"></a> +<h4>Using Tidy</h4> +<p>Get and configure HTML <a href="http://www.w3.org/People/Raggett/tidy/"; target="_blank">Tidy</a> + for your editing environment. This terrific utility cleans up broken HTML instead + of merely complaining about it. As Todd Fahner, who is generally deemed one + of the leading experts in HTML composition writes, "I strongly recommend + using it to achieve the initial xhtmlification of the files. Unfortunately, + markup-oriented tools turn Velocity (formerly WebMacro) logic into hamburger, + so you can't run the tool on the source. But you can run it on the output and + then manually merge it back into the source. It's better than re-keying it all. + Use <a href="./tidyconfig.html">this</a> config file for Tidy.</p> +<p> I recommend you use Tidy if you have created your Web page using a text-processor + such as StarOffice or OpenOffice.org, or, if you have used a WYSIWYG HTML editor + such as Dreamweaver or Go Live, both of which impart their own characteristics. + (A good WYSIWYG editor that is quite clean is <a href="http://www.w3.org/Amaya/"; target="_blank">Amaya,</a> + which is preferred by the W3C. Amaya runs on Windows.</p> +<p><a href="#top">Back to top</a><br> + <br> + <br> + +<h4><a name="styles"></a>Style Sheets</h4> +<p> OpenOffice.org now uses style sheets. This is good, as style sheets allow + us to place all the formatting information on one sheet which a browser then + refers to. As a result, both page size and access time are reduced, dramatically + so. But there are some consequences. If a user has turned off the style sheet + option in their browser, they will not see the page as it has been designed. + They will see something considerably drabber, but still perfectly functional.</p> +<p><b>Consequences.</b> Our style sheet determines the font and font-face: of + the Arial, Helvetica, sans-serif family; h1 is black, h2 is #cc3300 (a reddish + brown), h3, h4, black. If you stipulate your own fonts and font-faces, your + page may not display properly, as the browser will essentially pick and choose + syntagmatically from the options presented it. Your page may look a mess, in + short.</p> +<p>Therefore: do not stipulate any font or font-face. Leave it blank. If you have + created a page that's a conversion from a StarOffice or OpenOffice.org document, + see if you can use Tidy to clean it up. If you cannot, see if you can strip + the font and font-face information by hand, so that only the font heading information + (h1, h2, h3, etc.) remains. And if that fails, don't worry, probably nothing + <i>bad</i> will happen, your page will just look a little odd. </p> +<p><b>Note. </b>If you would like additions to the style sheet, please let me + know by sending mail to <a href="mailto:[email protected]";>[email protected]</a>. +</p> +<p><a href="#top">Back to top</a><br> + <br> + <br> + <a name="linking"></a> +<h4>Linking, Or, How to Write Links That <i><b>Work</b></i></h4> +<p><u><b>Absolute vs. Relative Links</b></u></p> +<p><i><b>We now use relative links.</b></i></p> +<p><b>Note: </b>Please use relative links of the form described below: +<ul> + <li>For top-level, "index.html" pages, use : "<font face="Courier New, Courier, mono">/[directoryname]/[doc.html]</font>" + when referring to documents in the directory <i>below the one in which the + index.html</i> <i>is located.</i> That is, if you have an index.html page + that refers to, say, "specialstyles.html" in the directory "special," + you would use "<font face="Courier New, Courier, mono">/special/specialstyles.html</font>". + Failure to use this convention will routinely result in broken links. </li> + <li>In contrast, when referring to documents <i>within a directory</i>, please + use: "<font face="Courier New, Courier, mono">[doc.html],</font>" + without a preceding slash. If you precede the filename with a slash, you will + take the browser to top-level directory. + <ul> + <li>Thus, if you are writing a link from within the index.html page of the + <font face=Courier New, Courier, mono"> "main"</font> directory referring + to a document in a subdirectory, it would be <font face=Courier New, Courier, mono"> + /foo/foobar.html</font>. And if you aer writing a link from the "<font face="courier, new, courier, mono">paper.html</font>" + page within the <font face=Courier New, Courier, mono"> /main/</font> + directory to the <font face="Courier New, Courier, mono">/foo/foobar.html</font> + page, you would write as: "<font face="Courier New, Courier, mono"><a + href="foo/foobar.html"></font>", without the preceding + slash. This is because if you include it, it tells the browser to go to + the root directory, which unless you are writing from the root, is not what you + want.</li> + </ul> + </li> + <li>Do not precede the filename with a period, as in "<font face="Courier New, Courier, mono">./[doc].html</font>". + Doing so will result in unpredictable behavior (of SourceCast). </li> + <li>When referring to links <i>above</i> the directory in which you are working, + use the standard convention of "<font face="Courier New, Courier, mono">../</font>" + per directory rung. Thus, if you are in <font face="Courier New, Courier, mono">/foo/</font> + and you want to refer to "<font face="Courier New, Courier, mono">whee.html</font> + in /main/ you would write: "<font face="Courier New, Courier, mono"><a + href="../whee.html"></font>" ; and so on, with <font face="Courier New, Courier, mono">../</font> + denoting a move up to the root index of that directory.</li> +</ul> +<p><b>Longer explanation</b>. The tendency in OpenOffice.org has been to use absolute + links. That is, links of the form, "<font face="courier, courier new">http://www.openoffice.org/styles/index_template.html</font>" + referring to a file in the same directory as this document, rather than "<font face="courier, courier new">/styles/index_template.html</font>" + (written in the <font face="Courier New, Courier, mono">www/index.html</font> + page). Both addresses refer to the same document--the index template; the former + is, however, is called "absolute" because the path won't change to reflect any + movement of the directory in which the documents live. In contrast, a "relative" + link, "<font face="courier, courier new">/index_template.html</font>" allows + for greater flexibility. All documents in the <font face="courier, courier new">/styles/</font> + directory can be moved along with the directory, and HTTP addresses will work, + no matter where they are subsequently placed. </p> +<p>Thus, if I were to relocate "<font face="courier, courier new">http://www.openoffice.org/styles/index_template.html</font>" + to, say, the <font face="Courier New, Courier, mono">/betterstyles/</font> directory, + I'd have to rename each and every HTTP address, which would be a real pain. + But if I did the same for "<font face="courier, courier new">/index_template.html</font>" + I wouldn't have to rename anything, as long as I kept the logic of directories + and indexes straight.</p> +<p><a href="#top">Back to top</a><br> + <br> + <br> + <a name="projectindex"></a> +<h4>The Project Index Page</h4> +<p>SourceCast has transformed some of the features of the project index page, + or homepage. The most important: we no longer use a table to represent all the + mailing lists, archives, and subscription information. Instead, the top navbar + has a link that more than adequately provides this information. See below, <a href="#samplepage">Sample + Page</a>, for a more or less typical index page. You can also go directly to + the project index page template: <a href="index_template.html">http://www.openoffice.org/styles/index_template.html</a>.</p> +<p>As well, the project owner's name is now automatically generated by SourceCast, + meaning that you do not have to provide it.</p> +<br> +<br> +<a name="templates"></a> +<h4>Index Page Templates</h4> +<p>An "index page" is the homepage of a directory. It is what is delivered + when someone enters, say, "http://www.openoffice.org/". The server + will look for the index page and serve it up; if it is lacking, nothing will + happen. SourceCast allows you to configure your index page while you are creating + a project, or even to use the HTML text that you enter in a box in the project + creation page. But for better homepages (and ones that will more reliably be + served up), we recommend you create and load to CVS an index page.</p> +<p>Regardless of whether you intend on using the SourceCast provision or creating + an index page, the same question obtains: What should you put on your index + page? Enough so that visitors and prospective developers will know something + about the project, the goals, the things that have to be done. Accordingly, + I have created an <a href="index_template.html" target="_blank">index page template</a>. + It is for generic projects, and has sections for statements about the mission + of the project, history, a table for to-dos or modules, and so on. Configure + it by deleting or duplicating some elements. </p> +<p><b>Note.</b> SourceCast has made it trivially easy to subscribe and unsubscribe + to mailing lists and to view and search mailing list archives. Visitors need + only click on the "Mailing Lists" link on the project's top navbar + to view the options. However, consider encouraging participation in the project + by having a brief description of the mailing lists, and what they are about. + You need not have links for subscribing or viewing archives, as those are taken + care of by the project navbar Mailing List link.</p> +<p>The template below should provide you with a quick means of starting a new + index page. If, however, you prefer to create your index page using StarOffice + or OpenOffice.org, please at least follow the conventions described above and + presented below. To use this, simply </p> +<ul> + <li><a href="index_template.html" target="_blank">Generic project index template</a></li> +</ul> +<p><a href="#top">Back to top</a><br> + <br> + <br> +<h4><a name="samplepage"></a>Sample: Viewed as HTML</h4> +<p>If you are curious about how the above page looks like in "HTML," + the below Whiteboard index template exemplifies how simple the coding is. </p> +<table width="100%" border="1" bordercolor="#99ccff" cellpadding="4" cellspacing="0"> + <tr> + <td> + <p><font face="Courier New, Courier, mono" size="-1"><!--Start here. + Do not add any header HTML--></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><!--Heading: H2, + default font (we use css, which defines color (as #cc6600) and font face; + body text: default; subheadings: H4, default font--></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><!--Language here + is supposed to offer a start, not a finish. Feel free to change it as + necessary, but try to keep within the bounds described.--></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><!--Project mailing + lists, project news, are all taken care of now by SourceCast's top navbar. + You do not need to add a table for them.--></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><!--You might wish + to include a "to-dos" list or something like that.--><h2>[Projectname] + Project </h2></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><p><i>Last + modified: [date]</i></p></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><br><br> + <br><br> + <br> + <h4>Mission Statement</h4><br> + <p>A sentence or two explaining the purpose of the project</p> + <br> + <br> + <br><br> + <h4>Background</h4><br> + <p>A short history, if relevant, of the project.</p><br> + <br><br> + <h4>Project Summary</h4><br> + <p>[A short paragraph informing interested people of the project's + scope and to-dos. You might wish instead to include a simple table listing + to-dos or associated projects, as below:]</p></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><br><br> + <table cellpadding="4" cellspacing="1" bgcolor="#ffffff" + width="100%"></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><tbody> <br> + <tr> <br> + <td colspan="3" bgcolor="#00315a" align="Center"> + <br> + <div align="left"><font color="#ffffff" size="-1"><b> + [To-dos]/[associated projects]</b></font></div></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></td><br> + </tr><br> + <tr> <br> + <td bgcolor="#99ccff" align="Center" width="30%"> + <br> + <div align="left"><font color="#00315a" size="-1"> + <b>[Type]</b></font></div></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></td><br> + <td bgcolor="#99ccff" align="Left"> <font + color="#00315a" size="-1"> <b>[Description]</b></font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></tr><br> + <tr> <br> + <td bgcolor="#f0f0f0" width="30%"> <font + size="-1"> <b>[item 1] </b></font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td bgcolor="#f0f0f0" + align="Left">&nbsp;</td><br> + </tr><br> + <tr> <br> + <td bgcolor="#f0f0f0" width="30%"> <font + size="-1"> <b>[item 2] </b></font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td bgcolor="#f0f0f0" + align="Left">&nbsp;</td><br> + </tr><br> + <tr> <br> + <td bgcolor="#f0f0f0" width="30%"> <font + size="-1"> <b>[item 3] </b></font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td bgcolor="#f0f0f0" + align="Left">&nbsp;</td><br> + </tr><br> + <br> + </tbody> <br> + </table><br> + <p><br> + <!--Simply replace the items with your own, or delte this table. Style: + font size, -1; default face. --></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></p><br> + <br><br> + <h4>Participation</h4><br> + <!--This language can be changed!--><br> + <p> Much of our work takes place in our mailing lists page, which + can viewed by clicking on the &quot;Mailing Lists&quot; link in + the navbar above. From there, you can subscribe to our lists and view + archives. Please familiarize yourself with the discussions that have taken + place. Once you have done so, don't hesitate to join in! A convention + is that new members introduce themselves briefly before they present ideas + and opinions to the community.</font></p> + <p><font face="Courier New, Courier, mono" size="-1"><p>&nbsp;</font></p> + </td> + </tr> +</table> + +<br> +<p><b>Note: </b>You will notice the absence of header and footer tags; the static + element takes care of that.</p> +<p><a href="#top">Back to top</a><br> + <br> +<br> +<br> +<h3>Tables<a name="tables"></a></h3> +<p>We have two primary table structures. One is simpler than the other; use it + when you have fewer headings to cover. Depending on the nature of the information + to be displayed, it can consist of two nested tables: the outside table provides + the border, the inside the data. The more complex table has no border and uses + only one table to supply the content. </p> +<br> +<h4>The Simple Table<a name="simpunbordered"></a></h4> +<p>Most of our tables are of a simple design and are unbordered. That is, the + border is either left blank </p> +<p>Not all of our tables have borders. Indeed, most of our tables do not have + borders. The logic that determines your aesthetic decision: the nature of the + information that must be represented in the table. A table needing a header + and column heads will not need the border. The final call, however, is up to + you. For what it is worth, mailing list tables (such as the example below) have + no borders, but informational tables, such as news tables, do. As a rule, avoid + replicating information, e.g., don't have a table title outside the table and + also within the table, as a heading.</p> +<br> +<h4>Sample: The Simple Table<a name="simpunbsample"></a> </h4> +<br> +<p>From the homepage of the <a href="http://udk.openoffice.org/";>UDK</a> Project, + I have taken a sample table that is neatly laid out. The same table, with the + HTML coding shown, is displayed <a href="#simpsamphtml">below</a>. (By the way: + the legacy trend is to center the heading, etc.; I am moving away from that, + and urging all to position the headers on the left.)<br> + <br> +<table cellpadding="4" cellspacing="1" bgcolor="#ffffff" width="100%"> + <tr> + <td colspan="2" bgcolor="#00315A" align="CENTER"><font color="#ffffff" size="2"><b> + Interesting modules outside the UNO Development Kit Project </b> </font></td> + </tr> + <tr> + <th bgcolor="#99CCFF" align="CENTER"><font color="#00315A" size="2"><b> Module + </b> </font> </th> + <th bgcolor="#99CCFF" align="CENTER"><font color="#00315A" size="2"><b>Function + </b></font></th> + </tr> + <td bgcolor="#f0f0f0" valign="top"><code><a href="cpp/ref/sal/index.html">sal</a></code></td> + <td bgcolor="#f0f0f0" valign="top"> The System abstraction layer implements + a basic abstraction of the underlying system. For your components to be system + independent you should you SAL. SAL includes abstractions for thread creation + and synchronization. Mechanisms for process communication and file system + access are also part of this library. Management of libraries and profiles + is also included. Functions for creating and manipulating strings and wide + strings belong to SAL. SAL only exports functions conforming to the c calling + convention. So, it should be suitable to be a system abstraction for any language. + </td> + </tr> + <td bgcolor="#f0f0f0" valign="top"><code><a href="cpp/ref/store/index.html">store</a></code></td> + <td bgcolor="#f0f0f0" valign="top"> This project provides the hierarchical storages + for the component registry. </td> + </tr> +</table> +<br> +<p><b>Particulars</b> +<ul> + <li>Table width: 100%</li> + <li>Cell Pad: 4</li> + <li>Cell Space: 1</li> + <li>Border: Leave blank</li> + <li>Border Color: Leave blank</li> + <li>Background: Leave blank</li> + <li>Cell Color: #fofofo</li> +</ul> +<p>Note how white lines structure the table cells? That's because the <i>page</i> + background is white (#ffffff) but each cell's background is off-white (#fofofo). + You can achieve the same effect by setting the table's background to off-white + (#fofofo) and setting the border to white (#ffffff). The table below, from the + Mirrors page, does just that.</p> +<br> + +<table width="100%" cellpadding="4" bgcolor="#F0F0F0" cellspacing="1" border="1" bordercolor="ffffff"> + <tr> + <td colspan="8" bgcolor="300315A"> + <div align="left"><font size="-1"><b><font color="#ffffff">Current Mirror + Sites</font></b></font></div> + </td> + </tr> + <tr> + <td width="7%" bgcolor="#99ccff"> + <div align="left"><font size="-1"><b>Type</b></font></div> + </td> + <td width="44%" bgcolor="#99ccff"> + <div align="left"><font size="-1"><b>URL</b></font></div> + </td> + <td width="15%" bgcolor="#99ccff"> + <div align="left"><font size="-1"><b>Login</b></font></div> + </td> + <td width="15%" bgcolor="#99ccff"> + <div align="left"><font size="-1"><b>Password</b></font></div> + </td> + <td width="19%" bgcolor="#99ccff"><b><font size="-1">Source</font></b></td> + <td width="19%" bgcolor="#99ccff"><b><font size="-1"> Binaries</font></b></td> + <td width="19%" bgcolor="#99ccff"><b><font size="-1">Solver</font></b></td> + <td width="19%" bgcolor="#99ccff"> + <div align="left"><font size="-1"><b>Maintainer</b></font></div> + </td> + </tr> + <tr> + <td width="7%"> + <div align="left">FTP</div> + </td> + <td width="44%"> + <div align="left"><a href="ftp://openoffice:@ftp.ists.pwr.wroc.pl/"; target="_blank">ftp://openoffice:@ftp.ists.pwr.wroc.pl/</a></div> + </td> + <td width="15%"> + <div align="left">openoffice</div> + </td> + <td width="15%"> + <div align="left"><font face="Courier New, Courier, mono"><</font>none<font face="Courier New, Courier, mono">></font></div> + </td> + <td width="19%">633 (all platforms)</td> + <td width="19%">633 (all platforms)</td> + <td width="19%"> </td> + <td width="19%"><a href="mailto:[email protected]";>Bartek Maruszewski</a></td> + </tr> + <tr> + <td width="7%"> + <div align="left">FTP</div> + </td> + <td width="44%"> + <div align="left"><a href="ftp://borft.student.utwente.nl"; target="_blank">ftp://borft.student.utwente.nl</a></div> + </td> + <td width="15%"><anonymous></td> + <td width="15%"><none></td> + <td width="19%">633, 627, 625, 617</td> + <td colspan="2">633 (Linux, Win32), in 5 MB parts</td> + <td width="19%"><a href="mailto:[email protected]";>Michael Niblett</a>*</td> + </tr> + <tr> + <td width="7%"> + <div align="left">HTTP</div> + </td> + <td width="44%"> + <div align="left"><a href="http://borft.student.utwente.nl/openoffice/";>http://borft.student.utwente.nl/openoffice/</a></div> + </td> + <td width="15%"><n/a></td> + <td width="15%"><none></td> + <td width="19%">633, 627, 625, 617</td> + <td colspan="2">633 (Linux, Win32), in 5 MB parts</td> + <td width="19%"><a href="mailto:[email protected]";>Michael Niblett</a>*</td> + </tr> + <tr> + <td width="7%">HTTP</td> + <td width="44%"><a href="http://sapi.vlsm.org/openoffice/";>http://sapi.vlsm.org/openoffice/</a></td> + <td width="15%"><anonymous></td> + <td width="15%"><none></td> + <td width="19%"> </td> + <td width="19%">633 (ZIP for Win32)</td> + <td width="19%"> </td> + <td width="19%"><a href="mailto:[email protected]";>Rahmat M. Samik-Ibrahim</a></td> + </tr> + <tr> + <td width="7%">FTP</td> + <td width="44%"><a href="ftp://sapi.vlsm.org/openoffice/";>ftp://sapi.vlsm.org/openoffice/</a></td> + <td width="15%"><anonymous></td> + <td width="15%"><none></td> + <td width="19%"> </td> + <td width="19%">633 (ZIP for Win32)</td> + <td width="19%"> </td> + <td width="19%"><a href="mailto:[email protected]";>Rahmat M. Samik-Ibrahim</a></td> + </tr> + <tr> + <td width="7%">FTP</td> + <td width="44%"><a href="ftp://sapi.vlsm.org/openoffice/";>ftp://sapi.vlsm.org/openoffice/win32split/</a></td> + <td width="15%"><anonymous></td> + <td width="15%"><none></td> + <td width="19%"> </td> + <td colspan="2">633 (ZIP for Win32) in 1440000 byte parts</td> + <td width="19%"><a href="mailto:[email protected]";>Rahmat M. Samik-Ibrahim</a></td> + </tr> + <tr> + <td width="7%">HTTP</td> + <td width="44%"><a href="ftp://sapi.vlsm.org/openoffice/";>http://sapi.vlsm.org/openoffice/win32split/</a></td> + <td width="15%"><anonymous></td> + <td width="15%"><none></td> + <td width="19%"> </td> + <td colspan="2">633 (ZIP for Win32) in 1440000 byte parts</td> + <td width="19%"><a href="mailto:[email protected]";>Rahmat M. Samik-Ibrahim</a></td> + </tr> + <tr> + <td width="7%">HTTP</td> + <td width="44%"><a href="http://office.qkaka.com/";>http://office.qkaka.com/</a></td> + <td width="15%"><n/a></td> + <td width="15%"><n/a></td> + <td width="19%"> </td> + <td width="19%">localized 627 zip </td> + <td width="19%"> </td> + <td width="19%"><a href="mailto:[email protected]";>H.Z.</a></td> + </tr> + <tr> + <td width="7%">FTP</td> + <td width="44%"><a href="ftp://ftp.3way.com.hk";>ftp://ftp.3way.com.hk</a></td> + <td width="15%"><anonymous></td> + <td width="15%"><none></td> + <td colspan="3">All current binaries, solver, and source; files in parts.</td> + <td width="19%"><a href="mailto:[email protected]";>Nelson Lau</a></td> + </tr> +</table> +<br> +<p><b>Particulars</b> </p> +<ul> + <li>Table width: 100%</li> + <li>Cell Pad: 4</li> + <li>Cell Space: 1</li> + <li>Border: 1</li> + <li>Border Color: #ffffff</li> + <li>Background: #fofofo</li> +</ul> +<p><b>Note:</b> You can cut 'n' paste this table into any document needing a mailing + list table. (And, by deleting the elements, you can use the table for other + purposes.)</p> +<p><a href="#top">Back to top</a><br> + <br> + <br> +<h4> Simple, Unbordered Table, in HTML<a name="simpsamphtml"></a></h4> +<blockquote> + <table width="100%" bordercolor="#99ccff" cellpadding="2" cellspacing="0" border="1"> + <tr> + <td> <font face="Courier New, Courier, mono" size="-1"><table cellpadding="4" + cellspacing="1" bgcolor="#ffffff" width="100%"></font> + <p><font face="Courier New, Courier, mono" size="-1"><tr> </font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td colspan="2" + bgcolor="#00315A" align="CENTER"><font color="#ffffff" + size="2"><b> </font></p> + <p><font face="Courier New, Courier, mono" size="-1">Interesting modules + outside the UNO Development Kit Project </b> </font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></tr></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><tr> </font></p> + <p><font face="Courier New, Courier, mono" size="-1"><th bgcolor="#99CCFF" + align="CENTER"><font color="#00315A" size="2"><b> + </font></p> + <p><font face="Courier New, Courier, mono" size="-1">Module </b> + </font> </th></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><th bgcolor="#99CCFF" + align="CENTER"><font color="#00315A" size="2"><b>Function + </font></p> + <p><font face="Courier New, Courier, mono" size="-1"></b></font></th></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></tr></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td bgcolor="#f0f0f0" + valign="top"><code><a href="cpp/ref/sal/index.html">sal</a></code></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td bgcolor="#f0f0f0" + valign="top"> The System abstraction layer implements a + basic abstraction of the underlying system. For your components to be + system independent you should you SAL. SAL includes abstractions for + thread creation and synchronization. Mechanisms for process communication + and file system access are also part of this library. Management of + libraries and profiles is also included. Functions for creating and + manipulating strings and wide strings belong to SAL. SAL only exports + functions conforming to the c calling convention. So, it should be suitable + to be a system abstraction for any language. </td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></tr></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td bgcolor="#f0f0f0" + valign="top"><code><a href="cpp/ref/store/index.html">store</a></code></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td bgcolor="#f0f0f0" + valign="top"> This project provides the hierarchical </font></p> + <p><font face="Courier New, Courier, mono" size="-1">storages for the + component registry. </td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></tr></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></table></font></p> + </td> + </tr> + </table> +</blockquote> +<p><a href="#top">Back to top</a><br> + <br> + <br> +<h4>The Nested Table<b><a name="nestedtable"></a></b></h4> +Here is a nested table, also from the homepage. Note: it is unbordered.<br> +<br> +<table width="100%" bordercolor="#99ccff" bgcolor="#ffffff" cellpadding="0" cellspacing="0"> + <tr> + <td height="18" bordercolor="#99ccff" bgcolor="#00315A"><font size="-1" color="#ffffff"><b>Truly + useful news</b></font></td> + </tr> + <tr> + <td> + <table width="100%" border="0" cellpadding="2" height="100%"> + <tr> + <td height="8" width="82%"><font size="-1"> <a href="/about_us/surveyreport.pdf">Community + Survey Report (472KB pdf)</a></font></td> + <td height="8" align="right" width="18%"><font size="-1">3 August</font></td> + </tr> + <tr> + <td height="8" width="82%"><font size="-1"><a href="http://www.openoffice.org/white_papers/index.html";>Roadmap: + the guide to OpenOffice.org</a></font></td> + <td height="8" align="right" width="18%"><font size="-1">9 July</font></td> + </tr> + <tr> + <td height="8" width="82%"><font size="-1"><a href="http://www.openoffice.org/dev_docs/source/download.html";>Build + 633</a></font></td> + <td height="8" align="right" width="18%"><font size="-1">18 June</font></td> + </tr> + <tr> + <td height="12" width="82%"><font size="-1"><a href="http://whiteboard.openoffice.org/screenshots/index.html";>Screenshots</a></font></td> + <td height="12" align="right" width="18%"><font size="-1">9 July</font></td> + </tr> + <tr bordercolor="#99ccff"> + <td width="74%" height="14"><font size="-1"><a href="http://www.openoffice.org/trulyusefulnews.html";>Truly + useful archives (two weeks plus)</a></font></td> + <td width="18%" height="14" align="right" bgcolor="#ffffff"><font size="-1">Always</font></td> + </tr> + </table> + </td> + </tr> +</table> +<br> +<p> A nested table consists of at least two tables, an exterior, bordered table, + and an interior table with invisible borders; this is where the content is. + The basic colors and styles of the nested table are like the simple, un-nested + table. The advantage of nesting tables lies, then, in that you can create a + bordered table with cell demarcators that differ from the exteriors. This can + be quite useful.</p> +<br> +<h4>Table Formatting, Exterior, General<a name="extformatting1"></a> </h4> +<ul> + <li>Width: 100% </li> + <li>Height: Leave blank; in pixels </li> + <li>Cell pad: 0</li> + <li>Cell space: 0</li> + <li>Align: Default</li> +</ul> +<p><b>Note</b>: The border for the above table is not set; you can, for your particular + table, however, set it to "1" and make the exterior color light blue: + "#99CCFF. </p> +<br> +<h4>Table Formatting, Exterior, Particulars<a name="extformatting2"></a> </h4> +<blockquote> + <p>This external table includes a row for the header. </p> +</blockquote> +<ul> + <ul> + <li>Header text: White (#ffffff), bold, no formatting. Size: you can alter + this by shrinking it to -1; that call is up to you. </li> + <li>Heading background: Dark blue (#00315A)<br> + </li> + </ul> +</ul> +<p><a href="#top">Back to top</a><br> + <br> + <br> +<h4>Table Formatting: Interior Table<a name="formattingint1"></a> </h4> +<p>The interior table is a regular table with the border set to 0 or left blank. + This way, you can organize information in a tabular fashion without having the + borders of the cells interrupt your aesthetic. The rule is:</p> +<ol> + <li>Make your table, setting border = 0 or leave it blank. (There is a difference + in the settings. Play around a little; I prefer to set the border to blank.)</li> + <li>Position the interior table within the exterior table and set the width + = 100%; leave the height blank, in pixels. The interior table should map perfectly + to the limits of the exterior table. </li> + <li>You can also do other things to accomplish the same effect, such as coloring + the cells, etc. Experiment; it's a pleasant way to use up time<br> + <br> + </li> +</ol> +<h4>Interior Table Particulars<a name="inttableparts"></a></h4> +<blockquote> + <p>The interior table above has the following characteristics:</p> +</blockquote> +<ul> + <ul> + <li>Border = 0</li> + <li>Cell Pad = 2 (you can raise it; lowering it is not recommended)</li> + <li>Cell Space = 0 or leave blank</li> + <li>Content background: Pale blue (#fofofo) (as will all tables)</li> + <li>Content text: Black, default font, no formatting. Size: you can shrink + the size to -1; that call is up to you.</li> + </ul> +</ul> +<p><a href="#top">Back to top</a><br> + <br> + <br> +<h4><font color="#000000">Here is what this table looks like in HTML<a name="inttableHTML"></a></font></h4> +<blockquote> + <table width="100%" bordercolor="#99ccff" cellpadding="2" cellspacing="0" border="1"> + <tr> + <td> + <p><font face="Courier New, Courier, mono" size="-1"><table width="100%" + bordercolor="#99ccff" bgcolor="#ffffff" cellpadding="0" + cellspacing="0"></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><tr> </font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td height="18" + bordercolor="#99ccff" bgcolor="#00315A"><font + size="-1" color="#ffffff"><b>Truly </font></p> + <p><font face="Courier New, Courier, mono" size="-1">useful news</b></font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></tr></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><tr> </font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td> </font></p> + <p><font face="Courier New, Courier, mono" size="-1"><table width="100%" + border="0" cellpadding="2" height="100%"></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><tr> </font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td height="8" + width="82%"><font size="-1"> <a href="/about_us/surveyreport.pdf">Community + Survey Report (472KB pdf)</a></font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td height="8" + align="right" width="18%"><font size="-1">3 + August</font></td> </font></p> + <p><font face="Courier New, Courier, mono" size="-1"> </tr></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><tr> </font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td height="8" + width="82%"><font size="-1"><a href="http://www.openoffice.org/white_papers/index.html">Roadmap: + the guide to OpenOffice.org</a></font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td height="8" + align="right" width="18%"><font size="-1">9 + July</font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></tr></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><tr> </font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td height="8" + width="82%"><font size="-1"><a href="http://www.openoffice.org/dev_docs/source/download.html">Build + 633</a></font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td height="8" + align="right" width="18%"><font size="-1">18 + June</font></td> </tr> </font></p> + <p><font face="Courier New, Courier, mono" size="-1"><tr> <td + height="12" width="82%"><font size="-1"><a + href="http://whiteboard.openoffice.org/screenshots/index.html">Screenshots</a></font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td height="12" + align="right" width="18%"><font size="-1">9 + July</font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></tr></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><tr bordercolor="#99ccff"> + </font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td width="74%" + height="14"><font size="-1"><a href="http://www.openoffice.org/trulyusefulnews.html">Truly + useful archives (two weeks plus)</a></font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"><td width="18%" + height="14" align="right" bgcolor="#ffffff"><font + size="-1">Always</font></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></tr></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></table></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></td></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></tr></font></p> + <p><font face="Courier New, Courier, mono" size="-1"></table></font></p> + </td> + </tr> + </table> +</blockquote> +<br> +<p><a href="#top">Back to top</a><br> + <br> + <br> +<h4>Sample Nested Table <a name="sampnestedtable"></a></h4> +<p>Here is a sample nested table. It may be easier to add content to the interior + table first, then cut and paste the completed interior table into the exterior + table shell. So, I've split them up.</p> +<table width="100%" border="1" cellpadding="0" bordercolor="#99ccff" cellspacing="0"> + <tr bgcolor="#ffffff" bordercolor="#99ccff"> + <td height="16" bordercolor="#99ccff" bgcolor="#00315A"><font size="-1" color="#ffffff"><b>[Your + heading here]</b></font></td> + </tr> + <tr> + <td bgcolor="#ffffff"> </td> + </tr> +</table> +<br> +<table width="100%" border="0" bordercolor="#99ccff" cellpadding="2"> + <tr> + <td height="12" width="82%"><font size="-1"><a href="http://www.openoffice.org/about_us/communitypage.html"; target="_blank">[content]</a></font></td> + </tr> + <tr> + <td height="12" width="82%"><a href="http://www.openoffice.org/mirrors.html";><font size="-1">[content]</font></a></td> + </tr> + <tr> + <td height="12" width="82%"><font size="-1" color="#666699"><a href="http://www.openoffice.org/MSFilters.html";>[content]</a></font></td> + </tr> +</table> +<br> +<p><a href="#top">Back to top</a><br> +<hr> +<h3>Conclusion<a name="conclusion"></a></h3> +<h4>Another style guide<a name="otherguide"></a></h4> +<p>Todd Fahner has created a brief but beautifully clear <a href="http://collabnet.cleverchimp.com/notes/prodstandards/"; target="_blank">style + guide</a> that also explains how to use style sheets. It is still a work in + progress, so be sure to check back on it periodically, but I heartily recommend + it.</p> +<p>And, if you have any questions, or wish to add (reasonable) material, please + let me know: <a href="mailto:[email protected]";>[email protected]</a>.</p> +</body> +</html> diff --git a/content/lingucomponent/thes_dic.html b/content/lingucomponent/thes_dic.html new file mode 100644 index 0000000..165e5f1 --- /dev/null +++ b/content/lingucomponent/thes_dic.html @@ -0,0 +1,10 @@ +<html><head> + <title>Thesaurus Dictionaries</title> + <meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> + </head> + <body> + <a href="download_dictionary.html">return to Table of Contents</a><br /> + + <p><a href="http://wiki.services.openoffice.org/wiki/Dictionaries";>This page has been moved to the Wiki</a></p> + </body> +</html> diff --git a/content/lingucomponent/thesaurus.html b/content/lingucomponent/thesaurus.html new file mode 100755 index 0000000..cee868b --- /dev/null +++ b/content/lingucomponent/thesaurus.html @@ -0,0 +1,50 @@ +<html><head> +<title>Thesaurus Development</title> +<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=UTF-8"> +</head> +<body> + <h2>Lingucomponent Sub-Project: Thesaurus Development </h2> + + <p>The goal of this project is to improve existing thesauri for OpenOffice.org + and to create new thesauri for languages that don't have one yet.</p> + + <p>This project started by searching for and finding a synonym list for + English (US) that was compatible with the OpenOffice.org licensing and + then using that list and some simple software to develop a thesaurus for + OpenOffice.org 1.x. OpenOffice.org 2.x now uses a thesaurus automatically + built from the data in <a href="http://wordnet.princeton.edu";>WordNet</a>. + The internal file format has also changed to a text-based one.</p> + + <h4>TODO</h4> + + <ul> + <li><a href="http://lingucomponent.openoffice.org/issues/buglist.cgi?Submit+query=Submit+query&component=lingucomponent&subcomponent=thesaurus&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short [...] + the list of all open thesaurus issues</a></li> + <li>Create new thesauri (see below)</li> + </ul> + + <h4>Downloads</h4> + + <ul> + <li><a href="MyThes-1.zip">MyThes-1.zip (4,5MB)</a> - standalone version of the MyThes thesaurus code. + This includes a thesaurus for en_US in its new format for OOo 2.0 (but not yet the WordNet-based + thesaurus).</li> + <li><a href="http://www.danielnaber.de/wn2ooo";>wn2ooo</a>, the script used to create the OOo + thesaurus from WordNet data.</li> + </ul> + + <h4>Creating a new thesaurus</h4> + + <p>If you are willing to maintain a website to collect and coordinate a community + developed synonym list for any language we need your help. Please send an e-mail to + [email protected] listing your skills and interests in being + involved in this project. A web-based software for building a new thesaurus is + <a href="http://www.openthesaurus.de";>OpenThesaurus</a>, which is already successfully + used to maintain the German, Polish, and other thesauri. All you need is some knowledge of + MySQL and a Java-enabled server space to run your own version of OpenThesaurus.</p> + + <hr /> + + <br /> +</html> +</body>
