• Log InLog In
  • Register
Liquid`
Team Liquid Liquipedia
EDT 01:15
CEST 07:15
KST 14:15
  • 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
[ASL22] Ro24 Preview: Siren's Call8[ASL22] Ro24 Preview: Summer's End9Serral wins HomeStory Cup 2915Serral wins Maestros of the Game 244ByuL, and the Limitations of Standard Play3
Community News
New 3v3 BGH Ladder (and more) on ShieldBattery!35Weekly Cups (August 17-23): Zerg dominate the week6Weekly Cups (August 10-16): SHIN doubles2GSTL Returns in 2026!45Weekly Cups (Aug 3-9): Protoss get shut out7
StarCraft 2
General
SC4ALL II: SC2 Player Announcement 6/8 - Maru How would you feel about frequent/monthly balance patches for SC2? Weekly Cups (August 17-23): Zerg dominate the week Daily SC2 Player Grid - feedback wanted Balance hotfix patch 5.0.16b (July 16)
Tourneys
Sparkling Tuna Cup - Weekly Open Tournament 2026 GSTL Announcement IntoTheTV X SOOP SC2 League : Weekly & Monthly PIG STY FESTIVAL 8.0! (13 - 23 August) WORTEX 2026 - Hungarian SC2 Finals Budapest
Strategy
[G] Having the right mentality to improve
Custom Maps
Nexus Wars 2021 GUIDE [M] (2) Industrial Park
External Content
Mutation # 541 Binary Choice The PondCast: SC2 News & Results Mutation # 540 Dodge This Mutation # 539 Thunder Dome
Brood War
General
New 3v3 BGH Ladder (and more) on ShieldBattery! ASL22 General Discussion BW General Discussion Pros React To: Calm's Big Brain Play Vs Mini [Personal Project Share] Terran Defense v0.60
Tourneys
[ASL22] Ro24 Group F [Megathread] Daily Proleagues BSL LAN Party - Kraków 29-30 August - OPEN SIGNUPS Escore Tournament - Season 3
Strategy
Replay Review Process - What do you do? Game Theory for Starcraft Odyssey Mineral Stack Saturation Fighting Spirit mining rates
Other Games
General Games
Nintendo Switch Thread Stormgate/Frost Giant Megathread General RTS Discussion Thread Anyone here play Quakeworld back in the day? EVE Corporation
Dota 2
Browser Invoker Combo Trainer & Speedrun Simulator Official 'what is Dota anymore' discussion
League of Legends
[TL LoL EUW IHs] Teemo shall perish TSM pausing esports and CLG Dead
Heroes of the Storm
Heroes of the Storm 2.0
Hearthstone
Deck construction bug
TL Mafia
TL Mafia Power Rank TL Mafia Community Thread NeO.D_StephenKing vs This Guy From 1 Million Dance
Community
General
Things Aren’t Peaceful in Palestine US Politics Mega-thread Russo-Ukrainian War Thread European Politico-economics QA Mega-thread The Letting Off Steam Thread
Fan Clubs
MarineLorD Fan Club The Creator Fan Club The ShoWTimE Fan Club
Media & Entertainment
Movie Discussion! Anime Discussion Thread
Sports
Football (Soccer) Thread TeamLiquid Health and Fitness Initiative For 2023 MLB/Baseball 2023 NBA General Discussion
World Cup 2022
Tech Support
Computer Build, Upgrade & Buying Resource Thread
TL Community
The Automated Ban List Northern Ireland Global Starcraft
Blogs
Regacy Esports: The Bh…
regacyesports
Violent Games and Crime Rate…
TrAiDoS
LOCKPICKING NOOB
LUCKY_NOOB
Cathedral Of CS And NY pizza a…
FuDDx
Please support my new stand…
Peanutsc
Customize Sidebar...

Website Feedback

Closed Threads



Active: 8220 users

Japanese language

Blogs > Rus_Brain
Post a Reply
Normal
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
Germany2597 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.
AmericanUmlaut
Profile Blog Joined November 2010
Germany2597 Posts
March 29 2012 20:45 GMT
#21
On March 30 2012 02:00 Tobberoth wrote:
Show nested quote +
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.

Oops, that was a horrible brain fart. You're right, of course .
The frumious Bandersnatch
Sickkiee
Profile Blog Joined May 2011
Japan607 Posts
March 29 2012 23:52 GMT
#22
Remember that even if it sounds polite or business-like to you, it may not sound the same to us.

T_T
Lifes too short to be small.
Gurpreet_Singh
Profile Joined December 2021
1 Post
December 04 2021 11:12 GMT
#23
--- Nuked ---
Normal
Please log in or register to reply.
Live Events Refresh
Next event in 4h 45m
[ Submit Event ]
Live Streams
Refresh
StarCraft 2
summit1g6741
WinterStarcraft554
NeuroSwarm 149
ProTech117
StarCraft: Brood War
Britney 27877
GuemChi 2195
actioN 659
Bale 114
Noble 30
Icarus 7
League of Legends
JimRising 737
Super Smash Bros
Mew2King48
Other Games
Livibee161
Maynarde123
RuFF_SC280
[ Show 11 non-featured ]
StarCraft 2
• AfreecaTV YouTube
• intothetv
• Kozan
• IndyKCrew
• Migwel
StarCraft: Brood War
• Light_VIP 66
• BSLYoutube
• STPLYoutube
• ZZZeroYoutube
League of Legends
• Lourlo1118
• Rush963
Upcoming Events
Sparkling Tuna Cup
4h 45m
Afreeca Starleague
4h 45m
Monday Night Weeklies
10h 45m
GSL
1d 5h
OSC
1d 7h
PiGosaur Cup
1d 18h
Kung Fu Cup
2 days
Replay Cast
2 days
The PondCast
3 days
IntoTheTV X SOOP
4 days
[ Show More ]
CranKy Ducklings
5 days
Sparkling Tuna Cup
6 days
OSC
6 days
Liquipedia Results

Completed

BSL 2026 LAN: Kraków
PiG Sty Festival 8.0
Light Tournament 2026

Ongoing

KCM Race Survival 2026 Season 3
K-JUNGMAN
ASL Season 22
Super Anchor Qualifying S3
CSL Season 22: Qualifier 2
RSL Revival: Season 6
Big Dog Cup 2026 Div 1
BLAST Open Fall 2026
Esports World Cup 2026
Esports World Cup 2026: LCQ
BLAST Bounty Summer 2026
BLAST Bounty Summer Qual
Stake Ranked Episode 3
XSE Pro League 2026
IEM Cologne Major 2026

Upcoming

CSL 2026 AUTUMN (S22)
Escore Tournament S3: King of Kings
Acropolis #5
Acropolis #5 - TRS
Blizzard Classic Cup 2026
Acropolis #5 - GSA
Acropolis #5 - GSB
HSC XXX
SC4ALL II: StarCraft II
Kung Fu Cup 2026 Grand Finals
RSL Offline Finals
Calamity Invitational
BLAST Rivals Fall 2026
IEM Beijing 2026
Stake Ranked Episode 5
PGL Masters Bucharest 2026
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
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.