Talk:糖蜜

From Wiktionary, the free dictionary
Latest comment: 3 years ago by Octahedron80 in topic Hakka and Teochew
Jump to navigation Jump to search

Hakka and Teochew[edit]

@Octahedron80 Did you have a source for adding these pronunciations? — justin(r)leung (t...) | c=› } 03:32, 8 October 2020 (UTC)Reply

I just copied from 糖 and 蜜. Since Thai is derived from it. --Octahedron80 (talk) 03:34, 8 October 2020 (UTC)Reply

@Octahedron80: It's best not to infer. For Hakka, we do not support dialects other than Sixian (spoken in Taiwan) and Meixian, which are probably not the donor dialects to Thai. I'm also not sure if both Teochew readings are applicable. — justin(r)leung (t...) | c=› } 03:39, 8 October 2020 (UTC)Reply
Hakka is the origin of Thai terms sometimes, because various immegrants came from the southern of China via the sea. As in this [1] Hakka, Hainan[ese], and Canton[ese] happened other than Teochew and Hokkien. (But ตังเม is not mentioned there; I can call it is newly discovered) --Octahedron80 (talk) 03:45, 8 October 2020 (UTC)Reply
@Octahedron80: I'm not doubting the etymology. I'm just doubting that Sixian (which is what you added) or Meixian are the dialects that gave words to Thai. — justin(r)leung (t...) | c=› } 03:52, 8 October 2020 (UTC)Reply
@Octahedron80: It could still be Hakka, but just not Sixian. Meixian is possible, but other dialects of Hakka are probably more common in Thailand. — justin(r)leung (t...) | c=› } 04:01, 8 October 2020 (UTC)Reply
@Octahedron80: Why is the t in ตังเม and แตงเม unaspirated? 糖 has tʰ in both Min Nan and Hakka. 04:23, 8 October 2020 (UTC)Reply
I don't know but it is not impossible to happen; like ต in เย็นตาโฟ that is from 釀豆腐. --Octahedron80 (talk) 04:46, 8 October 2020 (UTC)Reply
Hmm, just looking at the entries, and the vowel in the first syllable also looks really un-Hakka in both words. — justin(r)leung (t...) | c=› } 04:28, 8 October 2020 (UTC)Reply
I think to state as "from a dialect of Chinese" may be safer. --Octahedron80 (talk) 04:40, 8 October 2020 (UTC)Reply