資源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 道具

Supposing that the 提案 and 契約s have been 受託するd and all, now it's time to 令状. All 令状ing is done in Microsoft Word. As of 中央の-2003, we've switched from Microsoft Word to OpenOffice.org's Writer. Authors and Editors are encouraged to use OOo 同様に - there are 見解／翻訳／版s for both Windows and Linux, but if you prefer to use Word, that's 承認する. We've been swapping とじ込み／提出するs 支援する and 前へ／外へ for nearly a year, and have 設立する very few problems.

We have a Style Guide and a Word template (part of the Hentzenwerke Author 道具) that you’ll use to create your 一時期／支部s. The link is at the end of this 文書.

Let's suppose the players are Al 小説家 and Andrea Writer (the authors), Terry 専門家技術者 (tech editor) and Carmen Careful (copy edit and layout), and the 調書をとる／予約する is called There's Something About Data (TSAD).

First thing that happens is that the authors create a 始める，決める of folders on their computer, like so:

BOOKS
   TSAD
      CHAPTERS
      SOURCECODE
         CH01
         CH02
         CH03

Source code for each 一時期／支部 goes in its own directory, while all of the 一時期／支部s for the 調書をとる／予約する go into the same directory. The 指名するing 条約 for the 一時期／支部 とじ込み／提出するs (explained in just a few moments) will 確実にする that everyone can keep the 一時期／支部s straight even after there are dozens of them in one directory.

Now on to the 令状ing.

1. Al creates a new DOC とじ込み／提出する using the Hentzenwerke Publishing .DOT template, turning 改正 示すs ON. Al 令状s the first 草案 of 一時期／支部 1 of the 調書をとる／予約する There's Something About Data, and 指名するs the とじ込み／提出する TSAD01_01AN.DOC. "TSAD01" stands for 一時期／支部 1 of the Data 調書をとる／予約する, while "01AN" stands for 改正 1 by Al 小説家. (公式文書，認める that the 改正 starts with a 主要な 無 "01", not just a 独房監禁 "1". This is because it 定期的に happens that 改正s go past 9, and then it's 平易な to lose 跡をつける of the most 現在の 見解／翻訳／版 because they're not 適切に alphabetized in とじ込み／提出する listings. This is important, folks!)

2. Al sends this first 草案 to me for a general review. The 目的 of this review is for me to look at the content and style of the 令状ing. As I've said before, I'm very, very picky about the 調書をとる／予約するs we produce, and having a pass at the 構成要素 this 早期に helps 少しのd out problems when it's easier to 直す／買収する，八百長をする them. This step is 特に helpful to new authors who are still learning the ropes as far as 令状ing. I'll also 公式文書，認める any problems with 尊敬（する）・点 to the style guide. I'll make annotations 同様に as 改正s in the text, 指名する the new とじ込み／提出するs TSAD01_02WH.DOC, and return it to Al. I try to get this とじ込み／提出する 支援する within a day; いつかs it takes two days.

