Updated Dutch ij info as per #118

rosettatype · May 16, 2023 · 0ff93b8 · 0ff93b8
1 parent 2f8ce5e
commit 0ff93b8
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/lib/hyperglot/hyperglot.yaml b/lib/hyperglot/hyperglot.yaml
@@ -8187,11 +8187,11 @@ nld:
     auxiliary: ȷ
     base: A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Á Â Ä È É Ê Ë Í Ï Ó Ô Ö Ú Û Ü Ĳ a b c d e f g h i j k l m n o p q r s t u v w x y z á â ä è é ê ë í ï ó ô ö ú û ü ĳ
     design_requirements:
-    - A vast amount of Dutch data uses <i><j> (<I><J> in uppercase) to represent the Dutch lange ij.
+    - A vast amount of Dutch data uses <i><j> (<I><J> in uppercase, never <I><j>) to represent the Dutch lange ij.
     - |
-      Unicode and corresponding legacy encodings provide a digraph <ĳ> (<Ĳ> in uppercase) to simplify software support for situations when the lange ij ought to behave like a single unit, e.g. when text gets additional tracking or when changing cases. It is up to the font developers to decide whether they want to treat lange ij as a single unit during tracking or not or whether they want to leave the <ĳ> and <Ĳ> unaffected. For the sake of clarity: uppercase lange ij cannot be represented as <I><j>.
-    - Stressed lange ij is usually represented as <í><j>, but <í><j́> when technically possible as per the 1996 spelling.
-    - The <j> should lose its dot when combined with a combining acute.
+      Unicode provides a digraph <ĳ> (<Ĳ> in uppercase) to simplify software support for situations when the lange ij ought to behave like a single unit, e.g. when changing cases or when text gets additional tracking.
+    - Font developers can decide whether they want to treat lange ij, when spelled as <i><j> or <I><J>, as a single unit during tracking or not. It is recommended that <ĳ> and <Ĳ> always act as single units when tracking.
+    - Stressed lange ij is usually represented as <í><j>, but <í><j́> when technically possible as per the 1996 spelling reform. Note that the <j> should lose its dot when combined with a combining acute.
     - |
       Warning: Generally, fonts should not add an acute that is not present in the text, e.g. add acute above the <j> after the <í>. Many Dutch speakers use níet instead of níét, góed instead of góéd, zíjn instead of zíj́n and a font should not make either look like they have an additional acute. There is also the issue of foreign names in Dutch text, like Níjar or Szíj, which would be displayed incorrectly.
     marks: ◌̀ ◌́ ◌̂ ◌̈