資源s - 令状/Edit for Hentzenwerke

Wanna 令状 or edit a 調書をとる／予約する? Here's all you need to know about how the publishing 過程 作品 here.

• About HWP
• The Publishing 商売／仕事
• The 過程 at HWP
• 提案するing a 調書をとる／予約する
• The 契約
• Getting Paid
• Doing the 令状ing and Editing
• Source Code
• Ebook Stuff
• Our Covers
• Going to 圧力（をかける）
• Marketing
• 令状ing Whitepapers
• So You Want to be an Author
• So You Want to be a Tech Editor
• The HWP Author 道具

提案するing a 調書をとる／予約する

The idea

Some of the time, I have an idea for a 調書をとる／予約する. This idea may come up from something I've run into in my own day-to-day work as a developer, or from something I read online, or even from a conversation with someone. In any 事例／患者, I'll 草案 a "使節団 声明" for the 調書をとる／予約する - two to four 宣告，判決s that 逮捕（する）s "What's in it for me?" from the point of the reader. I'll also 述べる who the ーするつもりであるd reader is, 名簿（に載せる）／表（にあげる） ideas for the content, and perhaps sketch out a very rough 草案 of an 輪郭（を描く）.

In other 事例／患者s, a 見込みのある author will have an idea and come to me to publish their 調書をとる／予約する. When they come to me, it’s usually very casually, 問い合わせing about a general topic, along the lines of a two-paragraph email. This is usually a good idea, since you wouldn’t want to spend a lot of time on a 提案 only to find that someone else had beaten you to the punch.

The author or authors

At this point, if it's my idea, I'll search for an author. いつかs I have an idea for a 可能性のある author because I already know someone with the 技術 始める，決める needed for the topic in question, or because I’ve spoken to someone who has 表明するd 利益／興味 in that topic. Other times I'll put out feelers for new prospects. And still other times I'll look through my 名簿（に載せる）／表（にあげる） of people who have 接触するd me in the past and who have 示すd they'd be 利益／興味d in 令状ing, but don't have a 明確な／細部 topic in mind.

Of course, if an author has already pitched an idea to me, that part is settled. I will never take an author's idea and give it to someone else unless the author willingly gives it up, or commits to it and then 繰り返して shows that they're unable to 会合，会う that committment.

Occasionally an author will not want to 請け負う an entire 調書をとる／予約する by themselves, either because they don't have the time to do the whole 調書をとる／予約する by themselves, or because they don't feel comfortable with some of the 支配する 事柄. They may want me to approach someone to be a co-author, or may have already 麻薬中毒の up with someone before pitching the idea to me.

If 利益／興味d, we’ll go 支援する and 前へ／外へ about the idea as I have them flesh out their idea in greater and greater 詳細（に述べる）, and they ask questions that aren’t answered here. The goal is for the author(s) to 現在の a 提案 for the 調書をとる／予約する to me.

The 提案

A 提案 is a 文書 that does two things - (1) sells me on the 調書をとる／予約する, and (2) 供給するs me with （警察などへの）密告，告訴（状） that I can use to sell my 顧客s - both my distributors and resellers 同様に as people who come 直接／まっすぐに to our website.

A 見本 提案 is 含むd in the Author 道具 here. It 含むs （警察などへの）密告，告訴（状） about what's going in the 調書をとる／予約する as 井戸／弁護士席 as who the 的 audience is. The 提案 also 含むs an 輪郭（を描く） and a schedule. If more than one person is 伴う／関わるd in 令状ing the 調書をとる／予約する, one of the authors 伴う／関わるd will need to take the 主要な 役割 in the 調書をとる／予約する. The lead author is responsible for 調整するing the work between the other authors and the tech editor 同様に as 配達するing 一時期／支部s to me.

Once the author (or authors) has been selected and agreed that they'd like to do the 調書をとる／予約する, it's time to get 負かす／撃墜する to the guts of the 提案 - the 輪郭（を描く） and schedule of 令状ing. The 輪郭（を描く） is essentially a （米）棚上げする／（英）提議する of contents fleshed out to the first 始める，決める of major headings - in other words, a 名簿（に載せる）／表（にあげる） of 一時期／支部s and major topics to be covered in each 一時期／支部. Having an abstract (one to two paragraphs) for each 一時期／支部 is really a good idea at this point, but not 要求するd.

