Testimonials

See what our customers say about our products and servicesSee what our customers say about our products and services.


Books

Man and Woman, One in Christ: An Exegetical and Theological Study of Paul's Letters

Man and Woman, One in Christ, the latest book by Philip Payne. Signed copy only $19.99 plus shipping. Also see  NT essays by Payne, available for free download.


The Codex Vaticanus open, showing that each leaf has its original shape

Bibliorum Sacrorum Graecorum Codex Vaticanus B is the only color facsimile of the oldest surviving manuscript of virtually the entire Bible in Greek. It was written about A.D. 350 and is regarded as the most important manuscript of the Greek Bible. The photographic quality and color reproduction is amazingly faithful to the original. Most of the 450 numbered copies printed for sale have already been sold, so availability is limited. The $5580 price includes express shipping and insurance.


Codex Sinaiticus Facsimile, available for a short time for $475.

Codex Sinaiticus facsimile, The remarkably clear color facsimile of the fourth-century Codex Sinaiticus of all the NT and half of the LXX plus Tobit, Judith, 1 and 4 Maccabees, Wisdom, Sirach, Barnabas, and the Shepherd is available for a limited time for $699.95, Order Form. We believe this is by far the best price available anywhere. The list price is $999. Shipping the 32 lb box by UPS ground is $59 within the USA 48 states. Shipping to the UK is $149 and $129 to most other western European countries, Hong Kong, Japan, and Korea are $149. Egypt, Israel, India, and Singapore are $169. 828 pages 13.5 x 16.5 in., cloth with slipcase. ISBN: 9781598565775


Le manuscrit B de la Bible

Le manuscrit B de la Bible, probably the most important book on Codex Vaticanus ever written, with PB Payne's historic chapter on Distigmai. Only $49.95 plus shipping.


FAQ — Windows


How do I find help for problems using the Windows products? Linguist's Software Windows products include detailed support documentation for technical problems. To find help in the product manuals:

  • If your product included an installer that placed files on the Windows Start menu go to Start | Programs | Linguist's Software | <product name> | Troubleshooting Manual.

  • If your product was not added to the Start menu, but was purchased since mid-2002, you will find help in the Troubleshooting Manual in PDF format on the product diskette or CD.

  • If your product was purchased between late 1999 and late 2002 you will find these issues addressed in the Getting Started section of the Installation and Getting Started Manual or in the electronic help file (Linguist.hlp) included on the product diskette.

  • If your product was purchased between 1997 and 1999 these issues are addressed in the included Technical Manual.

  • Products purchased prior to these dates have technical issues addressed in the product User's Manual.


Following are solutions for the most common problems users encounter. If you do not find your problem addressed here please contact us for support.

Are your Windows products Windows 10, 8, 7 and Vista compatible? Although the fonts you purchased from Linguist's Software since mid-1997 are compatible with Windows 10, 8, 7 and Vista, the keyboard software that worked in Windows NT4, 2000, and XP is not compatible with Windows 10, 8, 7 or Vista, and must be updated. We have completed many of these keyboards, but some are still to be done. This table lists the products that are Windows 10, 8, 7 and Vista compatible. If you own a product that has not been updated for Windows 10, 8, 7 and Vista you may install it using the instructions for Windows XP. During installation, if you see the black command window appear on screen with the little message "Starting installation of keyboard files" be sure to click Cancel. This will produce an error message, and the installation will end, however, everything except the keyboards will be installed correctly. If you do not see the black command window with the message, then the keyboards will seem to install, but they will not appear in the Windows Language Toolbar, nor will they work. You will be able to open your documents and view and print them, but you must use alternate input methods (such as the Insert Symbol command in Word) for editing. If you would like to be notified when your product is ready for Vista please contact us.

The Installation process stops before finishing (my computer "hangs during installation"). This is usually caused by interference from another program that started when Windows started. The problem can be eliminated by using the Windows System Configuration Utility. Please follow these steps: Advanced Users; Novice Users.

For Advanced Users: How To Do A Clean Boot Using the System Configuration Utility

1. Click "Start", click "Run", type "msconfig" (without the quotation marks), and then click "OK".
2. In "System Configuration Utility", click the "Services" tab, and then click to select the "Hide all Microsoft Services" check box.
3. Click "Disable All"
4. Click "Startup" tab.
5. Click "Disable All"
6. Click "Apply" then "Close"
7. Restart computer
8. Insert the Linguist's Software CD and install the Linguist's Software program.

When the installation is complete, and you have printed the Welcome message, you must bring your computer out of a clean boot.

1. Click "Start", click "Run", type "msconfig" (without the quotation marks), and then click "OK".
Note: you can choose to do the following steps or just click "normal startup"
2. In "System Configuration Utility", click the "Services" tab, and then click "Enable All"
3. Click "Startup" tab.
5. Click "Enable" All
6. Click "Apply" then Close
7. Restart computer

For Novice Users: Detailed Instructions For Using The System Configuration Utility

1. Save your work and close all programs.
2. Go to Start, Run, and type "msconfig" (without the quotations) and press Enter. This starts the System Configuration Utility. Click on the "General" tab if it is not already selected. There should be a bullet in "Normal startup"; this is the way Windows normally starts.
3. If the setting for you is different make a note of it, so you can choose it again later.
4. In the System Configuration Utility that opens select "Selective Startup", and then uncheck everything except "Load System Services" and "Use Original BOOT.INI". (This will prevent all third-party programs from starting when Windows boots up.)
5. Click on the "Services" tab.
6. Place a check in "Hide all Microsoft Services". Now you will see only Services provided by other software manufacturers, not Microsoft. Click "Disable All". Now uncheck "Hide all Microsoft Services" to restore the services made by Microsoft. You will see that only Microsoft services are now selected.
7. Go back to the General tab to confirm your earlier selections ("Selective Startup" and only "Load System Services" and "Use Original BOOT.INI").

In the next step your computer is going to shut down and restart with only Windows' very basic services running. The purpose of this is to eliminate any other software that might be interfering. It does no damage to Windows.

8. Click OK and your computer will shut down and restart. After Windows comes up you will get an alert message telling you the computer did not load all the services (I do not remember the exact message). Click the OK to close the message. A moment later the System Configuration Editor will come up. Click CANCEL to close it. (Do not click OK or your system will reboot. We will do this later.)

9. Use Windows Explorer to navigate to the folder where you have stored our files, or insert your CD and run them off the CD. Attempt to run the installation again by double-clicking on it if it does not start automatically. If the installation is successful the last step it to print a one-page set of instructions.

