• Log InLog In
  • Register
Liquid`
Team Liquid Liquipedia
EST 00:33
CET 06:33
KST 14:33
  • Home
  • Forum
  • Calendar
  • Streams
  • Liquipedia
  • Features
  • Store
  • EPT
  • TL+
  • StarCraft 2
  • Brood War
  • Smash
  • Heroes
  • Counter-Strike
  • Overwatch
  • Liquibet
  • Fantasy StarCraft
  • TLPD
  • StarCraft 2
  • Brood War
  • Blogs
Forum Sidebar
Events/Features
News
Featured News
Team Liquid Map Contest #235[ASL22] Finals Preview: Sweet Victory!12[ASL22] Ro4 Preview: Mirror Mirror6[ASL22] Ro8 Preview: Within Reach5[ASL22] Ro8 Preview: In A Tizzy11
Community News
Weekly Cups (Nov 9-15): Clem and herO take over1Dark completes military service, returns to SC215[BSL23] RO16 Group Stage20Weekly Cups (Nov 2-8): herO back on top?2Weekly Cups (Oct 26 - Nov 1): MaxPax, herO, Solar win0
StarCraft 2
General
Team Liquid Map Contest #23 Dark completes military service, returns to SC2 Weekly Cups (Nov 9-15): Clem and herO take over StarCraft open world shooter announced at BlizzCon No more SC2 streamers on team liquid?
Tourneys
Sparkling Tuna Cup - Weekly Open Tournament RSL goes to London! 2026 Offline Finals Nov 21-22 Sea Duckling Open (Global, Bronze-Diamond) Dark returns! GSL CK #7 4v4 Team Battle (Nov 19) soO & FanTaSy return! SC2 Kevin Scrim 4v4 (Nov 16)
Strategy
[H] ZvP Mid-Late Game: Stalkers Collossi HT
Custom Maps
[G] How to playtest arcade maps Starcraft 2 Advance [D] the control group Simple Questions/Answers
External Content
Mutation # 552 Secret Storm The PondCast: SC2 News & Results Mutation # 551 Robotic Revival Mutation # 550 Graveyard Shift
Brood War
General
BW General Discussion List of top players active on ShieldBattery NaDa's Body Shield Battery Server New Patch BGH Auto Balance -> http://bghmmr.eu/
Tourneys
SC1 Kevin Scrim hosted by SOOP (Nov 18-19) [IPSL] Winter 26-27 Round of 16! [Megathread] Daily Proleagues 2v2v2v2 Tournament Stage 2: Players
Strategy
Pluto's TvP 5Marine 2Medic Push Simple Questions, Simple Answers Infested Terran strategies in 2026 Nuke strategy worked in K-League 2026-11-09
Other Games
General Games
Nintendo Switch Thread Stormgate/Frost Giant Megathread Free Space RTS Game, optimised f. Phone/Tablet etc List of Game Threads The PlayStation 5
Dota 2
League of Legends
[TL LoL EUW IHs] Teemo shall perish
Heroes of the Storm
Heroes of the Storm 2.0
Hearthstone
Deck construction bug
TL Mafia
TL Mafia Community Thread
Community
General
US Politics Mega-thread Trading/Investing Thread Artificial Intelligence Thread Russo-Ukrainian War Thread Things Aren’t Peaceful in Palestine
Fan Clubs
Fan Club Resource Thread Reynor Fan Club The Flash Fan Club
Media & Entertainment
Movie Discussion! Anime Discussion Thread [Manga] One Piece
Sports
Football (Soccer) Thread TeamLiquid Health and Fitness Initiative For 2023
World Cup 2022
Tech Support
Computer Build, Upgrade & Buying Resource Thread
TL Community
The Automated Ban List Recent Gifted Posts
Blogs
The time I organised my…
AssyrianKing
Why I built Repalyzer (1.1.…
BlueStar
Innovate or Game Over?
TrAiDoS
ShieldBattery on Mac
Kraekkling
Can Bots Beat Pros?? Starcr…
namkraft
StarCraft improvement
iopq
Socialism Anyone?
GreenHorizons
Customize Sidebar...

Website Feedback

Closed Threads



Active: 9957 users

Japanese language

Blogs > Rus_Brain
Post a Reply
1 2 Next All
Rus_Brain
Profile Blog Joined June 2006
Russian Federation1894 Posts
March 29 2012 13:30 GMT
#1
Bros,

Can I ask you for a little help?

I have a file which I need to send to Japan so they could clarify the information.

Request text should be as follows:

""
Dear Sirs,

Would you be so kind to clarify whether it was really your shipyard, who built this vessel.

Please kindly provide your answer in english to Kirill Patyrykin:
kgp@pomosch.com

Thank you very much in advance.
""

Can you help me to translate better than google translate with all these desu-politeness stuff?

*
patyrykin.net
Skilledblob
Profile Joined April 2011
Germany3392 Posts
March 29 2012 13:44 GMT
#2
just send them a proper english email? I am sure they'll be able to find someone who can speak english or in your case russian if they sell outside of Japan
Tobberoth
Profile Joined August 2010
Sweden6375 Posts
Last Edited: 2012-03-29 14:19:20
March 29 2012 13:49 GMT
#3
It's far from perfect, but here's a decent try which should at least be far better than google translate.

拝啓

そちらの造船所がこの船を作り上げたかどうか、明らかにしてもらえませんか?

もしよかったら、下記のメールアドレスに英語でお答えを
kgp@pomosch.com

よろしくおねがいします。

敬具

It's not a perfect translation, the first sentence is more like:
Would it be possible for you to clarify if your shipyard made this boat or not?

And the one above the mail is:
If you would, please send your english answer to the mail written below
rgfdxm
Profile Joined December 2006
United States239 Posts
March 29 2012 14:17 GMT
#4
On March 29 2012 22:49 Tobberoth wrote:
まらえませんか?


Typo there, should be 「もらえませんか?」
Tobberoth
Profile Joined August 2010
Sweden6375 Posts
March 29 2012 14:19 GMT
#5
On March 29 2012 23:17 rgfdxm wrote:
Show nested quote +
On March 29 2012 22:49 Tobberoth wrote:
まらえませんか?


Typo there, should be 「もらえませんか?」

Indeed, fixed.
Ecael
Profile Joined February 2008
United States6703 Posts
Last Edited: 2012-03-29 15:04:28
March 29 2012 15:00 GMT
#6
I'd recommend you just to use English, but what Tobberoth provided should get across fine.

It'd be a bit freaky if I was working in Japan and gets something with perfect keigo usage from outside of Japan anyway. Either way, you won't be continuing exchanges in Japanese in the first place, so as a customer you could easily have dropped most of the formality.

If I have to nitpick though, 明らかにして is a bit clunky and you'd be better off using just 教えて. Also rather than もらえる you should be using くださる. Oh, and it should be 宜しければ rather than よかったら.
AmericanUmlaut
Profile Blog Joined November 2010
Germany2599 Posts
March 29 2012 15:07 GMT
#7
I would also just use 作ったかどうか instead of 作り上げたかどうか, as the second implies that they made it for someone, which isn't clear from your description, and if they did make it for someone, but whoever they made it for is associated with your company, then you would need to use 作り下ったかどうか.

As the others have written, you can also just write in English, but I think it's a nice gesture to make the first contact in your target's native language.
The frumious Bandersnatch
Tobberoth
Profile Joined August 2010
Sweden6375 Posts
March 29 2012 17:00 GMT
#8
On March 30 2012 00:07 AmericanUmlaut wrote:
I would also just use 作ったかどうか instead of 作り上げたかどうか, as the second implies that they made it for someone, which isn't clear from your description, and if they did make it for someone, but whoever they made it for is associated with your company, then you would need to use 作り下ったかどうか.

As the others have written, you can also just write in English, but I think it's a nice gesture to make the first contact in your target's native language.

No, 作り上げる is not the same as 作って上げる. 作り上げる implies a sense of completion and is in my opinion more fitting for the situation at hand.
Rus_Brain
Profile Blog Joined June 2006
Russian Federation1894 Posts
March 29 2012 17:04 GMT
#9
Tobberoth thank you very much
patyrykin.net
Tobberoth
Profile Joined August 2010
Sweden6375 Posts
March 29 2012 17:06 GMT
#10
On March 30 2012 00:00 Ecael wrote:
I'd recommend you just to use English, but what Tobberoth provided should get across fine.

It'd be a bit freaky if I was working in Japan and gets something with perfect keigo usage from outside of Japan anyway. Either way, you won't be continuing exchanges in Japanese in the first place, so as a customer you could easily have dropped most of the formality.

If I have to nitpick though, 明らかにして is a bit clunky and you'd be better off using just 教えて. Also rather than もらえる you should be using くださる. Oh, and it should be 宜しければ rather than よかったら.

I must disagree, I can't think of a good way to use くださる in the sentence without it either sounding impolite or unnatural. However, one could use いただけますか to make it more polite than もらえませんか. 教えて would work fine, but I think this sounds more business-like.

As for 宜しければ vs よかったら, I'd say it's up to the level of politeness you want to achieve. It would fit well though.
Tobberoth
Profile Joined August 2010
Sweden6375 Posts
March 29 2012 17:08 GMT
#11
On March 30 2012 02:04 Rus_Brain wrote:
Tobberoth thank you very much

No problem. A japanese friend of mine is coming over in a few hours, I'll have her look over my mail and update it with her pointers.
Tasaio
Profile Joined March 2011
Japan61 Posts
March 29 2012 17:13 GMT
#12
That mail should get the point across just fine.

But other than what Ecael said earlier, using 拝啓 and 敬具 in this case is weirdly formal, and incorrect without a seasonal greeting. It's especially strange with the informal tone used later in the text.

Also, you should be presenting yourself in the start of the email.
Tobberoth
Profile Joined August 2010
Sweden6375 Posts
March 29 2012 17:36 GMT
#13
On March 30 2012 02:13 Tasaio wrote:
That mail should get the point across just fine.

But other than what Ecael said earlier, using 拝啓 and 敬具 in this case is weirdly formal, and incorrect without a seasonal greeting. It's especially strange with the informal tone used later in the text.

Also, you should be presenting yourself in the start of the email.

Yeah, I was unsure about adding it. Writing a proper japanese business letter is way too complicated (and quite a lot of work for such a small request), but since you don't want to be overly casual, I thought I'd add it in anyway, the receiver might consider it nice for a foreigner to attempt to write a bit more formal than needed.
Ecael
Profile Joined February 2008
United States6703 Posts
Last Edited: 2012-03-29 17:53:09
March 29 2012 17:50 GMT
#14
If we want to get technical then いただく is a bit more accurate than くださる insofar as you are requesting them to reveal information, though tbh the difference there is slim. I guess since this is written we can stick to いただく. Either way, もらえる would still be the 基本語, so the contrast in politeness level stood out. In terms of the politeness level you seemed to be aiming for overall, with the greetings included, the frankness that the rest of your sentences have was peculiar. That's why I focused my points to keep it more or less in keigo rather than have a dash of regular speak.

As for 明らかにする, that'd literally be asking for them to reveal themselves, which isn't as business like as it is bizarre, and further clashes with the general polite tone. About 作り上げる, it does imply that they were contracted by a third party to complete a request, so Umlaut is right.

The part about the greetings is like as Tasaio said, I completely didn't notice it but you would need the seasonal greeting and such to make that work, but afaik people don't really do business stuff like that. I guess introducing yourself at the start of the mail would only make sense too if we want to stick to a polite inquiry rather than just a casual note.

In all...would be much easier to use English

On March 30 2012 02:36 Tobberoth wrote:
Show nested quote +
On March 30 2012 02:13 Tasaio wrote:
That mail should get the point across just fine.

But other than what Ecael said earlier, using 拝啓 and 敬具 in this case is weirdly formal, and incorrect without a seasonal greeting. It's especially strange with the informal tone used later in the text.

Also, you should be presenting yourself in the start of the email.

Yeah, I was unsure about adding it. Writing a proper japanese business letter is way too complicated (and quite a lot of work for such a small request), but since you don't want to be overly casual, I thought I'd add it in anyway, the receiver might consider it nice for a foreigner to attempt to write a bit more formal than needed.

Then you should've stuck to all keigo lol
Tobberoth
Profile Joined August 2010
Sweden6375 Posts
March 29 2012 18:01 GMT
#15
On March 30 2012 02:50 Ecael wrote:
If we want to get technical then いただく is a bit more accurate than くださる insofar as you are requesting them to reveal information, though tbh the difference there is slim. I guess since this is written we can stick to いただく. Either way, もらえる would still be the 基本語, so the contrast in politeness level stood out. In terms of the politeness level you seemed to be aiming for overall, with the greetings included, the frankness that the rest of your sentences have was peculiar. That's why I focused my points to keep it more or less in keigo rather than have a dash of regular speak.

As for 明らかにする that'd literally be asking for them to reveal themselves, which isn't as business like as it is bizarre, and further clashes with the general polite tone. About 作り上げる, it does imply that they were contracted by a third party to complete a request, so Umlaut is right.

The part about the greetings is like as Tasaio said, I completely didn't notice it but you would need the seasonal greeting and such to make that work, but afaik people don't really do business stuff like that. I guess introducing yourself at the start of the mail would only make sense too if we want to stick to a polite inquiry rather than just a casual note.

In all...would be much easier to use English

Show nested quote +
On March 30 2012 02:36 Tobberoth wrote:
On March 30 2012 02:13 Tasaio wrote:
That mail should get the point across just fine.

But other than what Ecael said earlier, using 拝啓 and 敬具 in this case is weirdly formal, and incorrect without a seasonal greeting. It's especially strange with the informal tone used later in the text.

Also, you should be presenting yourself in the start of the email.

Yeah, I was unsure about adding it. Writing a proper japanese business letter is way too complicated (and quite a lot of work for such a small request), but since you don't want to be overly casual, I thought I'd add it in anyway, the receiver might consider it nice for a foreigner to attempt to write a bit more formal than needed.

Then you should've stuck to all keigo lol

I can't find any indication in several 国語辞書 that 作り上げる has any implication of doing it for a third party, do you have a source for that?

I also feel your exaggerating about 明らかにする, it means to reveal or to clarify, and implies removal of doubt. An example of a natural japanese sentence using it in a similar way would be 論点を明らかにする, it's not bizarre at all.
Tobberoth
Profile Joined August 2010
Sweden6375 Posts
March 29 2012 18:20 GMT
#16
There, my japanese friend rewrote my letter, so this should be far better:

拝啓

御社が例の造船を終えられたのかどうか、知らせて頂けますか。

下記のメールアドレスまで英語でお答えを送っていただければ幸いです。
kgp@pomosch.com

よろしくおねがいします。

敬具
Ecael
Profile Joined February 2008
United States6703 Posts
Last Edited: 2012-03-29 18:40:18
March 29 2012 18:34 GMT
#17
On March 30 2012 03:01 Tobberoth wrote:
Show nested quote +
On March 30 2012 02:50 Ecael wrote:
If we want to get technical then いただく is a bit more accurate than くださる insofar as you are requesting them to reveal information, though tbh the difference there is slim. I guess since this is written we can stick to いただく. Either way, もらえる would still be the 基本語, so the contrast in politeness level stood out. In terms of the politeness level you seemed to be aiming for overall, with the greetings included, the frankness that the rest of your sentences have was peculiar. That's why I focused my points to keep it more or less in keigo rather than have a dash of regular speak.

As for 明らかにする that'd literally be asking for them to reveal themselves, which isn't as business like as it is bizarre, and further clashes with the general polite tone. About 作り上げる, it does imply that they were contracted by a third party to complete a request, so Umlaut is right.

The part about the greetings is like as Tasaio said, I completely didn't notice it but you would need the seasonal greeting and such to make that work, but afaik people don't really do business stuff like that. I guess introducing yourself at the start of the mail would only make sense too if we want to stick to a polite inquiry rather than just a casual note.

In all...would be much easier to use English

On March 30 2012 02:36 Tobberoth wrote:
On March 30 2012 02:13 Tasaio wrote:
That mail should get the point across just fine.

But other than what Ecael said earlier, using 拝啓 and 敬具 in this case is weirdly formal, and incorrect without a seasonal greeting. It's especially strange with the informal tone used later in the text.

Also, you should be presenting yourself in the start of the email.

Yeah, I was unsure about adding it. Writing a proper japanese business letter is way too complicated (and quite a lot of work for such a small request), but since you don't want to be overly casual, I thought I'd add it in anyway, the receiver might consider it nice for a foreigner to attempt to write a bit more formal than needed.

Then you should've stuck to all keigo lol

I can't find any indication in several 国語辞書 that 作り上げる has any implication of doing it for a third party, do you have a source for that?

I also feel your exaggerating about 明らかにする, it means to reveal or to clarify, and implies removal of doubt. An example of a natural japanese sentence using it in a similar way would be 論点を明らかにする, it's not bizarre at all.

Meh I guess it is just an implication in some of the specific definitions, all of it just mean 作る・作り出す・製造 anyway. I just don't like 作り上げる because it can also mean でっち上げる

論点を明らかにする isn't bizarre, but telling someone to do that? Keep in mind that it means from はっきりさせる to 秘密・真相などを明らかにする. It won't be an inquiry, it'd be you demanding that they reveal what they know.

What your friend has bugs me a little, 造船 could mean many part of the process like design and such, no? I kinda assumed the guy wanted to know if it was put together at that shipyard.
Tobberoth
Profile Joined August 2010
Sweden6375 Posts
Last Edited: 2012-03-29 18:43:24
March 29 2012 18:39 GMT
#18
On March 30 2012 03:34 Ecael wrote:
Show nested quote +
On March 30 2012 03:01 Tobberoth wrote:
On March 30 2012 02:50 Ecael wrote:
If we want to get technical then いただく is a bit more accurate than くださる insofar as you are requesting them to reveal information, though tbh the difference there is slim. I guess since this is written we can stick to いただく. Either way, もらえる would still be the 基本語, so the contrast in politeness level stood out. In terms of the politeness level you seemed to be aiming for overall, with the greetings included, the frankness that the rest of your sentences have was peculiar. That's why I focused my points to keep it more or less in keigo rather than have a dash of regular speak.

As for 明らかにする that'd literally be asking for them to reveal themselves, which isn't as business like as it is bizarre, and further clashes with the general polite tone. About 作り上げる, it does imply that they were contracted by a third party to complete a request, so Umlaut is right.

The part about the greetings is like as Tasaio said, I completely didn't notice it but you would need the seasonal greeting and such to make that work, but afaik people don't really do business stuff like that. I guess introducing yourself at the start of the mail would only make sense too if we want to stick to a polite inquiry rather than just a casual note.

In all...would be much easier to use English

On March 30 2012 02:36 Tobberoth wrote:
On March 30 2012 02:13 Tasaio wrote:
That mail should get the point across just fine.

But other than what Ecael said earlier, using 拝啓 and 敬具 in this case is weirdly formal, and incorrect without a seasonal greeting. It's especially strange with the informal tone used later in the text.

Also, you should be presenting yourself in the start of the email.

Yeah, I was unsure about adding it. Writing a proper japanese business letter is way too complicated (and quite a lot of work for such a small request), but since you don't want to be overly casual, I thought I'd add it in anyway, the receiver might consider it nice for a foreigner to attempt to write a bit more formal than needed.

Then you should've stuck to all keigo lol

I can't find any indication in several 国語辞書 that 作り上げる has any implication of doing it for a third party, do you have a source for that?

I also feel your exaggerating about 明らかにする, it means to reveal or to clarify, and implies removal of doubt. An example of a natural japanese sentence using it in a similar way would be 論点を明らかにする, it's not bizarre at all.

Meh I guess it is just an implication in some of the specific definitions, all of it just mean 作る・作り出す・製造 anyway.

論点を明らかにする isn't bizarre, but telling someone to do that? Keep in mind that it means from はっきりさせる to 秘密・真相などを明らかにする. It won't be an inquiry, it'd be you demanding that they reveal what they know.

Well, it's not like you're demanding them to do something if you're asking them nicely to do something, してもらえませんか being quite a polite phrase. I guess it depends on your perspective, I certainly don't have enough experience with the phrase to say for sure, but since OP thinks they made the vessel and wants to know for sure, I see no problem in asking them to はっきりさせる, the semantic meaning fits perfectly fine, but of course, it's never that easy with a different language.

EDIT: As for 造船, I'm pretty sure it refers to the whole process of building a ship in general, so unless they only just manufactured it (and you want to indicate that with your word usage), I think it would work out. Obviously, the OP is a bit vague, so it's hard to say ^^
Ecael
Profile Joined February 2008
United States6703 Posts
March 29 2012 18:46 GMT
#19
On March 30 2012 03:39 Tobberoth wrote:
Show nested quote +
On March 30 2012 03:34 Ecael wrote:
On March 30 2012 03:01 Tobberoth wrote:
On March 30 2012 02:50 Ecael wrote:
If we want to get technical then いただく is a bit more accurate than くださる insofar as you are requesting them to reveal information, though tbh the difference there is slim. I guess since this is written we can stick to いただく. Either way, もらえる would still be the 基本語, so the contrast in politeness level stood out. In terms of the politeness level you seemed to be aiming for overall, with the greetings included, the frankness that the rest of your sentences have was peculiar. That's why I focused my points to keep it more or less in keigo rather than have a dash of regular speak.

As for 明らかにする that'd literally be asking for them to reveal themselves, which isn't as business like as it is bizarre, and further clashes with the general polite tone. About 作り上げる, it does imply that they were contracted by a third party to complete a request, so Umlaut is right.

The part about the greetings is like as Tasaio said, I completely didn't notice it but you would need the seasonal greeting and such to make that work, but afaik people don't really do business stuff like that. I guess introducing yourself at the start of the mail would only make sense too if we want to stick to a polite inquiry rather than just a casual note.

In all...would be much easier to use English

On March 30 2012 02:36 Tobberoth wrote:
On March 30 2012 02:13 Tasaio wrote:
That mail should get the point across just fine.

But other than what Ecael said earlier, using 拝啓 and 敬具 in this case is weirdly formal, and incorrect without a seasonal greeting. It's especially strange with the informal tone used later in the text.

Also, you should be presenting yourself in the start of the email.

Yeah, I was unsure about adding it. Writing a proper japanese business letter is way too complicated (and quite a lot of work for such a small request), but since you don't want to be overly casual, I thought I'd add it in anyway, the receiver might consider it nice for a foreigner to attempt to write a bit more formal than needed.

Then you should've stuck to all keigo lol

I can't find any indication in several 国語辞書 that 作り上げる has any implication of doing it for a third party, do you have a source for that?

I also feel your exaggerating about 明らかにする, it means to reveal or to clarify, and implies removal of doubt. An example of a natural japanese sentence using it in a similar way would be 論点を明らかにする, it's not bizarre at all.

Meh I guess it is just an implication in some of the specific definitions, all of it just mean 作る・作り出す・製造 anyway.

論点を明らかにする isn't bizarre, but telling someone to do that? Keep in mind that it means from はっきりさせる to 秘密・真相などを明らかにする. It won't be an inquiry, it'd be you demanding that they reveal what they know.

Well, it's not like you're demanding them to do something if you're asking them to do something. I guess it depends on your perspective, I certainly don't have enough experience with the phrase to say for sure, but since OP thinks they made the vessel and wants to know for sure, I see no problem in asking them to はっきりさせる, the semantic meaning fits perfectly fine, but of course, it's never that easy with a different language.

Yeah, but you don't use はっきりする lightly. In English, the difference between 教える and はっきりする would be like, if you would 'let me know' vs 'make it clear'. You can use the former nicely, the latter is you demanding them to divulge information to you.
Tobberoth
Profile Joined August 2010
Sweden6375 Posts
Last Edited: 2012-03-29 19:18:54
March 29 2012 19:08 GMT
#20
On March 30 2012 03:46 Ecael wrote:
Show nested quote +
On March 30 2012 03:39 Tobberoth wrote:
On March 30 2012 03:34 Ecael wrote:
On March 30 2012 03:01 Tobberoth wrote:
On March 30 2012 02:50 Ecael wrote:
If we want to get technical then いただく is a bit more accurate than くださる insofar as you are requesting them to reveal information, though tbh the difference there is slim. I guess since this is written we can stick to いただく. Either way, もらえる would still be the 基本語, so the contrast in politeness level stood out. In terms of the politeness level you seemed to be aiming for overall, with the greetings included, the frankness that the rest of your sentences have was peculiar. That's why I focused my points to keep it more or less in keigo rather than have a dash of regular speak.

As for 明らかにする that'd literally be asking for them to reveal themselves, which isn't as business like as it is bizarre, and further clashes with the general polite tone. About 作り上げる, it does imply that they were contracted by a third party to complete a request, so Umlaut is right.

The part about the greetings is like as Tasaio said, I completely didn't notice it but you would need the seasonal greeting and such to make that work, but afaik people don't really do business stuff like that. I guess introducing yourself at the start of the mail would only make sense too if we want to stick to a polite inquiry rather than just a casual note.

In all...would be much easier to use English

On March 30 2012 02:36 Tobberoth wrote:
On March 30 2012 02:13 Tasaio wrote:
That mail should get the point across just fine.

But other than what Ecael said earlier, using 拝啓 and 敬具 in this case is weirdly formal, and incorrect without a seasonal greeting. It's especially strange with the informal tone used later in the text.

Also, you should be presenting yourself in the start of the email.

Yeah, I was unsure about adding it. Writing a proper japanese business letter is way too complicated (and quite a lot of work for such a small request), but since you don't want to be overly casual, I thought I'd add it in anyway, the receiver might consider it nice for a foreigner to attempt to write a bit more formal than needed.

Then you should've stuck to all keigo lol

I can't find any indication in several 国語辞書 that 作り上げる has any implication of doing it for a third party, do you have a source for that?

I also feel your exaggerating about 明らかにする, it means to reveal or to clarify, and implies removal of doubt. An example of a natural japanese sentence using it in a similar way would be 論点を明らかにする, it's not bizarre at all.

Meh I guess it is just an implication in some of the specific definitions, all of it just mean 作る・作り出す・製造 anyway.

論点を明らかにする isn't bizarre, but telling someone to do that? Keep in mind that it means from はっきりさせる to 秘密・真相などを明らかにする. It won't be an inquiry, it'd be you demanding that they reveal what they know.

Well, it's not like you're demanding them to do something if you're asking them to do something. I guess it depends on your perspective, I certainly don't have enough experience with the phrase to say for sure, but since OP thinks they made the vessel and wants to know for sure, I see no problem in asking them to はっきりさせる, the semantic meaning fits perfectly fine, but of course, it's never that easy with a different language.

Yeah, but you don't use はっきりする lightly. In English, the difference between 教える and はっきりする would be like, if you would 'let me know' vs 'make it clear'. You can use the former nicely, the latter is you demanding them to divulge information to you.

Well, if you make "make it clear" a bit more polite, you get clarify. Then again, that certainly doesn't have to be true for Japanese, and you're probably correct that 明らかにする is not very good to use in a polite situation.
1 2 Next All
Please log in or register to reply.
Live Events Refresh
PiGosaur Cup
10:00
#108
Liquipedia
[ Submit Event ]
Live Streams
Refresh
StarCraft 2
RuFF_SC2 254
SortOf 54
ProTech12
StarCraft: Brood War
ToSsGirL 77
Bale 36
Noble 22
ZergMaN 21
sOs 12
Icarus 9
Force[name] 7
League of Legends
JimRising 718
Heroes of the Storm
Trikslyr53
Other Games
summit1g12046
WinterStarcraft521
C9.Mang0434
ViBE84
trigger6
Organizations
Other Games
gamesdonequick924
[ Show 10 non-featured ]
StarCraft 2
• AfreecaTV YouTube
• intothetv
• Kozan
• IndyKCrew
• Migwel
StarCraft: Brood War
• BSLYoutube
• STPLYoutube
• ZZZeroYoutube
Dota 2
• lizZardDota2120
League of Legends
• Rush1216
Upcoming Events
The PondCast
4h 28m
University League
4h 28m
LiuLi Cup
5h 28m
Rogue vs TBD
Maru vs TBD
OSC
10h 28m
Replay Cast
17h 28m
GSL
1d 5h
Maru vs Dark
Patches Events
1d 8h
OSC
1d 10h
Replay Cast
1d 17h
KCM Race Survival
2 days
[ Show More ]
Ultimate Battle
2 days
ZerO vs Bisu
RSL Revival
3 days
BSL
3 days
eOnzErG vs StRyKeR
Cross vs JDConan
RSL Revival
4 days
IPSL
4 days
Ret vs ggnore13
nOmaD vs Aether
BSL
4 days
Bonyth vs Doodle
Kyrie vs Jimin
Replay Cast
4 days
WardiTV Weekly
5 days
Kung Fu Cup
6 days
Solar vs Classic
ByuN vs SHIN
PiGosaur Cup
6 days
Liquipedia Results

Completed

Proleague 2026-11-16
Blizzard Classic Cup 2026
HCC Season 3

Ongoing

Acropolis #5
KCM Race Survival 2026 Season 4
International ShieldBattery League
BSL Season 23
IPSL Winter 2026-27
Calamity Cup Div. A Season 8
Underdog Cup 2026 Div 2-3
Stake Ranked Episode 6
BLAST Rivals Fall 2026
IEM Beijing 2026
PGL Masters Bucharest 2026
Stake Ranked Episode 5
1win Private Club #2
Thunderpick World Champ. '26
ESL Pro League Season 24
Stake Ranked Episode 4
1win Private Club #1
Logitech G Play Connect 2026
SL StarSeries Fall 2026
FISSURE Playground #3
BLAST Open Fall 2026

Upcoming

Sector 591
YSL S4
SC4ALL II: Brood War
NBSL 2026 Xiamen LAN
BSL 23: Non-Korean Championship
HSC XXX
Stellar Fest 2: Lunar Cup
StarCraft2 Weekly Open Tournament 2026 Grand Finals
SC4ALL II: StarCraft II
Kung Fu Cup 2026 Grand Finals
RSL Offline Finals
IEM Kraków 2027
PGL Bucharest 2027
BLAST Bounty Winter 2027
PGL Major Singapore 2026
TLPD

1. ByuN
2. TY
3. Dark
4. Solar
5. Stats
6. Nerchio
7. sOs
8. soO
9. INnoVation
10. Elazer
1. Rain
2. Flash
3. EffOrt
4. Last
5. Bisu
6. Soulkey
7. Mini
8. Sharp
Sidebar Settings...

Advertising | Privacy Policy | Terms Of Use | Contact Us

Original banner artwork: Jim Warren
The contents of this webpage are copyright © 2026 TLnet. All Rights Reserved.