On Tue, Mar 02, 1999 at 11:27:04AM -0600, Alejandro Aguilar Sierra wrote: > On Tue, 2 Mar 1999, Amir Karger wrote: > > > Alejandro, Asger, and other web-access folks: have you looked at the > > translation.php3 I sent in? > > I did but for some reason it doesn't work in my netscape (but it does in > my lynx): > > http://www.devel.lyx.org/translation.php3 > > What could be the problem? > Oops. I forget </table> and several </tr>'s. Here's a new version. The table is terrible; I'm sure an HTML-clued person will want to add paddings etc. -Amir
<? // What's the title of the page? $title = "Internationalization Effort"; // What's the short name of the page in the navigation bar? $item="Non-English"; // Who is the author? $author="[EMAIL PROTECTED]"; // What's the URL to this page? $this="translation.php3"; include("start.php3"); ?> <p> <img border=0 width=117 height=87 src="lyx_small3.gif" align=right> The LyX program and its documentation are developed in English. However, many LyX developers and users write or speak other languages. Contributions for LyX internationalization are always welcome. There are several sorts of contributions you could make, which are described below. Note that the main documentation for this can be found in the "Customization" document accessible from the LyX Help menu.</p> <p> This document may not always be up to date. Check the CVS distribution to find the latest files. <h2>Typing</h2> There are two different ways to make typing in different languages easier. <h3>Keyboard maps</h3> Keyboard maps allow users to type in various languages. Maps currently exist for the following languages/styles: <ul> <li> American (english with accents) <li> Brazil <li>Czech <li>European (various European languages) <li>French <li>German <li>Greek <li>Magyar <li>Polish <li>Portugese <li>Romanian <li>Swiss French <li>Swiss German <li>Slovak <li>Slovene <li>Transilvanian <li>Turkish </ul> To make a new kmap, you just have to create a <code>.kmap</code> file. Look at the files in the <code>lib/kbd</code> directory in the LyX distribution for examples.</p> <h3>Key bindings</h3> Key bindings allow you to use shortcuts that make sense in a different language. Bindings currently exist for: <ul> <li> French <li> German <li> Hungarian <li> Swedish </ul> To make a new binding, you need to create a <code>.bind</code> file. Look at the files in the <code>lib/bind</code> directory in the LyX distribution for examples. <hr> <h2>Menus and commands</h2> Translating the user interface into another language allows users who don't speak English to be much more comfortable with LyX. By "user interface" we mean both the menu items and the LyX error messages. If an installation is correctly configured, the correct language should automatically be loaded. LyX uses GNU <code>gettext</code> for this purpose.</p> <p> Translations currently exist for the following languages: <ul> <li>Czech <li>Danish <li>German <li>Spanish <li>Finnish <li>French <li>Hungarian <li>Dutch <li>Norwegian <li>Polish <li>Russian <li>Slovenian <li>Swedish <li>Turkish </ul> To make a new translation, you need to create a <code>.po</code> file. Check out the <code>po</code> directory in the LyX distribution for examples. <hr> <h2>Documentation</h2> One of the most useful contributions you can make to the LyX development effort is translating the documentation. Of course, there is a lot of documentation, so you might want some help. Here are the currently known translation efforts, with links to the head (or only) translator. <table border> <tr> <td> Language </td> <td> Status </td> </tr> <tr> <td> <a href="http://www.uni-sw.gwdg.de/~pit/LyX/LyX_de.html">German</a></td> <td> Mostly done </td> </tr> <td> <a href="http://home1.2.sbbs.se/pjp/lyx-sv.html">Swedish</a></td> <td> Intro, Tutorial </td> </tr> <td> <a href="http://lubr.regionet.cz/">Czech</a></td> <td> Tutorial </td> </tr> </table> It's probably best to translate the Tutorial first. That document will be seen by the most new users (hopefully!) and is most likely to be read from start to finish. Few people will read the whole User Guide, and it may be easier to look up one detail in English than to read a whole manual. Of course, the eventual goal is to translate everything.</p> <p> Other good files to translate at the beginning are the Introduction (Intro.lyx) and the splash document <code>lib/examples/splash.lyx</code>. These are very short files, so they'll be easy to translate quickly.</p> <p> For each document, you should translate <code>foo.lyx</code> to <code>xx_foo.lyx</code>, where <code>xx</code> is the two-letter language code. The German version of the splash page, for example, would be <code>lib/examples/de_splash.lyx</code>. <? include("end.php3"); ?>