10. Whether it is successful or not we now will restore your computer to normal.
a. Go to Start, Run, and type "msconfig" (without the quotes) and press Enter. In the System Configuration Editor that comes up select "Normal Startup".
b. Caution: If you discovered a non-default setting in step 2 above, and wrote down what that setting was, then instead of selecting Normal you should reselect that non-default setting in order to return your computer to the state it was in.
c. Click OK to shutdown and restart normally. Your computer will return to normal.

If running the installation was successful then you can continue setting up keyboards following the instructions in the one-page Welcome sheet you printed. You can then use the product normally.

Certain letters with diacritics cannot be typed in Microsoft Word. This can effect multiple language products. For example, when trying to type Greek using LaserGreek in Unicode fonts and the GreekLSClassical OT keyboard driver, you cannot add an acute accent or grave accent above a letter. Or, when using the TransIndicLSU font you can type A-underdot, but cannot type H-underdot, R-underdot, or S-underdot (which are supported by the font). You can also type A-tilde, but cannot type N-tilde.

  • This problem is caused by an advanced setting in Word called Use sequence checking which restricts input of certain sequences of letters. This setting becomes available in Word as soon as "complex script" supplemental language support is installed in Windows. In Word 2003 this setting is off by default, but in Word 2010 and 2007 it is on by default. Turning the setting off resolves the problem. To see if the trouble you are having is caused by this setting do this:

  • In Word 2003 go to Tools, Options…, Complex Scripts. Remove the check from before Use sequence checking, and click OK. (If the Complex Scripts page is not available in the Options… dialog box you do not have "complex scripts" language support installed, and this setting is not the source of the problem.)

  • In Word 2007 click on the Office Button, then click on Word Options, then Advanced. Under Editing Options remove the check from before Use sequence checking, and click OK. (If you do not have "Use sequence checking" near the bottom of the Editing Options section of the Advance Word Options dialog box then you do not have a "complex scripts" language or keyboard installed, and this feature is not the source of the problem.)

  • In Word 2010 click on the File menu item, then click on Options to open the Word Options dialog. Click on Advanced, then under Editing Options remove the check from before Use sequence checking, and click OK. (If you do not have "Use sequence checking" near the bottom of the Editing Options section of the Advance Word Options dialog box then you do not have a "complex scripts" language or keyboard installed, and this feature is not the source of the problem.)

  • After you turn off (or "uncheck") Use sequence checking, you will be able to type the letters with diacritics that were being restricted by Word.

The Ctrl-Alt+g keystroke does not work. Have you changed Word's default settings according to the Customize Word Settings document, but Ctrl-Alt+g still does not work? Do you have Google Desktop for Windows installed? Many Dell computers come with Google Desktop pre-installed. In addition, Google Desktop is installed as a free download along with certain other programs. Google Desktop has certain keyboard shortcuts (including Ctrl-Alt+g) enabled by default. This shortcut must be disabled in order to use Linguist's Software keyboard software. To do this see http://desktop.google.com/support/bin/answer.py?hl=en&answer=37219.

The Greek sigma changes to a final sigma when followed by an accented letter. This problem applies to LaserGreek in Unicode for Windows fonts when used with the GreekLS Classical deadkey keyboard in Microsoft Word for Windows. A sigma will be changed to a final sigma when followed by an accented letter if the "Ordinals (1st) with superscript" AutoCorrect feature is turned on in Microsoft Word. To correct this problem in Word 2007 click the Office Button, select Word Options, then Proofing, then AutoCorrect Options.... In Word 2003 click the Tools menu item and select AutoCorrect Options.... Now in both versions of Word select the "AutoFormat As You Type" page of the AutoCorrect dialog box, and deselect (remove the check from before) "Ordinals (1st) with superscript", and click OK. Now a sigma in the middle of a word will not change to a final sigma when followed by an accented letter. Note, however, that the automatic final sigma will cease to work, and you must manually enter a final sigma (by typing Shift+apostrophe).

Word 2007 does not properly embed all characters in an embeddable font. If you have a font licensed to be embedded in Word documents, and if you use Word 2007, you should save your Word document as a "Word 97-2003 Document" (a .doc document) in Word's Save As… dropdown menu, to insure all characters are properly embedded in the document. If you save a Word 2007 document as a Word 2007 format .docx document, some of the embedded characters will not be embedded, and will appear as empty boxes when viewed on a computer where the embedded font is not installed. If you must save the document as a .docx document, then uninstall the embedded font(s), open the saved document, and carefully check the embedded characters for any characters that failed to embed. (Note: You must have the embeddable version of a Linguist's Software font to embed the font in Word or in PDF. See the Font Embedding License application for details.)

The Windows Language Bar does not work as expected (or no longer works). If you use ZoneAlarm (ZA) or ZoneAlarm Pro version 6.0 there is a new feature in ZoneAlarm (called the OS Firewall) that prevents the Windows Language Bar from working normally. When you attempt to Apply settings in the Regional and Language Options Control Panel, or when you attempt to Restore the Language Bar from the Task bar to the upper right corner of the Desktop, or occasionally when you attempt certain other normal operations with the Language Bar, ZA will pop up a Security Alert warning you a program is attempting to do something to the CTF Loader (such as monitor keystrokes), and will prevent the action. In order to regain normal operation of the Windows Language Bar you must open ZA, select Program Control, select Programs, and select the CTF Loader. Then under Trust Level you must right click and choose Super (giving CTF Loader Super Trust level). ZA will then allow the operation, but will constantly pop up Security Alerts. On one of those alerts you must check the box to "remember" the setting and click Allow to force ZA to allow the normal operation of the Language Bar. Search the Zonelabs User's Forums for the term "CTF Loader" for more information on this "feature" of ZA.

I cannot type decimal characters 253 or 254 using the keyboard. The keystrokes used to enter decimal characters 253 and 254 in Linguist's Software fonts no longer work in Word 2007, 2003 or 2002, but continue to work in older versions of Word, and in other tested programs. Character code input (Alt+0253 and Alt+0254) also no longer works in Word 2007, 2003 or 2002 for these two characters. Microsoft has acknowledged this problem, however, currently has supplied no fix. (We have alternate input methods; please continue reading.)

In Linguist's Software Unicode-encoded fonts these two characters will be ý and þ. In our non-Unicode-encoded fonts they usually will be different, and will depend on the language. To learn which characters are affected in the non-Unicode font(s) you own see the Character Code Tables included with the Linguist's Software font product. Identify characters 253 and 254 and then locate those characters on the Keyboard Layout Chart(s) to see which keystrokes will no longer work.

