Recent submissions

Comment · 1 year ago
Comment · 1 year ago
The article nearly equivocates “Rather Useless” and “unambiguously the worst”. Python3 seems more coherent to me than the article's argument:

1. Python3 plainly distinguishes between a string and a sequence of bytes. The function `len`, as a built-in, gives the most straightforward count: for any set or sequence of items, it counts the number of these items.

2. For a sequence of bytes, it counts the number of bytes. Taking this face-palming half-pale male hodgepodge and encoding it according to UTF-8, we get 17 bytes. Thus `len("\U0001F926\U0001F3FC\u200D\u2642\uFE0F".encode(encoding = "utf-8")) == 17`.

3. After bytes, the most basic entities are Unicode code points. A Python3 string is a sequence of Unicode code points. So for a Python3 string, `len` should give the number of Unicode code points. Thus `len("\U0001F926\U0001F3FC\u200D\u2642\uFE0F") == 5`.

Anything more is and should be beyond the purview of the simple built-in `len`:

4. Grapheme clusters are complicated and nearly as arbitrary as code points, hence there are “legacy grapheme clusters” – the grapheme clusters of older Unicode versions, because they changed – and “tailored grapheme clusters”, which may be needed “for specific locales and other customizations”, and of course the default “extended grapheme clusters”, which are only “a best-effort approximation” to “what a typical user might think of as a “character”.” Cf. https://www.unicode.org/reports/tr29

Of course, there are very few use cases for knowing the number of code points, but are there really much more for the number (NB: the number) of grapheme clusters?

Anyway, the great module https://pypi.org/project/regex/ supports “Matching a single grapheme \X”. So:

  len(regex.findall(r"\X", "\U0001F926\U0001F3FC\u200D\u2642\uFE0F")) == 1
5. The space a sequence of code points will occupy on the screen: certainly useful but at least dependent on the typeface that will be used for rendering and hence certainly beyond the purview of a simple function.
Comment · 1 year ago
That would be …

  "\u{1F926}\u{1F3FC}\u200D\u2642\uFE0F".length == 7
… for Javascript.
Comment · 1 year ago
Comment · 2 years ago
No, the pressing issue of the Willy-Nicky telegrams was that Russia had mobilised her troops against Germany. Speaking about the Hague conference while setting troops in motion is hypocritical: you should wait out lengthy proceedings while we are invading your country. In the telegrams, William II tried to convince Nicholas II to stop the mobilisation. But Sergey Sazonov shortly thereafter made Nicholas II restart and escalate the mobilisation. At that point, a major war was inevitable.
Comment · 2 years ago
Comment · 2 years ago
What I said is the position held by historical linguists focussing on early Ancient Greek, e.g. Strunk (who wrote the paper about aeolisms that are archaisms), Leumann, Meier-Brügger (Griech. Sprachw. II W 201.2 quoting Leumann “Versetzung in eine vom Alltag ferne Atmosphäre”, II F 218.3), Wachter (who wrote the grammar accompanying the latest comprehensive Greek Ilias edition), e.g. “the epic poet used non-everyday forms”, “it is true that from the point of view of its formation, ἤμαρ is more archaic than ἡμέρη, but there is no doubt that ἡμέρη, which is attested in the whole of post-Homeric Greek, particularly in Ionic-Attic, was the current form at Homer's time.” etc.

No linguist studying early Ancient Greek thinks that the poet(s) of the Iliad and Odyssey “used their own contemporary language”.

“You enjoying archaic text has zero to do with” … indeed, so letʼs not miss the argument I actually made: one of the two reasons for your view seems to be that Homer “made it sound pleasant”, “people […] liked it”. I just wanted to convey that it is a non sequitur to induce a non-archaic, contemporary style from that, particularly in the case of an epic poem about older times. This genre usually has an archaic, non-everyday style. (Two links I had included there to parallel examples were scrubbed.)

If herein you did not mean to give a reason for your view, I am sorry for the detour.

The then remaining reason for your view seems to be that the Homeric poems were “composed to be passed orally and only later on written”. But this is also no evidence for a non-archaic, contemporary language because highly archaic poems can be transmitted orally, even for centuries (cf. the Vedic hymns).

Your wording can only mean the history of the Homeric poems, but to take a look at their prehistory: the Oral-Formulaic Theory (Parry, Lord) also does not speak against archaic, non-everyday language, on the contrary, it was developed inter alia to explain the most archaic forms in the Homeric poems.

