06/20 Question à mes 2.5 lecteurs francophones
Mon employeur vient de me faire passer un avenant à mon contrat de travail, sans me demander mon avis, et exige que je le signe. Est-ce légal…?
Mon employeur vient de me faire passer un avenant à mon contrat de travail, sans me demander mon avis, et exige que je le signe. Est-ce légal…?
I have been enrolled by iMorpheus in the Train Tales project. I have published a couple of short stories. Enjoy.
ㅏㅑㅓㅕㅗㅛㅜㅠㅡㅣ
The first four vowels in this illustration, with the vertical lines, were incompatible with the second four vowels, the ones with the horizontal lines. The last two vowels were neutral, as was another one, not shown here, which was written as a single dot and which has since fallen out of use. [some dude]
Nononono. There are two things wrong here. The first one is that the [in]compatibility stated above, in regard of syllable composition, is plain wrong. ㅗ and ㅏ could and still can combine — that’s how we write /wa/. ㅜ and ㅓ, ditto for /we/. Moreover, ㅛ and ㅑ, and ㅠ and ㅕ combined in Middle Korean, at least in the “漢字正音” [correct pronunciation of sinograms] usage to produce diphtongs that are not possible anymore today — and that could probably be reconstructed as */ywa/ and */ywe/.
The second one is that vowel harmony in Middle Korean, like in Mongolian or Turkish — and the main link, on that matter and others, with Korean is Mongolian, not Turkish — is based on two exclusive sets of vowels, {ㅏ, ㅗ, ㆍ} [a, o, ʌ] vs {ㅓ, ㅜ, ㅡ} [e, u, ɯ]. Neither Neither ㆍ nor ㅡ were neutral. ㅣ /i/ was indeed neutral and combined in different ways with both sets of vowels: ㅏ+ㅣ -> ㅐ, ㅜ+ㅣ -> ㅟ, ㅣ+ㅗ -> ㅛ, etc… I don’t have my Middle Korean dictionaries with me in HK, but I can remember at least one example: /kasʌy/ thorn vs /kusɯl/. The harmony rule extended to the grammatical particles that are suffixed to nouns, adjectives and verbs: /mʌl + ʌn/ [the] horse [as subject] vs /mɯl + ɯn/ [the] water [as subject].
Many years ago, when Oranckay worked for Digital Chosun, and produced quite a bit of their English Version, I told Oranckay that he should tell whoever was producing the web pages that the encoding should be, since these pages are for English-speaking people, ISO 8859-1 [I have converted to the Light Side™ now, and would advocate for UTF-8]. And mentionned that Korean-fonts-only curly quotes and apostrophes that show up in ISO 8859-1 as ¡° and shit should be converted and proper, internationally encoded chars should be used…
Pshaw. A few weeks after Oranckay passed on the message, they DID add the charset=iso-8859-1 definition. But they neither removed the euc-kr charset def, nor converted the ¡° ¡° crap… This double definition [and most browsers will keep the first one, euc-kr, discarding the second one…] has been for years there, and I am the culprit, I guess… When I tried Oranckay to go back to them and slap some sense in them, he told me getting them to add the iso charset definition had been painful enough, he wasn’t about to go there again and try to explain anything anymore to them. Which tells us how obtuse and ignorant these fellows are. And they still manage to run a large web site.
/me chuckles…
