The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: downing.nick@gmail.com (Nick Downing)
Subject: [TUHS] Mushi and Bagu
Date: Thu, 16 Feb 2017 03:13:39 +1100	[thread overview]
Message-ID: <CAH1jEzbmP+WqWkyN8U=oz04hw6faChy-9T09aiEsZYqhyzUciw@mail.gmail.com> (raw)
In-Reply-To: <20170215153008.5381F18C0BA@mercury.lcs.mit.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3297 bytes --]

Yes, I just looked it up too.

http://jisho.org/search/むし
States that mushi means "insect" and "the act of ignoring". (In Japanese
some verbs are nouns and used with the word "suru" meaning "do").

http://jisho.org/search/ばぐ
States that "bagu" means computer bug/error. That's also my recollection as
they use loan words for most of these technical things.

However, Japanese is NOT a complicated language. The spoken language is
very simple. The grammar and sound system are basically like English but
cut down and streamlined. It has a few unique features like "wa" but many
of the particles like "o" and "ga" have direct translations.

Where Japanese is harder to learn is the politeness levels of which there
are basically 4: rude, normal, polite and ultra polite. In ultra polite
there is a different vocabulary so that common actions such as seeing,
going, eating etc have to use a different word, however most ultra polite
language and basically all of the rude and polite language may be derived
systematically from the normal. We do this in English but less rigorously.

The other main thing is the writing system, well Japanese view it as a
beautiful thing and highly cultured but it's not. It's actually the world's
clunkiest writing system, in the 50s the Japanese government seriously
tried to get rid of it and replace with Latin letters like many other
sensible countries have done, and if they'd succeeded then learning
Japanese would be no more difficult than say Tagalog (Filipino) or Bahasa
(Indonesian/Malay). The reason they did not succeed is the many homonyms
resulting from Japanese's very limited sound system (about 50 syllables
compared with hundreds for English and thousands for Chinese or Vietnamese)
which makes Japanese a bit confusing/slow to read when written
phonetically. Note English also uses a similar system to disambiguate
homonyms.

cheers, Nick

On Feb 16, 2017 2:30 AM, "Noel Chiappa" <jnc at mercury.lcs.mit.edu> wrote:

>     > From: Larry McVoy
>
>     > Are you sure? Someone else said moshi was hi and mushi was bug. Does
>     > mushi have two meanings?
>
> Yes:
>
>   http://www.nihongodict.com/?s=mushi
>
> Actually, more than two! Japanese is chock-a-block with homonyms. Any
> given Japanese word will probably have more than one meaning.
>
> There's some story I don't quite recall about a recent Prime Minister who
> made a mistake of this sort - although now that I think about it, it was
> probably the _other_ kind of replication, which is that a given set of
> kanji
> (ideograms) usually has more than one pronunciation. (I won't go into why,
> see here:
>
>   http://mercury.lcs.mit.edu/~jnc/prints/glossary.html#Reading
>
> for more.) So he was reading a speech, and gave the wrong reading for a
> word.
> There is apparently a book (or more) in Japanese, for the Japanese, that
> lists
> the common ones that cause confusion.
>
> A very complicated language! The written form is equally complicated; there
> are two syllabaries ('hiragana' and 'katakana'), and for the kanji, there
> are
> several completely different written forms!
>
>         Noel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170216/49bdf86b/attachment-0001.html>


  reply	other threads:[~2017-02-15 16:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 15:30 Noel Chiappa
2017-02-15 16:13 ` Nick Downing [this message]
2017-02-15 18:16   ` Nemo
  -- strict thread matches above, loose matches on Subject: below --
2017-02-16  7:28 Rudi Blom
2017-02-16  9:36 ` jsteve
2017-02-16 10:42   ` Nick Downing
2017-02-16 13:49     ` Rudi Blom
2017-02-15 14:51 Nemo
2017-02-15 15:01 ` Larry McVoy
2017-02-15 15:04   ` John Floren
2017-02-15 15:27   ` Steve Nickolas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH1jEzbmP+WqWkyN8U=oz04hw6faChy-9T09aiEsZYqhyzUciw@mail.gmail.com' \
    --to=downing.nick@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).