TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Absolutely correct! We don't have a style guide and "it is a power
struggle". I guess the solution to this is the style guide.
On 6/26/08, Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
>
> In most cases local page break and paragraph return formatting isn't
> affected if the styles are updated. There isn't a "standard best practice"
> answer to your question, which is why I asked what your style guide
> says about handling this. The issue is developing an internal standard
> for the documents you prepare, defining specific conditions under
> which the standard can be bent or broken and then keeping everyone
> working within them. Your current situation sounds more like a power
> struggle between writers than a methodology issue.
>
> Gene Kim-Eng
>
>
> ----- Original Message -----
> From: "SB" <sylvia -dot- braunstein -at- gmail -dot- com>
> > Well, I may not have been clea on this, he wants to add the page break to
> > one heading occasionally (wwhen needed) but not to the whole style. My
> > concern is that as soon as you will need to update the styles, everything
> > will get messed up. I have experience that in the past. However, he says
> > that "we don't need to update the syles".
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Create HTML or Microsoft Word content and convert to Help file formats or
> printed documentation. Features include support for Windows Vista & 2007
> Microsoft Office, team authoring, plus more.
>http://www.DocToHelp.com/TechwrlList
>
> True single source, conditional content, PDF export, modular help.
> Help & Manual is the most powerful authoring tool for technical
> documentation. Boost your productivity! http://www.helpandmanual.com
>
> ---
> You are currently subscribed to TECHWR-L as sylvia -dot- braunstein -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
>http://lists.techwr-l.com/mailman/options/techwr-l/sylvia.braunstein%40gmail.com
>
>
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-