Source Code
Most of our 調書をとる／予約するs come with source code.
Any piece of code, whether it's a program snippet, the design
surfaces for forms or 報告（する）／憶測s, or scripts, should be 含むd
electronically so that the reader doesn't have to create them
by 手渡す. It's a convenience to the reader that most everyone
推定する／予想するs.
As you 令状, you should have 草案s of
the code you use as you 令状 the 調書をとる／予約する, and then use the time
while the 調書をとる／予約する is in layout and printing to produce the final
source code とじ込み／提出するs. Tech edit will need to review those; nothing
is more 悪化させるing to a reader than to find the source code
doesn't run, or doesn't match the text. But the final 見解／翻訳／版
of the source code is not 予定 at the time the 一時期／支部 is submitted
for copy editing.
Source code is 予定 at the time the 調書をとる／予約する starts shipping. There's
usually about a month between the time the final 一時期／支部 has
been sent to layout and the 調書をとる／予約するs land on 顧客's doorsteps,
so that's when the source code needs to get finished up.
How to 言及／関連 source code in your 調書をとる／予約する and
how to 一括 source code for download is 述べるd in 詳細（に述べる） in the HWP Style
Guide.
|
