Content deleted Content added
→no-merging s and t: Reply Tags: Mobile edit Mobile web edit Advanced mobile edit Reply |
→no-merging s and t: Reply |
||
Line 97:
::I thought allowing breaking was the right behavior, out of ignorance, but reviewing [https://www.unicode.org/reports/tr14/tr14-51.html the Unicode recommendation on the matter] makes me think I was wrong, and in fact line breaks shouldn't be allowed before semicolons or close-parentheses. A [[word joiner]] ⁠ could be used instead to get the correct behavior.
::There also is some intended way to do this in Unicode itself with variation selectors. I'm pretty sure this is the way, but not sure enough that I would want to put in on a page: {{zh|s=敬︀|t=敬|labels=no}} (text: 敬︀, 敬) {{zh|s=麻|t=麻︀|labels=no}} (text: 麻, 麻︀). The details of which variation selector to use for what is different for every character. It's a simple enough system, and the ideal solution if you're confident, but I'm not confident. The "text" renditions above should also display as the appropriate trad and simp variants — they don't on my system; the template displays them distinctly simply because they are distinct Unicode sequences (post-normalization). [[User:Dingolover6969|Dingolover6969]] ([[User talk:Dingolover6969|talk]]) 15:27, 28 April 2025 (UTC)
:::Chinese speaker (reader?) here, I usually gloss over the two different versions of the grass radical without noticing it. I've never heard of anyone caring about the difference. Unless we're discussing that radical specifically, I don't see the need to list both characters; if we ''are'' discussing that radical specifically, it might be better to use images, where the difference can be more clearly shown. I'm not firmly opposed to adding a merge=no option, but I haven't yet seen a case where it would be useful. [[User:Toadspike|<span style="color:#21a81e;font-variant: small-caps;font-weight:bold;">'''Toadspike'''</span>]] [[User talk:Toadspike|<span style="color:#21a81e;font-variant: small-caps;font-weight:bold;">[Talk]</span>]] 21:00, 28 April 2025 (UTC)
|