It is tricky: Japanese chat logs don't have all that much context to go on, and you have to make a judgment call as to what sort of "voice" they'd be speaking with. I gave them fairly informal young American programmer personalities but with just as much reason I could rewrite this to loko like it was two frat boys.
Disclaimer: I don't exactly go all-out for accuracy when translating to procrastinate about going to sleep.
I always enjoy (from an intellectual perspective) seeing two translations of the same thing...
When I compare your rewrite to mine, I notice that I semi-unconsciously had Matz and Keiju writing some lines as full sentences with correct English capitalization, and others as fragments starting with lowercase letters. That's often how English chatlogs look, after all. I have a Skype chatlog in my other window, talking with my product manager, that has a similar feel - I don't capitalize when I'm continuing the thought from a previous chat message.
And of course, I missed a few things you didn't - I'm not as conversant with tech-related Japanese.
It's tricky to come up with an idiomatic way to show two people discussing in Japanese an English play on words. Not to mention the Japanese "how is that spelled?" question that doesn't make sense in written English.
Wow, So Ruby was almost named Coral. Imagine programming in Coral on curtails.
Incidentally, there is actually a language named Coral ( a general purpose programming language based on ALGOL-60 http://en.wikipedia.org/wiki/Coral_66 )
keiju> ruby
keiju> a jewelry name after all
matz> put it alongside kanji?
Just FYI, this refers to the simpler hiragana characters sometimes put next to kanji characters (for people who don't read kanji very well). This is also often a source of confusion for people who see the <ruby> HTML5 tag and think that it's for the Ruby language.
[Pedantic note] They're not just for people who can't read kanji well: they're also used to provide a phonetic gloss for proper names (where the pronunciation is ambiguous or unique), or in literary contexts to indicate the intended pronunciation where unorthodox kanji are used for nuance.
I might try my hand at a translation with better flow... although, remember, the original is a chat log. Chat logs read in retrospect usually don't flow as well as natural conversation!
Certainly if one is fluent, that's a perfectly reasonable desire - I'm not, but I'm sure there's a significant amount lost in that translation process.
[+] [-] patio11|14 years ago|reply
http://pastebin.com/tHDPJsUt
It is tricky: Japanese chat logs don't have all that much context to go on, and you have to make a judgment call as to what sort of "voice" they'd be speaking with. I gave them fairly informal young American programmer personalities but with just as much reason I could rewrite this to loko like it was two frat boys.
Disclaimer: I don't exactly go all-out for accuracy when translating to procrastinate about going to sleep.
[+] [-] ejames|14 years ago|reply
When I compare your rewrite to mine, I notice that I semi-unconsciously had Matz and Keiju writing some lines as full sentences with correct English capitalization, and others as fragments starting with lowercase letters. That's often how English chatlogs look, after all. I have a Skype chatlog in my other window, talking with my product manager, that has a similar feel - I don't capitalize when I'm continuing the thought from a previous chat message.
And of course, I missed a few things you didn't - I'm not as conversant with tech-related Japanese.
It's tricky to come up with an idiomatic way to show two people discussing in Japanese an English play on words. Not to mention the Japanese "how is that spelled?" question that doesn't make sense in written English.
[+] [-] unknown|14 years ago|reply
[deleted]
[+] [-] GrooveStomp|14 years ago|reply
[+] [-] zach|14 years ago|reply
[+] [-] bitops|14 years ago|reply
[+] [-] dpapathanasiou|14 years ago|reply
I always thought the official name was "Practical Extraction and Report Language", or perl for short.
At least that's according to the man pages on my linux machine.
[+] [-] ayanb|14 years ago|reply
Incidentally, there is actually a language named Coral ( a general purpose programming language based on ALGOL-60 http://en.wikipedia.org/wiki/Coral_66 )
[+] [-] andrewflnr|14 years ago|reply
[+] [-] jarin|14 years ago|reply
[+] [-] threedaymonk|14 years ago|reply
[+] [-] 9999|14 years ago|reply
[+] [-] wccrawford|14 years ago|reply
[+] [-] ejames|14 years ago|reply
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-dev/5...
I might try my hand at a translation with better flow... although, remember, the original is a chat log. Chat logs read in retrospect usually don't flow as well as natural conversation!
[+] [-] xonev|14 years ago|reply
[+] [-] unknown|14 years ago|reply
[deleted]
[+] [-] contextfree|14 years ago|reply
[+] [-] unknown|14 years ago|reply
[deleted]
[+] [-] seagaia|14 years ago|reply
[+] [-] unknown|14 years ago|reply
[deleted]
[+] [-] unknown|14 years ago|reply
[deleted]
[+] [-] unknown|14 years ago|reply
[deleted]
[+] [-] access_denied|14 years ago|reply
[deleted]