Should 私の be omitted?What are the guidelines of omitting particles?Is there something omitted after だか in this sentence?Emphatic / Focus loss upon translating between active and passive sentences?Can volitional form mean 'you should …'Should it be のにです or ですのに when stating an omitted 2nd sentence in polite sentence?Is the causative-passive necessary hereHow should I translate “It was the most horrible time of my life”?creating a question given a responseIs a sentence ending with “か……。” a question or a questionative statement?
How often to check credit card statement
Why do 可不 and 可不是 by themselves imply agreement?
Totally Blind Chess
Is it possible to be admitted to CS PhD programs (in US) with scholarship at age 18?
Query on paper on entanglement in graph states
What factors do we need to consider in order to enable auto-growth settings for my PROD database
In what way were Renaissance battles like chess matches?
What are valid bugs
How to check if python package is latest version programmatically?
Washing the skin of a dead rat
Which Formula One races did Scuderia Ferrari not take part in?
Hikers in Halloween
Installing a patio door...why does the entire frame have to be square, level and plumb?
ASCII Pumpkin Carving
Why is Google's quantum supremacy experiment impressive?
Is there a systematic theory for Gibbs measures (better if on Hilbert spaces)?
How to deal with a 6 year old who was "caught" cheating?
Is this bible in Koine Greek?
Security risks of user generated HTML?
Can I be a pilot if I'm emotionally numb?
Teleportation is invented but it has nasty side-effects % of the time, how will that affect usage of the technology?
Gold plating versus Silver plating for electrical contacts?
A Caesar cipher in Python3
How does an all-female medieval country maintain itself?
Should 私の be omitted?
What are the guidelines of omitting particles?Is there something omitted after だか in this sentence?Emphatic / Focus loss upon translating between active and passive sentences?Can volitional form mean 'you should …'Should it be のにです or ですのに when stating an omitted 2nd sentence in polite sentence?Is the causative-passive necessary hereHow should I translate “It was the most horrible time of my life”?creating a question given a responseIs a sentence ending with “か……。” a question or a questionative statement?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
.everyonelovesstackoverflowposition:absolute;height:1px;width:1px;opacity:0;top:0;left:0;pointer-events:none;
I have the following sentence on my Japanese LinkedIn page:
私 の 目的 は 主導 と 代表的 な 執行 と 技術革新 通じて 例外的 な 質 を 生むて います。
It is meant to mirror my English mission statement:
"My mission is to deliver exceptional value through leadership, outstanding performance, and innovation."
My question is, should 私の be omitted?
grammar translation sentence ellipsis first-person-pronouns
add a comment
|
I have the following sentence on my Japanese LinkedIn page:
私 の 目的 は 主導 と 代表的 な 執行 と 技術革新 通じて 例外的 な 質 を 生むて います。
It is meant to mirror my English mission statement:
"My mission is to deliver exceptional value through leadership, outstanding performance, and innovation."
My question is, should 私の be omitted?
grammar translation sentence ellipsis first-person-pronouns
add a comment
|
I have the following sentence on my Japanese LinkedIn page:
私 の 目的 は 主導 と 代表的 な 執行 と 技術革新 通じて 例外的 な 質 を 生むて います。
It is meant to mirror my English mission statement:
"My mission is to deliver exceptional value through leadership, outstanding performance, and innovation."
My question is, should 私の be omitted?
grammar translation sentence ellipsis first-person-pronouns
I have the following sentence on my Japanese LinkedIn page:
私 の 目的 は 主導 と 代表的 な 執行 と 技術革新 通じて 例外的 な 質 を 生むて います。
It is meant to mirror my English mission statement:
"My mission is to deliver exceptional value through leadership, outstanding performance, and innovation."
My question is, should 私の be omitted?
grammar translation sentence ellipsis first-person-pronouns
grammar translation sentence ellipsis first-person-pronouns
edited Jun 26 at 21:56
Eiríkr Útlendi
22.5k1 gold badge41 silver badges76 bronze badges
22.5k1 gold badge41 silver badges76 bronze badges
asked Jun 26 at 20:22
Mike ShanahanMike Shanahan
928 bronze badges
928 bronze badges
add a comment
|
add a comment
|
1 Answer
1
active
oldest
votes
Since this is a formal statement, it's better to keep 私の. But people can understand the sentence without it because they know it's your profile.
What's worse about your sentence is that your sentence has a number of bad word choices and grammatical errors.
- 生むています is always ungrammatical. The te-form of 生む is 生んで.
- There is a subject-predicate mismatch. 私の目的は生んでいます is "My mission is (in the process of) producing something" rather than "My mission is to produce something". You have to nominalize 生む.
- 主導 refers to an act of leading, but it does not refer to an ability to take a lead role.
- 代表的な執行 sounds like "representative execution" rather than "outstanding performance".
- 例外的な does not have a positive connotation like that of "exceptional". 例外的な質 sounds like "peculiar quality" rather than "exceptional value".
- 通じて needs a particle を.
- (EDIT) This is a relatively minor problem, but consider using 目標 instead of 目的. The former refers to a long-term mission/goal, whereas the latter is closer to "purpose".
A corrected version is something like:
私の目標はリーダーシップ、高いパフォーマンス、イノベーションを通じて卓越した価値を生み出すことです。
Or if you don't like katakana loanwords, an alternative free translation would be:
私の目標は、指導力・実行力・革新力を通じて卓越した価値を生み出すことです。
3
I feel that this "exceptional" translates into 卓越した or 真似のできない.
– broccoli forest
Jun 27 at 3:35
@broccoliforest Yes that's better, thank you.
– naruto
Jun 27 at 4:30
Holy moly! Thank you so very much! I wish I could upvote multiple times! Thank you thank you!
– Mike Shanahan
Jun 27 at 9:43
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "257"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fjapanese.stackexchange.com%2fquestions%2f69108%2fshould-%25e7%25a7%2581%25e3%2581%25ae-be-omitted%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Since this is a formal statement, it's better to keep 私の. But people can understand the sentence without it because they know it's your profile.
What's worse about your sentence is that your sentence has a number of bad word choices and grammatical errors.
- 生むています is always ungrammatical. The te-form of 生む is 生んで.
- There is a subject-predicate mismatch. 私の目的は生んでいます is "My mission is (in the process of) producing something" rather than "My mission is to produce something". You have to nominalize 生む.
- 主導 refers to an act of leading, but it does not refer to an ability to take a lead role.
- 代表的な執行 sounds like "representative execution" rather than "outstanding performance".
- 例外的な does not have a positive connotation like that of "exceptional". 例外的な質 sounds like "peculiar quality" rather than "exceptional value".
- 通じて needs a particle を.
- (EDIT) This is a relatively minor problem, but consider using 目標 instead of 目的. The former refers to a long-term mission/goal, whereas the latter is closer to "purpose".
A corrected version is something like:
私の目標はリーダーシップ、高いパフォーマンス、イノベーションを通じて卓越した価値を生み出すことです。
Or if you don't like katakana loanwords, an alternative free translation would be:
私の目標は、指導力・実行力・革新力を通じて卓越した価値を生み出すことです。
3
I feel that this "exceptional" translates into 卓越した or 真似のできない.
– broccoli forest
Jun 27 at 3:35
@broccoliforest Yes that's better, thank you.
– naruto
Jun 27 at 4:30
Holy moly! Thank you so very much! I wish I could upvote multiple times! Thank you thank you!
– Mike Shanahan
Jun 27 at 9:43
add a comment
|
Since this is a formal statement, it's better to keep 私の. But people can understand the sentence without it because they know it's your profile.
What's worse about your sentence is that your sentence has a number of bad word choices and grammatical errors.
- 生むています is always ungrammatical. The te-form of 生む is 生んで.
- There is a subject-predicate mismatch. 私の目的は生んでいます is "My mission is (in the process of) producing something" rather than "My mission is to produce something". You have to nominalize 生む.
- 主導 refers to an act of leading, but it does not refer to an ability to take a lead role.
- 代表的な執行 sounds like "representative execution" rather than "outstanding performance".
- 例外的な does not have a positive connotation like that of "exceptional". 例外的な質 sounds like "peculiar quality" rather than "exceptional value".
- 通じて needs a particle を.
- (EDIT) This is a relatively minor problem, but consider using 目標 instead of 目的. The former refers to a long-term mission/goal, whereas the latter is closer to "purpose".
A corrected version is something like:
私の目標はリーダーシップ、高いパフォーマンス、イノベーションを通じて卓越した価値を生み出すことです。
Or if you don't like katakana loanwords, an alternative free translation would be:
私の目標は、指導力・実行力・革新力を通じて卓越した価値を生み出すことです。
3
I feel that this "exceptional" translates into 卓越した or 真似のできない.
– broccoli forest
Jun 27 at 3:35
@broccoliforest Yes that's better, thank you.
– naruto
Jun 27 at 4:30
Holy moly! Thank you so very much! I wish I could upvote multiple times! Thank you thank you!
– Mike Shanahan
Jun 27 at 9:43
add a comment
|
Since this is a formal statement, it's better to keep 私の. But people can understand the sentence without it because they know it's your profile.
What's worse about your sentence is that your sentence has a number of bad word choices and grammatical errors.
- 生むています is always ungrammatical. The te-form of 生む is 生んで.
- There is a subject-predicate mismatch. 私の目的は生んでいます is "My mission is (in the process of) producing something" rather than "My mission is to produce something". You have to nominalize 生む.
- 主導 refers to an act of leading, but it does not refer to an ability to take a lead role.
- 代表的な執行 sounds like "representative execution" rather than "outstanding performance".
- 例外的な does not have a positive connotation like that of "exceptional". 例外的な質 sounds like "peculiar quality" rather than "exceptional value".
- 通じて needs a particle を.
- (EDIT) This is a relatively minor problem, but consider using 目標 instead of 目的. The former refers to a long-term mission/goal, whereas the latter is closer to "purpose".
A corrected version is something like:
私の目標はリーダーシップ、高いパフォーマンス、イノベーションを通じて卓越した価値を生み出すことです。
Or if you don't like katakana loanwords, an alternative free translation would be:
私の目標は、指導力・実行力・革新力を通じて卓越した価値を生み出すことです。
Since this is a formal statement, it's better to keep 私の. But people can understand the sentence without it because they know it's your profile.
What's worse about your sentence is that your sentence has a number of bad word choices and grammatical errors.
- 生むています is always ungrammatical. The te-form of 生む is 生んで.
- There is a subject-predicate mismatch. 私の目的は生んでいます is "My mission is (in the process of) producing something" rather than "My mission is to produce something". You have to nominalize 生む.
- 主導 refers to an act of leading, but it does not refer to an ability to take a lead role.
- 代表的な執行 sounds like "representative execution" rather than "outstanding performance".
- 例外的な does not have a positive connotation like that of "exceptional". 例外的な質 sounds like "peculiar quality" rather than "exceptional value".
- 通じて needs a particle を.
- (EDIT) This is a relatively minor problem, but consider using 目標 instead of 目的. The former refers to a long-term mission/goal, whereas the latter is closer to "purpose".
A corrected version is something like:
私の目標はリーダーシップ、高いパフォーマンス、イノベーションを通じて卓越した価値を生み出すことです。
Or if you don't like katakana loanwords, an alternative free translation would be:
私の目標は、指導力・実行力・革新力を通じて卓越した価値を生み出すことです。
edited Jun 27 at 11:27
answered Jun 27 at 0:26
narutonaruto
191k9 gold badges201 silver badges383 bronze badges
191k9 gold badges201 silver badges383 bronze badges
3
I feel that this "exceptional" translates into 卓越した or 真似のできない.
– broccoli forest
Jun 27 at 3:35
@broccoliforest Yes that's better, thank you.
– naruto
Jun 27 at 4:30
Holy moly! Thank you so very much! I wish I could upvote multiple times! Thank you thank you!
– Mike Shanahan
Jun 27 at 9:43
add a comment
|
3
I feel that this "exceptional" translates into 卓越した or 真似のできない.
– broccoli forest
Jun 27 at 3:35
@broccoliforest Yes that's better, thank you.
– naruto
Jun 27 at 4:30
Holy moly! Thank you so very much! I wish I could upvote multiple times! Thank you thank you!
– Mike Shanahan
Jun 27 at 9:43
3
3
I feel that this "exceptional" translates into 卓越した or 真似のできない.
– broccoli forest
Jun 27 at 3:35
I feel that this "exceptional" translates into 卓越した or 真似のできない.
– broccoli forest
Jun 27 at 3:35
@broccoliforest Yes that's better, thank you.
– naruto
Jun 27 at 4:30
@broccoliforest Yes that's better, thank you.
– naruto
Jun 27 at 4:30
Holy moly! Thank you so very much! I wish I could upvote multiple times! Thank you thank you!
– Mike Shanahan
Jun 27 at 9:43
Holy moly! Thank you so very much! I wish I could upvote multiple times! Thank you thank you!
– Mike Shanahan
Jun 27 at 9:43
add a comment
|
Thanks for contributing an answer to Japanese Language Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fjapanese.stackexchange.com%2fquestions%2f69108%2fshould-%25e7%25a7%2581%25e3%2581%25ae-be-omitted%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown