<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto">Dear typologists,<br>
<br>
I would like to seek your advice on a database I am making.<br>
For my doctoral project, I am compiling a phonological database of 700+ Eurasian languages.<br>
The database includes basic information such as the list of word-finally permitted phonemes, maximal number of onsets in a syllable, etc.<br>
For this database, I would like your opinion on whether to include xenophonic (loanword-phonological) information or not.<br>
For example, should the database include phonemes that are only present in loanwords (such as /x/ in English)?<br>
If the language does not allow codas in native word/ but allow them in loanwords, should that information be allowed as well?<br>
If you were using the database, would you find such information helpful?<br>
<br>
Pros of adding the xenophonic information: <br>
The database would be more complete. Some xenophonic features can be very old (such as onset clusters in Tagalog, word-initial /r/ in Japanese, etc.), so in a sense they are "nativized" (although they may be still marked). If I mark the native phonology and
the loanword phonology distinctly in my database (e. g. Including /ts/ in French phonology but specifying that it only appears in loanwords), then the user can use the database with or without xenophonic information.<br>
<br>
Cons:<br>
The problem of including xenophonic information is that, when considering loanwords, it is difficult to judge what is part of a language's phonology or not.<br>
For example /f/ occurs in very recent Korean loanwords such as /f/ail 'file' or /f/eyispwuk 'Facebook' and it's difficult to say if this is really a part of Korean phonology.<br>
Many minority language speakers are also fluent in their national language (such as Russian or Spanish) and they may pronounce loanwords from the national language in their 'original' pronunciation (such as Tuvan speakers pronouncing Russian loanwords in Russian
pronunciation) and it's difficult to say if this means Russian phonology has fully integrated into Tuvan phonology.<br>
So where to divide the line between what is purely foreign and what has been nativized?<br>
On the other hand, distinguishing phonological features that are only present in loanwords from those that are also present in native words is quite straightforward and less controversial (although there is also the problem that we do not always know if a word
is a loanword or not).<br>
Lastly, since I've already finished a good part of the database (about 15%), if I want to also include xenophonic information then I would have to go through the whole database again, so there's this practical issue.<br>
<br>
So I would appreciate your advice on whether including xenophonic information would be substantially beneficial to you or not, if you were using the database.</div>
</div>
<div name="messageSignatureSection"><br>
From Hong Kong,
<div dir="auto">Ian</div>
</div>
<style type="text/css">
<!--
p
{margin-top:12px;
margin-bottom:12px}
div.WordSection1
{}
--> </style><img alt="" src="https://www.polyu.edu.hk/emaildisclaimer/PolyU_Email_Signature.jpg">
<p><br>
<em><font face="Times New Roman" size="3">Disclaimer:</font></em></p>
<p></p>
<p style="margin-left: 0.5in"><i><font color="black" face="Times New Roman" size="3"><span>This message (including any attachments) contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you
should delete this message and notify the sender and The Hong Kong Polytechnic University (the University) immediately. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited and may be unlawful.</span></font></i></p>
<p style="margin-left: 0.5in"><i><span><font face="Times New Roman" size="3">The University specifically denies any responsibility for the accuracy or quality of information obtained through University E-mail Facilities. Any views and opinions expressed are
only those of the author(s) and do not necessarily represent those of the University and the University accepts no liability whatsoever for any losses or damages incurred or caused to any party as a result of the use of such information.</font></span></i></p>
</body>
</html>