®DC12=1¯®DC11=1¯®DC13=a¯®SSLIST3;®C13¯. ¯®DC14=a¯®SSLIST4;®C14¯. ¯®SSBODYTEXT-N;®AL1¯®LS2LI¯®IP5DI,0DI,0DI¯¯®SSDEFAULTS¯®OBX1007.1,0¯®KYF®IDFRAMEWRK¯¯®OBO/LF¯®XODE¯®OBX/DE¯Chicago [1]: Chicago Manual of Style®OBX/BT¯®SSFRAMEWORK;1007/NB-STYLE.FWL/Academic Style Manual Headings¯®DC1=1.1.1.1.1¯®GC|OP:DB=C:\NBWIN\IBIDEM\BRUCE\BRUCE;FL=C;TY=FN;IT=Chicago Manual of Style (Footnote/Endnote);CS="; ";DE="";IF=;FS=1;EA=E,3,1,3,1,N;RL=Chicago Manual of Style (Bibliographic);SO=A;RF=X;RT=®LS2LI¯®FC¯®IP0IN,3DI¯Bibliographyÿ-¶®FL¯¯®GC¯®USDEFAULTS¯®SSLEVEL1,NB=1;®NB2¯®DC2=1.1.1.1¯®XODECO¯¯®USLEVEL1;¯®SSCOUNTER1;®C1¯¯®SSTITLE1,UL=1,FC¯®SSTITLEEND1; ¯®SSBODYTEXT1,LS=2LI,IP=0.5IN,0IN,0IN,HY=0¯®USDEFAULTS¯®SSLEVEL2,NB=1;®NB2¯®DC3=1.1.1¯®XODECO¯¯®USLEVEL2;¯®SSCOUNTER2;®C2¯¯®SSTITLE2,UL=1¯®SSTITLEEND2; ¯®SSBODYTEXT2,LS=2LI,IP=0.5IN,0IN,0IN,HY=0¯®USDEFAULTS¯®SSLEVEL3,NB=1;®NB2¯®DC4=1.1¯®XODECO¯¯®USLEVEL3;¯®SSCOUNTER3;®C3¯¯®SSTITLE3,UL=1,IP=0.5IN,0IN,0IN¯®SSTITLEEND3;. ¯®SSBODYTEXT3,LS=2LI,IP=0.5IN,0IN,0IN,HY=0¯®USDEFAULTS¯®OB¯®SZ14PT¯®MD+BO¯®MD+IT¯®FC¯Technical Support Frequently Asked Questions®MD-BO¯®MD-IT¯ November 11, 2005 ®SZ11PT¯®FL¯ If you encounter any problems in using Nota Bene, you may be able to find the solution in this file. The list of problems below is followed by the problems with solutions. You can use the search dialog (Edit, Find/Replace or Ctrl+F) to search for the problem that you are experiencing, or you can skim through the problems that are listed in different categories. Updated versions of this file (TS-FAQ.NB) may be posted on our website (®HK1Web|www.notabene.com/download/nbhelp/TS-FAQ.html¯click®HK0¯ here to check now). If that version is more recent (the date will be posted on the site) than the above date, you should: • Close this file • Download the new TS-FAQ.NB • Save it in your NBWIN\SUPPORT folder, replacing the older version ®LD-¯ ®C12¯) Problem: An existing NB for Windows Ibidem database has been moved to another drive and/or folder, and it can no longer be accessed. Solution: As long as you know the new location of the database (i.e, the drive or folder to which it has been moved), you can create a new entry for that database in the database list that specifies the new location of the data files. 1. Remove the old database (the one installed in the old location) from the database list --In Ibidem, select File, Maintain; then select the database, click Remove, and then click Close to close this dialog (respond Yes to the prompt about saving changes) 2. Add the database (in its new location) to the database list --In Ibidem, select File, Open, click the Add button, type in a short name and description, select the location of the new database (we recommend using the Browse button, rather than typing it). When you press Enter, the list of databases in that location will be shown in the Filename box. Select the one you want, and then click OK 3. To use this new database in an existing file that had cited sources in the database in its old location, you will need to reselect the new database for that file --In NB, select Format, Bibliographic References, Active Database, and select the newly-added entry for the database and click OK ®LD-¯ ®C12¯) Problem: Entries in the Annotations field of my Ibidem record appear in footnotes or reference list in my document Solution: The problem is that you’ve checked the Include Annotation box on the Document Style dialog. To exclude annotations, go to your Nota Bene document and --select Format, Bibliographic References, Document Style, and then, on both the In-Text Citation Format and Reference-List Format tabs, make sure the Include Annotation box is not checked. ®LD-¯ ®C12¯) Problem: When I generate a bibliography from my Ibidem database, entries in the Annotations field appear even when using the Standard Format (on the Generate, Bibliography or Subject Bibliography dialogs), and when the Include Additional Fields box is not checked. Solution: --Go to Ibidem Tools, Options, and uncheck the Include Annotation box. ®LD-¯ ®C12¯) Problem: What is obviously a bibliographic database does not function as such--for example, no preview box is displayed, the options under Generate list reports and other similar items rather than Bibliographies and Subject Bibliographies, etc. Solution You’ll have to reset the database type back to bibliographic in Ibidem. --Go to File, Maintain Database, select the database, and click on the Maintain button --Select Edit General Information, click OK, and change the Type field back to Bibliographic --Click OK. ®LD-¯ ®C12¯) Problem: Records added to Ibidem do not seem to alphabetize correctly when generating a bibliography or when displaying the table view in alphabetical order (by author, title, etc.). Solution: In most cases, Ibidem can add index records as you add or edit them. This means that records are incorporated and can be alphabetized and searched after you create them. However, occasionally, this on-the-fly indexing is no longer possible (the internal space reserved for expansion has filled up). When that happens, while the records are added and/or edited, they do not get properly alphabetized (and you may not be able to search for them using the fast search). You can solve this problem by rebuilding your index from the beginning. To do this, go to File, Maintain, select the database, and then click the Maintain button. Then, in the Maintenance Options dialog, select Rebuild Index from Beginning and click OK. ®LD-¯ ®C12¯) Problem: When trying to open a database through Ibidem, it says “Cannot open Lock file for database [databasename].” Solution: In Ibidem, go to File, Maintain, select the problem database, and click the Maintain button. In the Maintenance Options dialog, select Unlock Database, and click OK. You will be shown a message about unlocking your database. If you wish to proceed, click Unlock. You can then access your unlocked database by selecting Re-Open Database and clicking OK. ®LD-¯ ®C12¯) Problem: There is a reference in my Bibliography/Works Cited list that is not cited in the body of the text. Solution: You may have insertd citations in the file which you specified should be included only in the reference list (you did this by checking the "Include Only in Reference List" checkbox at the top of the Insert/Edit citation dialog that is displayed when you cite a record from Ibidem). Currently, the only way to find these references is to switch to Codes View, and then search for "FL=[any alphanumeric]" (without the quotes; insert the "[any alphanumeric]" symbol using the Special Characters button to the right of the Find field). Citations designated for inclusion only in the reference list will have an "R" as one of the values after the "FL=" string. If you want to delete an entry, click in the "FL=" command string, press Ctrl+[=] to highlight the entire string (that starts with «GC....») and delete it. Then do the same for the immediately following blank «GC» code. ®LD-¯ ®C12¯) Problem: When I generate a bibliography from in-text citations at the end of a file, items published in the same year by the same author are differentiated: Smith 1998a, Smith 1998b, etc. But when a bibliography is generated from Ibidem as a separate file, the "a"'s and "b"' s vanish, leaving just Smith 1998 and Smith 1998. Solution: The only context in which a reference list should use "a," "b," "c," etc. is when those works are referenced in short-form author-year citations, and when such references need to be disambiguated because they have the same author and year. These conditions are not met when a stand-alone bibliography is generated, and so we do not implement that feature in this context, since it is not relevant. While we can consider adding this as an option in the future, for the moment it will not work. In the meantime, there are two options, both somewhat onerous: 1. If the bibliography is for a manuscript of cited works, but is being generated separately because you want additional works that you do not want to have cited in the paper to be included in the list of works, you can go back to the manuscript and cite those other works for inclusion only in the Reference List (check the first checkbox on the Insert/Edit Citation dialog), and then generate the reference list as part of the process of updating the citations in the file. 2. You can manually add these subscripts to the bibliography generated from Ibidem (although that will of course require reading through the entire list). ®LD-¯ ®C12¯) Problem: The dropdown list for journals does not include names of journals that I've used. Solution: The dropdown lists on the left of Ibidem fields are not authority lists, but predefined lists shipped with the program (the content of which cannot be changed by the user). Authority lists, which contain the data previously entered by the user, are always on the right of the field in Ibidem. By default, Ibidem does not set up an authority list of journal names. However, you can set up your database to do this by going to File, Maintain Database. Select your database and click Maintain. Choose Edit Properties on the Maintain Database dialog, and click OK. On the Index Key tab in the Properties dialog, click Add Key, select the journal field, set it to use a Lookup list, and specify the number of characters you want for the largest entry in the list. After accepting these changes, you will need to reindex your database (File, Maintain Database, Rebuild Index from Beginning), but thereafter you should have a dropdown authority list of journal names which reflects your actual usage. ®LD-¯ ®C12¯) Problem: I need Ibidem to format a citation in a particular way, but don’t know which style to use. Do you have a comprehensive list of how each style formats different works? Solution: No, there is no such list. Indeed, providing it would be almost (even probably literally) impossible, since it would require reproducing huge portions of the various style formats that we support (there are about a thousand). Given those constraints (including copyright issues), the next best thing is what we've already done, which is to enhance the preview panel (accessed by going to View, Preview Panel) so that you can (a) select a record of the type whose formatting you are concerned about, and then (b) cycle through the various styles in the preview panel to see which style comes closest. (The best way to do this is to right click in the preview panel, select Style, then double click in the combo box of the style [In-Text or Reference List] you want, and then use the up and down arrow keys to cycle through the styles [double clicking selects that combo box, and then removes the drop-down portion of it, so that you can cycle through the options while seeing the entire preview]). ®LD-¯ ®C12¯) Problem: I want to separate my end-of-manuscript reference list into two sections, one with primary sources, and the other with secondary sources. Solution: You cannot currently do this automatically, though for the moment, there are two workarounds: 1. You can generate the reference list, and then change it into a non-dynamic one (right click in the reference list, and click Dynamic On/Off), and manually move the entries around. Note that you should do this as the very last stage of your work, after you’re certain that you do not need to update the citations further. That’s because (a) if you keep the Dynamic flag off (i.e., keep the reference list green), and then update the paper, the reference list will not be rewritten (of course, this is not a problem, and may in fact be what you want, as long as you are not adding any new works), while (b) if you turn the Dynamic option on for the reference list, it will be rewritten from scratch when you update citations, and you will lose all your painstaking changes. 2. You can also create separate subsets in Ibidem of the various kinds of works in your database (the easiest way to do so is to add a particular phrase [such as “primary,” “secondary,” “archival,” etc.] to some field [either existing or new] in the database, and then do a search to find all such records, and save them as a subset), and then produce separate stand-alone bibliographies of those subsets (using Generate, Bibliography). Then suppress the reference list for the paper (go to Format, Bibliographic References, Document Style, and uncheck the Include Reference List option), and merge the two separately generated bibliographies at the end of the manuscript. Note that with this approach you will be able to more easily accommodate changes made to a paper (you can easily regenerate the separate lists, and merge them in), but you must be sure that the subsets are set up to include only those references you want included in the bibliography for the current paper. ®LD-¯ ®C12¯) Problem: Does Ibidem provide a format for citing websites? Solution: At the moment, no. That's largely because when the Ibidem formatter was first written, virtually none of the styles had established standards for this (and this is a style-by-style issue). Things are slowly getting cleared up now (but even the major styles change their recommendation from edition to edition), and once the dust clears a little bit we should enable you to format such citations. For the moment, there are two options: 1. Create a record for the source using the Full Record format. In the Alternate Form field, type the full website citation as it should look in your document. Then, when you insert that citation, select the Cite Instead option and choose the Alternate Form field. Check the As Default box if appropriate. 2. When you insert the citation, select the non-dynamic option (check the Override Dynamic box on the dialog that lets you insert a citation, or right click on an existing citation) to turn the citation into an editable (green) cite. Then edit the citation as you would any other text. ®LD-¯ ®C12¯) Problem: I want to move Orbis textbases from an old computer to a new one. Solution: You will need to recreate your textbases from scratch on the new system, unless: 1. Absolutely ALL the files—the individual files that make up the textbase, and the index/database management files (usually in the \NBWIN\ORBIS folder)— are on the exact same drive, and in precisely the same subdirectories, as on your previous system, and 2. You still have your old ORBIS.INI file (from your \NBWIN\USERS\DEFAULT subdirectory) If, and only if, the above conditions are met exactly, you can then copy the above mentioned ORBIS.INI file from your old system to \NBWIN\USERS\DEFAULT on your new system. But if not, you will need to recreate all the textbases. ®LD-¯ ®C12¯) Problem: How useful are Orbis’ ‘special keywords’? When I am writing, I find that I don’t want to think about adding keywords to my text. Isn't it much more useful to use the synonyms feature for this purpose? For example, rather than adding the special keyword ‘money’ to all instances of ‘luxury’ in the text, it seems much easier to create a synonym-group for money which includes ‘luxury’. Solution: In the situation described, where you want more, rather than fewer, entries to be found for a given term, using synonyms makes most sense. Use special keywords when you want fewer matches—i.e., more selective searches. For example, you might have thousands of passages about money or luxury, but a half dozen are really important, and you sometimes want to retrieve just those. You can do so if you mark these with the special keywords. ®LD-¯ ®C12¯) Problem: When I open a file, I get a dialog that says, “Select File Format.” How should I respond? And how can one prevent it from being shown at all? Solution: The Select File Format dialog is displayed whenever (a) you have the Format drop-down box on the File, Open dialog set to Auto Detect, but (b) Nota Bene’s auto-detect file mechanism is unable to recognize the format of the file you are trying to open. While Auto Detect can usually determine the format of the file, it cannot do so for “pure text” files--i.e., those that contain no formatting codes of any kind--since these are in fact identical with ASCII files insofar as their auto-detect characteristics are concerned. If you have a lot of such files, and thus get this message often, and you're always opening NB for Windows files, you should probably set the Format drop-down box on the File, Open dialog to NB for Windows instead (since there's then no benefit in using auto detect). This is also a good choice even if you have many NB for DOS files to open, since even if the format is set to NB for Windows, if a file is in DOS format, NB will ask if you want to convert it (from DOS). However, if you open many files in other formats (e.g., Word and/or RTF), you will find it easier to leave the format drop-down box set to Auto Detect. In cases when you do open a pure text file that doesn't contain any formatting codes, you should simply switch the format to NB for Windows. If, when you open a file, the Select File Format message appears, then Nota Bene does not recognize the format and needs your help to figure out how to convert and display it. You should therefore select the format that the original file was in. ®LD-¯ ®C12problem¯) Problem: How does one share documents created in NB that contain classical or koine Greek and/or Hebrew with other people? Solution: The answer to this question depends on how your file will be used by the person you are sharing it with. 1. If your goal is to have the recipient be able to read (but not edit) your text, the best approach is to create a PDF (Portable Document Format) file, which will essentially freeze the document as it appears on your screen and save it in a format that can opened and printed by the recipient using the free Adobe Acrobat Reader. You can create a PDF file using various versions of Adobe software, or by purchasing the pdfFactory program from us (because not all Adobe versions work, we recommend using pdfFactory or pdfFactoryPro. See ®HK1Web|http://www.notabene.com/pdffactory.html¯www.notabene.com/pdffactory.html®HK0¯ for details). The advantages of creating PDF output are: ÿwü  higher quality output than you can otherwise achieve when converting the files to another format (see below), since NB’s superior character-rendering scheme is utilized (rather than the much more limited font-only solutions of other software) ÿwü  anybody--whether running Windows, Mac, or Unix, etc.--can read the files ÿwü  recipients of a PDF file can read the document without having multilingual fonts installed on their systems, or needing to purchase them. Many people find that creating PDF files from NB gives them the best of both worlds—NB's superior multilingual rendering and sophisticated document layout, and cross-platform readability. Acrobat files are often used for content delivery on the web. 2. However, if you are not able to use PDF format, or if you need to share an NB file for editing in a program other than Nota Bene, you can save your file as an RTF (Rich Text Format) file. This can be done in a number of ways, and the best method will depend on the capabilities of the program that will be used to edit your file. Lingua handles non-Roman character input differently from other word processing programs (e.g., Microsoft Word). Whereas other word processing programs can only display the limited character set of a given font, NB uses a unique font rendering system that allows you to enter over 1,700 distinct characters and to add over 230 distinct accents to any character in virtually any combination. This means that in order to allow your NB document to be viewed and edited in another program, the characters in your document will need to be encoded in a different font and then converted to RTF. Furthermore, the recipient must have a font installed that can handle multilingual text. To save your file in RTF format, -- Go to File, Save As -- From the Formats drop-down list, select RTF--Custom, click OK. -- The Conversion Options: RTF Encoding dialog will appear, giving you several options for encoding your document. Normally, the best option will be to convert files to RTF using Unicode encoding.®IP@TS1,@TS1¯ 2a) ®MD+UL¯Unicode encoding®MD-UL¯. ®AL1¯®LL.4LI,0LI¯As with other fonts, to successfully view RTF documents converted using Unicode encoding, the receiving party would need to have a Unicode font available that supports Greek or Hebrew characters. This is particularly the case for Greek, where the accents and breathing marks needed for classical and koine Greek will not be converted properly without such a font. As for Hebrew, although the vowels are available in virtually all Unicode ®MD+IT¯fonts®MD-IT¯ (and the cantillation marks in some), many ®MD+IT¯programs ®MD-IT¯(including many versions of Word) cannot properly position them, with the result that only consonantal text will be properly displayed. Note also that the software for which you are preparing RTF output may handle Hebrew differently—some will be able to automatically flip the Hebrew characters, while others will not. This means that you may need to create different versions of the RTF export file, one with the Reverse Hebrew checkbox on the Conversion Options: RTF Export dialog checked, and another with it unchecked. Unfortunately, there’s no way to be sure which option is required unless you know exactly what software your recipient is using, as well as how it is configured. 2b) ®MD+UL¯Linguist Software font encoding®MD-UL¯.®MD-UL¯ These Linguist Software fonts are high-quality fonts, and will produce very good output, but the receiving party would need to have these fonts installed on their system in order to view your file. If you are sending the file to a publisher (and not an individual), they may very well already have these fonts, since they are standard fonts used by many people in classics, Judaic studies, and biblical studies. 2c) ®MD+UL¯Scholar's Press/SBL font encoding®MD-UL¯. These fonts can be downloaded (free) from the SBL (Society of Biblical Literature) web site (®HK1Web|http://www.sbl-site.org/¯www.sbl-site.org®HK0¯). Using them may be the best choice if you are sending your material off to publishers for typesetting, since the publisher either already has these, or can easily obtain access to them, and thus should be able to easily convert the encodings to the Greek and/or Hebrew used in their typesetting systems. This presence of this alternative, if only as a last resort, should in fact make it possible for you to do all your work in Nota Bene, experiencing its many benefits, and still send publishers the multilingual RTF text that they may request.®IP0,0¯ ®LL0LI,0LI¯--If you leave the Save As Defaults box at the bottom of the Conversion Options: RTF Encoding dialog checked, then the next time you save a file as an RTF file, you can select RTF -- Defaults in the Formats box of the Save As dialog and the same settings will be applied without opening the Conversion Options dialog. --Click OK The file will be saved as an RTF file. You will be asked if you want to open the RTF file. If you click Yes, then the file will be opened using whatever program on your computer is associated with the .RTF extension. If you have Microsoft Word installed on your computer, the .RTF extension is usually associated with Microsoft Word. If you are converting several files at the same time, you can click to check the "Remember Format" box. This will retain the format you selected so that you do not have to change it each time. Remember to change the format back to Nota Bene for Windows and to uncheck the "Remember Format" box when you are finished. ®LD-¯ ®C12¯) Problem: Does Nota Bene support Unicode (especially in relationship to the web)? Solution: This is a somewhat complicated question. For the most part, Nota Bene is indeed Unicode aware—for example, it can read and write Unicode Greek and Hebrew files, and it uses the WGL4 Unicode fonts for the Greek and Hebrew consonants (although not for vowels, accents, etc., which it gets from its own inventory). While it does not use Unicode internally (virtually no program does, since each has its own internal data storage structure [Word is no exception]), it shares with Unicode the notion that changing languages is a far different thing than selecting a font. Using this approach to composing multilingual text NB can not only support a wide range of characters available in Unicode (as well as many that are not), but it also provides a number of other benefits: ÿwü  NB’s sophisticated multilingual information processing system addresses the rendering requirements that are so crucial to multilingual text (i.e., the proper placement of accents and other modifiers, etc.) which Unicode does not. ÿwü  You can easily (and globally) change the font of mixed multilingual text without the languages disappearing. ÿwü  There is only a single encoding for a given accent, which the program's sophisticated rendering engine knows how to properly place above/below the character, regardless of its width (i.e., there are not two or three different "width" accents, from which you have to choose the correct one for the particular character). ÿwü  You can write in Hebrew, Greek or Cyrillic and mix languages in the same document or even on the same line. You can select a right-to-left orientation so that Hebrew text will begin at the right margin. Or you can integrate Hebrew in a document with a primary left-to-right orientation. In either case, Hebrew characters will be entered from right to left and words will wrap properly from line to line. Accents, breathing marks and Hebrew vowels and cantillations are entered easily with pop-up dialogs and/or simple key combinations. ÿwü  In addition to full right-to-left functionality in Hebrew, vowels and accents are positioned much more accurately. The program will automatically take into account the height or width of a character in placing a vowel or accent. For letters that vary depending on their position in a word (e.g., the Greek sigma), Lingua will automatically select the correct form. ÿwü  You don't have to use awkward keyboard layouts to get the correct characters, or worry about which version/width of the accent you choose By offering an implementation of these functions, NB essentially is, to use a metaphor, adding muscle to Unicode’s bones. Because these benefits are available only when using NB, we suggest converting your document to PDF format (see above) in order to make your document available on the web. In the event that you are not able to use PDF format, you can also save files (using the Save As dialog in NB) in RTF format, using Unicode encoding (select the RTF--Custom option) (see above). Any web program that can read in Unicode RTF should be able to create HTML files from these. However, when you convert an NB file to another, less sophisticated environment, the benefits of NB’s character rendering system may be lost. ®LD-¯ ®C12¯) Problem: Long filenames are sometimes truncated when those files are saved in NB. Solution: In versions of NB before 6.1, people occasionally reported sporadic truncation of long filenames. This has been fixed in versions 6.1 and following. However, we still sometimes hear reports of another problem, namely that long filenames are not working under some circumstances when Norton System Works is installed. Specifically, it appears that the activation of the Norton Protected Recycle Bin in Norton System Works 2003 (and probably earlier versions) prevents NB from properly retaining the long filename. We hope to address this problem with Norton some day, but for the moment you will need to disable that option within Norton. (As we understand it, this Norton feature offers a somewhat redundant level of protection when deleting files—it appears to save files not only after the first delete [as Windows does in general by sending them to the Recycle Bin], but even when subsequently deleting them from the Recycle Bin.) ®LD-¯ ®C12¯) Problem: When Nota Bene creates a backup file, why is the .BAK extension added to any existing extension, resulting in a double extension (e.g., FILENAME.NB.BAK)? Solution: In earlier versions of NB in which backup files would replace any extension with the .BAK extension, it was easy to lose the backup of two files with the same name, but different extension. In such cases, the backup of both of files would then be named FILENAME.BAK (for example, CHAPTER1.NT and CHAPTER1.TST would both be backed up to CHAPTER1.BAK). The current method avoids that conflict, thus preserving backups for every file. ®LD-¯ ®C12¯) Problem: The text in all of my documents is displayed as a vertical line on the left side of the screen. It prints properly and displays properly in Show Codes view and Draft view, but I can't work with it in Graphics view. Solution: You should never encounter this in version 8.0. But if for some totally unexpected reason you do, here’s the reason, and a solution. Nota Bene uses a printer driver to generate the display. This problem has to do with some temporary incompatibility between the printer driver that Nota Bene is using and the driver that is active in Windows. While installing a new printer does not usually result in this problem, it is likely that you just installed a printer or that you just installed or reinstalled Nota Bene. One of the following two steps will fix this problem: 1, Click File, Print, and then click the Reselect button beside the name of the printer. 2, If step 1 does not fix the problem, then click the Setup button on the same dialog, and change a single property on that dialog (choose one that it is easy to set back, such as Orientation [Portrait vs. Landscape]) and click OK to return to the NB Print dialog. The problem should now be fixed, but you should click Setup again to reset whatever property you just changed back to the original setting. One of these two steps will once again cause Nota Bene's printer driver to match the active one, and correct the problem you are describing. You will most likely not encounter this problem again.In graphics view, all my text appears vertically, down the left side of the page. ®LD-¯ ®C12¯) Problem: How do I import/convert files from another program. Solution: See Help File “Convert to Nota Bene” ®LD-¯ ®C12¯) Problem: An image is too wide to fit on the page. Solution: There are a number of alternative (but not mutually exclusive) options. You can: --Remove any borders around the image, since these take up space --Double click on the image, and then uncheck borders on the frame toolbar --Make the frame wider by turning off auto-width (auto-width sizes the frame to fit the object, but it never creates a frame wider than the width of the text on the page); by setting the width manually, you can override this limitation --Double click on the image, uncheck Auto Width, and use the sliders to increase the size as desired --Change the margins for your entire paper (make them narrower) so that the image as is (with borders) can fit within those margins --Reduce the size of the image to fit --Double click on the image, click on the image again to select it, and then choose Format, and change Size/Scale After making the above adjustments, if the image is still wider than the text width, you may still need to drag the image to the left to center it on the page, especially if the image has a blank left margin. (Portions of an image that extend into the margins on a page may not show up properly on screen during editing, but they should print.) ®LD-¯ ®C12¯) Problem: What does the «IC» command do? Solution: The IC command is related to a group of commands (for example, headers and footers, paper size, etc.) that must be defined before the first printable character on the page in order to take effect on that page. But in some circumstances, you might like to define a series of commands together at the top of the page (e.g., headers for the entire document), and have some of them take effect on the first page, while the others don't function until the following page. The "IC" command (which stands for "Insert Character") performs this function—although any commands after it may precede the first printable character on that page (and thus, theoretically, should take effect on the current page), in fact they will not take effect until the following page. ®LD-¯ ®C12¯) Problem: I can’t get this image to display in my document. I’m sure I did not check the “Display Image/Object as Icon” box in the Images and Objects dialog—so why does the image display as an icon in the file? Solution: NB does not actually draw images/objects itself, but uses other existing programs to render them within a document. This means that the question of whether you can insert an image directly into an NB document depends on what format that image is in and whether you have an OLE server installed for that kind of image/object . For our purposes, an OLE server is a program that can be used to actually edit an image in that format. For example, bitmap images (with a .BMP extension) are often linked to the Microsoft Paint program, which is included in most Windows systems (under Start button, All Programs, Accessories). So if you insert a bitmap image, the NB will use Paint to render the image in the document. By contrast, although you can view a JPEG file on most systems (because Explorer lets you do so), some people do not have JPEG editors installed, so they cannot directly include them in NB files. However, if you do want to insert a JPEG or GIF image, for example, but you don’t have an OLE server for that kind of file, there is a way around this problem. The solution is to use another program to open the image, then save it that program’s native format. For example, if you have Photoshop on your system, you can open a JPEG in Photoshop and save that file as a Photoshop file with a .PSD extension. Alternatively, if you have Microsoft Word on your system, you can create a Word document that contains just that image (since Word does some of this rendering itself, not calling on the other program), and save it as a Word file with a .DOC extension. Then, in NB, you can include, that Word document or Photoshop image instead of the original file. The results will be just as if you had embedded the image directly—you can put a border around it, text can wrap around it, etc. ®LD-¯ ®C12¯) Problem: I’d like to use a spell checker for British, rather that US, English. Solution: Go to Proof, Spell to open the Spell Check window. From the Dictionary drop-down list on the right of the window, select English (UK). The British dictionary will be activated the next time you open Nota Bene, so quit and restart. ®LD-¯ ®C12¯) Problem: I want to change the overall spacing of a framework. Solution: The easiest way to change the line spacing of your entire document (for example, to 1.5 lines per inch, instead of 2) is by using Format, Page Layout, selecting the Spacing tab (ignoring the warning about Frameworks that will be displayed), and then choosing the desired spacing ("one and a half" in this case) and (after making sure that the Apply to box still reads "Document Default") clicking OK. If you've not already tried to change the spacing of individual levels (as described below), this will change the spacing for all the framework items; if you have set the spacing of framework items individually, whatever settings you make here will be ignored (a warning message appears in the Page Layout dialog that describes this) . Another way to change line spacing is to go to Format, Framework/Outline, and then select Edit. On the large Framework dialog, click the Body Text tab, and then the Spacing sub-tab, and make the change. Using this method you can change the spacing of each level of your framework individually. If you want to change the spacing for the entire document, be sure to make this change for all levels that are used. If you want to save these settings as a customized framework for use in the future, check the Save to Library box in the lower left of the large Framework dialog and click OK. You will then be prompted to provide a name for your user-defined framework. After entering the name, click Save. ®LD-¯ ®C12¯) Problem: I have right-to-left Hebrew text (for example, biblical verses), and want to insert left-to-right English paragraphs between them. Solution: You can do so either by (a) positioning the cursor at the end of the Hebrew line after which you want to insert the left-to-right paragraph, and pressing Ctrl+Shift + >, and then selecting "New Line/Paragraph After Current Paragraph" as the Apply To type, or (b) positioning the cursor at the beginning of the following line (which you want to come after your inserted left-to-right paragraph) and then pressing the same Ctrl+Shift + > key combination, but this time selecting "New Line/Paragraph Before Current Paragraph" as the Apply To type. ®LD-¯ ®C12¯) Problem: The footnote separator seems to work correctly when used in a single chapter of manuscript, but when I combine the individual chapters in a manuscript file, the separator is incorrectly indented for all chapters other than the first. Solution: In NB, the format of footnotes (including the separators) depends on the formats in effect when the footnotes are defined. This enables the footnote format to pick up settings from the surrounding text, so that—unless specified explicitly in the footnote definition—the footnotes will automatically adjust to changes in the surrounding text (e.g., font). What is likely happening here is that while there is no paragraph indentation at the beginning of the component file (where the notes are defined), there is at the end of the component file. This end-of-file indentation remains active when the files are combined into a manuscript, and thus affects the footnote separators in all chapters after the first. To correct this, make sure that the paragraph indentation at the end of each component file is canceled: 1. At the very end of the component file, go to Format, Paragraph, and then select None in the Indentation tab. 2. Make sure that "Insertion Point Forward" is selected in for the Apply To drop-down list. ®LD-¯ ®C12¯) Problem: My footnotes don’t print on the page on which they occur. Solution: This is, in fact, a very complicated question. Two issues might be involved here: (a) the footnotes start on the right page, but carry over some lines to the next page, or (b) they don't actually begin until the page following that on which the note call position actually appears. The first of these is perfectly appropriate and, in fact, required in many cases. The second, however, is not. The latter issue is caused by the fact that the existing bottom margin settings do not give the program enough leeway to properly keep the notes on the correct page. Specifically, in addition to the standard bottom margin, NB allows you to set “text flow” adjustments (see Format, Page Layout, and then click the Text Flow button). It is these adjustments that allow you to specify how much longer, or shorter, you are willing to let the page be in order to keep the various elements (footnotes, widows and orphans, etc.) positioned properly. In general, although you can also increase the amount by which the page can become longer, the most reliable way to make sure that NB can properly break pages (the way that produces the most pleasing and appropriate results) is to increase the amount by which the pages can become shorter. The behind-the-scenes page composition issues involved here are very complex (widows and orphans need to be prevented, while room needs to be made for both notes and the note separators), so it may be easiest to see the issues from an example: If the first footnote on a page with double spacing occurs on what would be the very last line of text on that page (thus requiring the note itself to appear below the last line of the page), NB obviously cannot accommodate that note on that page unless the amount by which you’ve specified the page can become longer is large enough to account for (a) both the footnote separator (at least a line, but usually two) and (b) the first line of the note itself. If you have not explicitly allowed NB to increase the page length by that much when it is necessary, NB then tries to move the line containing the note to the next page. But—since the text is doubled-spaced—if you’ve not allowed the page to become at least 2 lines shorter (and that’s leaving out widow and orphan control, which might require even additional lines), NB cannot do that either. Caught between the impossibility of following either of the two rules (governing shorter and longer pages) that have been imposed, NB simply breaks the pages as you’ve written them. But if you allow shorter pages on the Page Layout, Text Flow dialog (we’d recommend setting it to at least 4 lines), NB will then be able to keep the beginning of notes on the pages on which they belong. Note that you can also make these changes in Expanded/Codes View by changing the third and fourth values of the «BT.....» command: The third value specifies the permissible margins for longer pages, while the fourth specifies those allowed for shorter page. It’s the ®MD+IT¯difference®MD-IT¯ between these values and the second BT setting, which is the normal bottom margin, that is important. (Note that the Page Layout dialog lets you specify the difference, while the command itself uses the absolute values for regular, longer, and shorter pages.) See: Widows and orphans don’t seem to work ®LD-¯ ®C12¯) Problem: Widows and orphans don’t seem to work. Solution: Widow/orphan control is only one of many factors that are taken into account when pages are broken. Other considerations—the normal, minimum, and maximum bottom margin settings, along with the requirement that at least the first line of a note be on the same page as the note call number—actually take precedence over preventing widows and orphans. In many cases, these various requirements are contradictory, and a completely satisfactory resolution is not possible. Indeed, the Chicago Manual of Style notes that “a manuscript peppered with footnote references, two or more of which might fall in the last line of text on the printed page, may well be a typesetter’s nightmare. Similarly, several long footnotes . . . present a sometimes insoluble problem in any kind of page makeup (15.42). . . . [The solution] requires the cooperation of the author or editor or both (19.40).” The problems for page makeup are particularly acute for double-spaced papers (as opposed to publication-quality manuscripts), since preventing widows and orphans requires moving two lines (the actual line of text, along with the intervening blank line) at page breaks, thus either shortening or lengthening the page by that number of lines. While there’s very little you can do about the requirement that the body of notes begin on the same page as where they are called (and, as noted above, this is always a higher priority than widow and orphan control), you can increase the chance of widows and orphans being prevented by making sure that the page margins have enough leeway to allow that to happen. Specifically, for there to be any chance for widow and orphan control to be in effect, the difference between the normal bottom margin and the smallest or largest ®MD+IT¯allowable ®MD-IT¯bottom margin must be at least equal to one line of text. The Nota Bene defaults, which are based on publication-quality manuscripts, allow for a difference of one and a half lines (for both largest and smallest allowable margins). But these default settings will not work in double-spaced text, since, as noted above, two full lines need to be moved to avoid bad breaks. When setting the minimum and maximum bottom margin, it’s not uncommon to allow pages to become longer by fewer lines (say, one line) than one allows them to become shorter (perhaps one would accept a page that is two or three lines shorter). This is in fact what we recommend, especially when double spacing. The normal bottom margin is set using Format, Page Layout, and then setting the Body Text setting in the frame labeled Bottom. The minimum and maximum settings are adjusted using the Text Flow button on this same dialog. The first setting on the Bottom of Page portion of the Text Flow Adjustments dialog (Allow Page to be Shorter than Normal by: . . .) specifies how many lines you are willing for the page to be shorter than the standard page length. The second setting (Allow Page to be Longer than Normal by: . . .) specifies how many lines longer than the standard length you are willing for the page to become. If using double spacing, at least one of these settings must be two lines or more in order for widows and orphans to work properly. Finally, to repeat what was said at the outset: If you make the necessary adjustments as described above, widows and orphans may still be encountered if preventing them would lead to an even more problematic bad break, specifically related to unlinking footnotes to the page on which they appear. Furthermore, you need to remember that sometimes preventing a widow or orphan on the current page would lead to even more troublesome breaks at the bottom of the next page, and page break calculations need to take that into account. In short, a total ban on widows and orphans may require the “cooperation of author and editor or both.” See: My footnotes don’t print on the page on which they occur. ®LD-¯ ®C12¯) Problem: Can I run NB on a Mac? The answer is cautiously “yes,” but with qualifications. 1. A number of people (probably at least a couple of dozen or more) report running NB successfully under Virtual PC on the Mac. And there are likely others who simply haven't told us of their experience. Although one part-time NB employee tried this years ago (with apparent success), nobody else here at Nota Bene has. 2. However, we cannot (lacking a Mac in house, among other reasons) support it. This means that if there is any problem on a Mac, we would need to be able to reproduce that problem on a PC, or else we will not be able to fix it. 3. On the other hand, to date there are no known Mac-only issues. (We did recently have somebody call us with a printer-related installation problem, which we were not able to solve ourselves, although we were able suggest things that helped the computer consultant who was installing the system to get it to work.) 4. Although, to the best of our knowledge, NB runs properly on a Mac with Virtual PC, the major issue is speed—performance will always be more sluggish on Mac's than on PC's. (But see next point.) 5. If possible, you should run Windows 98, not XP, on Virtual PC. Here’s what one NB user had to say about this: “I thought you might like an update on my experiences running NB 6.1 on the Virtual PC on my PowerBook. I was ready to despair this week because NB ran like sludge on the VPC running Windows XP Pro, with a noticeable time-lag between typing and seeing on the screen. I called the folks at Connectix and they suggested several modifications to WXP to speed things up. But a colleague suggested installing an old copy of Win98 on the VPC and running NB on that. Well it works like a charm now!” What follows is an email from a Mac user who is running Nota Bene, discussing a number of relevant issues: -----Original Message----- From: notabene@piper.hamline.edu [mailto:notabene@piper.hamline.edu] Sent: Friday, January 02, 2004 12:11 PM To: Multiple recipients of list NOTABENE Subject: Re: Virtual PC and Nota Bene on the MacIntosh [Comment to which email is response]: You have to keep in mind that you will have three layers between the machine and NB: Mac operating system, Virtual PC, Windows whatever, NB. True, but Virtual PC is surprisingly efficient and non-intrusive, a thin "layer" if you will. When combined with today's fast processors such as a G4, you might not feel NB is slowed down significantly. As for simplicity, the Mac "layer" and the VPC "layer" can become totally invisible when using NB, so that's hardly an issue. On the other hand, you'll probably experience your Mac working a lot harder with VPC running, especially if your Mac is a mini-laptop like mine. Think heat and fan noise. The origin of this thread was a desire to eliminate similar problems on a Windows laptop, so if that's your objective, don't bother with VPC. [Comment to which email is response]: The Virtual PC program does not come with the Windows operating system. You have to buy Windows and add that layer too (unless you already own a copy you can install). VPC is not cheap ($129), not including Windows. Also note that VPC does NOT run on a G5 yet. Microsoft is "working on it". Also, reports of incompatibilities and non-functioning Windows features are increasingly common. [**Virtual PC 7 has recently been released and can be run on a PowerMac G5**] Back in the good old days, before MS bought out VPC, my own experience was that VPC/Windows was as stable as Windows on an Intel machine. What's terrifying about VPC is that with MS now doing the programming and service, complaints are mounting rapidly. Is that surprising? ®LD-¯ ®C12¯) Problem: Auto Check and Replace does not seem to work. Solution: Auto Check and Replace should: 1. Give you audio feedback (but nothing else) if the word you are typing is not entered as a replacement pair in your personal dictionary (but your computer speaker/sound system needs to be turned on) --Example: Try typing "theer" 2. Change the word to the corrected form if you have a replacement pair entered into your dictionary --Example: When you type "the," "the" should appear instead If that's not what's happening, you should: 1. Check that you have a personal spelling dictionary active. Go to Proof, Spell, and click User Dict... Browse to your dictionary and click Load. 2. Make sure that the correction that you expect is actually entered as an Auto Replace/Correction Pair in your dictionary (in case some setting on your computer makes the audio feedback for unrecognized words inaudible). Click Edit under your dictionary path in the Edit Custom Dictionary dialog. Scroll down to find the word pair you are looking for. If it is not there, you can type the misspelled word and replacement text and then click Add. ®LD-¯ ®C12¯) Problem: Some Hebrew vowels (such as the holem) look odd or don’t appear at all when I use the NB Moriah or NB Ramah font. Solution: A little background about how NB works will help in understanding the issues involved. When languages are selected in NB Lingua Workstation, Nota Bene does not switch fonts, but simply changes the character set of the existing font. This procedure works well for Greek and Cyrillic in all versions of Windows. However, in Windows 95, it did not work for Hebrew, since the Hebrew characters were missing in the fonts shipped with Windows 95. Lingua Workstation compensated for this deficiency by including the NB Ramah and NB Moriah fonts. Although it appeared to the user that NB was handling Hebrew just as it did Greek and Cyrillic, without actually switching fonts, in fact behind the scenes NB would switch to the appropriate Hebrew font (but without actually including a Use Font [] command in the file, as would otherwise normally be necessary). This problem was removed in Windows 98 and higher--the basic fonts (Times New Roman, Arial, Courier New, etc.) shipped with those versions of the Windows all include the Hebrew alphabet. In addition, these versions of Windows also include still other large-character-set fonts, some of which also include Hebrew characters. Therefore, when you select Hebrew in one of these versions of Windows, it is these Windows fonts which will be used (rather than NB Ramah or NB Moriah). Users of these Windows versions who want to use the two native NB Hebrew fonts, NB Ramah and NB Moriah, can still do so, but only by selecting them as fonts using the appropriate Use Font commands. The presence of these competing font-rendering systems does create problems for users of Windows 98 and higher because the font metrics and accent positions differ between the two systems. Lingua Workstation assumes that the Windows fonts will be used, and includes a LINGUA.TBL file that positions the accents properly for those fonts, but not for the native NB Hebrew fonts. However, if a user elects to use the NB Ramah and NB Moriah fonts instead, this LINGUA.TBL file will not produce the same elegant results that Windows 95 users were accustomed to. That’s why an alternate LINGUA.TBL file is provided for those who wish to use the NB Ramah and NB Moriah fonts instead. To use the LINGUA.TBL file for NB Ramah and NB Moriah, follow these steps: 1. Quit NB 2. In Windows Explorer, change the name of the LINGUA.TBL file in \NBWIN (perhaps to LINGUAOK.TBL) 3. Change the name of the LINGUA95.TBL file in \NBWIN to LINGUA.TBL 4. Restart NB To restore the original LINGUA.TBL file for the Windows fonts, follow these steps 1. Quit NB 2. In Windows Explorer, change the name of the LINGUA.TBL file in \NBWIN back to LINGUA95.TBL 3. Change the name of the LINGUAOK.TBL file in \NBWIN (saved earlier) back to LINGUA.TBL 4. Restart NB ®LD-¯ ®C12¯) Problem: When I paste text between NB and other applications, I get unwanted font and line spacing changes. Solution: The issues differ depending on whether you are pasting text into NB or from NB into another program: 1. If you are pasting from another application to NB, you have two choices: a. Text and Formats: Ctrl + V will paste in the text in your document and keep the formatting from the other application (assuming that the material copied in the other application was saved with the formats [in RTF format] by that other application) b. Text Only: To paste text without the formatting from another application, press Ctrl+Shift + V (or Edit, Paste Special...) to access the Paste Special dialog. Select Unformatted Text to past in only the text (i). If you would like to set Ctrl + V to paste in unformatted text, select the Options button on the Paste Special dialog (Ctrl+Shift + V). Check the box under the Pasting From Clipboard section of the Clipboard dialog. 2. If you are pasting from NB into another application, the situation is a little more complex: NB ordinarily saves both text and format (in RTF format) to the clipboard. If the receiving application has the same Paste Special option as in NB (see above), you may be able to use that to control what actually gets pasted. If it does not (as is not infrequently the case), you can prevent NB from saving formats to the clipboard in the first place by selecting the Options button on the Paste Special dialog (Ctrl+Shift + V) and checking the checkbox under the Saving (Cutting/Copying) to Clipboard section. ®LD-¯ ®C12¯) Problem: My toolbars don’t show up. Solution: The first thing to check is that: 1. There is no check mark before the View, Full Window (Toggle) option, and 2. The desired toolbars are selected under View, Interface Options (the toolbars you want to display should be checked). If that doesn’t fix the problem, you should be able to resolve it by using Windows Explorer to copy the NB.INI file from \NBWIN\USERS\INITIAL to \NBWIN\USERS\DEFAULT (if you installed Nota Bene in a different folder, substitute that folder name instead of "\NBWIN" above). This replaces your customized configuration file with our default shipping version. (But note that other customizations will also be lost.) Please note that depending on your system configuration, NB.INI may show up as an icon with only the name NB (without the .INI extension displayed); if you select View, Details (in My Computer or Windows Explorer), however, it should display Configuration Settings in the Type column. But before you overwrite the version that exists in \NBWIN\USERS\DEFAULT, we'd be grateful if you could email that (likely defective) version to us, so that we can try to figure out why it's become corrupted. ®LD-¯ ®C12¯) Problem: I have a lengthy document on my home computer that I want to print out an another machine using a different printer (e.g., Apple Laser Printer). But when I open the document on the other computer (with identical software and Windows version) the pagination has changed and the numbers at the top of the page are closer to the first line of text than they are on my home machine. What setting do I need to adjust to rectify this difference, i.e., to have the document maintain identical pagination on both computers? Solution: What you are trying to achieve—absolutely identical pagination and line placement—may not actually be possible, since both are controlled by the active printer driver, and, depending on configuration, different devices have different font metrics (different glyphs with different widths and vertical leading). That means that you cannot be assured of identical results in what are actually two different environments (the same version of NB and operating system notwithstanding). While that means that you are somewhat at the mercy of the new device in regards to pagination (aside from whatever manual adjustments you can make [page breaks, line spacing, etc.]) , you should be able to change the spacing between the bottom of the running header and the body text for a particular printer by going to Format, Page Layout, and then, in the Margins tab, making changes to the Top settings for Header and Body Text. ®LD-¯ ®C12¯) Problem: Files I create in pdfFactory seem to use a smaller font, and have narrow text width (and thus larger margins) than the file appears to have in Nota Bene. Solution: The problem is likely that when you print the file from Adobe Acrobat, the Page Scaling option on the Acrobat print dialog is set to something other than "None" (perhaps it is "Shrink Large Pages"). Once you set this to “None,” it should print with the same dimensions you see in Nota Bene. ®LD-¯ ®C12¯) Problem: When I copy text from an email into Nota Bene, there appear to be carriage returns at the end of every line, and not only at paragraph ends. How can this be avoided? Solution: Email programs (including Outlook) usually save a hard carriage return at the end of every line, even internal to a paragraph, and Nota Bene is simply converting that correctly. (More sophisticated programs, such as word processors, save a soft line end character at the end of lines within paragraphs.) In version 8, press Ctrl+Shift+Del to change these hard carriage returns to a space. However, in cases when two paragraphs are contiguous, without any blank separating line, paragraphs will not be kept distinct. ®LD-¯ ®C12¯) Problem: I’m having troubling installing the program from the CD. Solution: First make sure that: 1. You rebooted your computer right before you installed. 2. You disabled your anti-virus program before installation (if you have Norton, right click on the icon [usually a shield] at the bottom right of the screen, and uncheck the "Enable File System..." option; be sure to re-enable it after installation is completed) If, after rebooting and checking to make sure that the anti-virus program is disabled, you are still unable to install the program, email ®HK1Email|technicalsupport@notabene.com¯technicalsupport@notabene.com®HK0¯ and you will be sent a link to a private URL where you can download the entire program. In almost all cases, this is the best solution. Be aware that the download process will take only 5 minutes or so on a fast internet connection, and between 45 minutes and an hour on a 56K (dial-up) modem. If the machine on which you want to install the program lacks an internet connection, or you are worried about the time or ease of downloading the program, you can attempt to copy the contents of the CD to a folder on your hard drive, and then install Nota Bene from there. To copy the CD to the hard drive: A. Create a temporary folder on your hard drive (preferably named something like \NBTEMP) B. Insert the CD into the CD drive Make sure that the installation does not start automatically if your system is set to auto run --You may be able to prevent this by holding the SHIFT key when inserting the CD --Failing that, at the first opportunity click the Cancel button to stop the installation process C. Using My Computer or Windows Explorer, select the CD drive (double click on it), and then select all the files on it (press Ctrl + A to select all files). Copy them to the clipboard by pressing Ctrl + C D. Back up to the top level in the same program (My Computer or Explorer), select your hard drive (double clicking it), and then open up the previously created \NBTEMP folder (by double clicking it), and paste in the files from the CD (Ctrl + V) E. If all the files copy without error, double click on the SETUP.EXE file that was just copied (or go to Start, Run, and type in "c:\nbtemp\setup.exe" (without the quotes) and press OK) If the above process does not work, we could send you another disk. If the CD we originally sent was defective a new CD will probably solve the problem. However, if the problem lies in an incompatibility between our CDs and your system’s CD drive, a new disk won’t fix it. In these cases, we recommend downloading the full program from our website. ®LD-¯ ®C12¯) Problem: Although there is enough room for the entire footnote to fit on a page, the last line of the note is always moved to the next. Solution: The problem is caused by invalid settings in the BT (bottom margin) command, specifically relating to the positions of the footer relative to the last line where footnotes are allowed to appear. This is probably most easily understood by starting from a specific example. Suppose the current settings are: BT1.6CM,1.6CM,0.97CM,2.23CM (The first number after the BT command (1.6cm) is the distance from the bottom of the page to the bottom of the running footer. The second number (1.6cm) is the distance from the bottom of the page to the bottom of the text area. The third number (0.97cm) is the minimum distance from the bottom of the page to the bottom of the text area. (see FAQ #33 and #32). The fourth number (2.23cm) is the maximum distance from the bottom of the page to the bottom of the text area.) While the last three numbers are perfectly valid, the first is not, since it tells the program that the running footer should be positioned on the same line as the last line of text, which is an impossibility. When composing the page, NB starts at the footer position (this by definition is the last printable line on the page) and this value takes priority over all others. Because the last line of text cannot be on that same line, NB cuts the page short by one line (in this case that last line is the footnote), and moves it to the next. This can be fixed by setting this first value to be smaller than the other settings in the BT command (e.g., .6CM instead of 1.6CM, in this example). This can be done either by changing the Footer position in the Format, Page Layout dialog, or by editing the values in Expanded/Show Codes View ®LD-¯ ®C12¯) Problem: How do you set page numbering to pick up again after a series of pages which you don’t want to have numbered? Solution: This is best addressed by using an example. Suppose you have a document with pages 1 to 23, and then you want five unnumbered pages, and then the next page to pick up again at number 24. Assuming that you have a running header or footer set up to print the page numbers, you need to issue a Set Page 1 command at the beginning of the document (NB automatically starts with 1, so this is not strictly necessary). Then, at the top of the first page you want to be unnumbered, set a new header (Format, Headers/Footers, and select Beginning of Current Page) that has no page number. Then, at the top of the page you want to be numbered 24, set another page number command to Start At 24. However, for this latter command the page number under Type must be set to "Begin Sequential," not "Continue Sequential." If it is set to the latter, the program would use page number 29 (after reaching 23, the program would continue counting for the next five pages, even though the numbers were not printed). Manually setting this page number means that, if the document changed, and what was originally page 23 became page 25, you would need to manually adjust the numbering page again to account for this change. In other words, there is no way for the continued number to "float"--i.e., always be six more than the last printed number. For manuscript files, this means that, although all set-page numbers in component files that are included in a larger manuscript file can, and should, use the "Continue Sequential" option (it's ok also to do so for the first, since, in the absence of any prior page numbering, "Continue Sequential" is treated as "Begin Sequential"), the command to pick up a number at a particular point after a broken sequence requires that the number be set to "Begin Sequential," and thus manually adjusted if the page number changes. ®LD-¯ ®C12¯) Problem: I’ve set up an outline where the SSTYLES include BOTH the counters AND the following punctuation/space in hopes of further automating entry. But on my screen in Graphics view the indents are all messed up. Solution: This is one of those issues that may qualify for that overused defense that it "works as designed." The problem here is that: (1) indentation commands take effect on the current line only if they precede all printable text on that line (2) the style definition includes printable text (after the semicolon; even before adding this punctuation, there is admittedly a command, and while this displays in the document, it is not treated as printable text) (3) when a style is used, the presence of printable text of any kind sets a flag which is subsequently checked when any format commands also contained in that style are output; this flag tells the program that the commands are not to take effect on the current line, but only starting on the next line Although this may seem counter-intuitive, or bad design (you would think that the precise placement of the format commands after the semicolon should determine whether they are treated as occurring before the printable text, or after it), there are in fact various complicated internal reasons why NB works this way. There is a workaround, namely using one style to set the indentation, and then another to set the counter and punctuation. That's the approach adopted by frameworks/outlines, where a "textless" does the former, and a does the latter. You could adopt this approach yourself, or, better yet, utilize NB’s framework/outline elements. This latter, while it has significant overhead in terms of the number of commands it relies on, gives you all sorts of useful capabilities lacking in homegrown outlines (you can outdent, indent, move items up and down, select with a single keystroke either a single point or an entire branch, add or suppress underlying text, and view it in outline view, with many different options, among other things). ®LD-¯ ®C12¯) Problem: Nota Bene always puts a blank page after the endnotes. Solution: NB for Windows has always had a tendency to put an extra blank page after endnotes (since any text following where notes are dumped always starts on a new page, and Nota Bene is implicitly outputting the codes to ensure that that will happen). While this blank page will be suppressed when documents are combined together in a manuscript, it does waste paper. You should be able to suppress this blank page for the current document by going to Expanded/Codes View and deleting the «PG»¶ at the end of the «SS{ENDNOTE1};....» command at the top of the file. But doing so may not be safe in every circumstance. In general, having those commands make endnotes work better, especially when multiple chapters with endnotes are combined into a book-length manuscript. ®LD-¯ ®C12¯) Problem: Hebrew does not get flipped properly (and editing is difficult) in Show Codes View. Solution: Typing in Hebrew in Show Codes View has never worked, nor have we ever intended for it to work. The issues here are actually very complex. Codes view has traditionally not tried to interpret ANY commands (in NB for DOS, for example, you could not even see the languages properly in Expanded View). In Windows, we made a concerted effort to show the characters themselves, but still do not otherwise format the document (including flipping the Hebrew). Codes view, in other words, is an attempt to show the data stream of the file in a non-formatted way. The strange behavior here that some people encounter results from different versions of Windows (mostly earlier versions) that leave the output of drawing functions intact. XP, however, when it sees characters in the Hebrew range, tries to do its automatic reversing everywhere, flipping (against NB's desires!) some of the characters (the regular forms), but not others (Nota Bene's smart characters, which XP does not know are actually Hebrew as well). ®LD-¯ ®C12¯) Problem: If an image in a frame is given a fixed position at the bottom of the page, and text is added at the beginning of that page, what happens to the image? Does it stay where it is supposed to be relative to the new text as a whole or does it get pushed to the next page?nn Solution: It should stay at that fixed position on the bottom of that page (with some existing text moved to the next page, being pushed there by the newly added text) unless the command that fixes the frame in that position is actually positioned with the text that is moved to the next page (you can see whether or not this is the case in Show Codes View), in which case the image will move along with this command. In short, the logic is more or less like this: If the text where the frame is physically defined (regardless of where it is rendered on the page) can fit on a page, the frame will be positioned at that position on that page; if the text must move to the next page, the image will be positioned at the designated position on the page to where that text moves (where the frame is defined). This mean that for frames as well as for some other commands (e.g., running headers) to be positioned without surprises, they need to be defined near hard-page breaks. Otherwise, they will float as described above. ®LD-¯ ®C12¯) Problem: The tilde character no longer displays in any view but expanded/codes. Solution: This has to do with a change in the way NB displays the marker for soft hyphens. In earlier versions of NB, the tilde character served as the soft hyphen character (and was entered with Ctrl+[-]); this character was only visible in Expanded/Codes view, and would not print. The tilde key, while it entered what looked like a regular printable tilde, actually entered a differently encoded character. This method of distinguishing the printable tilde from the soft hyphen marker served NB well for many years, but the use of the tilde as part of the shortened form of long filenames (for example, in directories invoked using the command line) caused complications (i.e., the tilde character in the filename was invisible in a directory). We have change the way this works in more recent versions so that the tilde can be used in long filenames, URLs, etc: --Instead of the tilde character, we now used the standard Windows soft hyphen (character 173) as the soft hyphen character. This means that it is this character, not the tilde, which is invisible in all views but Expanded/Codes. --The standard NB keyboard now inserts a single-byte tilde rather than the three-byte one so that the regular tilde can be used in filenames and URLs, etc. (Theoretically, we could have retained the original assignment, where the tilde key entered the three-byte version, but then it would not have worked in filenames.) If you now discover that the tilde key inserts a character that is not visible in Graphics View and does not print, the problem is that while the keyboard now inserts the regular version, the soft hyphen has not yet been reassigned on your system. To change this, select Proof, Hyphenation, and click the Select Hyphen button. Then select the Standard Windows Soft-Hyphen Character. Once you’ve made this change, if you’ve used the soft hyphen character in files, you will need to change the existing single-byte tilde to the new single-byte Windows soft hyphen character. You can also do this using the same menu--check the Convert Soft Hyphen Characters.... option, and click OK. ®LD-¯ ®C12¯) Problem: DOS labels don’t get converted properly. Solution: In DOS, labels had two different purposes: (a) to mark entries for cross referencing, and (b) to as a tag which helps you locate items in a file. In NB for Windows, they are used only for the former (a). For the latter function (b), annotations (Ctrl+Shift+Alt+F1-F9, or from the menu--Insert, Annotation) are used in recent versions of NB (although their content is not visible unless you put the cursor on the highly visible annotation marker itself). However, when you convert DOS files to NB for Windows, the program can not determine the function of each label in your DOS file. Therefore, the program automatically converts them to cross-reference labels. In graphics view, these are visible as raised blue dots—you must switch to Show Codes view to view the full label. However, if you did not used labels for cross referencing in your DOS file, then you can change all the labels in a file into annotations by going to Expanded View, and doing a global change of every "<