From: Sergey Matveev <stargrave@stargrave.org>
Date: Sat, 5 Oct 2024 15:03:17 +0000 (+0300)
Subject: Link to Git
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=0bddcaaaeeea81924196fa79c96c3dc1243f35fed686a78dfefba1fe300a756b;p=keks.git

Link to Git
---

diff --git a/spec/encoding/blob.texi b/spec/encoding/blob.texi
index 68f2a4d..c0c2d6b 100644
--- a/spec/encoding/blob.texi
+++ b/spec/encoding/blob.texi
@@ -1,4 +1,5 @@
 @node Blobs
+@cindex BLOB
 @section Blobs
 
 Blob (binary large object) allows you to transfer binary data in chunks,
diff --git a/spec/encoding/float.texi b/spec/encoding/float.texi
index 6ba4850..98fd3ef 100644
--- a/spec/encoding/float.texi
+++ b/spec/encoding/float.texi
@@ -1,4 +1,9 @@
 @node Floats
+@cindex FLOAT16
+@cindex FLOAT32
+@cindex FLOAT64
+@cindex FLOAT128
+@cindex FLOAT256
 @section Floats
 
 Floats are encoded in IEEE 754 binary formats: half, single, double,
diff --git a/spec/encoding/index.texi b/spec/encoding/index.texi
index 640eeff..e2ab3b2 100644
--- a/spec/encoding/index.texi
+++ b/spec/encoding/index.texi
@@ -1,4 +1,5 @@
 @node Encoding
+@cindex encoding
 @unnumbered Encoding
 
 YAC can store various primitive scalar types (strings, integers, ...),
diff --git a/spec/encoding/int.texi b/spec/encoding/int.texi
index a1429cf..0d71a40 100644
--- a/spec/encoding/int.texi
+++ b/spec/encoding/int.texi
@@ -1,4 +1,5 @@
 @node Integers
+@cindex INT
 @section Integers
 
 Integers can be encoded in short or long form. Separate types are used
diff --git a/spec/encoding/prim.texi b/spec/encoding/prim.texi
index b2f48b2..76c3ab0 100644
--- a/spec/encoding/prim.texi
+++ b/spec/encoding/prim.texi
@@ -1,4 +1,7 @@
 @node Primitives
+@cindex NIL
+@cindex FALSE
+@cindex TRUE
 @section Primitives
 
 Very primitive types like NIL (None, Null), boolean FALSE and TRUE are
diff --git a/spec/encoding/str.texi b/spec/encoding/str.texi
index edbe391..51d3089 100644
--- a/spec/encoding/str.texi
+++ b/spec/encoding/str.texi
@@ -1,4 +1,6 @@
 @node Strings
+@cindex BIN
+@cindex STR
 @section Strings
 
 There are two kinds of strings: binary and UTF-8 (human-readable ones).
diff --git a/spec/encoding/tai64.texi b/spec/encoding/tai64.texi
index b8f694a..0a56ea0 100644
--- a/spec/encoding/tai64.texi
+++ b/spec/encoding/tai64.texi
@@ -1,4 +1,7 @@
 @node TAI64
+@cindex TAI64
+@cindex TAI64N
+@cindex TAI64NA
 @section TAI64
 
 Datetime is represented in @url{http://cr.yp.to/libtai/tai64.html, TAI64}
diff --git a/spec/encoding/uuid.texi b/spec/encoding/uuid.texi
index 7db1df2..5063883 100644
--- a/spec/encoding/uuid.texi
+++ b/spec/encoding/uuid.texi
@@ -1,4 +1,5 @@
 @node UUID
+@cindex UUID
 @section UUID
 
 128-bit big-endian @url{https://datatracker.ietf.org/doc/html/rfc9562, UUID}'s
diff --git a/spec/format/cer.texi b/spec/format/cer.texi
index 9cc1a5d..674b0fd 100644
--- a/spec/format/cer.texi
+++ b/spec/format/cer.texi
@@ -1,4 +1,5 @@
 @node Certificate
+@cindex Certificate
 @section Certificate format
 
 Certificate is the @ref{SignedData} structure with @code{/load.t} equals
diff --git a/spec/format/hashed.texi b/spec/format/hashed.texi
index e7ed8cb..7509779 100644
--- a/spec/format/hashed.texi
+++ b/spec/format/hashed.texi
@@ -1,4 +1,5 @@
 @node HashedData
+@cindex HashedData
 @section HashedData format
 
 Integrity protected container, analogue to CMS'es DigestedData structure.
diff --git a/spec/format/prv.texi b/spec/format/prv.texi
index 20bb566..c4192db 100644
--- a/spec/format/prv.texi
+++ b/spec/format/prv.texi
@@ -1,4 +1,5 @@
 @node PrivateKey
+@cindex PrivateKey
 @section PrivateKey format
 
 Private key is stored in trivial map:
diff --git a/spec/format/signed.texi b/spec/format/signed.texi
index a0e4707..40601b8 100644
--- a/spec/format/signed.texi
+++ b/spec/format/signed.texi
@@ -1,4 +1,5 @@
 @node SignedData
+@cindex SignedData
 @section SignedData format
 
 Signing of arbitrary data can be done in two ways: either with
diff --git a/spec/index.texi b/spec/index.texi
index 7072e71..5469bed 100644
--- a/spec/index.texi
+++ b/spec/index.texi
@@ -24,7 +24,7 @@ of structured data. But why!?
     representation of the structured data, allowing its usage in
     cryptography-related contexts.
 @item It should support enough data types to be able to replace JSON
-    transparently
+    transparently.
 @end itemize
 
 Are not there any satisfiable codecs?
@@ -77,7 +77,14 @@ encoding. YAC is Ain't a CBOR. Its other important differences:
 
 @insertcopying
 
+@include install.texi
 @include encoding/index.texi
 @include schema.texi
 @include format/index.texi
 @include registry.texi
+
+@node Concepts Index
+@unnumbered Concepts Index
+@printindex cp
+
+@bye
diff --git a/spec/registry.texi b/spec/registry.texi
index 735e0f4..50b54e1 100644
--- a/spec/registry.texi
+++ b/spec/registry.texi
@@ -1,4 +1,5 @@
 @node Registry
+@cindex Registry
 @unnumbered AI registry
 
 There is example registry of known algorithm identifiers.