Search (3 results, page 1 of 1)

  • × author_ss:"Wright, J.C."
  • × theme_ss:"Register"
  1. Wright, J.C.: How to index online (1997) 0.00 
    0.0020506454 = product of:
  0.004101291 = sum of:
    0.004101291 = product of:
      0.008202582 = sum of:
        0.008202582 = weight(_text_:a in 3729) [ClassicSimilarity], result of:
          0.008202582 = score(doc=3729,freq=6.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.1544581 = fieldWeight in 3729, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=3729)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    Many back-of-the-book indexers are now taking on projects published on CD-ROM, accessed through a Web site or through internal intranet. Outlines the scope of online indexing and discusses factors affecting the methods used to index online, the index display, and how work will proceed. Considers: the boundaries within which the index will be placed; authoring tools; how the index is displayed; how the indexing gets into the files; the kinds of files included in the project; time schedules; equipment needs; and fees for online projects. Includes a brief list of further readings about indexing online documents
    Type
    a
  2. Wright, J.C.: Indexing after the millenium 1 : getting the tools right (1998) 0.00 
    0.001353075 = product of:
  0.00270615 = sum of:
    0.00270615 = product of:
      0.0054123 = sum of:
        0.0054123 = weight(_text_:a in 4644) [ClassicSimilarity], result of:
          0.0054123 = score(doc=4644,freq=2.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.10191591 = fieldWeight in 4644, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=4644)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Type
    a
  3. Wright, J.C.: ¬The world of embedded indexing (2000) 0.00 
    0.0011717974 = product of:
  0.0023435948 = sum of:
    0.0023435948 = product of:
      0.0046871896 = sum of:
        0.0046871896 = weight(_text_:a in 217) [ClassicSimilarity], result of:
          0.0046871896 = score(doc=217,freq=6.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.088261776 = fieldWeight in 217, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.03125 = fieldNorm(doc=217)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    Here's the scenario: Your favorite client calls to tell you they are changing their processes. "We've decided to go completely electronic and embed the indexing in the files. Can you do that?" It looks like your life and the way you do your work is going to change if you say yes. But before you do, make sure you know enough about the new process to know whether you want to take on the project. Embedded indexing brings a whole new level of complexity to the indexing process. You will need to incorporate new software technologies and special editing/index-compiling skills with the traditional thought and analysis that has always gone into the indexing process. What do we mean when we say you can embed indexing into files? The simplest answer is the one that Nancy Mulvany gives in Indexing Books: Embedded indexing software is generally a feature found in word processing or page design software such as WordPerfect or Ventura Publisher. Embedded indexing software allows the indexer to insert index entries (or tags for entries) directly into the document's text files. In other words, instead of writing an index in CINDEX, Macrex, or SkyIndex, you put the index entries directly into the same files that are used to create the book. Many companies use Microsoft Word, PageMaker, FrameMaker, or Quark to create their manuals and books, editing, layout, and printing directly from the program files. Pasting up pages manually and creating galleys are not part of electronic publishing. Everything lives in files, from the time it is written until the time it goes to the publisher's printing plates. When you embed indexing codes into these files, the publisher has no worry about what page numbers go into the index until the very end. If needed, files can go through layout, content and copy-edit changes even after indexing is completed. This approach also permits indexing and text to be re-used in the next edition or even converted into hyperactive links!
    Type
    a

Years