NotoSans: Update to 2.013

All the different ligature removal calls are becoming more and more a
problem, because we have only one config.json for all fonts in a
font-root-directory. But the Noto variants have the ligatures in
different lookups. With the new font we finally remove lookups in the
new font that have a completely different contents then the lookups we
wanted to remove in the other family.

So the config.json is becoming more flexible: Now first we seach in the
concrete font file directory and only if there is no config we progress
to the font root directory and search there.

See also commit
d9f7dbe23  Prepatched fonts: Revive some ligature removal

Here we have
* fi and similar in lookup 41
* l-dot and similar in lookups 13, 14, 15

Fixes: #1472

Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>

bin/scripts/gotta-patch-em-all-font-patcher!.sh

@@ -224,9 +224,12 @@ function patch_font {
     source "$(find_font_root "$config_parent_dir")/config.cfg"
   fi
 
-  if [ -f "$config_parent_dir/config.json" ]
+  if [ -f "$config_dir/config.json" ]
+  then
+    # load font configuration file and remove selected ligatures:
+    font_config="--removeligatures --configfile $config_dir/config.json"
+  elif [ -f "$config_parent_dir/config.json" ]
   then
-    # load font configuration file and remove ligatures (for mono fonts):
     font_config="--removeligatures --configfile $config_parent_dir/config.json"
   else
     font_config=""

src/unpatched-fonts/Noto/README.md

@@ -9,4 +9,5 @@ The **Noto Mono** is an ancient font, nowadays the equivalent is Noto Sans Mono.
 The `ldot` ligatures are removed because the map to only one advance width.
 
 Version: 2.000 (20170915)
+Version: 2.013 (2022) for Noto Sans
 Version: 1.0 (2007) for Noto Mono