![]() | Tree of Life Template‑class | ||||||
|
I see that this now handles {{
taxon italics|Felis silvestris catus × Prionailurus bengalensis bengalensis}}
, to produce ''Felis silvestris catus'' × ''Prionailurus bengalensis bengalensis''. Ideally this would be ''Felis silvestris catus'' × ''Prionailurus bengalensis bengalensis'' (assuming the   is actually needed).
The exact input may sometimes have a thin- or hair-space character, or none at all, for hybrids with their own unique names, e.g. ×Amarcrinum which would ideally be auto-kerned to × ''Amarcrinum'' (with a hair-space, encoded the way that actually works cross-browser) – both for readability/accessibility and for cleaner data (actual separation of the epithet from the connecting term). The fully spaced style × Amarcrinum is also attested but is kind of bletcherous, and easily confusing to non-botanists; it looks like an error, while closely grouping with a hair-space markedly reduces this effect by making it a unit: × Amarcrinum. I suggest that input of × Amarcrinum (or x Amarcrinum, × Amarcrinum, etc.) be output as × ''Amarcrinum'' also. I would surmise that in the run-together case, of × fused directly to the genus, that it wouldn't be practical to detect a mistaken x, since some epithets begin with x.
Another case like this is the + used to indicate a graft chimaera, like + Laburnocytisus, if the template's not already detecting that. That interpolated character should also be hair-spaced and non-italic, I would think. Screen readers should have it easier, interpreting it as "plus" followed by some kind of whitespace then a name to pronounce, rather that a string of unidentified code to sound out character-by-character. — SMcCandlish ☏ ¢ 😼 07:49, 10 December 2018 (UTC)
The output ''Elaeagnus <span style="font-style:normal;">×</span> submacrophylla'' isn't going to work right in cases where the style needs to be flipped, as in a book title. See {{
Hybrid}}
for how I handled that (by adding an |invert=
parameter). That template also does some other stuff that might be worth adapting, if the cases are close enough. Lua makes me want to bite someone, so I did it in old-school template code, though someone is free to convert the template to Lua if it would be more efficient or capable that way. —
SMcCandlish
☏
¢ 😼
08:04, 10 December 2018 (UTC)
![]() | Tree of Life Template‑class | ||||||
|
I see that this now handles {{
taxon italics|Felis silvestris catus × Prionailurus bengalensis bengalensis}}
, to produce ''Felis silvestris catus'' × ''Prionailurus bengalensis bengalensis''. Ideally this would be ''Felis silvestris catus'' × ''Prionailurus bengalensis bengalensis'' (assuming the   is actually needed).
The exact input may sometimes have a thin- or hair-space character, or none at all, for hybrids with their own unique names, e.g. ×Amarcrinum which would ideally be auto-kerned to × ''Amarcrinum'' (with a hair-space, encoded the way that actually works cross-browser) – both for readability/accessibility and for cleaner data (actual separation of the epithet from the connecting term). The fully spaced style × Amarcrinum is also attested but is kind of bletcherous, and easily confusing to non-botanists; it looks like an error, while closely grouping with a hair-space markedly reduces this effect by making it a unit: × Amarcrinum. I suggest that input of × Amarcrinum (or x Amarcrinum, × Amarcrinum, etc.) be output as × ''Amarcrinum'' also. I would surmise that in the run-together case, of × fused directly to the genus, that it wouldn't be practical to detect a mistaken x, since some epithets begin with x.
Another case like this is the + used to indicate a graft chimaera, like + Laburnocytisus, if the template's not already detecting that. That interpolated character should also be hair-spaced and non-italic, I would think. Screen readers should have it easier, interpreting it as "plus" followed by some kind of whitespace then a name to pronounce, rather that a string of unidentified code to sound out character-by-character. — SMcCandlish ☏ ¢ 😼 07:49, 10 December 2018 (UTC)
The output ''Elaeagnus <span style="font-style:normal;">×</span> submacrophylla'' isn't going to work right in cases where the style needs to be flipped, as in a book title. See {{
Hybrid}}
for how I handled that (by adding an |invert=
parameter). That template also does some other stuff that might be worth adapting, if the cases are close enough. Lua makes me want to bite someone, so I did it in old-school template code, though someone is free to convert the template to Lua if it would be more efficient or capable that way. —
SMcCandlish
☏
¢ 😼
08:04, 10 December 2018 (UTC)