“older translations […] can be quite expansive over original. Given that this particular translation has the same length as original.” Sorry, but this is not correct, you wrote yourself “the translation is shorter then some other translations”. Emily Wilsonʼs translation has the same number of verses, as metric translations usually have, but uses the iambic pentameter instead of the considerably longer dactylic hexameter. Note that I donʼt criticize her decision. (On the contrary, I sympathize with the view that the English iambic verse may correspond a little bit better to the Greek dactylic verse. I know, in the end, Germanic metrical language and Ancient Greek metrical language are very different anyway.)

“This is kind of weird argument given there older translations you don't take issue with” … Look, I havenʼt made and donʼt intend to make any comment about any translation at all. In particular, I donʼt take issue with Wilsonʼs translation. I just wanted to corroborate the little objection made by DiscourseFan against a tiny, understandable and innocuous misconception. I deplore that the argument has rather deteriorated since then, will not engage further and wish you well.

Comment · 3 years ago
The point at issue I was referring to was yours, not his. I had the passage in mind I quoted; to quote and refer more concisely and precisely perhaps:

“But, when they created it [= Iliad or Odyssey] originally, they used their own contemporary language”

No, “they” did not. The Iliadʼs and Odysseyʼs language was nobodyʼs contemporary language. Not for the 8th century, not for the 5th. It has too many archaisms and dialectisms (aiolisms). (Note: Some forms seen as aiolisms in earlier research are understood as archaisms now.)

Yes, people enjoyed it, very much. But people can enjoy something that sounds archaic and unusual, not like contemporary speech. Particularly, when it is an epic poem about older times. That is quite common. I for one enjoy that, too, YMMV.

Your point “it was meant to be remembered and listened to” is difficult to unpack: Yes, this is true both for the time before and after a Homeric poem was composed as the whole that we know, but true in a very different manner. In any case, it is no evidence against archaisms (and aiolisms).

So:

“do you translate it into contemporary English or archaic one”

Archaic would be a little bit more authentic than contemporary.

Contemporary may be a better fit for many readers today – perhaps the ease of access is paramount when the translation competes with infinitely more permanently accessible information and entertainment than there was in the 8th century BC.

Comment · 3 years ago
Comment · 3 years ago
“robigo”, genitive “robiginis”, feminine.
Comment · 3 years ago
I, conversely, lack the knowledge to quite get the allusion to a Hallmark card or a Thomas Kincaid painting.

I guess that Kincaid paintings are considered subpar by connoisseurs. That wouldnʼt be the thing with Morgenstern. He is popular, but not that popular, and was sufficiently unconventional at his time to be seen as a genuine creative artist.

That is a comparison in terms of connoisseurship (or snobbery). If I had to make a comparison in terms of how the workʼs nature, Iʼd say that the shorter poems are like Roger Price droodles.

Comment · 3 years ago
Yes, but somehow it worked in a not-so-tangible way.

Germany for one apparently gave much more https://en.wikipedia.org/wiki/World_War_II_reparations than it got out of the https://en.wikipedia.org/wiki/Marshall_Plan#Expenditures in reverse. Imagine the allies had extracted much more wealth from Afghanistan or the Irak than they have put into it – itʼs inconceivable.

Slightly alternative explanation for West Germany, combining what others have said:

- First stage: The allies under US leadership were running the country anyway, they did it well and there was sufficient cooperation by Germans, for whom the Germany that was defeated represented an entity utterly discredited on account of the most horrible crimes against humanity.

- Second stage: The feeling “the Americans are actually on our side – defeating us they have liberated us and then helped us to a new state in which we can live better than ever before, plus they are protecting us from the USSR” became more or less mainstream.

(The experience in East Germany was completely different of course.)

So I think the most important factor was that American victory and American predominance were associated with liberation and freedom.

Comment · 3 years ago
Comment · 3 years ago
Yes, you are right, and the whole story of the laryngeal theory is quite exciting. – Saussureʼs initial evidence was a set of Sanskrit forms; and his argumentation went like:

- There is e.g. a root meaning ‘carry’ having the full grade “bʰar” and a corresponding zero grade “bʰr̩” (within the regular ablaut system of Sanskrit).

- Then there is e.g. a root meaning ‘clean’ having the full grade “pavi” and a corresponding zero grade “pū”.

- So we have “bʰar” : “pavi” = “bʰr̩” : “pū” or, re-grouped, “bʰar” : “bʰr̩” = “pavi” : “pū”.

