Rebrand the source as TigerVNC. It is my hope that this patch is

minimal but still complete. The rebranding was done using a script:

find trunk -name .svn -prune -o -type f -exec rep.sh \{\} \;
pushd trunk
svn revert doc/TODO doc/registered-codes.txt doc/ft-protocol-problems.txt doc/rfbtight.tex
perl -pi -e 's|tightvnc|tigervnc|g' unix/configure.ac win/configure.ac unix/README

With rep.sh looking like:

perl -pi -e 's|TightVNC|TigerVNC|g' "$@"
perl -pi -e 's|www\.tightvnc\.com/bugs\.html|www\.tigervnc\.org|g' "$@"
perl -pi -e 's|www\.tightvnc\.com|www\.tigervnc\.org|g' "$@"
perl -pi -e 's|devteam\@tightvnc\.com|tigervnc-devel\@lists\.sourceforge\.net|g' "$@"
perl -pi -e 's|TigerVNC Team|TightVNC Team|g' "$@"
perl -pi -e 's|TigerVNC Group|TightVNC Group|g' "$@"
perl -pi -e 's|TigerVNC protocol|TightVNC protocol|g' "$@"
perl -pi -e 's|TigerVNC-specific|TightVNC-specific|g' "$@"
perl -pi -e 's|Vendor signatures: standard VNC/RealVNC, TridiaVNC, and TigerVNC|Vendor signatures: standard VNC/RealVNC, TridiaVNC, and TightVNC|g' "$@"
perl -pi -e 's|TigerVNC vendor|TightVNC vendor|g' "$@"
perl -pi -e 's|TigerVNC extension|TightVNC extension|g' "$@"
perl -pi -e 's|protocolTigerVNC|protocolTightVNC|g' "$@"
perl -pi -e 's|TigerVNC additions were|TightVNC additions were|g' "$@"
perl -pi -e 's|TigerVNC 1\.2|TightVNC 1\.2|g' "$@"
perl -pi -e 's|TigerVNC authentication type|TightVNC authentication type|g' "$@"



git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@3621 3789f03b-4d11-0410-bbf8-ca57d06f2519

1 files changed, 6 insertions, 6 deletions

diff --git a/unix/x0vncserver/x0vncserver.man b/unix/x0vncserver/x0vncserver.man
index 91bb956b..e98030ef 100644
--- a/unix/x0vncserver/x0vncserver.man
+++ b/unix/x0vncserver/x0vncserver.man
@@ -1,6 +1,6 @@
-.TH X0VNCSERVER 1 "Dec 23, 2008" "TightVNC" "TightVNC Manual"
+.TH X0VNCSERVER 1 "Dec 23, 2008" "TigerVNC" "TigerVNC Manual"
 .SH NAME
-x0vncserver \- TightVNC Server for X displays
+x0vncserver \- TigerVNC Server for X displays
 .SH SYNOPSIS
 .B x0vncserver
 .RI [ options ]
@@ -8,8 +8,8 @@ x0vncserver \- TightVNC Server for X displays
 .B x0vncserver -version
 .SH DESCRIPTION
 .B x0vncserver
-is a TightVNC Server which makes any X display remotely accessible via VNC,
-TightVNC or compatible viewers.  Unlike \fBXvnc\fP(1), it does not create a
+is a TigerVNC Server which makes any X display remotely accessible via VNC,
+TigerVNC or compatible viewers.  Unlike \fBXvnc\fP(1), it does not create a
 virtual display.  Instead, it just shares an existing X server (typically,
 that one connected to the physical screen).
 .SH OPTIONS
@@ -148,7 +148,7 @@ right and/or from the bottom of the screen.  Offsets are optional, +0+0 is
 assumed by default (top left corner).  Video area is not checked for actual
 changes, it is assumed to be changing continuously and is sent in each screen
 update.  Normally, video area is compressed with JPEG (if allowed by the
-client).  Note that this setting can be overriden by TightVNC clients
+client).  Note that this setting can be overriden by TigerVNC clients
 supporting VideoRectangleSelection protocol extension.  In other words,
 clients may choose video selection themselves, but if they do not, then the
 \fBVideoArea\fP parameter will take effect.  If the argument is empty, no
@@ -226,6 +226,6 @@ responding.  Default is 20000.
 .BR Xvnc (1),
 .BR vncpasswd (1),
 .br
-http://www.tightvnc.com/
+http://www.tigervnc.org/
 .SH AUTHOR
 This manual page was written by Constantin Kaplinsky.