There are three alternate methods to get around this problem: 1) Use the Insert Symbol feature from the Word menu (Insert, Symbol, [then "More Symbols" in Word 2007], then select the font and character, and click Insert); 2) type the character in WordPad and copy and paste the character into Word; and 3) create a Word Shortcut keystroke for those two characters. To do this in Word 2003 and 2002, select the character, go to Insert, Symbol, Shortcut Key..., and type your desired shortcut key in the field called Press New Shortcut Key. Click Close twice to return to Word. To do this in Word 2007 select the character then go to Insert, Symbol, More Symbols..., Shortcut Key..., and type your desired shortcut key in the field called Press New Shortcut Key. Click Close twice to return to Word.

Typing produces boxes in InDesign 2.0 in Windows 2000. Boxes are produced when using Linguist's Software ASCII-encoded TrueType fonts with InDesign 2.0 in Windows 2000. This does not happen with other combinations of InDesign and Windows. For example, the fonts display correctly with InDesign 2.0 and InDesign CS in Windows XP. Linguist's Software Unicode-encoded fonts are unaffected by this InDesign problem. At this time we do not know the cause of this problem.

Overstrikes do not print using the HP Color LaserJet 5550 printer. With default driver settings, overstriking diacritics do not print using the Color LaserJet 5550 printer. To overcome this problem you must change the printer's properties. Go to Start, Control Panel, Printers and Faxes, right click on your LaserJet 5550 printer and click on Properties. Then go to Advanced, Drivers, and select 4550 Emulation, and click OK.

The ASCII-to-Unicode Converters do not convert text originally typed with very old Linguist's Software fonts. When Microsoft released Office 97 they changed the way Office applications handle fonts. This required an update to our Windows font library (and required users to update their fonts). Text typed with older fonts that were not updated must first be updated to the current ASCII-encoded font before the ASCII-to-Unicode Converter will convert the text to the corresponding Unicode-encoded font. See the System Requirements for the individual ASCII-to-Unicode Converter products for specific font/product version requirements.

Text typed in Microsoft PowerPoint 2003 changes to the Arial font. PowerPoint (included in Microsoft Office 2003) is not compatible with most Unicode-encoded fonts from Linguist's Software (except for LaserHebrew in Unicode, which is supported). All text is changed to the Arial font, whether typed with the keyboard, input using Insert Symbol, or pasted from Word using the Windows clipboard. PowerPoint users should type their text in Word or another Unicode-compatible application, and save the text as a graphic for import into PowerPoint. Users can also use WordArt to create their text. To do this in PowerPoint go to Insert | Picture | WordArt and type your text, formatting it as desired. Alternatively, users can type directly into PowerPoint using our non-Unicode fonts. Note: PowerPoint 2003 is compatible with LaserHebrew in Unicode for Windows. (The reason our Hebrew is supported in PowerPoint when the other Unicode-encoded fonts are not is that Microsoft has added support for what are called Complex Scripts, which includes right to left alphabets such as Hebrew, but Microsoft has not yet added support for non-Complex Scripts, such as Latin alphabets, Greek and Russian. Support for these alphabets is planned by Microsoft for the next version of Windows.)

Accents are distorted or wrong on screen but print correctly. In Windows XP Microsoft introduced a technology called ClearType designed to improve screen display on LCD screens (used on laptops and certain flat panel displays). When it works it produces a dramatic improvement over older technologies used in Windows (called 'anti-aliasing' or 'smoothing edges of screen fonts'). When ClearType is used on some CRT (cathode ray tube) displays it can dramatically corrupt screen display of accents (and other diacritics such as Hebrew vowel points). At least one customer has also reported this corruption on a laptop display. The solution is to turn off ClearType. In Windows XP go to Start | Control Panel | Display | Appearance | Effects, and under Use the following method to smooth edges of screen fonts change ClearType to Standard. Click OK to return to the Appearance tab. Click Apply to save the change, allowing you to immediately see the results in your document. If this does not improve the display of accents in your document then repeat the steps as before, first changing the setting to Standard and then removing the check from before Use the following method to smooth edges of screen fonts. This turns off all font smoothing. Click OK to return to the Appearance tab. Click Apply to see the results in your document.

None of the dead key keystrokes work. When you type a deadkey (for an accent or other diacritic) followed by the letter you want accented, if you either get the letters/symbols shown on both keys, or you get only the base letter, there are two probable causes:

  • You may not have the Linguist's Software keyboard set up and/or chosen. If you have set up the keyboard following instructions in the Setup Manual then be sure you are selecting the keyboard from the Language Toolbar in the upper right corner of your desktop, or from the two-letter icon in the System Tray, before you begin typing. See the product User's Manual for complete instructions.

  • The other possible cause of this problem may be the presence of a freeware utility program called Allchars, which allows input of European (accented Latin) letters using the Ctrl key. The Allchars utility will disable dead key input. Disable or uninstall Allchars to restore use of dead key input. Note that Windows provides for typing accented Latin letters through use of keyboards (which will not interfere with each other), so extra utilities such as Allchars are not needed. Note also that all Unicode-encoded fonts from Linguist's Software include the entire Latin 1 character set and a keyboard file to type those accented letters. To see these fonts click on Products and select Unicode-encoded fonts.

Three keystrokes do not work (Ctrl-Alt+d, Ctrl-Alt+i, Ctrl-Alt+l). There is a bug in the Intel® Extreme Graphics 2 Driver that disables three keystrokes in Windows (Ctrl-Alt+d, Ctrl-Alt+i, and Ctrl-Alt+l). Intel is aware of the problem, and there is a work-around. You must disable the Hot Keys feature in the Intel(R) Extreme Graphics Control Panel applet.

  • In Windows 2000 go to Start | Settings | Control Panel and double click on the Intel(R) Extreme Graphics icon.
  • In Windows XP go to Start | Control Panel.

  • If the Windows XP Control Panel is in Classic View you will se the Intel(R) Extreme Graphics icon in the Control Panel window. Double click on it to open it.

  • If the Windows XP Control Panel is in Category View you will see Pick a category on the right side of Control Panel. On the left side of Control Panel click on Other Control Panel options found in small print under See Also, and then double click on Intel(R) Extreme Graphics. (If nothing appears under See Also then click on See Also to open the list of Control Panels. Then click on Other Control Panel options.)

  • At the top of the Intel(R) Extreme Graphics window that opens click on the Hot Keys tab.

  • Remove the check from the box labeled Enable Hot Keys to disable the Hot Keys feature, and click OK to save this change. Close Control Panel. The three keystrokes will now work.

  • This bug applies to Windows 2000 and Windows XP computers using the Intel® 82830M, 82845G, 82852/82855, and 82865G Graphics Controllers.

