Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Jul 2005 18:14:13 +0200
From:      Jeremie Le Hen <jeremie@le-hen.org>
To:        Mark Linimon <linimon@lonesome.com>
Cc:        freebsd-doc@FreeBSD.org, Jeremie Le Hen <jeremie@le-hen.org>
Subject:   Re: developpers-handbook: tools-intro is incorrect
Message-ID:  <20050727161412.GT1610@obiwan.tataz.chchile.org>
In-Reply-To: <20050727143941.GA7172@soaustin.net>
References:  <20050727114821.GS1610@obiwan.tataz.chchile.org> <20050727143941.GA7172@soaustin.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--0eh6TmSyL6TZE2Uz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi Mark,

On Wed, Jul 27, 2005 at 09:39:41AM -0500, Mark Linimon wrote:
> On Wed, Jul 27, 2005 at 01:48:21PM +0200, Jeremie Le Hen wrote:
> > Note that the patch is a little bit fat regarding of what it's
> > supposed to do, because I needed to redo line wrapping.
> 
> Well, that's not the standard way things are done in -doc-land :-)
> The problem is that multiline changes make life harder for the translators
> since it makes it less obvious what has changed.
> 
> So the correct change to e.g. remove 7 words (like your first one) leaves
> a short line and that's acceptable.  If desired, a later change can more
> the whitespace around, but if so that one gets done with "translators
> please ignore".
> 
> In any case since whitespace in the document doesn't affect the rendering
> it is more often than not left that way, especially for short lines.  It's
> also less CVS churn that way.

Sorry, I didn't know that but I could have guessed it myself, since this
way is far more easier to handle modifications.

I attached two patches with this mail.  The first one removes the
innuendo saying that Perl still belongs to FreeBSD source tree.

The second one improves the advocacy for FreeBSD by giving some examples
of common compilers and interpreters available from ports.

Feel free to use whatever you want, that's just my 2 cents.

Thank you for the documentation effort.
Regards,
-- 
Jeremie Le Hen
< jeremie at le-hen dot org >< ttz at chchile dot org >

--0eh6TmSyL6TZE2Uz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="devtool_noperl.patch"

Index: chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml,v
retrieving revision 1.44
diff -u -p -u -r1.44 chapter.sgml
--- chapter.sgml	18 Mar 2005 02:16:39 -0000	1.44
+++ chapter.sgml	27 Jul 2005 15:59:03 -0000
@@ -36,7 +36,7 @@
 
     <para>FreeBSD offers an excellent development environment.
       Compilers for C, C++, and Fortran and an assembler come with the
-      basic system, not to mention a Perl interpreter and classic &unix;
+      basic system, not to mention classic &unix;
       tools such as <command>sed</command> and <command>awk</command>.
       If that is not enough, there are many more compilers and
       interpreters in the Ports collection.  FreeBSD is very

--0eh6TmSyL6TZE2Uz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="devtool_portsadvocacy.patch"

Index: chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml,v
retrieving revision 1.45
diff -u -p -u -r1.45 chapter.sgml
--- chapter.sgml	18 Mar 2005 02:16:39 -0000	1.45
+++ chapter.sgml	27 Jul 2005 16:11:32 -0000
@@ -39,7 +39,9 @@
       basic system, not to mention classic &unix;
       tools such as <command>sed</command> and <command>awk</command>.
       If that is not enough, there are many more compilers and
-      interpreters in the Ports collection.  FreeBSD is very
+      interpreters in the Ports collection, like Objective Caml and
+      Pascal compilers as well as Perl, Python and Ruby interpreters.
+      FreeBSD is very
       compatible with standards such as <acronym>&posix;</acronym> and
       <acronym>ANSI</acronym> C, as well with its own BSD heritage, so
       it is possible to write applications that will compile and run

--0eh6TmSyL6TZE2Uz--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050727161412.GT1610>