[111533] in tlhIngan-Hol
[tlhIngan Hol] Meta: Discussions about new words found in Netflix'
daemon@ATHENA.MIT.EDU (Felix Malmenbeck)
Tue Oct 10 07:16:10 2017
X-Original-To: tlhingan-hol@lists.kli.org
From: Felix Malmenbeck <felixm@kth.se>
To: "tlhingan-hol@kli.org" <tlhingan-hol@kli.org>
Date: Mon, 9 Oct 2017 14:08:38 +0000
Reply-To: tlhingan-hol@kli.org
Errors-To: tlhingan-hol-bounces@lists.kli.org
--===============4986819593428249760==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_150755811905143369kthse_"
--_000_150755811905143369kthse_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
As Lieven has mentioned previously on this mailing list, the Klingon subtit=
les for Star Trek: Discovery include a few new words from Maltz. These will=
be revealed in full at the qepHom'a' in mid-November. Until then, the only=
way to learn these words is to watch the show and compare the subtitles to=
the dialogue. Sometimes the meanings are quite clear, and at other times t=
hey require some guesswork.
I personally quite like this approach; I enjoy the "hunt", and it's actuall=
y how I first envisioned learning Klingon might work, until I learned it wa=
sn't used consistently in the various series.
That being said, it is a bit unfair to our American chuDpu', who don't have=
access to these subtitles. So, it seems reasonable that those of us who *c=
an* access them should use this mailing list to share our findings (with di=
sclaimers that they include speculation).
So, the question then is, how shall we go about it?
Since there seems to be a consensus that we should wait for 48 ours after t=
he US release before sharing plot details, should we have a similar guideli=
ne for words found in the subtitles?
Or should we perhaps aim to share the relevant subtitles and corresponding =
English sentences as quickly as possible (with spoiler warnings for the rel=
evant episode), so that everybody can join in the analysis/speculation as e=
arly on as possible?
//loghaD
--_000_150755811905143369kthse_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none"><!--P{margin-top:0;margin-b=
ottom:0;} --></style>
</head>
<body dir=3D"ltr" style=3D"font-size:12pt;color:#000000;background-color:#F=
FFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>As Lieven has mentioned previously on this mailing list, the Klingon sub=
titles for Star Trek: Discovery include a few new words from Maltz. These w=
ill be revealed in full at the qepHom'a' in mid-November. Until then, the o=
nly way to learn these words is
to watch the show and compare the subtitles to the dialogue. Sometimes the=
meanings are quite clear, and at other times they require some guesswork.<=
br>
</p>
<p><br>
</p>
<p>I personally quite like this approach; I enjoy the "hunt", and=
it's actually how I first envisioned learning Klingon might work, until I =
learned it wasn't used consistently in the various series.</p>
<p>That being said, it is a bit unfair to our American chuDpu', who don't h=
ave access to these subtitles. So, it seems reasonable that those of us who=
*can* access them should use this mailing list to share our findings (with=
disclaimers that they include speculation).</p>
<p><br>
</p>
<p>So, the question then is, how shall we go about it?<br>
</p>
<p>Since there seems to be a consensus that we should wait for 48 ours afte=
r the US release before sharing plot details, should we have a similar guid=
eline for words found in the subtitles?</p>
<p><br>
</p>
<p>Or should we perhaps aim to share the relevant subtitles and correspondi=
ng English sentences as quickly as possible (with spoiler warnings for the =
relevant episode), so that everybody can join in the analysis/speculation a=
s early on as possible?</p>
<p><br>
</p>
<p>//loghaD<br>
</p>
</body>
</html>
--_000_150755811905143369kthse_--
--===============4986819593428249760==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
tlhIngan-Hol mailing list
tlhIngan-Hol@lists.kli.org
http://lists.kli.org/listinfo.cgi/tlhingan-hol-kli.org
--===============4986819593428249760==--
