(note that CLDR canonical order of variants is alphabetical)
This could obviously benefit further from non-" quoting that better accommodates XML contents, but this issue does not require it. Narrowly, I would propose a change to docs/ldml/tr35.md like
--- docs/ldml/tr35.md
+++ docs/ldml/tr35.md
@@ -3806,7 +3806,7
-> source=ja-Latn-fonipa-hepburn-heploc
+> `source="ja-Latn-fonipa-hepburn-heploc"`
>
-> rule ="\<languageAlias type="und-hepburn-heploc"
->
-> replacement="und-alalc97">"
+> `rule="<languageAlias type="und-hepburn-heploc" replacement="und-alalc97">"`
>
-> result="ja-Latn-alalc97-fonipa" // note that CLDR canonical order of variants is alphabetical
+> `result="ja-Latn-alalc97-fonipa"`
+>
+> (note that CLDR canonical order of variants is alphabetical)
This particularly impacts the example in subsection 4 “Replacement”, https://unicode.org/reports/tr35/#4.-replacement :
Above that, XML excerpts and source/type examples are presented in monospace, so the example should instead look more like this:
This could obviously benefit further from non-
"quoting that better accommodates XML contents, but this issue does not require it. Narrowly, I would propose a change to docs/ldml/tr35.md like--- docs/ldml/tr35.md +++ docs/ldml/tr35.md @@ -3806,7 +3806,7 -> source=ja-Latn-fonipa-hepburn-heploc +> `source="ja-Latn-fonipa-hepburn-heploc"` > -> rule ="\<languageAlias type="und-hepburn-heploc" -> -> replacement="und-alalc97">" +> `rule="<languageAlias type="und-hepburn-heploc" replacement="und-alalc97">"` > -> result="ja-Latn-alalc97-fonipa" // note that CLDR canonical order of variants is alphabetical +> `result="ja-Latn-alalc97-fonipa"` +> +> (note that CLDR canonical order of variants is alphabetical)There is also text in e.g. “Key And Type Definitions” https://unicode.org/reports/tr35/#Key_And_Type_Definitions_ / Lateral Inheritance https://unicode.org/reports/tr35/#Lateral_Inheritance / etc. that might be formatted in monospace as part of fixing this issue.