File xsd-3.3.0-xsdcxx-rename.patch of Package xsd

File xsd-3.3.0-xsdcxx-rename.patch of Package xsd (Revision 07a9d029835ebc71f14a8d923f31265d)

Currently displaying revision 07a9d029835ebc71f14a8d923f31265d , Show latest

diff -up xsd/documentation/xsd.1.rename xsd/documentation/xsd.1
--- xsd/documentation/xsd.1.rename	2010-06-20 15:45:31.000000000 +0300
+++ xsd/documentation/xsd.1	2010-06-20 15:46:24.000000000 +0300
@@ -1,16 +1,16 @@
 .\" Process this file with
-.\" groff -man -Tascii xsd.1
+.\" groff -man -Tascii xsdcxx.1
 .\"
 .TH XSD 1 "April 2010" "XSD 3.3.0"
 .SH NAME
-xsd \- W3C XML Schema to C++ Compiler
+xsdcxx \- W3C XML Schema to C++ Compiler
 .\"
 .\"
 .\"
 .\"--------------------------------------------------------------------
 .SH SYNOPSIS
 .\"--------------------------------------------------------------------
-.B xsd
+.B xsdcxx
 .I command
 .B [
 .I options
@@ -20,19 +20,19 @@ xsd \- W3C XML Schema to C++ Compiler
 .I file
 .B ...]
 .in
-.B xsd help
+.B xsdcxx help
 .B [
 .I command
 .B ]
 .in
-.B xsd version
+.B xsdcxx version
 .\"
 .\"
 .\"
 .\"--------------------------------------------------------------------
 .SH DESCRIPTION
 .\"--------------------------------------------------------------------
-.B xsd
+.B xsdcxx
 generates vocabulary-specific, statically-typed C++ mapping from W3C XML
 Schema definitions. Particular mapping to produce is selected by a
 .IR command .
@@ -96,7 +96,7 @@ Print usage information and exit. Use
 .PP
 .RS
 .RS 3
-.B xsd help
+.B xsdcxx help
 .I command
 .RE
 .PP
@@ -203,7 +203,7 @@ For example, if you have file
 with namespace
 .B http://example.com/hello
 and you run
-.B xsd
+.B xsdcxx
 on this file, then the string in question will be:
 
 .B hello.xsd. http://example.com/hello
@@ -1877,7 +1877,7 @@ option. With this approach you don't nee
 .\"
 .SH DIAGNOSTICS
 If the input file is not a valid W3C XML Schema definition,
-.B xsd
+.B xsdcxx
 will issue diagnostic messages to
 .B STDERR
 and exit with non-zero exit code.
diff -up xsd/documentation/xsd.xhtml.rename xsd/documentation/xsd.xhtml
--- xsd/documentation/xsd.xhtml.rename	2010-06-20 15:47:29.000000000 +0300
+++ xsd/documentation/xsd.xhtml	2010-06-20 15:47:30.000000000 +0300
@@ -50,19 +50,19 @@
 
 <h1>NAME</h1>
 
- xsd - W3C XML Schema to C++ Compiler
+ xsdcxx - W3C XML Schema to C++ Compiler
 
 <h1>SYNOPSIS</h1>
 
 <dl id="synopsis">
- <dt><code>xsd command [options] file [file ...]</code></dt>
- <dt><code>xsd help [command]</code></dt>
- <dt><code>xsd version</code></dt>
+ <dt><code>xsdcxx command [options] file [file ...]</code></dt>
+ <dt><code>xsdcxx help [command]</code></dt>
+ <dt><code>xsdcxx version</code></dt>
 </dl>
 
 <h1>DESCRIPTION</h1>
 
- <code>xsd</code> generates vocabulary-specific, statically-typed
+ <code>xsdcxx</code> generates vocabulary-specific, statically-typed
 C++ mapping from W3C XML Schema definitions. Particular mapping to
 produce is selected by a <code>command</code>. Each mapping has
 a number of mapping-specific <code>options</code> that should
@@ -104,7 +104,7 @@
 
 <dt><code>help</code></dt>
 <dd>Print usage information and exit. Use
- <code>xsd help command</code>
+ <code>xsdcxx help command</code>
 for command-specific help.
 </dd>
 
@@ -174,7 +174,7 @@
 
 For example, if you have file <code>hello.xsd</code>
 with namespace <code>http://example.com/hello</code> and you run
- <code>xsd</code> on this file, then the string in question
+ <code>xsdcxx</code> on this file, then the string in question
 will be:
 
 <code>hello.xsd. http://example.com/hello</code>
@@ -1575,7 +1575,7 @@ namespace .*
 <h1>DIAGNOSTICS</h1>
 
 If the input file is not a valid W3C XML Schema definition,
- <code>xsd</code> will issue diagnostic messages to STDERR
+ <code>xsdcxx</code> will issue diagnostic messages to STDERR
 and exit with non-zero exit code.
 
 <h1>BUGS</h1>