

- Asturian: piña (Spain, via Latin)
- Tagalog: pinya (Philippines, via Spanish)
- Afrikaans: pynappel (Southern Africa, via Dutch like English)
- Japanese: painappuru
- Korean: painaepeul
- Welsh: pîn-afal, afal pin
- .
- Chamicuro: mawuli (Peru)
- Cherokee: notsiiYusdisvgata (USA)
- Chinese, Cantonese: bo1 lo4, fung6 lei4-2
- Chinese, Hakka: vòng-lì
- Chinese, Hokkien: ông-lâi
- Chinese, Mandarin: bōluó, fènglí, huánglí
- Dusun, Central: tintingabai (Malaysia)
- Hawaiian: hala kahiki
- Isan: bàk-nát (Thailand)
- Kaqchikel: ch’op (Guatemala)
- Khmer: mnŏəh (Cambodia)
- Lao: māk nat
- Malayalam: kaita (India)
- Melanau, Central: piseng (Malaysia)
- Nahuatl: matzahtli (Mexico)
- Ojibwe: zhingwaako-mishiimin (USA, Canada)
- Pali: kharattaca, madhuketakī, bahunettaphala (India, SL, SE Asia)
- Thai, Central: sàp-bpà-rót
- Tibetan: thang 'bras
- Vietnamese: dứa, cây dứa, thơm, cây thơm, khóm, cây khóm





Maybe it’s time. E.g. waiting for IT to walk over or remote in, or doing something slower because the user is explaining what they’re doing.
I find that waiting for the click to have a result makes some problems not appear, vs. the user double/right clicking something 6 times because they don’t want to wait. Me waiting for the OS to finish loading everything, vs. the user clicking something 6 times while services or even UI elements are still loading.