• Log InLog In
  • Register
Liquid`
Team Liquid Liquipedia
EST 08:31
CET 14:31
KST 22:31
  • 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
RSL Season 3 - Playoffs Preview0RSL Season 3 - RO16 Groups C & D Preview0RSL Season 3 - RO16 Groups A & B Preview2TL.net Map Contest #21: Winners12Intel X Team Liquid Seoul event: Showmatches and Meet the Pros10
Community News
BGE Stara Zagora 2026 announced12[BSL21] Ro.16 Group Stage (C->B->A->D)4Weekly Cups (Nov 17-23): Solar, MaxPax, Clem win3RSL Season 3: RO16 results & RO8 bracket13Weekly Cups (Nov 10-16): Reynor, Solar lead Zerg surge2
StarCraft 2
General
BGE Stara Zagora 2026 announced SC: Evo Complete - Ranked Ladder OPEN ALPHA When will we find out if there are more tournament Weekly Cups (Nov 17-23): Solar, MaxPax, Clem win Weekly Cups (Nov 10-16): Reynor, Solar lead Zerg surge
Tourneys
Constellation Cup - Main Event - Stellar Fest RSL Revival: Season 3 Tenacious Turtle Tussle [Alpha Pro Series] Nice vs Cure $5,000+ WardiTV 2025 Championship
Strategy
Custom Maps
Map Editor closed ?
External Content
Mutation # 501 Price of Progress Mutation # 500 Fright night Mutation # 499 Chilling Adaptation Mutation # 498 Wheel of Misfortune|Cradle of Death
Brood War
General
BW General Discussion BGH Auto Balance -> http://bghmmr.eu/ A cwal.gg Extension - Easily keep track of anyone Which season is the best in ASL? soO on: FanTaSy's Potential Return to StarCraft
Tourneys
[Megathread] Daily Proleagues [BSL21] RO16 Group B - Sunday 21:00 CET [BSL21] RO16 Group C - Saturday 21:00 CET Small VOD Thread 2.0
Strategy
Game Theory for Starcraft How to stay on top of macro? Current Meta PvZ map balance
Other Games
General Games
Nintendo Switch Thread The Perfect Game Stormgate/Frost Giant Megathread Beyond All Reason Should offensive tower rushing be viable in RTS games?
Dota 2
Official 'what is Dota anymore' discussion
League of Legends
Heroes of the Storm
Simple Questions, Simple Answers Heroes of the Storm 2.0
Hearthstone
Deck construction bug Heroes of StarCraft mini-set
TL Mafia
Mafia Game Mode Feedback/Ideas TL Mafia Community Thread
Community
General
Russo-Ukrainian War Thread US Politics Mega-thread The Big Programming Thread Things Aren’t Peaceful in Palestine Artificial Intelligence Thread
Fan Clubs
White-Ra Fan Club
Media & Entertainment
[Manga] One Piece Movie Discussion! Anime Discussion Thread
Sports
2024 - 2026 Football Thread Formula 1 Discussion NBA General Discussion MLB/Baseball 2023 TeamLiquid Health and Fitness Initiative For 2023
World Cup 2022
Tech Support
Computer Build, Upgrade & Buying Resource Thread
TL Community
Where to ask questions and add stream? The Automated Ban List
Blogs
Esports Earnings: Bigger Pri…
TrAiDoS
Thanks for the RSL
Hildegard
Saturation point
Uldridge
DnB/metal remix FFO Mick Go…
ImbaTosS
Customize Sidebar...

Website Feedback

Closed Threads



Active: 2508 users

Japanese language

Blogs > Rus_Brain
Post a Reply
1 2 Next All
Rus_Brain
Profile Blog Joined June 2006
Russian Federation1893 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
Germany2581 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 Federation1893 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
WardiTV Korean Royale
12:00
Playoffs
SHIN vs ReynorLIVE!
TBD vs herO
Solar vs TBD
WardiTV984
TKL 357
IndyStarCraft 241
Rex136
Liquipedia
[ Submit Event ]
Live Streams
Refresh
StarCraft 2
TKL 357
IndyStarCraft 241
Reynor 233
Rex 136
MindelVK 29
StarCraft: Brood War
Britney 61128
Sea 9412
Rain 2392
Horang2 1549
Soma 724
actioN 671
BeSt 568
Larva 567
firebathero 410
Rush 285
[ Show more ]
hero 251
Last 170
Barracks 155
Hyun 135
zelot 107
Sharp 96
Mong 84
JYJ51
Sea.KH 44
sorry 44
Noble 31
Shinee 25
ajuk12(nOOB) 20
Terrorterran 18
IntoTheRainbow 11
Dota 2
Gorgc5234
singsing2595
XcaliburYe361
Counter-Strike
x6flipin734
zeus379
Other Games
B2W.Neo1882
crisheroes290
Fuzer 278
DeMusliM242
Hui .231
KnowMe29
Organizations
Other Games
gamesdonequick768
StarCraft 2
CranKy Ducklings183
Dota 2
PGL Dota 2 - Main Stream104
StarCraft: Brood War
CasterMuse 31
StarCraft 2
Blizzard YouTube
StarCraft: Brood War
BSLTrovo
sctven
[ Show 14 non-featured ]
StarCraft 2
• AfreecaTV YouTube
• intothetv
• Kozan
• IndyKCrew
• LaughNgamezSOOP
• Migwel
• sooper7s
StarCraft: Brood War
• blackmanpl 41
• Michael_bg 2
• BSLYoutube
• STPLYoutube
• ZZZeroYoutube
Dota 2
• WagamamaTV608
League of Legends
• Jankos3197
Upcoming Events
3D!Clan Event
29m
3DClanTV 52
BSL 21
6h 29m
Hawk vs Kyrie
spx vs Cross
Replay Cast
10h 29m
Wardi Open
22h 29m
Monday Night Weeklies
1d 3h
StarCraft2.fi
1d 3h
Replay Cast
1d 10h
Wardi Open
1d 22h
StarCraft2.fi
2 days
PiGosaur Monday
2 days
[ Show More ]
Wardi Open
2 days
StarCraft2.fi
3 days
Replay Cast
3 days
The PondCast
3 days
Replay Cast
4 days
Korean StarCraft League
5 days
CranKy Ducklings
5 days
SC Evo League
5 days
BSL 21
6 days
Sziky vs OyAji
Gypsy vs eOnzErG
Sparkling Tuna Cup
6 days
Liquipedia Results

Completed

Proleague 2025-11-28
RSL Revival: Season 3
Eternal Conflict S1

Ongoing

C-Race Season 1
IPSL Winter 2025-26
KCM Race Survival 2025 Season 4
YSL S2
BSL Season 21
CSCL: Masked Kings S3
Slon Tour Season 2
META Madness #9
SL Budapest Major 2025
ESL Impact League Season 8
BLAST Rivals Fall 2025
IEM Chengdu 2025
PGL Masters Bucharest 2025
Thunderpick World Champ.
CS Asia Championships 2025
ESL Pro League S22
StarSeries Fall 2025
FISSURE Playground #2

Upcoming

BSL 21 Non-Korean Championship
Acropolis #4
IPSL Spring 2026
Bellum Gens Elite Stara Zagora 2026
HSC XXVIII
RSL Offline Finals
WardiTV 2025
Kuram Kup
PGL Cluj-Napoca 2026
IEM Kraków 2026
BLAST Bounty Winter 2026
BLAST Bounty Winter 2026: Closed Qualifier
eXTREMESLAND 2025
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 © 2025 TLnet. All Rights Reserved.