Lo sai che avevo iniziato a augrdarla ma non mi aveva preso? Ora visto che anche tu la giudichi cosi bene sare0 il caso che la riprenda con maggiori attenzione.Io quest'anno oltre a Lost e Desperate Housewives ho iniziato a guardare Six Degrees (sempre di JJ Abrams) che mi ha preso non poco.E ovviamente aspetto con ansia l'inizio di 24

Mr. Farbey,You've given me a great idea for a post; I will write about this in a day or so.Microsoft Word works well when the people who use it have been atirned to use it well. Sounds like a cliche, but when I was involved in using Word to create, edit, and collaborate on documents that were published in-house, the only problems that would surface were user-created, not application created.If you begin with best practices, which is to start with a template that all users would adhere to, the application being used is almost not a factor. For a manual that would incorporate work from six or seven individual researchers and would have fold-out tables, charts, graphs, and images, there really was no issue in assembling the document into one Word document. In the editing process, the person charged with assembling the document would have to make the styles consistent across the board. That might mean eliminating some stray Arial font text or it might mean going through all of the endnotes to make certain they followed the correct format.Once that editor had control of the document, it made publication easier. It made converting the document to a printed soft-cover book easier as well. Even pdf conversion was a quick and painless process.So, yes. Word is fine. You can't have rogues out there, deviating from the template of the finished product. And you have to invest in the editing process. But work, it does, and it did in my experience.

Once again, someone has ptonied out the fact that MS Word is not really suitable as an enterprise technical writing tool unless it is heavily customized. Have programmers create special document-creation interfaces, create locked purpose-built ribbons, use SEQ fields instead of native numbering   Here we go again. I've seen and heard this exact same thing too many times. No offense intended, but this is kind of like the college sophomore year epiphany of technical writing.  Sooner or later everyone stumbles on this idea like it's a new and blinding revelation, and really it's as old and worn as the Appalachians.People keep saying Word will work for tech writing IF you change this  and customize that and renoberate the other thing. Face it, this is like saying that a car will work as a helicopter if you totally rebuild every part of it. If you have to spend that much time, effort, and money making it work the way you want, it would be worth your while if only in avoided irritation to go get something that already works the way you need it to work. And if you have to try to change your corporate culture to make the tool usable, it's NOT worth the effort. You are supposed to use tools, not the other way around.

Its such as you read my thoughts! You paaepr to know so much about this, such as you wrote the book in it or something. I think that you just could do with some percent to force the message house a bit, but other than that, that is fantastic blog. An excellent read. I will definitely be back.

Sub copia_inc()
    ActiveCell.Copy
    c = ActiveCell.Column
    r = ActiveCell.Row
    Cells(r, c - 1).Select
    Selection.End(xlDown).Offset(1, 0).Select
    c1 = ActiveCell.Column
    r1 = ActiveCell.Row
    Cells(r1, c).Select
    Range(Cells(r1, c), Cells(r, c)).Select
    'per incollare tutto, formato e dato e/o formula
    ActiveSheet.Paste
    'per incollare solo il valore, la scrivo commentata altrimenti ti sovrascrive l'incolla precedente
    
    'Selection.PasteSpecial Paste:=xlPasteValues, Operation:=xlNone, SkipBlanks _
        :=False, Transpose:=False
    'disabilito l'area selezionata dell'incolla
    Application.CutCopyMode = False
End Sub