diff --git a/CMakeLists.txt b/CMakeLists.txt
index 15ad178..ff66b8e 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -1,5 +1,5 @@
 cmake_minimum_required(VERSION 3.9)
-project(collocatordb VERSION 1.7.0 DESCRIPTION "Storing and retrieving collocation counts based on RocksDB")
+project(collocatordb VERSION 1.8.0 DESCRIPTION "Storing and retrieving collocation counts based on RocksDB")
 set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -g -fno-rtti")
 set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -g")
 
diff --git a/README.md b/README.md
index a5c5edb..fd4916f 100644
--- a/README.md
+++ b/README.md
@@ -193,6 +193,26 @@
 
 ## Changes
 
+* v1.8.0 (2026-09-04)
+  * `logDice` and `dice` are computed as Rychlý (2008) defines them,
+    `14 + log2(2*f12/(f1+f2))`, without the window size factor that used to
+    multiply `f1`. Adding `f1 * window_size`, a count of window positions, to
+    `f2`, a count of word tokens, mixed units and made the coefficient
+    asymmetric, and since that term dominated the denominator for a frequent
+    node, it penalized rare collocates. Values are higher than before, by up to
+    `log2(window_size)`, and comparable to those of other tools such as Sketch
+    Engine
+  * `ldaf` is unchanged. It is the auto focus score, whose denominator grows
+    with the width of the selected window, which is what makes it sensitive to
+    how concentrated a pair is and thus orders collocates well. It lives in
+    `ca_focus_score()` now, so that it no longer looks like a variant of
+    `logDice`, from which it is deliberately different and on another scale
+  * the first collocate of every query is scored with the right window size.
+    `true_window_size` counts the positions a pair was observed in, but started
+    at one while the first key of the iteration already incremented it, so that
+    the first collocate came out with a window one position too wide, and thus
+    with `pmi`, `npmi`, `md`, `lfmd` and `llr` too low, by up to one bit
+
 * v1.7.0 (2026-08-09)
   * single-key increments are collected in a batch and written in one rocksdb
     write per batch, instead of one write per increment. The batch size can be