How can I tell if I need an upgrade? Most of our products have regular updates that improve character shapes, change the character set, add fonts to the product, or make other non-critical changes that do not absolutely require you to upgrade. But there are four points in the life of our products that are critical enough they do require an upgrade. It is easy for you to check your products to see if you need an upgrade.  Do you need an upgrade? Check prices. Check current product version numbers.

When I open Linguist's Software Bible texts in a non-US version of Word for Windows and then copy and paste text from the Bible texts into a new file, spaces are sometimes placed in the file in the middle of words. Before copying and pasting text from the Linguist's Software Bible text files, first save the files as a Word for Windows file in the native format of your non-US version of Word for Windows. You must do this because the Bible text files in Linguist's Software Bible products are formatted as "Word 6/95 (*.doc)" files, using the US version of Word. This is so the files may be opened by any version of Word for Windows, including Word 6.0, Word 95, Word 97, Word 2000, and Word 2002, or by any version of WordPad (which ships free with Windows). If you open these Word files in a non-US version of Word for Windows and attempt to copy and paste text from these files into another Word or WordPad file, your word processor may add spaces in the middle of some words. Occasionally these spaces will appear on screen as boxes. To avoid this please save the files in the format native to your version of Word or WordPad before copying and pasting text from the files. Go to File, Save As..., and in the "Save as type:" list box select "Word Document (*.doc)" and save the files one at a time. You may then open and use the files normally in any version of Word or WordPad. This action will prevent text copied out of your version of Word from being corrupted when pasted into new files.

When I try to install Linguist's Software fonts Windows gives an error message and will not allow installation. All versions of Windows except Windows 2000 place a limit on the number of fonts that may be installed or on the size of the fonts folder. When these limits are reached Windows will display an error message and not allow installation of more fonts until other fonts are first uninstalled. Users may install a maximum of around 1000 TrueType fonts in Windows Me, 98 and 95. The exact number of TrueType fonts which may be installed varies and depends on the length of the TrueType font names and file names. In Windows NT 4.0 the font folder size is limited to 48 MB. Installation of Service Pack 5 or 6 increases this limit to 128 MB. In Windows 3.1 the number of TrueType fonts that may be installed is somewhere between 500 and 1000. The actual number depends on the length of filenames and paths of the fonts. As a practical note users should be aware that Windows startup time increases as the number of installed fonts increases.

I cannot input the character in ASCII position 130 in a Linguist's Software font; my word processor instead inputs the character in ASCII position 145. This behavior is caused by the Smart Quotes feature of your word processor. Smart Quotes affects the apostrophe (the single straight quote), the double straight quote (shift-apostrophe), and the character in ASCII position 0130 (which is typed with different keystrokes depending on the product). In a standard Windows code page 1252 (Latin 1) font ANSI character 0130 is the "Single Low Quotation Mark" used in some European languages. (It looks like a comma or a single curly quote on the baseline.) With Smart Quotes turned on this character will be converted to ANSI character 0145, the standard curly quote, just as will be the apostrophe (or single straight quote). Therefore, to input ASCII 130 in any of our Windows fonts Smart Quotes must be turned off or the character in position 130 will be changed to whatever is in ASCII 145 in our font. To see which character in your Linguist's Software font is affected look at the Character Code table inside the back cover of the User's Manual. To turn off Smart Quotes in Word for Windows go to Tools | AutoCorrect... | AutoFormat As You Type and deselect "Straight quotes with smart quotes". Click OK.

When I type the backslash key my non-English version of Word inputs the Yen sign instead of the character on the Linguist's Software keyboard layout chart. Non-English versions of Microsoft Word have an option that can cause Word to input the Yen sign when the backslash key is typed. To deactivate this option in Word go to Tools | Options | Compatibility. In Word 2000, in the Options window deselect "Convert backslash characters into yen signs" and click OK. In Word 97 and Word 95, in the Options window select "Don't convert backslash characters into yen signs" and click OK. The option is not available in Word 6, which is not affected.

Some text pasted into PowerPoint 2000 cannot be formatted in the correct font. Text formatted in some Linguist's Software fonts, if copied to the Windows clipboard from Word 2000 or Word 97, will paste into PowerPoint 2000 incorrectly. Certain characters will be formatted by PowerPoint in the Times New Roman font and cannot be changed back again to the correct Linguist's Software font. The solution is to use Word for Windows version 6 or 7 (Word 95) instead of Word 2000 or Word 97, copy it to the clipboard from Word 6 or 7, and paste it into PowerPoint. If the text does not include any overstriking diacritics users may also use WordPad instead of Word 6 or 7. Note that this problem only happens when text is copied to the clipboard and pasted into PowerPoint from Word 2000 or Word 97. All characters may be typed directly into PowerPoint without problems. It is only when text is pasted into PowerPoint from Word 2000 or Word 97 that the problem occurs.

WordPad does not display overstriking accents on screen. The versions of WordPad that ship with Windows 95 and Windows NT have bugs in them that sometimes cause overstriking accents not to appear on screen when typed. This is a screen refresh problem and the accents can be made to appear by forcing your screen to be refreshed. You can do this by hitting Backspace, by causing your text to wrap to the next line, or by ending a paragraph by hitting Enter. Occasionally you must cause the text to completely scroll off screen before the screen will refresh. When scrolled back on screen the accents will appear. To avoid these problems use a more advanced word processor such as Word for Windows.

WordPad puts a space after accents. The versions of WordPad that ship with Windows 98 and Windows 2000 have bugs in them that give width to zero-width overstriking accents. This causes a space to appear after every overstrike is typed. There is no fix for this. Users must use a different word processor when using fonts that contain overstriking characters.

After rebooting my computer my keyboard settings are changed. I have the third-party program Kyrillica 97 installed. The German program Kyrillica 97 for Windows installs its own keyboards. After setting up Linguist's Software keyboards according to the instructions in our Installation and Getting Started Manual and then rebooting your computer, Kyrillica will change the settings of the Linguist's Software keyboards so they will not work. Please contact us for a modified setup file which will allow Linguist's Software keyboards to work at the same time as Kyrillica 97 keyboards.

Can I use your fonts to create a Windows Help file in a certain language? You would be able to create a Help file using our font, but the font you used would have to be installed on any computer opening the Help file or Windows will display the text you type in a standard Windows font (Arial or MS Sans Serif, etc.). Therefore, you would have to license a copy of our font for every computer on which you installed the Help file. (To initiate such a License Agreement request, please download the license application, complete it as completely as possible, and fax it to the number given. Our company president will contact you with a proposal.) An alternative way you could create the text for your Help file is to use a graphics program to convert the non-English text into small bitmap graphics which you include in the Help file. This way you only have to purchase one copy of the font (the one you use to create the graphics files), acknowledge use of the font in your Help file and provide a link to our site so viewers could come to us if they want to buy the font. See paragraph 3 of the Software License for the form of the acknowledgement.

