[brlcad-commits] SF.net SVN: brlcad:[51043] brlcad/trunk/src/conv/asc/g2asc.1

[<tbr...@us...>]

Revision: 51043
          http://brlcad.svn.sourceforge.net/brlcad/?rev=51043&view=rev
Author:   tbrowder2
Date:     2012-06-09 11:27:20 +0000 (Sat, 09 Jun 2012)
Log Message:
-----------
make man page references consistent with their parens, change rsh to ssh, tidy synopsis format

Modified Paths:
--------------
    brlcad/trunk/src/conv/asc/g2asc.1

Modified: brlcad/trunk/src/conv/asc/g2asc.1
===================================================================
--- brlcad/trunk/src/conv/asc/g2asc.1	2012-06-09 11:19:51 UTC (rev 51042)
+++ brlcad/trunk/src/conv/asc/g2asc.1	2012-06-09 11:27:20 UTC (rev 51043)
@@ -50,7 +50,7 @@
 .SH DESCRIPTION
 The local machine binary representation
 of an
-.IR mged (1)
+.IR mged(1)
 database is inherently non-portable.
 .I g2asc
 and
@@ -72,7 +72,7 @@
 and
 .I asc2g
 are typically used to convert binary
-.IR mged (1)
+.IR mged(1)
 files to an ASCII format.  This was traditionally performed so the
 files could be transferred to another machine in a portable format.
 Although no longer necessary for the current binary geometry database
@@ -80,17 +80,17 @@
 process is still necessary if manipulating older ("v4" format)
 geometry database files.  On the local machine, files are converted to
 ASCII using
-.IR g2asc (1),
+.IR g2asc(1),
 then transferred to the remote machine.  On the remote machine, the files
 are then converted back to the binary representation for that machine using
-.IR asc2g (1).
+.IR asc2g(1).
 .SH EXAMPLE
 .I
-g2asc  file.g  file.asc
+g2asc file.g file.asc
 .br
 scp file.asc remote:file.asc
 .br
-rsh remote "asc2g  file.asc  file.g"
+ssh remote "asc2g file.asc file.g"
 .SH DIAGNOSTICS
 The diagnostics are intended to be self-explanatory.
 .SH SEE ALSO

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.