The schedule is the 名簿（に載せる）／表（にあげる） of dates that the author will 配達する final 一時期／支部s to me for copy edit. I'll explain what has to be done ーするために 配達する a 一時期／支部 ready for copy edit in the "Doing the 令状ing and Editing" section. The point now is that the author has to commit to 配達するing 一時期／支部s of their 調書をとる／予約する on a 正規の／正選手 schedule, taking into account their work schedule, family かかわり合いs, traveling or vacations, and 一般に how much of a life they want to have during the 令状ing. And the 構成要素 they 配達する is 推定する／予想するd to be “done” ? ready for copy edit, review, and then layout into pages that will be printed. There’s no room for “Still need to 研究 this その上の” comments in 構成要素 submitted for copy edit.

The lead author and tech editor both are 要求するd to 服従させる／提出する a 進歩 報告（する）／憶測 each week. 失敗 to do so will have an 逆の 影響する／感情 on the 収入s of the person who fails to 服従させる／提出する their 報告（する）／憶測s on time.

While the author wants to 配達する their 調書をとる／予約する as soon as possible - so that we can start selling it - it's a bad idea for an author to commit themselves to a schedule that they may not be able to 会合，会う. It's best for an author to give themselves some wiggle room so that they can 会合，会う each 最終期限 they 始める，決める. I've become 意味ありげに いっそう少なく 許すing about 行方不明の 最終期限s over the past year. If an author 予知するs 可能性のある 問題／発行するs getting in the way, they should 会社にする／組み込む extra time in your schedule. One can always 配達する 一時期／支部s 早期に!

The 残り／休憩（する） of the players

Assuming that I 受託する the 提案 submitted to me, it's now time to flesh out the 残り／休憩（する） of the 乗組員. The next player is the Tech Editor.

Here is are the 明確な／細部 必要物／必要条件s of the tech editor:

1. Review each 一時期／支部 as it arrives from the author for technical correctness.
2. Review source code to make sure that (1) it runs, (2) it matches the code in the 調書をとる／予約する, or, if bugs are 設立する in the code after the 調書をとる／予約する ships, that appropriate について言及する is made (we have errata pages on our website).
3. Return 一時期／支部s 7 days after 領収書 from the author.

As a practical 事柄, the 量 of interaction between tech editor and author 変化させるs によれば the 調書をとる／予約する. Some authors have a 見通し and they roll straight ahead, 簡単に turning over finished 一時期／支部s to their tech editor. Other authors prefer to 共同製作する with their tech editor more, asking for their input about how to go about something. And, some tech editors are more merciless than others, requesting that the author 令状 and rewrite - we recently had a 事例／患者 where an entire 20 page 一時期／支部 was 事実上 thrown out by the tech editor.

The 底（に届く） line is that the 調書をとる／予約する has to be 広大な／多数の／重要な. It's the author's 責任／義務 to make that happen, but it's the tech editor's 責任／義務 to make sure that the author doesn't (inadvertently or 故意に) slide crap into the 調書をとる／予約する. The tech editor doesn't have to make the 是正s; he just has to yell STOP THE PRESSES! Remember that the tech editor gets their 指名する on the cover of the 調書をとる／予約する too.

I may have someone in mind, but I'll also ask the author if they have someone in mind. This conversation 現実に usually begins while the 調書をとる／予約する 提案 is 存在 fleshed out ? so that the 調書をとる／予約する doesn’t get held up or 発射 負かす／撃墜する because of the 欠如（する） of a tech editor. Depending on who （機の）カム up with the idea in the first place, the 重荷（を負わせる） is usually on the author to do most of the legwork here. They're probably more familiar with the 明確な／細部 area in question than I am (hey, if they're going to 令状 a 調書をとる／予約する, they'd better be!), and thus would very likely have better 接触するs.

I like to have people who are 明白な in the appropriate community to be 伴う／関わるd in the 調書をとる／予約する. It 供給するs 信用性 to the 調書をとる／予約する 同様に as a bit of 'marketing oompf.' (Even if they don't 促進する the 調書をとる／予約する themselves, others will do so.) And if they're 明白な in the community, then they かもしれない will be better 知らせるd, since 存在 online often affords them （危険などに）さらす to a wide 範囲 of viewpoints.

I 扱う the other folks 伴う／関わるd, 含むing copy edit, layout, ebook 生産／産物, 索引ing, artists, and so on.

Now it's time for 契約s.

支援する to 最高の，を越す