Overstriking accents are not printing correctly. Some printer drivers are set by manufacturers so their default settings will not properly handle overstriking characters. The solution is to go into your Printer settings or Properties dialog box and change the settings from Auto to almost anything else. For example, on a laser printer you can change the settings for printing TrueType on the Fonts tab of the Printer Properties dialog box from "Auto" to "Print TrueType as Graphics". On the HP 832C inkjet open the Printer Properties dialog box and on the Color tab place a check before "Print as grayscale." Write down the default settings and then experiment with one setting change at a time. If you cannot find one that works check the printer manufacturer's web site for an updated driver. If updating the driver does not work you should change printer drivers to see if the driver is indeed the problem. (To install a new printer driver go to Start | Settings | Control Panel and open Printers. Select Add New Printer.) If you are using a laser printer try installing the HP LaserJet III driver. If you are using an inkjet printer try installing the HP DeskJet 500 driver. Try printing your file with the older driver to see if everything prints correctly. You may lose certain features your printer supports but this test will help show you whether or not your printer driver is the problem. If it is, contact your printer manufacturer for help.

Some of your Bibles are published in Write format. What is that? Will it work in Word? Microsoft Write is the free and very basic word processor that shipped with Windows 3.1. WordPad is the free and basic word processor that ships with Windows 95/98/NT/2000. Microsoft Word and WordPad both can open Write files. Thus Write format is the most basic of the formats. It can be opened by all owners of Windows, no matter what word processor they use (because they can be opened by WordPad, free with Windows). So you can indeed open the files in Word. If you wish to use these files in Word, we recommend you open the Write files in Word and save them as Word files for all subsequent use.

When I use Insert Symbol to input characters into a file the words do not wrap correctly. This is a feature of Microsoft Word, which inserts a code around all characters input into a file with the Insert Symbol command. This code causes Word to treat the characters as Symbol-encoded. Word will not properly word wrap Symbol-encoded text (nor will the Word spell checker check Symbol-encoded text). The solution is to input the characters using the keyboard driver and keyboard layout chart supplied with our product or input the characters using ASCII code input as described in our User's Manual.

When I type I get different results from what the keyboard chart shows (I get different characters or windows open, a footnote is inserted, or other unexpected things happen). You must change the default settings in your word processor. Complete instructions for doing this in Microsoft Word are in your product manual. For other applications see the online help file, Linguist.hlp, found on your product diskette.

Linguist's Software fonts show in the Word 2000 font menu in their own script, making it difficult to figure out the names of the fonts. I prefer font names in Latin letters. Word 2000 has an option allowing fonts to be listed in their own font or script. While this is good for Latin fonts it makes it difficult to identify non-Latin fonts. To turn off this feature go to the Tools menu, select Customize, choose the Options tab and deselect "List font names in their font".

I own Linguist's Software fonts purchased before Word 97 was released by Microsoft. When I type in Word 2003, 2002, 2000 or 97: 1) I get nothing but little boxes, rectangles, or question marks; or 2) Word wrap is not correct; the line wraps in the middle of words; or 3) Spell-checking does not work; or 4) Files I have created in earlier versions of Word using older fonts from Linguist's Software do not open correctly in Word 2003, 2002, 2000 or 97. With the release of Word 97 (and Office 97), Microsoft changed the way Office products handle fonts in Windows. This change affects fonts from Linguist's Software and many other third party font foundries. You must upgrade your Linguist's Software fonts to make them compatible with Word 97 (and later versions, such as Word 2000).

Fonts that are available in other programs do not appear in Word's font menu. This happens when the default printer is set to a printer that does not support TrueType fonts (such as the Generic/Text Only printer). Refer to your Linguist's Software documentation under Word 2000, 97, 7.0, and 6.0 for Windows for instructions to correct this. This will also fix the problem for other applications, such as WordPad.

When I attempt to insert a character from a Linguist's Software font into my file using the Insert | Symbol menu command, the Linguist's Software font does not appear in the Symbols Font: list box. This is a known bug in Microsoft Word, versions 2.0-97. Refer to your Linguist's Software documentation under Word 2000, 97, 7.0, and 6.0 for Windows for instructions to correct this.

In the Keyboard Properties box, when I click on the Apply or Okay buttons to complete the association of a keyboard layout with an input locale (in Windows 2000/NT) or language (in Windows 98/95), Windows tells me it cannot find the needed keyboard file and to put my Windows CD in the CD-ROM drive. This usually is caused by one of two problems: 1) Your network administrator has set your permissions to disallow installation of keyboards; or 2) a Windows bug is causing Windows to think you are trying to install a standard Windows keyboard, when you are not. In this situation the file Windows is looking for is often already installed, but Windows still is confused. See product documentation under Windows 98/95 - General for complete instructions on correcting this problem.

In Windows 2000/NT4 when I type, some characters appear as boxes. In your word processor you must turn off Allow fast saves. See product documentation under Windows 2000/NT 4.0 - General for complete instructions.

When I type all characters appear as boxes. There are at least two possibilities: you have chosen an input locale which requires a 32-bit font, or your font is too old to work with Windows 2000/NT/98 and you must upgrade it. See product documentation under Windows 2000/NT 4.0 - General and Windows 98/95 - General for complete instructions.

After installing the keyboard files Windows will not start or starts only in Safe Mode. This usually is caused by attempting to install the Windows 3.1 Keyboard Switcher into Windows 98/95. See product documentation under Windows 98/95 - General for complete instructions to recover. If your product does not have a Windows 98/95 installer you will have to upgrade. To determine if your product has a Windows 98/95 installer use Windows Explorer to look on the diskette for the SETUP95.EXE file. If it is not present, you must upgrade.

When I try to add a keyboard layout in the Language tab of the Keyboard Properties box, I get a blank dialog box with the message, "Old-style keyboard driver detected, pane disabled." This usually is caused by mistakenly installing the Windows 3.1 keyboard driver into Windows 98/95. Complete instructions for correcting this are in your product documentation under Windows 98/95 - General.

When I try to install the keyboards by running SETUP95.EXE, a black DOS screen appears for just an instant and then goes away, nothing else happens, and the keyboards are not installed. (When I go to the keyboard properties list of keyboards, they are not present.) You will have to install the keyboards using an alternate method. Complete instructions are in product documentation under Windows 98/95 - General.

When I go to the Keyboard Properties box to add a keyboard layout, there is no Language tab. This problem is caused by a third-party software that has changed the Windows environment. The solution is in the manual under Windows 98/95 - General.