3. Depending on the severity of the feedback, Al may 改訂する his work and return it to me for a second once-over (although, I guess, it wouldn't be a 'once over' then, would it?). This usually doesn't happen, but it's an 選択 利用できる to the author.

4. Once Al and I have finished our 支援する-and-前へ／外へ cycle, Al sends it to Andrea, 指名するd, for example, TSAD01_05AN. 

5. Andrea makes a copy of this とじ込み／提出する, 指名するing it TSAD01_06AW.DOC. She reviews the 一時期／支部, makes changes, asks questions, and so on. Sends it 支援する to Al. 

6. They go 支援する and 前へ／外へ a number of times, as many times as they feel they need to. Perhaps just once, perhaps a half dozen times or more. 

7. At some point, Al finally decides the 一時期／支部 is pretty darn good and calls it やめるs with the 支援する and 前へ／外へ 商売／仕事. Andrea is relieved to not have to listen to Al whine any more. Al 受託するs or 拒絶するs all 改正s as appropriate, 指名するs the とじ込み／提出する TSAD01_09AN.DOC, and sends it to Terry for tech edit. 公式文書，認める that at this point, the 文書 is 完全に clean of editing 公式文書，認めるs from both authors. In other words, the last author to have touched the 文書 受託するs all 改正s.

The only time this would not be true is if the 調書をとる／予約する is 存在 written during a beta cycle and an author needs to check on something in a 未来 解放（する） of the beta. In this 事例／患者, the author 示すs the item to come 支援する to like so:

     *\\\ Is this supposed to work like this? Check 支援する during beta 2///

8. Terry gets the とじ込み／提出する, makes a copy 指名するd TSAD01_10TT.DOC, and makes sure 改正s are ON again. Terry tech edits and returns the 一時期／支部 to Al.

9. Al and Terry might have a couple of go-arounds. Or they might not. At some point, Al will decide that the 一時期／支部 is DONE-DONE-DONE. He 受託するs or 拒絶するs all 改正s as appropriate, saves the 一時期／支部 as TSAD01_11AN.DOC, and sends a 完全に clean copy to Whil for copy edit. 

公式文書，認める that by this point, the 一時期／支部 should be perfectly (井戸／弁護士席, 承認する, 公正に／かなり 井戸／弁護士席) formatted. It doesn't have to be perfect, but the better it is, the いっそう少なく work has to be done in Layout, which will then help the author(s) make more money in the long run.

Important: Also 公式文書，認める that Al, Andrea, and Terry are all submitted 週刊誌 status 報告（する）／憶測s to Whil using the status 報告（する）／憶測 form 設立する in the Hentzenwerke Author 道具 at the end of this 文書. It is 批判的な that each author and editor communicate with me on a 週刊誌 basis about the 進歩 (or 欠如（する） thereof) they're making against their schedule. The very fastest way to get on my bad 味方する is to fail to 報告（する）／憶測 in once a week. Occasionally an author 落ちるs behind, and feels that by hiding, they'll somehow become invisible. Bad idea. Really bad idea.

10. Whil sends the 一時期／支部 to Carmen for copy edit. Her 責任／義務 is to turn the author's 文書 into finished English prose. She will also review the 文書 for other 是正s, such as 訂正する 人物／姿／数字 and （米）棚上げする／（英）提議する numbering, proper use of styles - anything that will help the 一時期／支部 get closer to layout.

She makes a copy, 指名するing the とじ込み／提出する TSAD01_12CC.DOC. She turns 改正 示すs on and copy edits. Copy edit means both turning the author's 文書 into finished English prose and reviewing the 文書 for other 是正s, such as 訂正する 人物／姿／数字 and （米）棚上げする／（英）提議する numbering, proper use of styles, and anything else that will help the 一時期／支部 get closer to layout. Once done with copy edit, Carmen will return the とじ込み／提出する to Whil, who then passes the とじ込み／提出する 支援する to Al. The edits that Carmen has made are 明白な, and she has probably asked the author questions that the author has to answer.

Typically, Carmen will have made some changes that the author will need to review to make sure that the 初めの meaning wasn't changed. Additionally, Carmen may have some questions about 意図 or a 欠如（する） of clarity somewhere. Remember, Carmen, while experienced with technical 文書 editing, and 一般に familiar with the 支配する 事柄, is not an author or a programmer, and will need to rely on the author's technical 専門的知識.

The Al will answer any of the questions raised by Carmen, review the copy editor edits, and return the 一時期／支部 to Whil. The next time Al sees the 一時期／支部, it'll have been laid out and ready for printing.

11. Al makes a copy of the 一時期／支部, 指名するing it TSAD01_13AN.DOC. 改正s are turned ON and are 明白な in the とじ込み／提出する. He reviews the 一時期／支部, answers the questions from copy edit, and leaves edits alone if they're 承認する or changes edits that he doesn't agree with. He sends the 一時期／支部 支援する to Whil, who sends it 支援する to Carmen for layout.

12. Carmen does layout. This is usually done in large chunks, rather than at a discrete 一時期／支部 at a time. She goes through an entire 一時期／支部, reviewing changes to copy edit questions and edits, 受託するs or 拒絶するs all 改正s as appropriate, numbers the pages, takes care of headers and footers, 確実にするs that 言及／関連s to other 一時期／支部s are 正確な (いつかs 一時期／支部 numbers change order or disappear altogether), arranges graphics, and so on.

Carmen asks the authors 直接／まっすぐに about any last minute changes instead of passing とじ込み／提出するs 支援する and 前へ／外へ.

13. Carmen produces PDFs of the 調書をとる／予約する and sends them to each author (and the tech editor, if the tech wants) for final review. These PDF とじ込み／提出するs are what will be going to the printer (they 変える the PDF とじ込み／提出する 直接／まっすぐに to film), so it's the last chance for the author to 立証する what's 存在 printed, and to make any last minute changes. Experienced authors know this step as "author review of page proofs". Last minute changes are frowned upon at this point, as we are anxious to get this 調書をとる／予約する printed. At the same time, if there's something wrong, now is the time to 訂正する it.

If the authors or tech editor see anything that has to be changed, they correspond with Carmen 経由で email.

14. Once Carmen has heard 支援する from all authors/tech editor that the 調書をとる／予約する is 承認する (or received all changes), she will make those changes, produce one final PDF, and send it to Whil for 配達／演説／出産 to the printer.

Publisher Input: What happens when Paul Publisher reviews one of the 一時期／支部s after it's been tech edited (or even copy edited), and has a bunch of new questions? First of all, 延期するs 原因（となる）d by this circumstance do not negatively 影響する／感情 the author's schedule, since this is out of the 支配（する）／統制する of the author or editor. 

There are 現実に a couple sub-シナリオs (is that a word?) here. In the first 事例／患者, if an author is nervous about what they're 令状ing (first-time jitters, for example) or if I am 特に 利益／興味d in 詳細（に述べる）s of a topic, we all should build in time for my review. Ideally, that would come before tech edit - in fact, most ideally, even before co-author review - as 公式文書，認めるd earlier.

The second シナリオ is when I review a 一時期／支部 after it's been through copy edit. This doesn't happen often, but when it does, the author typically becomes やめる annoyed with me. This can 延期する the 調書をとる／予約する because the author may feel the need for a second tech edit. In practice, there's not a need for a second copy edit - any 改正s will be copy edited at the same time layout is done.

Dates: 公式文書，認める that the final 一時期／支部 is to be submitted to me by the date on the schedule. That means that the author should 計画（する） on enough time for 十分な go-arounds with their tech editor ーするために 会合，会う the schedule. Our 基準 tech editor 契約 gives a tech editor 7 days to review a 一時期／支部 and return it (yet another 推論する／理由 for authors to keep 一時期／支部s short ? so that their tech editor can turn them around quickly!)

How about a practical example? The date I'm 利益／興味d in for a 明確な／細部 一時期／支部 is the date the author gets it to me after all tech editing and author review has been done, and so it's ready for copy editing. Suppose it takes an author a week to do a 一時期／支部, then it takes the tech editor a week to review it, and then three days for the author to review what he's commented on, and then three more days for the tech editor to review the changes that the author has made based on the tech editor’s comments, and then a couple of days for the author to review the tech editor’s second review, and send it in to me.

So if the author started on the 1st, it'd go to tech edit on the 8th, 支援する to the author on the 15th, 支援する to tech edit on the 18th, to the author on the 21st, and, finally, to me on the 23rd. Yeah, that sounds like a lot of 支援する and 前へ／外へ time for a 選び出す／独身 一時期／支部, but remember that 一時期／支部s are done in 平行の, not serial. So the author could be doing an 初めの 草案 of 一時期／支部 5, reviewing tech edits of 一時期／支部 3, and thinking about pieces that are going to go in 一時期／支部 6. At the same time, tech edit is reviewing 一時期／支部 2 for the second time, reviewing 一時期／支部 4 for the first time. And copy edit is working on 一時期／支部 1, which has already been submitted. That sounds like a lot of work, but, really, it’s not. The reviews usually go by very quickly.

In the above シナリオ, the date I'm 利益／興味d in, and will 持つ／拘留する the author to, is the 23rd. So while working up a schedule, an author will want to, er, pad their schedule so that they can 会合，会う the 23rd date to me. What successful authors often do is (1) get a couple of 一時期／支部s in the bank (before they're really 予定), (2) try to stay ahead in 事例／患者 of 予期しない interruptions (which always occur), and (3) build in some time to account for sickness, bad weeks at work, vacation, major rewrites based on feedback from tech edit, etc.

