Gnus development mailing list
 help / color / mirror / Atom feed
From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Japanese Honorifics
Date: Tue, 5 Oct 1999 14:07:16 -0400	[thread overview]
Message-ID: <99Oct5.140838edt.115201@gateway.intersys.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "05 Oct 1999 13:42:30 +0200"

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

* Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)  on Tue, 05 Oct 1999
| I don't know any Japanese at all, and I wonder: is `-san' a suffix
| used when speaking of a person informally; somewhat like the use of
| first name (rather than `Mr' or `Ms' and last name) in the Western
| culture?  Or is it part of his name?

The -san honorific is, as has been pointed out, similar to the English
Mr./Ms./Mrs. honorifics.  Context determines the degree of formality.  It
is never used self-referentially.

The -chan (feminine) and -kun (masculine) 'honorifics' are diminutives.
Their primary use is familial, a younger sister or brother.  They are
infrequently substituted for -san when the speaker is a superior (like your 
boss) but is also a friend (or at least considers himself to be a friend).
The diminutives are also very infrequently used incorrectly between
otherwise very close friends.

Then there is the archaic -dono honorific.  The meaning is highly dependant
on context
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE3+j5Tgl+vIlSVSNkRAhg0AJ9UfBaGVaZt351uwlztYAxHNLwa5wCfcfeY
HD3mxmcZLrpeJrjIYMCkvEw=
=SnIh
-----END PGP SIGNATURE-----

-- 
Rat <ratinox@peorth.gweep.net>    \ Do not taunt Happy Fun Ball.
Minion of Nathan - Nathan says Hi! \ 
PGP Key: at a key server near you!  \ 



                 reply	other threads:[~1999-10-05 18:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=99Oct5.140838edt.115201@gateway.intersys.com \
    --to=ratinox@peorth.gweep.net \
    /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).