- We already know (since the times of the great Indian grammarians) that, in ablaut, “v” corresponds to “u” (samprasāraṇa). All synchronic observations, by the way, about these different kinds of roots were already made by the Indian grammarians in the first millennium BC, too; and they called the roots à la “bʰar” “aniṭ” ‘without i’ and the roots à la “pavi” “sēṭ” ‘with i’.

- “bʰar” : “bʰr̩” is the regular ablaut pattern understandable as: ‘the full grade has the short vowel (“a” in Sanskrit, “e” in PIE), the zero grade lacks it.’

- Saussures brilliant and simple idea was to trace back “pavi” : “pū” to this very same basic pattern.

- To make this work he assumed a sound in the ‘clean’-root that became “i” between consonants but vanished with compensatory lengthening after sonantic “u”. (Saussure denoted this sound here with the cover symbol “A” in small caps.) So the older, regular pattern can be reconstructed as (in more modern notation):

- “bʰar” : “bʰr̩” = “pavH̩” : “puH”, which yields:

- “bʰar” : “bʰr̩” = “pavi” : “pū” as attested.

This argumentation is fairly compelling IMHO because it complies with Occamʼs razor by assuming that a second complicated, seemingly irregular morphological pattern leads back to the simpler, regular pattern we have to assume anyways, and that this simpler pattern was complicated by sound change – which is the normal way of linguistic change.

But it got even better.

- Saussure then drew attention to the Sanskrit verb formations of the seventh and ninth class (again, already classified and extensively described by the Indian grammarians), which both had an infix, i.e. a morphological element inserted into the root (not prepended like a prefix or appended like a suffix):

- 7th, e.g. “yunakti” ‘yokes (up)’ (the English word is a cognate), built like “yu·na·k-ti” with zero grade “yug” (and “g” → “k” before voiceless “t”), “na”-infix and personal ending “ti”.

- 9th, e.g. “punāti” ‘cleans’ – our pavi/pū-root again. But now with a short “u”? And with an infix “nā” instead of “na” as in “yunakti”? So … “u” instead of “ū” and “nā” instead of “na” … and both is already explained by the coefficient, because then we have to reconstruct:

- “pu·na·H-ti”, because the na-infix had to be inserted before the last consonant of the root. And this formation “pu·na·H-ti” is, again, exactly the same pattern as:

- “yu·na·k-ti”, just with “H” : “k”.

So far this argument justifies to assume one “coefficient”, in the case of the “pavi”-root denoted as “A” (in small caps) by Saussure and “h₂” nowadays. Saussure assumed two – denoting the other as “O̬”, nowadays “h₃” – because he also already noticed the coloring effect you explained in your comment below: The compensatorily lengthened Sanskrit “ā” sometimes corresponds to e.g. Greek and Latin “ā”, sometimes to Greek and Latin “ō”; for the latter Saussure introduced the “O̬”. His argumentation here is more difficult and partly outdated, because he wrote his mémoire (published 1879) in a time when another major discovery was not yet fully taken into account: So far, Indo-Europeanists had assumed that Sanskrit “a” originated from Proto-Indo-European “a”. When Saussure wrote his mémoire, it had become clear that it was necessary to assume at least two diffent vowels here, which both became Indian “a”.

Comment · 3 years ago
Thank you, thatʼs it: one of the biggest validations of the methodology for reconstructing languages. – Little nitpicks, if you allow:

- Saussure reconstructed only two of the three consonants now called “laryngeals” and called them “coefficients sonantiques”. Saussureʼs two sounds would be h₂ and h₃ in modern notation. The Danish linguist Möller added the third (h₁) and suggested that they were laryngeals.

- In Hittite, not all of the laryngeals are preserved: the Hittite sound transcribed as “ḫ” is certainly not a reflex of h₁, which had no reflexes in Hittite, and it certainly is a reflex of h₂. Whether it can also be a reflex of h₃ is contested.

(Edit: Your explanation below about the coloring by laryngeals is also correct in principle; just the specific example is problematic: because of Latin “ovis”, Greek “ὄις” we know that the late PIE form was “Howis” with “o” not “a”, either from “h₃éwis” with “h₃e” → “o” or from “h₂ówis”. The Hittite word you quoted may be evidence for the latter: “h₂ówis” → Hittite “ḫawis” with uncontested “h₂” → “ḫ”.)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton