[latex3-commits] [latex3/babel] docs: Start 3.96. (29a1c9c)

[github at latex-project.org]

Repository : https://github.com/latex3/babel
On branch  : docs
Link       : https://github.com/latex3/babel/commit/29a1c9ccb76a885d4857d795ab3b2c008f3d54a0

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

commit 29a1c9ccb76a885d4857d795ab3b2c008f3d54a0
Author: Javier <email at localhost>
Date:   Fri Oct 20 19:11:04 2023 +0200

    Start 3.96.


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

29a1c9ccb76a885d4857d795ab3b2c008f3d54a0
 docs/news/whats-new-in-babel-3.96.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/docs/news/whats-new-in-babel-3.96.md b/docs/news/whats-new-in-babel-3.96.md
new file mode 100644
index 0000000..340fb45
--- /dev/null
+++ b/docs/news/whats-new-in-babel-3.96.md
@@ -0,0 +1,27 @@
+# What's new in babel 3.96
+
+** Draft **
+
+## Improved `onchar`
+
+Besides optimizing it for speed, a somewhat surprising behavior has
+been fixed. Let’s suppose you have decided to write some untagged Serbian
+text in an English document, so you write:
+```tex
+\babelprovide[onchar = ids fonts]{serbian}
+```
+This handles every Cyrillic letter, including those in something like:
+```
+\foreignlanguage{bulgarian}{български}
+```
+
+To avoid it, `onchar` is now applied only if the original and the target scripts
+are different.
+
+## ASCII encoding
+
+As suggested by Udi Fogiel, with the macro `\asciiencoding` you can
+retrieve and modify its value, which is determined by `babel` (it’s the
+same used in `\ensureascii`).
+
+## Fixes
\ No newline at end of file