In the Keyboard Properties box, when I click on the Properties button to associate a keyboard layout with a language, there are two similar keyboards available, such as "GreekLS-US" and "GreekLS US". This rarely happens and then only when upgrading certain previously installed Linguist's Software products. Complete instructions for correcting this are in product documentation under Windows 98/95 - General.

The "Install New Font" Menu Command is missing in my Fonts folder. This is a Windows problem, and not related to Linguist's Software Windows fonts. Complete instructions for correcting this are in Linguist's Software product documentation under Windows 98/95 - General.

Fonts that I have installed and which are listed in the Fonts folder are not available to be selected within programs. This is a Windows problem, and not related to Linguist's Software Windows fonts. Complete instructions for correcting this are in Linguist's Software product documentation under Windows 98/95 - General.

TrueType fonts do not appear in my Fonts folder. This is a Windows problem, and not related to Linguist's Software Windows fonts. Complete instructions for correcting this are in Linguist's Software product documentation under Windows 98/95 - General.

When I try to install Linguist's Software TrueType fonts for the first time, I get the following error message: The <fontname> TrueType font is already installed. To install a new version, first remove the old version. This is a Windows problem, and not related to Linguist's Software Windows fonts. Complete instructions for correcting this are in Linguist's Software product documentation under Windows 98/95 - General.

Previously created documents are printed differently or the formatting is changed when I view the document. This is a Windows problem, and not related to Linguist's Software Windows fonts. Complete instructions for correcting this are in Linguist's Software product documentation under Windows 98/95 - General.

Typing in a Linguist's Software font produces nonsense. If almost everything you type is wrong check to be sure you have installed and are using the proper keyboard for the font you are using. Refer to the Installation section of the product User's Manual. If only selected characters are incorrect, you must change the default settings in your word processor. Complete instructions for doing this in Microsoft Word are in your product manual. For other applications see the online help file, Linguist.hlp, found on your product diskette.

I get different characters in print than I do on the screen; or everything works except a couple of characters. This probably is a printer driver problem. Refer to your Linguist's Software documentation under Windows 98/95 - General for more information and help in correcting it.

When I try to follow the keyboard layout chart, nothing happens when I press Ctrl-Alt\ (backslash) or Shift+Ctrl-Alt\ (backslash). This is a hardware problem, and not related directly to fonts. Refer to your Linguist's Software documentation under Windows 98/95 - General for more information.

My password no longer works. I cannot get into my system. The Password dialog box for Windows startup (if you have password protection turned on, or are on a network) and for your Windows screen saver will be affected by the default language you select. Refer to your Linguist's Software documentation under Windows 98/95 - General for more information and help in correcting it.

As I type in a Linguist's Software font, my word processor suddenly reverts to the default (Times New Roman) font. See the electronic help file (Linguist.hlp) found on your Linguist's Software product diskette for information and help in correcting this. Look under Troubleshooting, WordPad. This solution should also fix the problem in other applications.

When using Publisher 2000 I cannot input the characters in ASCII positions 142 or 158 in a Linguist's Software font. Instead I get a Z-caron or z-caron (Z-hacek or z-hacek). Normally if characters cannot be input by keystroke following our keyboard layout chart, they may be input using ASCII code input where the user holds down the left Alt key and types zero plus the three-digit ASCII code on the numeric keypad, and then releases the Alt key. In Publisher this works for all characters except ASCII values 142 and 158. To input these two characters, hold down the right Alt key and type zero plus 142 or 158 using the numeric keypad and then release the R-Alt key.

