Rename paper/ directory to papers/

This complies with the [directory.papers] Beman Standard rule.

Author: ednolan

.pre-commit-config.yaml

@@ -21,4 +21,4 @@ repos:
     hooks:
       - id: codespell
 
-exclude: 'paper/'
+exclude: 'papers/'

CMakeLists.txt

@@ -53,5 +53,5 @@ if(BEMAN_UTF_VIEW_BUILD_EXAMPLES)
 endif()
 
 if(BEMAN_UTF_VIEW_BUILD_PAPER)
-    add_subdirectory(paper)
+    add_subdirectory(papers)
 endif()

README.md

@@ -337,8 +337,8 @@ beman.utf_view is based on P2728 and P3705.
 - The latest official revision of P2728 can be found at https://wg21.link/p2728
 - The latest official revision of P3705 can be found at https://wg21.link/p3705
 - The unofficial latest draft Markdown source for each paper can be found in this repository:
-  - At [paper/P2828.md](https://github.com/bemanproject/utf_view/blob/main/paper/P2728.md)
-  - At [paper/P3705.md](https://github.com/bemanproject/utf_view/blob/main/paper/P3705.md)
+  - At [papers/P2828.md](https://github.com/bemanproject/utf_view/blob/main/papers/P2728.md)
+  - At [papers/P3705.md](https://github.com/bemanproject/utf_view/blob/main/papers/P3705.md)
 - P2728's committee status page can be found at https://github.com/cplusplus/papers/issues/1422
 
 ## Authors

paper/CMakeLists.txt papers/CMakeLists.txtpaper/CMakeLists.txt renamed to papers/CMakeLists.txt

@@ -46,7 +46,7 @@ as a sequence of 32-bit unsigned integers. The building blocks of an encoding
 are _code units_, and UTF-32 has the most direct mapping between code points
 and code units.
 
-![](../../paper/images/utf32.png){ width=400px }
+![](../../papers/images/utf32.png){ width=400px }
 
 Any values greater than `0x10FFFF` are rejected by validators for being
 outside the range of valid Unicode.
@@ -56,9 +56,9 @@ codespace used to top out at `0xFFFF`. Code points outside this range are
 represented using _surrogates_, a reserved area in codespace which allows
 combining the low 10 bits of two code units to form a single code point.
 
-![](../../paper/images/utf16.png){ width=400px }
+![](../../papers/images/utf16.png){ width=400px }
 
-![](../../paper/images/utf16_2.png){ width=300px }
+![](../../papers/images/utf16_2.png){ width=300px }
 
 UTF-16 is rendered invalid by improper use of surrogates: a high surrogate not
 followed by a low surrogate or a low surrogate not preceded by a high
@@ -72,9 +72,9 @@ code unit is either a start byte, which describes how long the subsequence is
 (two to four bytes long), or a continuation byte, which fills out the
 subsequence with the remaining data.
 
-![](../../paper/images/utf8.png){ width=750px }
+![](../../papers/images/utf8.png){ width=750px }
 
-![](../../paper/images/utf8_2.png){ width=400px }
+![](../../papers/images/utf8_2.png){ width=400px }
 
 UTF-8 code unit sequences can be invalid for many reasons, such as a start
 byte not followed by the correct number of continuation bytes, or a UTF-8
@@ -216,7 +216,7 @@ underlying view. `operator*` provides the current element of the buffer.
 Below is an approximate block diagram of the iterator. Bold lines denote
 actual data members of the iterator; dashed lines are just function calls.
 
-![](../../paper/images/iterator.png){ width=500px }
+![](../../papers/images/iterator.png){ width=500px }
 
 The `to_utf_view::@*iterator*@` is converting the string `Qϕ学𡪇`
 from UTF-8 to UTF-16. The user has iterated the view to the first UTF-16 code
@@ -284,7 +284,7 @@ The table below compares the error handling behavior of the `to_utf16` and
 "Substitution of Maximal Subparts" section of the Unicode standard:
 [@SubstitutionExamples]
 
-![](../../paper/images/error_handling.png){ width=750px }
+![](../../papers/images/error_handling.png){ width=750px }
 
 ## Code Unit Views