Problem

When a 文書 gets opened, printed and の近くにd, StarOffice asks whether the changes should be saved. Many 使用者s don't understand this and – depending on the 現在の work 状況／情勢 – いつかs even feel uncertain about which 決定／判定勝ち（する） they should make (Have I changed anything erroneously? Didn't I save my 最新の changes? ...)

Background

When a StarOffice 使用／適用, like Writer, receives the “print” 命令（する）, it 成し遂げるs a couple of 活動／戦闘s before it 現実に prints the 文書:

Updating the 文書 info (とじ込み／提出する – 所有物／資産／財産s) and 始める，決める the “last printed” date.
Updating the fields in the 文書
かもしれない reformatting the whole 文書 because the printer driver used for printing is different from the printer driver the 文書 was created for 初めは.

As it takes やめる some 工学成果／努力 to find out whether or not these 準備s 現実に change the 文書, the “修正するd” 旗 is 始める，決める by default, as soon as an 使用／適用 starts the print 準備s.

Of course it would be a better 解答, if the 使用／適用s knew whether changes were 誘発する／引き起こすd by printing or by other 活動／戦闘s. This would also give us the chance to change the 警告 message that's 陳列する，発揮するd when an unsaved, 修正するd 文書 gets の近くにd. But the 工学 cost to distinguish between the source of the changes is very high (first incomplete 見積（る）: 1 week planning, at least 2 weeks of 実施, 付加 time for 実験（する）ing), and we don't feel like solving this problem is 価値（がある） the cost.

解答

As an 代案／選択肢,more simple approach, we should 申し込む／申し出 an 選択 that 抑えるs the modification of the “文書修正するd” 旗 by the print 過程. This 選択 would not be active by default, but if a 使用者 feels 混乱させるd by the 現在の行為, he can choose to 活動させる／戦時編成する it.

Behind the scenes, the status of the “文書修正するd” 旗 would be saved as soon as the printing 過程 gets 誘発する／引き起こすd and it would be reset to the saved value after printing has finished. Of course the changes について言及するd above would still be made, it would be just the status of the 文書 that's “locked” against changes. If the 文書 has been 修正するd before it was printed, the status after printing would be “修正するd”. If it has just been opened with no (a)自動的な／(n)自動拳銃 changes (like 誘発する／引き起こすd by 大型のs or updated links), it would show the status “unmodified” after printing. If the 使用者 subsequently changes the 文書, the status would change accordingly, i.e. Switch to “修正するd”.

There are some disadvantages to this 解答:

If the 使用者 doesn't save the 文書 after printing, the changes will be lost, so the printed 文書 is “newer” than the saved 文書
(This would also be the 事例／患者 if the 使用者 decides not to save the 文書 when asked about this)
The “last printed” 文書 info field would not 含む／封じ込める the 訂正する value
(same as above; today the field also doesn't get updated if a 文書 is printed from the system 爆撃する (like from the 状況 menu in Windows Explorer))

I consider these disadvantages to be a 穏健な price that the 使用者支払う／賃金s for his convenience. And anyway, we would not make this setting the default, so the 使用者 himself would be 責任がある changing this 行為.

How does the 使用者 learn about the new feature?

As 述べるd in the background section, we do not want to distinguish between general changes and changes 誘発する／引き起こすd by the printing 過程. So we can't 修正する the 警告 message box that asks the 使用者 if his changes should be saved, because we don't know which changes 原因（となる）d this box to appear.

An 代案／選択肢 way to 知らせる the 使用者 is to 陳列する，発揮する the Help スパイ／執行官 together with the message box. The Help スパイ／執行官 leads the 使用者 to a description of this feature in our help system.

その上の specification 詳細（に述べる）s

追加する an 選択 to 道具s – 選択s – General
This is maybe not the most natural 選択 page for this setting, but 予定 to other dialogs 存在 already “十分な”, this is the best 妥協 for this setting.
The 選択 should be called: Printing 始める，決めるs “文書修正するd” status. It should be に先行するd by a separator line labeled “文書 status”
In German: Drucken setzt “Dokument geändert” Status (separator label: Dokumentstatus)

活動／戦闘 Items

提案する specification	Lutz Höger
述べる the feature and maybe the technical background	Frank Peters
Optionally save and 回復する the 文書 status when printing	Mathias Bauer
器具／実施する道具s – 選択s UI	Oliver Specht
器具／実施する誘発する／引き起こす for Help スパイ／執行官	Oliver Specht
令状 feature e-mail	Oliver Specht
Translate UI and documentation	Rafaella Braconi