From: H.G.Muller <hgm@hgm-xboard.(none)>
Date: Tue, 8 Nov 2016 21:01:16 +0000 (+0100)
Subject: Update README file (changelog) and man page
X-Git-Tag: v2.3~7
X-Git-Url: http://winboard.nl/cgi-bin?p=uci2wb.git;a=commitdiff_plain;h=12cceb578f4644d57904c3797d0c52acf415c705;hp=aee345a6b5d8582e826af026fad391d477db7272

Update README file (changelog) and man page
---

diff --git a/README.txt b/README.txt
index 2de28a4..41e2d80 100644
--- a/README.txt
+++ b/README.txt
@@ -50,6 +50,11 @@ H.G.Muller
 
 Change log:
 
+8/11/2016 2.3
+Implement handling of 'UCI_Variant' option for variant announcement and selection
+Pass 'info string variant' line as 'setup' command to allow engine-defined variants
+Set 'UCI_Opponent' option in accordance with CECP 'name' and 'computer' commands
+
 22/11/2016 2.2
 Use USI gameover command to relay game result
 Handle USI win claims
diff --git a/uci2wb.pod b/uci2wb.pod
index 2ceb94c..5ccd18e 100644
--- a/uci2wb.pod
+++ b/uci2wb.pod
@@ -44,8 +44,9 @@ instead of the standard KxR notation.
 =item B<-var <variant>>
 
 Forces uci2wb to announce to the GUI it supports (only) the specified variant.
-There is no standardized way for UxI engines to announce what they can play,
-so if these are not the standard variants implied by the protocol choice,
+Although a UCI_Variant option has been proposed as a way for UxI engines to announce what they can play,
+(and is supported by uci2wb), not many engines implement this.
+So if these are not the standard variants implied by the protocol choice,
 (but, f.e. seirawan or 6x6+6_shogi) it has to be configured on the
 uci2wb command line through this option.