From: Claudio F Filho <[EMAIL PROTECTED]> Date: Thu, 11 Aug 2005 09:51:53 -0400
Hi, > > How are the translated licenses texts added to the languagepacks? Or should > > they be added as issues? > > I'm talking about files LICENSE_<ab-CD> and LICENSE_<ab-CD>.html. Thanks. > Is a good idea, but the *bigger* problem is that FSF not recognizes the > (unofficial) translations. Is a old fight between many contries that the the file LICENSE_?? doesn't contain the licenses under which OOo is licensed (LGPL/SISSL) but only contains reference to them: --- cut here --- You may only copy and distribute this program consistent with the requirements and distribute this Program consistent with the requirements of either the GNU General Public License (GPL) and GNU Lesser General Public License (LGPL) or the Sun Industry Standards Source License (SISSL), respectively, depending on whether you elected to obtain access to this program via the GPL/LGPL Option or the SISSL Option. Copies of the GPL, LGPL and SISSL licenses can be found http://www.openoffice.org/project/www/license.html ------------------------------------ Third Party Code. Additional copyright notices and license terms applicable to portions of the Software are set forth in the THIRDPARTYLICENSEREADME.html file. ------------------------------------ Copyright 2002,2005 Sun Microsystems, Inc. --- cut here --- I think this is perfectly acceptable to be translated... -- Pavel Janík # Basic IBM dingbats, some of which will never have a purpose clear # to mankind -- 2.4.0 drivers/char/cp437.uni --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
