From owner-cvs-doc@FreeBSD.ORG Mon Dec 8 06:07:53 2008 Return-Path: Delivered-To: cvs-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A11A106564A; Mon, 8 Dec 2008 06:07:53 +0000 (UTC) (envelope-from manolis@FreeBSD.org) Received: from kane.otenet.gr (kane.otenet.gr [83.235.67.31]) by mx1.freebsd.org (Postfix) with ESMTP id 653058FC1D; Mon, 8 Dec 2008 06:07:52 +0000 (UTC) (envelope-from manolis@FreeBSD.org) Received: from atlantis.dyndns.org (athedsl-4377730.home.otenet.gr [79.130.60.114]) by kane.otenet.gr (8.13.8/8.13.8/Debian-3) with ESMTP id mB867nvW004962; Mon, 8 Dec 2008 08:07:50 +0200 Message-ID: <493CB9B5.3060002@FreeBSD.org> Date: Mon, 08 Dec 2008 08:07:49 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.17 (X11/20081011) MIME-Version: 1.0 To: Giorgos Keramidas References: <200812080310.mB83AsFH024922@repoman.freebsd.org> In-Reply-To: <200812080310.mB83AsFH024922@repoman.freebsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-7 Content-Transfer-Encoding: 7bit Cc: doc-committers@FreeBSD.org, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: doc/el_GR.ISO8859-7/articles/compiz-fusion article.sgml doc/el_GR.ISO8859-7/articles/cvs-freebsd article.sgml doc/el_GR.ISO8859-7/articles/dialup-firewall article.sgml doc/el_GR.ISO8859-7/articles/explaining-bsd article.sgml doc/el_GR.ISO8859-7/articles/formatting-media article.sgml doc/el_GR.ISO8859-7/articles/freebsd-questions article.sgml ... X-BeenThere: cvs-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the doc and www trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2008 06:07:53 -0000 Giorgos Keramidas wrote: > Log: > When editing or merging these files with UTF-8 as the default > character set, they may be replaced/re-encoded. Try to inhibit > auto-conversion to UTF-8, until we (inevitably?) switch to > el_GR.UTF-8 some time in the future. > > Guess switching to UTF8 will also solve our PDF creation issues?