If this is the author’s first 調書をとる／予約する with HWP, they’ll likely want to send 草案s of the first few 一時期／支部s by me (even before they go to tech edit.) I won't review them word for word as much as for general approach and style, 同様に as how the author is 組織するing their thoughts and such, although if I see anything glaring I’ll probably make 公式文書，認めるs 権利 in the 文書.

If you 港／避難所’t sensed this yet, it’s probably pointless to について言及する it now, but I will just to make it explicit. My 職業 here is to help the author and tech editor produce a 広大な／多数の／重要な 調書をとる／予約する. The only 推論する／理由 I’ve been harping on the schedule so much is that we make かかわり合いs to 顧客s and our distributor based on the schedule that the author 供給するs me, and if the 調書をとる／予約する is late, they get annoyed, and we 行方不明になる chances for 昇進／宣伝s and other marketing 適切な時期s. Our distributor, in particular, makes かかわり合いs to their 顧客s based on the schedule we 供給する them. If we're late, they look bad to their 顧客s, a 状況／情勢 we will not 許容する.

When 押し進める comes to 押す, a 広大な／多数の／重要な 調書をとる／予約する 配達するd late will always take 優先 over a mediocre one 押し進めるd out on time. There are 財政上の 攻撃する，衝突するs when a 調書をとる／予約する is late, and the author 株 those 攻撃する，衝突するs with the publisher, but in the long run, a 広大な／多数の／重要な 調書をとる／予約する 配達するd late will still out-earn a mediocre 調書をとる／予約する 配達するd too 早期に.