Template talk:Times

"Template:Ü" listed at Redirects for discussion

An editor has asked for a discussion to address the redirect Template:Ü. Please participate in the redirect discussion if you wish to do so. Glenwing (talk) 12:54, 1 January 2020 (UTC)

Line break behavior

When I use {{times}} without parameters I would expect the template to do some wrap management similar to {{snd}}, i.e. it should generate the following HTML

 × 

It appears to generate a normal space before the × ~Kvng (talk) 22:12, 24 April 2024 (UTC)

The template puts a thin space on both sides of the multiplcation cross. — Christoph Päper 09:55, 26 April 2024 (UTC)

Is there such a thing as a thin non-breaking space? ~Kvng (talk) 13:09, 26 April 2024 (UTC)

I should note that this behavior is known and is already called out (though not very prominently) in the documentation:

Resolution numbers can also be entered (optionally) as parameters to the template. This has the advantage of preventing the resolution from being split across lines by word wrapping, which can occur when the numbers are outside the template.

There is a thin non-breaking space (U+202F) that could be used instead. I do not remember why I used the normal thin space instead when I wrote the template. Maybe have been lack of support across browsers or something like that. I remember similar issues with the ratio template, where Firefox on Android in particular does not support the default WP font, and uses the second backup option instead or something like that, which didn't support the ratio sign character and so that one character then gets substituted with an even further down font instead, which makes it mismatched. But such issues may have been resolved since then. I haven't been checking over the years so it's worth revisiting. I originally tried to resolve it by putting the HTML no-wrap tag, but that one doesn't prevent line breaks at the point between the preceding character and the tag. So I just left it with the condition that you need to use enclosed arguments in order to prevent line breaking. Anyway, I updated the sandbox page to use the non-breaking thin space (U+202F), and it appears to be just fine, and the line wrapping is now prevented with both inside and outside arguments as desired. So this is promising. But we should check on a variety of systems and browsers to see if there are any issues before updating the live template.  — Glenwing (talk) 18:33, 26 April 2024 (UTC)

MOS:UNITSYMBOLS requires full spaces (preferably non-breaking), not thin spaces. -- Beland (talk) 18:24, 2 January 2026 (UTC)

 ×  is not a unit so I'm not sure that applies here. ~Kvng (talk) 23:03, 2 January 2026 (UTC)

That guideline mentions how to use "×" with and without units. -- Beland (talk) 23:54, 2 January 2026 (UTC)

I see that now. ~Kvng (talk) 01:01, 3 January 2026 (UTC)