mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <kalin@ThinRope.net>
To: David Eger <eger@havoc.gtf.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] Translate Japanese comments in arch/v850  ( was: Alphabet of kernel source)
Date: Sun, 27 Jun 2004 14:48:02 +0900	[thread overview]
Message-ID: <40DE5F92.8000703@ThinRope.net> (raw)
In-Reply-To: <20040624061642.GA8506@havoc.gtf.org>

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]

David Eger wrote:
>>>http://www.yak.net/random/linux-2.6.4-utf8-cleanup-jp.diff
>>
>>Ok, this Japanese is only in the comments.
>>I can translate that in no time and fix this diff.
> 
> actually, I'm pretty sure the diff is correct against 2.6.4 - the bytes
> should all be correct, as I checked it with someone who works with
> said files...

OK, I had a few idle minutes, so I did patch the Japanese comments in arch/v850.

I am not exactly 100% sure I translated it correctly since I have no idea what exactly was that NEC v850 evaluation board, but should be OK (say 95% sure).

Patches just the comments, so code is untouched.

The other thing is that one of the files was encoded (i.e. readable) in iso-2022-jp, the other in euc-jp...
No idea how patch will handle this, I hope it doesn't bother with locale settings, etc.

Attaching as application/octet-stream in a hope for better handling of i18n issues, sorry for the inconvenience.

Here goes the patch:

Signed-off-by: Kalin KOZHUHAROV <kalin@thinrope.net>


[-- Attachment #2: v850-jp2en.diff --]
[-- Type: application/octet-stream, Size: 1947 bytes --]

  reply	other threads:[~2004-06-27  5:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 21:06 Alphabet of kernel source Pete Zaitcev
2004-06-23 21:46 ` David Eger
2004-06-23 22:18   ` Kalin KOZHUHAROV
2004-06-24  6:16     ` David Eger
2004-06-27  5:48       ` Kalin KOZHUHAROV [this message]
2004-06-23 21:58 ` Andries Brouwer
2004-06-24 11:06 ` Richard B. Johnson

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=40DE5F92.8000703@ThinRope.net \
    --to=kalin@thinrope.net \
    --cc=eger@havoc.gtf.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®