In WordPerfect 12.0, certain characters cannot be input into a document. Due to a bug in WordPerfect, many characters in third-party fonts (such as Linguist's Software fonts) cannot be entered into a WordPerfect 12 document using Linguist's Software (LS) keyboard drivers. However, these characters may be inserted manually, one character at a time, using Insert Symbol. To do this select the LS font in your font menu, then go to the Insert menu and select Symbol. In the Set field select Current Symbols. The Number field will then change to 12,xxx (where xxx is the two or three digit ASCII value of the highlighted character), and the LS characters will appear in the Symbol window. Scroll through the characters to find the character you want and click Insert. Alternatively, you can go directly to any desired LS character by entering its three digit ASCII number and clicking Insert. For example, in the Number field type 12,225 and character 225 will immediately be selected in the window. Click Insert to insert it into your file. (To find the three digit ASCII value of any LS character check the Character Code Tables included with the LS product. These tables are either in the back of your User's Manual or in PDF format on the Windows Start menu.)

In WordPerfect 11.0, certain characters cannot be input into a document. Due to a bug in WordPerfect, many characters in third-party fonts (such as Linguist's Software fonts) cannot be entered into a WordPerfect 11 document using Linguist's Software (LS) keyboard drivers. However, these characters may be inserted manually, one character at a time, using Insert Symbol. To do this find the three digit ASCII value of the LS character by checking the Character Code Tables included with the LS product. (These tables are either in the back of your User's Manual or in PDF format on the Windows Start menu.) In WordPerfect select the LS font in your font menu, then go to the Insert menu and select Symbol. In the Set field select Current Symbols. The Number field will then change to 12,xxx (where xxx is the two or three digit ASCII value of the highlighted character). The font used in the Insert Symbol dialog is a system font so it will not display the LS characters. But you can insert the desired LS character by entering its three digit ASCII number and clicking Insert. For example, in the Number field type 12,225 and in the dialog box the a-acute will become highlighted, since ASCII 225 is the a-acute in a standard Windows font. Click Insert to input character 225 from the LS font chosen in your font menu.

In WordPerfect 10.0, certain characters cannot be input into a document. Due to a bug in WordPerfect, eleven characters in third-party fonts (such as Linguist's Software fonts) cannot be input in any way into a WordPerfect 10 document. These characters are ASCII values 128, 152, 166, 168, 173, 175, 176, 180, 181, 183 and 184. There is nothing that can be done about this until Corel fixes this bug. We recommend you check with Corel at 1-800-77-COREL for any product updates, or check their web site for patches.

In WordPerfect 9.0, certain characters cannot be input into a document. Due to a bug in WordPerfect, eleven characters in third-party fonts (such as Linguist's Software fonts) cannot be input in any way into a WordPerfect 9 document. WordPerfect instead changes them to the Arial font with code page 1252. (See the electronic help file, Linguist.hlp, for a list of these characters.) There is nothing that can be done about it until Corel fixes this bug. They are aware of it. We recommend you check with Corel at 1-800-77-COREL for any product updates, or check their web site for patches.

In WordPerfect 9.0, overstriking accents print as spaces. Due to a bug in WordPerfect, many overstriking accents do not print. Corel has been informed of this and is working on a fix. Corel periodically releases bug fixes and patches on their web site, or you can contact them at the Corel Orders Center at 1-800-77-COREL.

In WordPerfect 8.0, overstriking accents print as spaces. Due to a bug in WordPerfect, many overstriking accents do not print. Corel has released a patch that reportedly fixes this bug. If you own WordPerfect 8.0 Program Release 8.0.0.225 or higher you can download the patch from the Corel web site. If your Program Release of WordPerfect is lower than 8.0.0.225 you must contact the Corel Orders Center at 1-800-77-COREL, to obtain an updated version of Corel WordPerfect Suite 8. Apparently, you must pay for shipping and handling.

In WordPerfect 7.0, overstriking accents print as spaces. If you are using a font such as TransCyrillic which does not use overstriking accents, WordPerfect 7.0 for Windows will type your text correctly. If you use a font with overstriking accents, the accents will appear correctly on screen, but will be replaced by a space when you print. Corel created a patch that corrects this bug and included it in a Customer Care CD. This Customer Care CD is for registered owners of Corel WP Suite 6.1, Corel WP Suite 7.0, Corel Office Professional 3 for Win 3.1, and Corel Office Professional 7 for Win 95 in English. Registered users can call Corel Customer Service (1-800-772-6735 for North America; 353-1-706-3912 International) to order this Customer Care CD (if it is still available). Be prepared to provide your serial number. Note that there is a patch that fixes this problem in WordPerfect 8, and that overstrikes do work in WordPerfect 9.0. But note there is another known problem with that version (see above).

In WordPerfect 5.x and 6.0 overstriking accents print as spaces, and right margins are not right. The only solution for WordPerfect 5.x is to upgrade to a later version. If you are using a font such as TransCyrillic which does not use overstriking accents, WordPerfect 6.0 for Windows will type your text correctly. If you use a font with overstriking accents, the accents will appear correctly on screen, but will be replaced by a space when you print. Also, the cursor will move too far to the right whenever you type an overstriking accent. WordPerfect 6.0a fixes this problem. Under the Help menu choose About WordPerfect.... If your WordPerfect 6.0 for Windows has a date of 10/01/93, you must obtain an upgrade to 6.0a, or higher, before most features of third-party fonts will work. WordPerfect 6.0a, dated 4/20/94, allows you to type overstriking accents, displaying and printing them correctly. Note that overstrikes do work in WordPerfect 9.0, but there is another known problem with that version (see above).

Assorted characters do not type in any version of WordPerfect.

  • Due to a bug in WordPerfect 12, many characters in third-party fonts (such as Linguist's Software fonts) cannot be entered into a WordPerfect 12 document using Linguist's Software (LS) keyboard drivers. However, these characters may be inserted manually, one character at a time, using Insert Symbol. To do this select the LS font in your font menu, then go to the Insert menu and select Symbol. In the Set field select Current Symbols. The Number field will then change to 12,xxx (where xxx is the two or three digit ASCII value of the highlighted character), and the LS characters will appear in the Symbol window. Scroll through the characters to find the character you want and click Insert. Alternatively, you can go directly to any desired LS character by entering its three digit ASCII number and clicking Insert. For example, in the Number field type 12,225 and character 225 will immediately be selected in the window. Click Insert to insert it into your file. (To find the three digit ASCII value of any LS character check the Character Code Tables included with the LS product. These tables are either in the back of your User's Manual or in PDF format on the Windows Start menu.)


  • Due to a bug in WordPerfect 11, many characters in third-party fonts (such as Linguist's Software fonts) cannot be entered into a WordPerfect 11 document using Linguist's Software (LS) keyboard drivers. However, these characters may be inserted manually, one character at a time, using Insert Symbol. To do this find the three digit ASCII value of the LS character by checking the Character Code Tables included with the LS product. (These tables are either in the back of your User's Manual or in PDF format on the Windows Start menu.) In WordPerfect select the LS font in your font menu, then go to the Insert menu and select Symbol. In the Set field select Current Symbols. The Number field will then change to 12,xxx (where xxx is the two or three digit ASCII value of the highlighted character). The font used in the Insert Symbol dialog is a system font so it will not display the LS characters. But you can insert the desired LS character by entering its three digit ASCII number and clicking Insert. For example, in the Number field type 12,225 and in the dialog box the a-acute will become highlighted, since ASCII 225 is the a-acute in a standard Windows font. Click Insert to input character 225 from the LS font chosen in your font menu.


  • Due to a bug in WordPerfect 10, eleven characters in third-party fonts (such as Linguist's Software fonts) cannot be input in any way into a WordPerfect 10 document. These characters are ASCII values 128, 152, 166, 168, 173, 175, 176, 180, 181, 183 and 184. There is nothing that can be done about this until Corel fixes this bug. We recommend you check with Corel at 1-800-77-COREL for any product updates, or check their web site for patches.


  • Due to a bug in WordPerfect 9, eleven characters in third-party fonts (such as Linguist's Software fonts) cannot be input in any way into a WordPerfect 9 document. WordPerfect instead changes them to the Arial font with code page 1252. These characters are ASCII values 128, 136, 152, 166 (WordPerfect substitutes Arial character 126), 168, 173, 175, 176, 180, 181 and 184. There is nothing that can be done about this until Corel fixes this bug. They are aware of it. We recommend you check with Corel at 1-800-77-COREL for any product updates, or check their web site for patches.


  • WordPerfect 8.0 has problems with both encoding methods that it supports: The first way, called WordPerfect character sets, is incomplete, lacking characters where ANSI does not define them. These characters are 128-129, 141-144, and 157-158. The other way is called User Defined character set 12. These characters fail to display and/or print a zero-width overstriking character, or duplicate a character from another ANSI number (166). Corel has released a patch that reportedly fixes this bug. You can download the patch from the Corel web site, or you may contact the Corel Orders Center at 1-800-77-COREL.


  • WordPerfect 7.0 has problems with characters 128, 129, 131, 138, 140-144, 161-166, 170, 175, 178-180, 186, and 188-191, sometimes failing to display and/or print a zero-width overstriking character, or duplicating a character from another ANSI number. Corel created a patch that reportedly corrects this bug. You can download the patch from the Corel web site, or you may contact the Corel Orders Center at 1-800-77-COREL.


  • WordPerfect 6.1 does not apply a new font to characters 171 and 187. This problem can be corrected by using User Defined characters 12,171 and 12,187.


  • This type of problem has been true with every x.0 version, including WordPerfect 5.1 for Windows. In the past it has been corrected with the x.1 release. See Corel's web site for possible patches.

Imported texts are garbled in WordPerfect. With WordPerfect 8.0, 7.0, and 6.0a, if you import a text from another source which contains characters with ANSI numbers from 128 to 255, many of these characters will not be assigned the proper codes in WordPerfect. See the electronic help file (Linguist.hlp) found on your Linguist's Software product diskette for more information about this. Look under Troubleshooting, WordPerfect.

Character ANSI 255 does not type in some versions of WordPerfect. Older versions of WordPerfect do not allow character 255 under any circumstances. See the electronic help file (Linguist.hlp) found on your Linguist's Software product diskette for more information about this. Look under Troubleshooting, WordPerfect.

Installing Type 1 fonts with Adobe Type Manager gives error messages. If you have been using Adobe Type Manager to install Type 1 fonts in Windows, you will need Adobe Type Manager, version 2.5 or later. WordPerfect will not work with previous versions, but will give an error message.

The SymbolGreek font does not appear in WordPerfect's font menu, or, if it does appear, when I choose a SymbolGreek typeface WordPerfect uses the Symbol font instead of SymbolGreek. There is a bug in WordPerfect (various versions) that prevents any of the SymbolGreek family of typefaces from appearing in the font menu. (This can include SymbolGreek, SymbolGreek II, SymbolGreek IIP, and SymbolGreek IIPMono.) Some customers have overcome this problem by deleting the Symbol font (which comes with Microsoft Windows), and rebooting Windows. Other customers have fixed the bug by updating their version of WordPerfect with one or more of the patches available on the Corel web site. Apparently, WordPerfect is unable to distinguish typeface families if their names have a certain number of like characters in them. Since SymbolGreek will follow the Symbol font alphabetically, WordPerfect is apparently unable to distinguish the SymbolGreek families of typefaces. This causes WordPerfect either not to show the SymbolGreek font as installed, or if it does appear in the menu, not to recognize it and instead to use the Symbol font. (If you intend to delete the Symbol font be sure first to copy it to another folder or floppy disk for backup, in case you wish to reinstall it later. Linguist's Software does not recommend removing the Symbol font, since it is a Windows system font and may be required by parts of the system. Problems may occur if you delete it.)

Fonts do not appear in WordPerfect's font menu. If you have installed your fonts with Adobe Type Manager or the TrueType Fonts Control Panel and the fonts do not appear in the font menu of WordPerfect for Windows, you need to force WordPerfect to find the fonts. Under the File menu choose Printer Setup.... The Windows option must have a bullet before the fonts will work with WordPerfect 5.x.

I cannot type certain characters in Ventura Publisher 4.1. Ventura Publisher 4.1 was created to bring previous users of Ventura Publisher into Windows. It is not fully compatible with all possible characters in a Windows font. See the electronic help file (Linguist.hlp) found on your Linguist's Software product diskette for more information about this. Look under Troubleshooting, Ventura Publisher 4.1.

In Ventura Publisher, overstriking accents print as spaces, and the right margin is not correct.
Ventura Publisher 7 corrects this problem.

Overstriking accents do not appear or print correctly in Microsoft Works for Windows 3.x or 2.x. Microsoft Works for Windows 3.x and 2.x are not able to handle overstriking accents correctly. This problem has been eliminated in Works 4.0. You will need to upgrade or else use Windows Write or some more capable word processor, such as Word for Windows, Ami Pro for Windows, or WordPerfect 6.0a for Windows to overcome this problem.

I cannot type ASCII character 150 in Microsoft Works for Windows 3.x or 2.x. Works for Windows 3.x and 2.x have a character substitution problem. If you input ASCII or ANSI character 0150, Works 3.x and 2.x will not display or print that character. Instead, Works will substitute ASCII or ANSI 0045, which is a minus sign or hyphen in most fonts. This means that whatever character is in position 0150 (see the Character Chart in the User's Manual) will appear as a minus sign. You will need to upgrade to version 4 of Works, or use another word processor, such as WordPad or Word.

Fonts installed in the Windows 3.1 Control Panel do not show up in my applications, or else show on screen as a script-like system font. See the electronic help file (Linguist.hlp) found on your Linguist's Software product diskette for more information and help in correcting this. Look under Troubleshooting, Windows 3.1.

I cannot print Linguist's Software TrueType fonts. With some Windows 3.1 print drivers, there is a printer setting which suppresses printing any font which is not built into the printer. This setting renders TrueType soft fonts unusable, so it must be disabled. See the electronic help file (Linguist.hlp) found on your Linguist's Software product diskette for more information and help in correcting this. Look under Troubleshooting, Windows 3.1.

When I try to type ASCII codes using L-Alt0xxx, following the ASCII (Character) Code Charts in the back of the User's Manual, nothing happens. This can be caused by a number of things. Refer to your Linguist's Software User's Manual for complete instructions on entering ASCII codes. See the section called, "Using <product name> in <your version of Windows>." Especially on older systems, your applications may need extra time to handle the operation. See the electronic help file (Linguist.hlp) found on your Linguist's Software product diskette for more information and help in correcting this. Look under Troubleshooting, Windows.

When I type in Ami Pro(tm) 3.0 for Windows the accents do not appear on screen. When you type overstriking accents in Ami Pro 3.0 on some computers, the accents do not appear on screen until you hit Backspace, your text wraps automatically to the next line, or you end a paragraph by hitting Enter.

My fonts work in Windows Write, but do not show up in the font menu of Word for Windows, version 2. If your fonts work in Windows Write but do not appear in the font menu of Word for Windows, you need to force Word for Windows to find fonts. See the electronic help file (Linguist.hlp) found on your Linguist's Software product diskette for more information and help in correcting this. Look under Troubleshooting, Word 2.

I use Adobe Type Manager and the names of installed fonts do not appear in the font menu of Word for Windows, version 1. If you have installed your fonts with ATM and the fonts do not appear in the font menu of Word for Windows, you need to force Word to find the fonts. See the electronic help file (Linguist.hlp) found on your Linguist's Software product diskette for more information and help in correcting this. Look under Troubleshooting, Word 1.x.

Type 1 Fonts do not print from Windows 3.0. If you are using Windows 3.0 (and not 3.1 or later), and you can see your Type 1 fonts on screen but they will not print, follow the instructions in the Linguist.hlp help file found on your Linguist's Software product diskette to make the fonts available to the printer. Look under Troubleshooting, Windows 3.0 - Printing.


FAQ - General Questions Frequently Asked Questions of a General nature

FAQ - Macintosh Questions Frequently Asked Questions about our Macintosh products

Complete List of Frequently Asked Questions Complete List of all Frequently Asked Questions


Back to Top