From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Clemens Ladisch <clemens@ladisch.de>,
Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>
Cc: hayashi@clear-code.com,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
linux1394-devel@lists.sourceforge.net,
"ffado-devel@lists.sf.net" <ffado-devel@lists.sf.net>
Subject: Meaning of the name 'hinawa' and the intension
Date: Sun, 31 Jan 2016 20:44:17 +0900 [thread overview]
Message-ID: <56ADF391.7090901@sakamocchi.jp> (raw)
In-Reply-To: <56ADEF9C.50303@sakamocchi.jp>
Hi,
After published libhinwa, I sometimes got a question about the name
of 'hinawa'. Here, I describe it to the persions who are curious.
At first, I split:
FireWire = Fire + Wire
(Japanese/Chinese translation in the meaning)
-> U+706B[0] + U+7E04[1] (in ISO/IEC 10646)
(Japanese translation in the pronounciation)
-> Hi + Nawa
Actually, the meaning of 'Nawa' is near rope. In Japanese history, Hinawa
was used to fire musket guns introduced in Sengoku period, so the musket
gun is called as Hinawa-ju (Ju means general guns). I think there'is a
word in European culture corresponding to the hi-nawa, but I don't know it.
I select this name because in general the name of library (soname) must
be unique in a system. In my case, I judged it better to pick up words
from non-European language group.
[0] U+706B
http://www.unicode.org/cgi-bin/GetUnihanData.pl?codepoint=706b
[1] U+7E04
http://www.unicode.org/cgi-bin/GetUnihanData.pl?codepoint=7e04
Regards
Takashi Sakamoto
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
next prev parent reply other threads:[~2016-01-31 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 11:27 The location of libhinawa and hinawa-utils for FireWire sound devices ? Takashi Sakamoto
2016-01-31 11:44 ` Takashi Sakamoto [this message]
2016-01-31 11:45 ` About planning of libhinawa ITP to debian project Takashi Sakamoto
2016-01-31 11:50 ` Takashi Sakamoto
2016-02-02 14:04 ` Takashi Sakamoto
2016-02-07 3:10 ` Takashi Sakamoto
2016-02-07 13:10 ` Takashi Sakamoto
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=56ADF391.7090901@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=ffado-devel@lists.sf.net \
--cc=hayashi@clear-code.com \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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