[latex3-commits] [git/LaTeX3-latex3-babel] docs: News 3.64: Document select.write. (43e2f43)

[Javier]

Repository : https://github.com/latex3/babel
On branch  : docs
Link       : https://github.com/latex3/babel/commit/43e2f4326ff5ca6bcd170a943db4bd507bb922d7

>---------------------------------------------------------------

commit 43e2f4326ff5ca6bcd170a943db4bd507bb922d7
Author: Javier <email at localhost>
Date:   Wed Oct 6 18:55:51 2021 +0200

    News 3.64: Document select.write.


>---------------------------------------------------------------

43e2f4326ff5ca6bcd170a943db4bd507bb922d7
 docs/guides/locale-hebrew.md                       |  1 +
 docs/news/whats-new-in-babel-3.64.md               | 29 +++++++++++++++++++---
 .../guides/non-standard-hyphenation-with-luatex.md | 15 +++++++----
 3 files changed, 36 insertions(+), 9 deletions(-)

diff --git a/docs/guides/locale-hebrew.md b/docs/guides/locale-hebrew.md
index 0b18644..0a6f0c0 100644
--- a/docs/guides/locale-hebrew.md
+++ b/docs/guides/locale-hebrew.md
@@ -19,4 +19,5 @@ not included in TeX distributions.
 * [Hebrew name
   typesetting](https://tex.stackexchange.com/a/581010/5735)
 * [Help getting started with Hebrew in babel](https://tex.stackexchange.com/questions/138992/help-getting-started-with-hebrew-in-babel/611604#611604)
+* [Why aren’t dageshes aligned in Hebrew in LuaLaTex?](https://tex.stackexchange.com/questions/605202/why-arent-dageshes-aligned-in-hebrew-in-lualatex)
 
diff --git a/docs/news/whats-new-in-babel-3.64.md b/docs/news/whats-new-in-babel-3.64.md
index 5a79020..455dfda 100644
--- a/docs/news/whats-new-in-babel-3.64.md
+++ b/docs/news/whats-new-in-babel-3.64.md
@@ -1,6 +1,6 @@
 # What's new in babel 3.64
 
-''(Under development.)''
+*(Under development.)*
 
 2021-10-??
 
@@ -8,12 +8,33 @@
 
 Some new counters has been added to Japanese.
 
+## Revert fix for `\selectlanguage`
+
+In version 3.61 there was a partial fix for the `\write` issue with
+`\selectlanguage`. See [\selectlanguage pushes section to new
+page](https://github.com/latex3/babel/issues/114). As explained un the
+news page for that release «the fix is not perfect and it can even lead
+to some problems», but it was introduced in the hope these problems
+will be less frequent and not too serious, but it turned out it was not
+so.
+
+The previous behavior has been restored, but it can be configured in
+the following way:
+* `\babeladjust{ select.write = shift }, which shifts the skips down
+  and adds a `\penalty`. 
+* `\babeladjust{ select.write = keep }, which is again the default
+  behavior. With it the `\write` and the skips are kept in the order they are
+  written.
+
+I thinkk this issue must be considered a ‘known issue’, because it
+seems unfixable.
+
 ## Fixes
 
-* babel errors on document option "chinese" (#141)
+* Babel errors on document option `chinese` (#141)
 
-* In some ini files multiple `babel.name`’s were separated keys with a
-  preffix (`A`, `B`), and in some other they were grouped in a single
+* In some `ini` files multiple `babel.name`’s were separated keys with a
+  suffix (`A`, `B`), and in some other they were grouped in a single
   key with space separated names. Now only the latter system (a single
   key) is used.
  
\ No newline at end of file
diff --git a/news-guides/guides/non-standard-hyphenation-with-luatex.md b/news-guides/guides/non-standard-hyphenation-with-luatex.md
index cb6e5ae..68da3df 100644
--- a/news-guides/guides/non-standard-hyphenation-with-luatex.md
+++ b/news-guides/guides/non-standard-hyphenation-with-luatex.md
@@ -1,6 +1,5 @@
 # Non-standard hyphenation with `luatex`
 
-
 Here is a simple example of a declaration:
 ```tex
 \babelposthyphenation{ngerman}{ck}{
@@ -45,9 +44,11 @@ string. The nodes created are literal copies of the original, but with
 new characters.
 4. With `remove` the node is, well, removed (ie, it's like and empty
 `string=`).
-5. (Development) **Spaces** are declared with something like `space =.2
+5. **Spaces** are declared with something like `space =.2
 .1 0`. The values are in em units, and they are the natural width, the
-`plus`, and the `minus`. Here, you may need `data`, too.
+`plus`, and the `minus`. Here, you may need `data`, too. With
+`spacefactor` the unit is the font size of the current font (if the
+node is a glyph; you may need a `data=` pointing to a specific glyph).
 
 A few keys can be used in conjunction with `insert`, which must be the
 very first one in the replacement. 
@@ -66,8 +67,12 @@ to reduce the number of items in the replacement list:
 
 Dots, characters classes (with %) and char-sets (with `[]`, including
 complementing and ranges) are allowed, too. When using the dot, be
-aware it matches `|` and `=`, too. A matched `|` or `=` cannot be
-currently replaced by a string.
+aware it matches `|` and `=`, too. A matched `|` or `=` can be
+replaced with the hex value (at least 4 digits): `{007C}` and `{003D}`.
+`+`, `-`, `?` and `*` are allowed outside the `()`...`()` block, but
+not inside. So, `{a}|?()Á()` is a letter followed optionally by a
+discretionary, but only Á is actually transformed (in these cases, you
+may wanto to go back with the key `step`).
 
 Ordinary captures are allowed _inside_ the empty captures (they must
 resolve to exactly one character). In the pattern, **the syntax `{n}`**