<html aria-label="message body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I would add that in some cases, such as Literary Chinese, there is no practical way to do transliteration. Many publications transliterate Literary Chinese examples using the Mandarin readings transcribed in Pinyin, but this is anachronistic, and in any case such a transliteration is typically ambiguous without the original script. The alternative is to use Middle or Old Chinese reconstructions, but these are not standardised, and in any case, may raise philological issues that are tangential to the points that the examples are being used to make. So in this case at least, I think the only viable option would be to use the original script.<div><br></div><div>Siva<br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On 15 Nov 2025, at 1:14 pm, JOO Ian via Lingtyp <lingtyp@listserv.linguistlist.org> wrote:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-family: Arial, sans-serif;">Dear Konstantin,<o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-family: Arial, sans-serif;"><o:p> </o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-family: Arial, sans-serif;">I always add the original script as well as Latin (if not originally Latin), for example in<span class="Apple-converted-space"> </span><a href="x-msg://4/ianjoo.github.io/Thesis.pdf" style="color: rgb(70, 120, 134); text-decoration: underline;">my thesis</a>.<span class="Apple-converted-space"> </span><o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-family: Arial, sans-serif;">Even for phonetic scripts like Hangul, there are multiple transliteration methods (Yale, MR, RR) and a Korean speaker might not be familiar with all of them, and even if they are, reading in Hangul is always much easier.<o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-family: Arial, sans-serif;">Even for non-Korean speakers, adding the original script in addition to Romanization increases cross-literature consistency. For example if one reader saw<span class="Apple-converted-space"> </span></span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">갓</span><span lang="KO" style="font-family: Arial, sans-serif;"><span class="Apple-converted-space"> </span></span><span lang="EN-US" style="font-family: Arial, sans-serif;">`Korean hat’ as<span class="Apple-converted-space"> </span><i>kas<span class="Apple-converted-space"> </span></i>(Yale transcription) in one article but as<span class="Apple-converted-space"> </span><i>gat</i><span class="Apple-converted-space"> </span>(RR transcription) in another, having the Korean spelling in addition to Latin would enable the reader to acknowledge that they are the same lexeme.<o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-family: Arial, sans-serif;">Other than this practical reason, I would argue that adding the original script is in fact in line with the spirit of typology, which is to embrace and celebrate linguistic diversity, which includes written diversity.<o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-family: Arial, sans-serif;"><o:p> </o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-family: Arial, sans-serif;">From Otaru,<br>Ian<o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-family: Arial, sans-serif;"><o:p> </o:p></span></div><div><div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-family: Arial, sans-serif;">- - - - - - - - - - - - - - - - - - - - - -</span><span style="font-family: Arial, sans-serif;"><span class="Apple-converted-space"> </span><span lang="EN-US">-</span></span><span style="font-family: Arial, sans-serif;"><br></span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">朱 易安</span><span style="font-family: Arial, sans-serif;"> <br>JOO, IAN <br></span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">准教授</span><span style="font-family: Arial, sans-serif;"> <br>Associate Professor <br></span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">小樽商科大学</span><span style="font-family: Arial, sans-serif;"> <br>Otaru University of Commerce<o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-family: Arial, sans-serif;"><o:p> </o:p></span></div></div></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-family: "Apple Color Emoji";">🌐</span><span lang="EN-US" style="font-family: Arial, sans-serif;"> <a href="http://ianjoo.github.io/" style="color: rgb(70, 120, 134); text-decoration: underline;"><span style="color: rgb(113, 79, 188);">ianjoo.github.io</span></a><br>- - - - - - - - - - - - - - - - - - - - - - -</span><span lang="EN-US" style="font-family: Arial, sans-serif;"><o:p></o:p></span></div><div style="margin: 0cm; font-size: 12pt; font-family: Aptos, sans-serif;"><span lang="EN-US" style="font-family: Arial, sans-serif;"><o:p> </o:p></span></div><div id="mail-editor-reference-message-container"><div><div><div style="border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) currentcolor currentcolor; border-image: none; padding: 3pt 0cm 0cm;"><p class="MsoNormal" style="margin: 0cm 0cm 12pt 39.95pt; font-size: 12pt; font-family: Aptos, sans-serif;"><b><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">보낸</span></b><b><span lang="KO" style=""><span class="Apple-converted-space"> </span></span></b><b><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">사람</span></b><b><span style="">:<span class="Apple-converted-space"> </span></span></b><span style="">Lingtyp <<a href="mailto:lingtyp-bounces@listserv.linguistlist.org" style="color: rgb(70, 120, 134); text-decoration: underline;">lingtyp-bounces@listserv.linguistlist.org</a>></span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">이</span><span style="">(</span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">가</span><span style="">)<span class="Apple-converted-space"> </span></span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">다음</span><span lang="KO" style=""><span class="Apple-converted-space"> </span></span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">사람</span><span lang="KO" style=""><span class="Apple-converted-space"> </span></span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">대신</span><span lang="KO" style=""><span class="Apple-converted-space"> </span></span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">보냄</span><span style="">: Konstantin Henke via Lingtyp <<a href="mailto:lingtyp@listserv.linguistlist.org" style="color: rgb(70, 120, 134); text-decoration: underline;">lingtyp@listserv.linguistlist.org</a>><br></span><b><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">날짜</span></b><b><span style="">:<span class="Apple-converted-space"> </span></span></b><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">토요일</span><span style="">, 2025</span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">년</span><span style=""><span class="Apple-converted-space"> </span>11</span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">월</span><span style=""><span class="Apple-converted-space"> </span>15</span><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">일</span><span style=""><span class="Apple-converted-space"> </span>02:27<br></span><b><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">받는</span></b><b><span lang="KO" style=""><span class="Apple-converted-space"> </span></span></b><b><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">사람</span></b><b><span style="">:<span class="Apple-converted-space"> </span></span></b><span style=""><a href="mailto:LINGTYP@listserv.linguistlist.org" style="color: rgb(70, 120, 134); text-decoration: underline;">LINGTYP@listserv.linguistlist.org</a><span class="Apple-converted-space"> </span><<a href="mailto:lingtyp@listserv.linguistlist.org" style="color: rgb(70, 120, 134); text-decoration: underline;">lingtyp@listserv.linguistlist.org</a>><br></span><b><span lang="KO" style="font-family: "맑은 고딕", sans-serif;">주제</span></b><b><span style="">:<span class="Apple-converted-space"> </span></span></b><span style="">[Lingtyp] Should we include original scripts for examples in typological publications?<o:p></o:p></span></p></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;">Dear Lingtyp members,<o:p></o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;"><o:p> </o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;">I hope this is not an old topic with a consensus I'm not aware of. If it is, please forgive me for re-opening it.<o:p></o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;"><o:p> </o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;">In the overwhelming majority of example sentences/forms in typological publications I do not see another line providing the original script where one exists for the surveyed language (Thai, Chinese, Korean, Japanese, certain Slavic languages, etc.). It might be a domain-specific thing (I've mostly been working with spatial semantics) but researchers in other domains may have been wondering about the same thing.<o:p></o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;"><o:p> </o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;">I understand that adding another written representation to the Latin transliteration does not serve the endeavor of typology, which is based on segments that are ideally naturally produced (i.e. spoken) and that especially non-phonemic/phonetic scripts do not add any value for the greater part of a broader audience of researchers and other readers. Instead, adding these scripts eats up space and may even be perceived as an unnecessary show-off with something that looks pretty or exotic.<o:p></o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;"><o:p> </o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;">Having studied in Taiwan, where Mandarin speakers even in the academic realm are often not familiar with Pinyin, the de-facto standard Latin transliteration of their language, I frequently witnessed them struggle to read examples presented in their very own language if Chinese characters are missing. China, on the other hand, is arguably a rather rare case where the academically used transliteration (Pinyin with tone diacritics) does happen to be almost the same as the most common input method on electronic devices (Pinyin without tone diacritics). I'm not sure if my observation in Taiwan generalizes well, but I wouldn't be surprised if fellow researchers from Thailand, Korea, Japan, Russia etc. struggled to read their language in Latin transliteration. I'm actually quite surprised to see a discipline concerned with freeing itself from Eurocentric bias care so little about its accessibility to non-European contributors and readers.<o:p></o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;"><o:p> </o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;">That said, I may be overlooking something in addition to the few counter-points mentioned above. I do empathize with the argument that a push for naturalistic data might imply the wish to rid oneself of the burden of written representation (but then we might as well just provide all examples of spoken data in IPA, which I have seen a few researchers do even for familiar IE languages). I would also understand the space question if it weren't for the fact that everyone just reads PDFs now anyways. Layout/font-related issues should hardly pose a problem in the age of Unicode, either. Am I missing something, or are we really just being lazy?<o:p></o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;"><o:p> </o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;">I'd appreciate any input!<o:p></o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;"><o:p> </o:p></span></div></div><div><div style="margin: 0cm 12pt 0.0001pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;">Best,<o:p></o:p></span></div></div><div><div style="margin: 0cm 0cm 0cm 39.95pt; font-size: 12pt; font-family: Aptos, sans-serif;"><span style="font-size: 10.5pt; font-family: Arial, sans-serif;">Konstantin<br><br>PS: I'm obviously talking about cases where the original script adds readability for native speakers. Whether or not to add less commonly used scripts like Javanese to raise awareness or for similar reasons, is probably a different topic.<o:p></o:p></span></div></div></div></div></div></div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">Lingtyp mailing list</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">Lingtyp@listserv.linguistlist.org</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">https://listserv.linguistlist.org/cgi-bin/mailman/listinfo/lingtyp</span></div></blockquote></div><br></div></body></html>